A 5-Step Decision Framework for Founders Who Can't Do Everything
When every problem demands attention at once, this five-step framework cuts through the noise and tells you exactly what to do, delegate, or drop.
Jason Kirby· June 26, 2023· 3 min read
The short version
- Define a North Star first — everything that doesn't align gets dropped or backlogged immediately.
- Multiply your expected benefit by probability of success; raw cost-benefit without this step misleads you.
- Opportunity cost is the real filter: positive expected value isn't enough if something else yields more.
- A team member delivering 70% of your outcome is almost always worth the delegation trade-off.
- With repetition the full five steps compress to a 10-second mental check.
Most founders don't have a prioritization problem — they have a clarity problem. When twenty things feel urgent simultaneously, the issue isn't bandwidth; it's the absence of a repeatable filter. This framework gives you that filter. Run it often enough and it becomes a 10-second mental reflex.
Step 1: Define Your North Star
Before any prioritization can work, you need a North Star — a clear statement of your company's ultimate objective and core values. If you haven't defined this yet, block a full day off from operations, pull in your co-founders, and do the work. Everything downstream depends on it.
Once you have a North Star, the first question for every opportunity or problem is simple: does this align? If the answer is no, the item doesn't get evaluated further.
What to do with misaligned items:
Quickly eliminating misaligned work doesn't just save time — it removes the cognitive weight of half-considered obligations.
Step 2: Run a Cost-Benefit Analysis
For every item that survives the North Star filter, ask one blunt question: are the benefits worth the costs?
Costs are time, money, and resources required to reach a successful outcome. Benefits are the value of that outcome. If costs outweigh benefits, either drop the item or reframe the problem from scratch. There is no third option.
This step sounds obvious, but founders routinely skip it when they're excited about an opportunity. The discipline is in forcing the comparison before committing any resources.
Step 3: Weight by Probability of Success
Most people stop at cost-benefit. That's a mistake. A benefit that's only 30% likely to materialise is worth far less than the raw number suggests.
If you're pursuing something that isn't 100% guaranteed, you need to factor probability into the value equation.
The calculation is straightforward: multiply your estimated benefit by your estimated probability of achieving it. That adjusted figure is your real expected value — and it's the number that belongs in your cost-benefit equation, not the optimistic ceiling.
This single step regularly kills initiatives that looked attractive on paper. That's the point.
Step 4: Account for Opportunity Cost
Positive expected value isn't enough. The question is whether this is the highest-value use of your constrained resources right now.
Most early-stage companies are running lean. Committing to something good means not committing to something better. Before you act on an item that has cleared steps 1–3, ask whether there's another opportunity in your queue with a higher yield-to-input ratio. If there is, that one goes first.
This step enforces genuine prioritization rather than just task filtering. It's what separates a short task list from an optimized one.
Step 5: Decide Whether You Do It or Delegate It
Once you've confirmed an item is aligned, net-positive, probable, and the best use of resources — the final question is who executes it.
Founders default to doing everything themselves, especially early on. That instinct is understandable but expensive. Before you take something on personally, ask whether someone on your team could handle it.
A useful rule of thumb: if a team member can deliver 70% of the outcome you would achieve, that's almost always worth the trade. The 30% delta is the cost of freeing yourself for higher-leverage work. A good outcome that happens is better than a perfect outcome that never gets prioritized.
How to evaluate delegation:
- Identify who on your team has the relevant skill or capacity
- Estimate the probability they produce an acceptable outcome
- Compare that expected output to the cost of your own time on higher-value tasks
- Delegate if the math favors it — and it usually does
What the Framework Produces
Run all five steps and you end up with three clean buckets: do it yourself now, delegate it, or drop it. Your active task list shrinks dramatically. What remains is the work that actually moves the business.
The first few times you use this, budget real time — 30 to 60 minutes on significant decisions. With repetition, the logic internalizes. The goal is to reach a point where the filter runs in under 10 seconds for most choices, freeing mental bandwidth for the decisions that genuinely require it.
Questions founders ask
How long does this framework take to run in practice?
Initially, expect 30–60 minutes on major decisions. With repeated use, the logic internalizes and most decisions can be filtered in under 10 seconds.
What should I do with opportunities that don't align with my North Star?
Drop them or move them to a backlog in a tool like Asana or Trello. Don't evaluate them further until your North Star changes.
When is it worth delegating instead of doing something yourself?
If a team member can deliver roughly 70% of the outcome you would achieve, delegation is almost always worth it — freeing you for higher-leverage work.
Your situation isn't generic. Neither is the answer.
Ask your question and get a straight answer, sourced from 100+ founders and investors who have raised and exited at scale.
Ask your board