Handbook
/
Execution & Delivery
Prioritization for Startups
You can't do everything. Here's how to decide what matters most.
Startups have infinite things they could do and finite resources to do them. Every yes to one thing is a no to something else. Prioritization isn’t just choosing what to do—it’s accepting what you won’t do. The best startups aren’t the ones that do the most. They’re the ones that focus relentlessly on what matters.
Why Prioritization Is Hard
Everything Seems Important
You can build a case for anything:
•
That feature could get us a big customer
•
That marketing channel could unlock growth
•
That hire could solve our problems
But you can’t do everything.
Costs Are Hidden
The true cost isn’t just time:
•
Context switching
•
Delayed focus on key initiatives
•
Team cognitive load
•
Opportunity cost
Doing too much makes everything worse.
Saying No Is Uncomfortable
Declining things is hard:
•
Disappointing people
•
Missing opportunities (maybe)
•
Feeling like you’re not doing enough
But saying yes to everything is worse.
Principles of Prioritization
Fewer Things, Better
Less is more:
•
Depth over breadth
•
Excellence over adequacy
•
Finished over started
Half-done things deliver zero value.
Impact Over Effort
Prioritize based on:
•
Potential impact
•
Cost to pursue
•
Risk of not doing
Not just what’s easy or requested.
Reversibility Matters
Consider:
•
One-way doors (irreversible) → careful consideration
•
Two-way doors (reversible) → faster decision
Don’t over-deliberate reversible choices.
Time Horizon
Balance:
•
Urgent needs
•
Important but not urgent
•
Long-term investments
Don’t sacrifice tomorrow for today.
Prioritization Frameworks
The 80/20 Rule
20% of efforts drive 80% of results.
Apply it:
•
Which 20% of customers drive 80% of revenue?
•
Which 20% of features get 80% of usage?
•
Which 20% of activities create 80% of value?
Focus on the vital few.
ICE Scoring
Rate each option:
•
Impact: How much will this matter? (1-10)
•
Confidence: How sure are we? (1-10)
•
Ease: How easy is it? (1-10)
Score = Impact × Confidence × Ease
Compare scores, prioritize high scorers.
RICE Framework
Similar to ICE, for product:
•
Reach: How many people affected?
•
Impact: How much per person?
•
Confidence: How certain?
•
Effort: How much work?
Score = (Reach × Impact × Confidence) / Effort
The Eisenhower Matrix
Categorize by urgency and importance:
Urgent
Not Urgent
Important
Do first
Schedule time
Not Important
Delegate
Eliminate
Most of your time should be on “Important, Not Urgent.”
The One Thing
Ask: “What’s the ONE thing I can do such that by doing it, everything else will be easier or unnecessary?”
Radical focus on the highest-leverage activity.
Applying Prioritization
Company Level
What are the 2-3 things that matter most this quarter?
Filter everything through:
•
Does this support our top priorities?
•
If yes, how much?
•
If no, why are we considering it?
Team Level
Given company priorities:
•
What can this team do that has most impact?
•
What should we explicitly not do?
•
How do we protect focus?
Individual Level
Each day/week:
•
What’s the most important thing I can do?
•
What should I do first?
•
What should I skip?
Feature/Product Decisions
Evaluate each feature:
•
Customer impact
•
Business impact
•
Technical cost
•
Opportunity cost
Stack rank and cut from the bottom.
Common Prioritization Mistakes
Saying Yes to Everything
“We can probably fit that in.”
Result: Diluted focus, nothing done well.
Fix: Explicit prioritization. Clear no’s.
Prioritizing by Squeakiest Wheel
Whoever complains loudest wins.
Result: Reactive, not strategic.
Fix: Systematic evaluation, not squeaky wheel.
All Equally Important
“These are all P1s.”
Result: No actual prioritization.
Fix: Force rank. There can only be one #1.
Only Short-Term
Focusing only on immediate needs.
Result: Never building for the future.
Fix: Reserve capacity for important-not-urgent.
No Review
Priorities set once, never revisited.
Result: Outdated priorities, misallocated resources.
Fix: Regular priority review and adjustment.
Emotional Prioritization
Choosing based on what’s exciting, not impactful.
Result: Fun but not valuable work.
Fix: Objective evaluation frameworks.
Protecting Priorities
Make Them Visible
Everyone should know:
•
What are the priorities?
•
Why these?
•
What are we not doing?
Review Regularly
Priorities can change, but:
•
Review deliberately
•
Don’t change constantly
•
Explain changes
Use Priorities to Decide
When new opportunities arise:
•
How does this compare to current priorities?
•
Is it important enough to displace something?
•
What would we stop doing?
Learn to Say No
Practice phrases:
•
“That’s not a priority right now.”
•
“Let’s revisit that next quarter.”
•
“We can’t do that without stopping X.”
No is a complete sentence.
When to Reprioritize
Good Reasons
•
Major new information
•
Customer feedback changes understanding
•
Competitive dynamics shift
•
Previous priority completed
Bad Reasons
•
Something new seems exciting
•
Someone complained
•
It’s taking longer than expected
•
We’re bored with current priority
How to Change Priorities
If change is needed:
•
Make it explicit
•
Explain the rationale
•
Update everyone
•
Commit to new priorities
Key Takeaways
•
You can’t do everything; prioritization is choosing what you won’t do
•
Fewer things, better: depth over breadth, excellence over adequacy
•
Impact over effort: prioritize based on potential value, not just ease
•
Use frameworks: ICE, RICE, Eisenhower Matrix help objectify decisions
•
Force rank: “all P1s” means no prioritization at all
•
Protect time for important-not-urgent; don’t just chase immediate needs
•
Make priorities visible; everyone should know what matters and why
•
Review regularly but don’t change constantly; stability enables focus
•
Learn to say no: it’s a complete sentence
•
The One Thing: what can you do that makes everything else easier or unnecessary?
AIMake has access to all of this
Our AI has access to the entire Startup Handbook. Ask it anything about building your startup.
Get started →
← Previous
Meetings That Actually Work
Next →
Project Management for Startups