Advice, A Hire, Or A Growth System: How To Tell Which One You Need
An Operator Note from Trifecta
Most owners buy help before they know which kind of problem they have.
That isn’t a criticism. When growth stalls, the pressure to do something is real, and most leadership teams respond by bringing someone in. But the kind of help matters more than the decision to get it.
Three things sit on the shelf:
Advice from someone outside. When the team truly doesn’t know what to do yet and needs an answer: a consultant, a peer group, a conference.
A hire to fill the gap. When the system works and one seat is empty or missing a skill nobody in the building has.
A system that changes how the whole company runs. When the problem lives between departments, in the handoffs nobody owns.
Each one is the right answer to a different problem. Buy the wrong one and the money is the smallest loss. You lose two quarters, and your team collects one more piece of evidence that nothing changes.
Advice can’t fix a broken system. A new hire walks into the same broken handoff the last one did. And rebuilding the system is overkill when all you needed was one good person.
So the first question isn’t “Who or what should we bring in?” It’s “What kind of problem do we actually have?”
Our article, What Is a Growth Practice?, made the case that most stalls live between departments, not inside them. Its checkup sorts the answer two ways: a person or a system. In practice there are three, because a person can mean an adviser or a hire, and those two solve different problems and fail in different ways.
This note is the mechanics:
What each kind of help actually changes
Six questions to tell them apart
How to score them
How to read the answers when they don’t line up
Where the exercise breaks
One thing to watch downstream: the opening now defines all three options, so the “Start with what each one changes” section repeats a little. It still earns its place because it maps each option to the formula, but you could trim its first line to “Now look at what each one touches in the formula.”
Start With What Each One Changes
Every kind of help reaches a different part of the same formula:
Growth = [(Pipeline × Conversion × Team Capacity) × Traction] ÷ Drag
The three terms inside the parentheses are the engine. Most companies measure those and nothing else. Traction is how much of a leadership decision survives the trip to the customer, and it multiplies the engine. Drag is the rework, the unowned work and the decisions made twice that eat effort without producing motion, and it divides the engine.
Now look at what each kind of help touches.
A hire changes one term in the engine. Usually Team Capacity. Sometimes Conversion or Pipeline, when the person brings a skill nobody in the building has. That is a real lever, and when the constraint sits inside the engine, it is the right one.
Advice changes what you know. It moves no term on its own. A recommendation reaches the formula only when someone acts on it, which means it passes through Traction like every other decision your leadership team makes. Good advice delivered into low traction arrives at the customer as a fraction of itself.
A system changes the two terms outside the engine. It raises Traction and cuts Drag. It doesn't add a person or a new idea. It changes how the people and ideas you already have connect to each other.
That last point is why the order matters. The terms multiply and divide each other. A new hire's capacity enters the same system as everyone else's, so it pays the same toll. If a fifth of your team's week goes to rework, slow approvals and work bouncing between departments, a fifth of the new hire's week will go there too.
A hire adds to the engine. Drag still divides whatever the engine produces.
So the useful question isn't which kind of help is best. It's which term is actually holding your number down.
The Six Questions
Have each member of your leadership team answer these on their own: the owner, whoever leads sales, whoever leads marketing and whoever keeps the books. Written answers. No conferring.
The first three come from the checkup in What Is a Growth Practice? They tell you whether the problem sits inside a function or between functions. The last three separate advice from a system, which the first three can't do.
# | Question | Points to a hire if... | Points to advice if... | Points to a system if... |
1 | Is the problem inside one department, or between departments? | It sits clearly inside one department | Nobody is sure where it sits | It shows up in the handoffs between departments |
2 | Who owns the whole revenue number, from first contact to cash? | One name, and that person is missing a skill or the help to use it | One name, and they don't know what to change | More than one name, a long pause, or "all of us" |
3 | Would a new hire walk into the same broken handoff the last one did? | No. The seat is the problem | Not sure | Yes |
4 | Has a past recommendation already been made and not carried out? | No | No. You truly don't know what to do yet | Yes. You knew what to do and it didn't stick |
5 | Does the fix need more people, or the same people working to one definition? | More people, or a skill nobody has | An answer to a question nobody can answer yet | The same people, working from one definition |
6 | If outside help left tomorrow, what would keep running? | Not relevant. The hire stays | Nothing, and that's fine for a one-time question | Nothing. That's the problem |
Question four is the one that separates advice from a system most cleanly, and it deserves more than a line.
If the answer already exists somewhere in the building, in a binder, a board deck or last year’s offsite notes, you don’t have a knowledge problem. You have a follow-through problem. And follow-through hits the formula twice.
First, it costs Traction. A decision that never gets carried out never reaches the customer. It survives the meeting and dies on the way out of the room.
Then it adds Drag. An unfinished decision doesn’t go away. It comes back at the next offsite and gets made again. The team reworks the plan instead of working it, and the people who were asked to change learn to wait out the next initiative instead of committing to it. Rework, decisions made twice and a team that never fully bought in, all from one recommendation that didn’t stick.
That’s why the usual fixes don’t reach it. Another recommendation adds to the pile. An adviser’s job ends when the recommendation is delivered, by design. A new hire owns one seat, and follow-through breaks between seats, where nobody has the authority to hold their peers to it.
Follow-through across functions takes someone whose job is the whole system: someone who stays through the build, works it alongside your team, and hands it to a named owner who keeps it running. That’s the work a growth practice exists to do. We name the constraint, blueprint the fix, and install it with your team until they own it.
A recommendation that doesn’t stick costs you twice: once in Traction, again in Drag.
How To Score It
Count each person's answers by column. You don't need math for this part. You need to see where the answers cluster, and whether everyone's cluster lands in the same place.
Mostly hire. The constraint sits inside the engine, in one function, and the missing piece is a person or a skill. Hire well. Then give that person a written definition of what they own before their first day, so they inherit a standard instead of an argument.
Mostly advice. Your team truly doesn't know what to do yet. It's a strategic question with an answer someone can give you: which market to focus on, what to charge, which offer leads. Buy a clear answer, and set the date you will act on it before the engagement starts. Advice without a date is a document.
Mostly system. The constraint sits between functions, nobody owns the whole number and you already know some of what needs to change. The engine is mostly fine. Traction and Drag are not. More advice won't help, because the issue isn't knowing. It's doing, together, every week.
Here is what most owners don't expect. Advice is the rarest real answer of the three.
When it's serious, you stop shopping for opinions. Advice is an opinion, often a good one. It's the right purchase only when the opinion is the thing you're missing.
Most stalled teams already know a good share of what's wrong. They heard it from a consultant, read it in a board deck or said it themselves in a meeting. What they lack is a way to make it survive the trip from the conference room to the customer. Another recommendation can't fix that, because the recommendation was never the missing piece.
If you already know what to do and it still isn't happening, you don't need more advice.
Reading The Splits
Clean results are rare. The splits usually tell you more than the clusters do.
Hire and system. The most common split, and usually both halves are true. There is a real gap in one seat, sitting on top of a broken handoff. Fix the handoff first. Otherwise the new person walks into the same seam the last one did and gets measured against it.
Advice and system. The team knows part of the answer and is missing one decision. Name the decision, get the answer, then install it. Building a system before the decision is made means building around a question nobody has settled.
Hire and advice. The problem sits inside one function, but nobody agrees on what that function should be doing. Settle the strategy before you write the job description, or you will hire for the old strategy and wonder why the new person doesn't fit the new one.
Every leader in a different column. This is a reading, not a muddle. Four leaders who can't agree on where growth is stuck will make decisions that reach the customer as four different versions of the same plan. That is low Traction, visible in the room before it shows up in the numbers. Score it as a system answer.
The Meeting
Thirty minutes. Ten more than the checkup, because there are twice as many questions. Everyone brings written answers.
Don't open with the columns. Open with question two. Ask each person to say, out loud, who owns the whole revenue number. One name, move on. Several names, a long pause or "well, all of us," write down exactly what you heard. That sentence describes how revenue decisions really get made in your company, whatever the org chart says.
If the name you get is a RevOps or operations leader, ask one follow-up: when marketing and sales disagree, who settles it? If the answer is that it goes to the owner, that leader has the responsibility without the decision rights. That's a design problem, not a people problem.
Then compare clusters. Where the room agrees, you have a direction. Where it splits, use the section above to read the split.
Where the room splits on question one, settle it with records, not memory. Pull ten deals or leads from last quarter at random and walk them together. The randomness matters. If a leader picks the examples, you get a case being made instead of a system being seen.
Close the meeting by agreeing on one thing: which term in the formula the team believes is holding the number down. Not the fix. The term. Pipeline, Conversion, Team Capacity, Traction or Drag. A team that can name the term in one word has done more diagnosis in thirty minutes than most companies do in a year of department reviews.
Where This Breaks
The owner scores it alone. It's tempting, and it's the most common way this goes wrong. The owner's view matters most and is also the most likely to be shaped by what they already believe. Get at least three people's answers, or you are scoring a hypothesis instead of a company.
A real hiring need gets dismissed. Sometimes the answer really is a person. If the seat is empty or the skill doesn't exist in the building, a system won't create it. Don't let the appeal of "fix the system" talk you out of a hire you need. We install systems for a living, and we'll still tell you that.
A seam gets read as one person's performance. This is the expensive one. A broken handoff doesn't announce itself. It surfaces two quarters later as pipeline that won't convert, and by then it reads as a demand problem or a closing problem, which are the two things it isn't. A sales lead who keeps missing may be working against marketing's definition of a lead and finance's definition of a forecast. Replace that person and the next one walks into the same handoff. Question three exists to catch this. Answer it honestly.
In the meeting, when someone names a person, redirect to the step. "The record sat for six days," not "Dave sat on it for six days." Do it every time, calmly, and the room picks up the pattern.
Question four gets a polite answer. Nobody likes to admit the last engagement's recommendations are sitting in a binder. Ask it this way instead: "What did we agree to do in the last year that we haven't done?" The list will tell you more than the score.
Everyone agrees, fast. Be suspicious. Quick agreement usually means the answers are vague enough to fit everyone's existing view. Test it: read one real record from last quarter aloud and ask each leader where it got stuck. If they name different places, you don't have agreement yet.
The team scores only the engine. Leaders tend to answer question five in headcount, because headcount is what their reports show. Pipeline, Conversion and Team Capacity have dashboards. Traction and Drag usually don't. If every answer to question five is "more people," ask one follow-up: what did the last person we added spend their first ninety days on? If the answer is untangling handoffs, chasing approvals or redoing work, you just measured Drag.
The Sequence
Day one. Send the six questions to your leadership team. Ask for written answers within two days, without discussion.
Day three. Hold the thirty-minute meeting. Start with question two. End with one term.
Day four. Write one paragraph: which column the answers cluster in, where people split, which term the team agreed is holding the number down, and the first move. Share it with the same group.
Day thirty. Pull out that paragraph and ask question four about it. Has the first move happened? If it has, you have your answer about Traction. If it hasn't, you also have your answer about Traction.
What To Expect From A Growth System
The answers won't cluster as neatly as you'd hoped. That's normal, and it's useful. A split tells you where to look first, which is most of what a diagnosis is for.
Most teams find that question two was worth the whole exercise. Plenty of owners have never heard their leadership team answer it out loud.
And most teams discover that their reporting measures the engine and nothing else. If your answers point to Traction and Drag, you have found the part of the formula nobody is reporting on. That is usually the reason it hasn't been fixed.
When the Split Won’t Settle
Most teams get through the scoring and stall in the same place: four leaders, four columns, and nobody neutral enough to say which split matters.
If that’s where you land, that’s the conversation to have with us. Bring three things:
Each leader’s written answers
The list from question four
Your day-four paragraph
The raw answers matter more than any summary of them. In a 30-minute conversation, we’ll tell you which term we think is holding your number down, and whether the next move is a hire, an answer or a system. Sometimes it’s a hire, and we’ll say so.
Book 30 minutes to get started.
Comments