Problem Solving For Capacity, Capability, Priority or Budget?

Stop paying to fix the wrong problem.

Every Formula 1 team runs under a cost cap: a fixed budget, a limited number of people and limited time in the wind tunnel. When the season championship comes down to the final races, no team can buy its way out of trouble.

In 2025, McLaren led the championship with half the season still to run. The obvious move was to keep pouring money into making the car faster. McLaren asked a harder question first: what would more spending actually buy? Its car was already the fastest on the grid, and the gains left were small. So the team stopped upgrading and moved its people and budget to the following year's car. Red Bull kept spending and closed fast, but McLaren's Lando Norris held on to win the championship by two points. McLaren stopped paying to fix a problem it didn't have.

A business has a cap too: its cash, its margin and its people's hours. Because nobody writes it down, leaders rarely stop to ask the question McLaren did: what is actually holding us back? Capacity, capability, priority or budget?

What Stalled Growth Asks For

When growth stalls, every leader asks for more. More people. More budget. More tools. More time.

It's a natural response, and it comes from a good place. But one constraint tends to set off the next, and the next makes the first one worse.

Those four constraints look alike from a distance. Up close, they're different problems with different fixes. Fund a symptom instead of the source, and you burn margin, wear out your people and leave the root cause exactly where it was.

And don't assume the trouble starts below you. All four constraints live in the executive team too, and that's usually where the cascade begins. So before you sign off on more, find out where the trouble actually starts. At the end of this article is a one-hour exercise to do exactly that.

Four Problem Solving Constraints, Four Fixes

Each one has a symptom, a simple test and a fix that doesn't work for the others.

• Capacity: the team can't carry the load. Capacity is more than headcount. It's the attention, energy and management bandwidth of everyone the work touches. The work is known and the team knows how to do it, but there's more of it than the people and the process can absorb. The test: if we took work off this team's plate, would the stalled work get done, and done well? The fix: you can't create hours out of thin air, and asking people to absorb more is how you get burnout and turnover. Something has to come off the plate: stop lower-value work, cut the drag eating the hours people already have, or pace the growth goal to what the team can carry. Hiring helps too, but new people take months to ramp, so it's rarely the first or fastest lever. At the top: a CEO or leader who sits in every decision, so the work waits on them. The fix there is handing off decision rights, not adding hours to the leader's week.
  

• Capability: nobody in the building can do it. The work gets attempted and done poorly, or never started because nobody knows how. The test: if we gave the current team twice the time, could they do it? If not, it's capability. The fix: hire the skill, build it through training, or bring it in temporarily and make sure it transfers to your team before it leaves. At the top: a leader promoted for being great at the job who was never taught to lead, coach or forecast. That skill has to be built in the leader first, or it never reaches the team.
  

• Priority: the work keeps losing to other work. Everyone agrees it matters. It's in the plan every year. It never gets done, because something more urgent always wins. The test: what did this lose to last week, and who decided? The fix: a leadership decision. Something else has to stop. At the top: an executive team where every leader has a different number one. If the leadership team hasn't ranked the work together, nobody below them can.
  

• Budget: the money isn't there yet. The fix is known, the people are ready, the work is a priority, and the cash to fund it doesn't exist yet. The test: if the money appeared tomorrow, would we know exactly where it goes and what it buys? The fix: earn it. Spend is earned, not allocated. Build the budget from the pipeline up, and release each new tranche when the pipeline proves it can carry it. At the top: spend that follows the loudest voice in the room or a favorite project, instead of the evidence.

Notice how differently those fixes behave. Hiring solves capacity, but does nothing for priority. Training solves capability, but does nothing for budget. Money solves budget, but pouring it into a priority problem just buys more people to be pulled in too many directions. Each fix works on one problem, and only that one.

One Root Cause, Many Requests

The four constraints rarely show up alone. We've watched this pattern play out more than once. Leadership never ranks the year's initiatives, so everything is a priority. The team spreads itself across all of it and starts falling behind. That looks like a capacity problem, so the company hires. The new people get onboarded by a team that's already underwater, so nobody has time to train them properly, and the work they turn in is uneven. Now it looks like a capability problem, so the company brings in consultants or buys a tool. Costs climb faster than revenue, margin tightens, and by the next planning cycle the request is for more budget.

Four constraints, four sets of requests, one root cause. Every fix treated a real symptom. None of them touched the decision that was never made, so the cascade kept running, and each round cost more than the last.

It can start anywhere. A leadership team with nobody who can build a forecast the business trusts will struggle to set priorities with confidence. A budget squeeze can force a company to run so lean that the capacity problem turns into turnover, and turnover turns into a capability gap. Sometimes two root causes, say priority and capability, keep reinforcing each other, and they have to be worked together.

So when a request lands, don't stop at which constraint it is. Ask what caused it. Then ask what caused that. Keep going until you reach something that, if you fixed it, would ease the problems downstream. That's where the money and attention belong first.

Most "We Need More People" Problems Are Priority Problems

Of the four, priority is the one most often disguised as something else, and the one most likely to sit at the top of the cascade.

A team is asked to grow the pipeline, launch a new offer, clean up the CRM and support a key account, all this quarter. Every one of those is important. None of them is ranked against the others. So the team does a little of each, finishes none, and the leader reports back that they're stretched too thin. The request goes up the chain: we need more people.

The team had the hours. What it lacked was a decision. Add two more people, and you now have a bigger team doing a little of everything, at a higher cost.

Priority is the cheapest problem to fix, because it costs nothing but a decision. It's also the hardest, because someone at the top has to say no to something they care about. That's why it so often gets solved with a hire instead. A hire feels like progress. A decision feels like a loss.

Before you approve a headcount request, ask the leader one question: if you could stop one thing your team is doing today, what would it be? If they have an answer, you may have found the hours without hiring anyone.

Capacity Is Everyone's Hours

Capacity is where growth plans most often break, and it's the one leaders understand least, because they think about it for their teams but rarely for themselves or every level in between. A growth target isn't a number. It's hours, and those hours belong to real people.

Take a simple goal: grow revenue 25 percent next year. Walk it through the workflow. More leads to follow up, more discovery calls, more proposals, more contracts through legal, more onboarding, more invoices, more support tickets, more renewals. Each step lands on someone's calendar: a rep, an account manager, a project lead, someone in billing, someone in support, and every manager in between. If nobody has done that math, the growth number is a hope stacked on top of people who are already full.

And many already are. Microsoft's 2025 Work Trend Index, which surveyed 31,000 workers across 31 countries, found that 53 percent of leaders say productivity must increase, while 80 percent of the global workforce say they lack the time or energy to do their work effectively. Leaders are asking for more from people who are already telling them they have less.

That gap doesn't stay on a spreadsheet. It shows up in people. Gallup's research on burnout found that unmanageable workload and unreasonable time pressure are among the top five factors behind employee burnout, and that employees who frequently feel burned out are 2.6 times as likely to be actively looking for another job. An arbitrary growth target, handed down without understanding the work it creates, doesn't just miss. It costs you the people you were counting on to hit it.

We've seen it many times: a growth number set in the leadership room that can't be delivered with the current team. The people are good. Nobody mapped the work. The target arrives, the hours don't, and the best people leave first, because they're carrying the most.

Keep setting ambitious goals. But before the number is final, walk it through every workflow it touches and ask each leader: what will this take from your team, in hours, and do you have them? Then set the target the system can carry, or change the system so it can carry more.

Drag Eats Capacity Before It Reaches the Customer

There's one more reason adding people often disappoints. At Trifecta, we describe growth with a simple formula:

Growth = [(Pipeline × Conversion × Team Capacity) × Traction] ÷ Drag

Traction and Drag are the terms most leaders miss. Both are friction. Traction is productive friction: effort that grips and turns into forward motion, like a hard priority call or the work of building a new skill. Drag is pure resistance: rework, unclear ownership, slow approvals, duplicate meetings, work bouncing between departments. Traction multiplies what the engine produces. Drag divides it.

Say a fifth of every person's week goes to drag. Hire five people, and you get four people's worth of output. Subtract the time your team spends recruiting, onboarding and training them, and the first year may buy you closer to three. You paid for five. You got three.

Now flip it. Cut drag from a fifth of the week to a tenth, and every person you already have gets back half a day. Across a team of 40, that's the equivalent of several hires, with no recruiting, no ramp time and no added salary. That's why, when capacity is the problem, you look at drag before headcount. Drag is also a common place for a cascade to start: it eats hours, looks like a capacity problem, and triggers hiring into the same drag.

Every Request Says What It Fixes

One rule protects margin better than any approval process: every new line of spend has to say which of the four constraints it fixes, and whether that's the root cause or a symptom. That includes the leadership team's own initiatives. An executive's favorite project should pass the same test as a frontline headcount request.

Not "this will help growth." One word: capacity, capability, priority or budget. Then three answers:

• What's the evidence that this is the root cause, not a symptom? A backlog, a skill gap, a missed initiative, a pipeline that can carry the spend, and a clear answer to what's driving it.
  

• If it's a symptom, what's the cause, and who's fixing it? Funding a symptom can be the right short-term call, but only alongside a plan for the source. Otherwise the same request comes back next year, bigger.
  

• How will we know it worked? The specific number that should move, and by when.

This forces the requester to diagnose before they ask, which kills a surprising number of requests on its own. If nobody can say which problem a request fixes, don't fund it yet. That isn't a no. It's a not yet.

A One-Hour Exercise for Your Next Budget Meeting

Put every open request for people, money or tools on one page. Ask each member of the leadership team to tag every request with one word: capacity, capability, priority or budget. Do it individually first, then compare. Then, for each request, ask what's causing it and draw a line to that cause. Finally, ask the harder question: which of these constraints lives in this room?

Four things usually happen. Some requests get four different tags, which tells you nobody has actually diagnosed them. A surprising number get tagged as priority once people are honest, which means they need a decision, not a check. The lines start to converge, and requests that looked unrelated trace back to the same one or two causes. Fix those, and several of the other requests shrink or disappear on their own.

Then fix in order of cost. Make the priority calls first, because they cost nothing. Drag needs clearer ownership and better processes, so that comes next. Then fund the real capability gaps, then the real capacity gaps, and finally the budget-dependent bets as the pipeline proves it can carry them. That order is a default. If the root cause is a capability gap, it goes to the front of the line, and everything else waits. Funding around the root cause doesn't speed growth up. It just makes the cascade more expensive.

Before You Approve the Next Request

McLaren asked what more spending would buy before it spent another dollar. Ask the same question before you approve the next hire or budget line: which of the four constraints does it fix, and is that the cause or a symptom? If nobody can say, don't fund it yet.

• Capacity, capability, priority and budget are four different constraints with four different fixes.
  

• All four live in the executive team too, and that's where the fix has to start.
  

• A root cause sets off a cascade. Funding the symptoms keeps it running.
  

• Many "we need more people" problems are priority problems in disguise.
  

• More capacity poured into a high-drag system buys less than it costs.

This is the work we do at Trifecta. We start with the executive team, because when leaders are equipped to handle these constraints in themselves, every team below them feels it. Then we trace the cascade to where it starts, map growth targets to the hours they'll actually take, and install the fix with your team until they own it.

Growth shows up in two places: on the P&L and in your people. If you're wondering what real growth looks like for your company, let's talk.