What Are You Willing To Stop Doing?
A four-question spend check every business budget request should answer before you make your next move.
A request for two more people, a new tool or a bigger campaign line is a bet that one specific constraint is holding the business back. When the request doesn't name the constraint, nobody can check the bet. It gets approved on the strength of the person asking, and a year later nobody can say whether it worked. Most requests also skip the harder half of the bet: what else stops to pay for it.
Problem Solving For Capacity, Capability, Priority or Budget? named the four constraints that hold growth back and set one rule: every request says what it fixes, and whether that’s the root cause or a symptom.
The spend check puts that rule to work with four questions on one page. Every new hire, tool or business budget line answers them before it reaches a decision.
Step One: Put Every Business Budget Request On One List
Start with what's already waiting. Pull every open request for people, tools or budget into one list, including the leadership team's own initiatives. For each one, note who asked, what they asked for and what they said it would do.
Most lists look the same. The stated reason is some version of "help us grow" or "we're stretched." Very few requests name a constraint, and fewer still show evidence. The spend check is built to close that gap.
Artifact One: The One-Page Spend Check
Question | What a good answer looks like | Red flag |
1. Which constraint does this fix? | One word: capacity, capability, priority or budget | Two or more constraints with no primary one named, or ‘growth.’ |
2. What evidence says this is the root cause, not a symptom? | A backlog, a missed deadline, a skill nobody has, a pipeline that can carry the spend, plus what's driving it | A feeling, a complaint or a competitor's move, or a symptom with no plan for its cause |
3. What gets cut or deferred to make room? | A named project, tool or line item that stops or waits | "Nothing," or "we'll find it" |
4. What number moves, and by when? | One metric, a target and a date | "Better results," with no date |
Question 3 is the one most companies skip, and it's the one that stops the budget from growing every year. A request that can't name what it replaces asks the business to carry more without dropping anything. That's how capacity problems start.
Artifact Two: The Scoring Rule
Score each answer 0, 1 or 2.
0: missing, or a red flag
1: answered, but thin or untested
2: specific, with evidence someone else can check
Then sort the list.
7 or 8: act on it the way its constraint calls for. Capability and capacity requests get funded. Priority requests go to the leadership team for a decision, because the fix is something that stops. Budget requests get funded in tranches as the pipeline proves it can carry them.
4 to 6: send it back with the weak answers marked. Most come back stronger within a week.
0 to 3: defer it. The request can come back when the answers are better.
One rule overrides the total. A request that scores 0 on question 1 or question 2 is deferred, whatever else it scores. If nobody can name the constraint or show that it's the cause, the other answers don't matter. Funding a symptom can still be the right short-term call, but only when the request names the cause and who is fixing it. Otherwise the same request comes back next year, bigger.
Here is an illustrative example. Take a list of 12 open requests. Seven are labeled capacity. Under question 2, three show a real backlog that’s still there after rework and slow approvals are ruled out. Two turn out to be work losing to other work, which is a priority problem that needs a decision. Two are real capacity problems caused by drag, with teams losing hours to rework and slow approvals. Three requests get funded, two become leadership decisions, two become process fixes, and the rest wait.
How To Read The Result
If most requests score 7 or 8: The team already diagnoses before it asks. Use the check to keep that habit as the company grows.
If most requests fail question 1: Nobody is diagnosing. Run the one-hour tagging exercise from Problem Solving For Capacity, Capability, Priority or Budget? before the next budget meeting.
If most requests fail question 3: The budget grows by default. Every line gets added and nothing gets removed. Start there.
If most requests are labeled capacity: Test that label first. Capacity is the easiest answer to give and the one most often wrong.
The Meeting
Who's in the room: the leadership team and whoever controls the budget. Plan 60 minutes for the first round.
Each leader scores the list alone first, then the group compares. Start with the requests that got the widest spread of scores. A request that one leader scores 8 and another scores 3 hasn't been diagnosed yet, and that disagreement will teach the room more than any of the scores they agree on.
Where This Breaks
Everything gets labeled capacity. It's the safest-sounding answer. Apply the capacity test from the flagship: if we took work off this team's plate, would the stalled work get done, and done well? If the answer is no, it's a different constraint. If the answer is yes, check for drag before approving headcount. Rework, slow approvals and unclear ownership will eat a new hire's hours too, and fixing them first often shrinks the request.
Nobody names what gets cut. Leaders protect their own lines and write "nothing" for question 3. The owner or CEO has to require a named cut for anything above a set size, and hold to it the first time someone pushes back.
Evidence turns into a story. A paragraph about how busy the team feels scores 0 on question 2. Evidence is something another person can check: a backlog count, a missed date, a role nobody can fill.
The leadership team exempts itself. If an executive's favorite project skips the check, every leader below learns the check is optional. Score a request from the leadership team first.
The number has no date. "Improve conversion" is a hope. "Raise proposal-to-close by five points by the end of the second quarter" is a test. Without the date, nobody comes back to check.
You may not need help. If the list is short and the requests are already well argued, the template and one meeting may be all it takes. Use them.
The Order To Roll It Into Next Year's Budget
Before budget season: score what's open. Run the check on every open request. It gives the team a practice round on real requests, with lower stakes than next year's plan.
At kickoff: make the page required. Every new line in next year's budget arrives with the four answers. No page, no discussion.
During review: fund in order of cost. Make the priority decisions first, because they cost nothing. Fix drag 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 question 2 shows a capability gap is the root cause, it moves to the front of the line, and everything else waits.
Every quarter: check the numbers. Pull every funded request and compare its answer to question 4 with what actually happened. Requests that moved their number earn the next tranche. Requests that didn't come back to the table.
What To Expect
The first round defers more than it funds, and some leaders will hear that as a no. Hold the line. Requests that come back with a named constraint, real evidence and a named cut are better bets, and the budget stops growing by default. Within a quarter, most requests arrive with the four answers already filled in, because people learn to diagnose before they ask.
The Short Version
Every spend request should name the constraint it fixes.
Show it's the cause, not a symptom, before the dollar.
Name what gets cut or deferred, or the budget only grows.
Set the number and the date that proves it worked.
This is the Diagnose step in our work at Trifecta. We name the constraint, blueprint the fix, and install it with your team until they own it.
Want the one-page spend check as a ready-to-use template? Ask for it here. It's the page we use to start the conversation about where a company's budget should go first.
Comments