How to Decide What to Do When Everything Feels Urgent
Founder focus improves when urgency is separated from consequence and cost of delay.
A practical system for deciding what is truly urgent, what can wait, and what should stop consuming founder attention.
In short
- • Diagnose the decision before applying a tactic.
- • Use evidence and context to distinguish the likely causes.
- • Make the next action, trade-off and review point explicit.
When everything feels urgent, urgency has usually replaced a decision system.
A founder can spend a full day answering messages, fixing small issues, approving work, attending meetings, and reacting to requests while the decisions that determine the company's direction remain untouched.
The answer is not simply to work faster. It is to distinguish consequence from immediacy.
Start with the consequence of waiting
For every request ask:
- What happens if this waits until tomorrow?
- What happens if it waits a week?
- Who is actually blocked?
- Is the consequence financial, customer-facing, legal, operational, or merely uncomfortable?
- Is the decision reversible?
- What is the cost of being wrong?
- Does the founder personally need to decide?
This separates urgency from importance.
Use four triage buckets
Act now: waiting creates serious or irreversible consequences.
Schedule: important work that can wait for a defined decision window.
Delegate: necessary work where someone else can make the decision.
Drop: work whose consequence does not justify its cost.
The purpose is not perfect categorization. It is preventing every incoming request from becoming the founder's next command.
Protect learning time
Reactive work can crowd out learning.
Y Combinator's startup guidance emphasizes talking to users, building something people want, and avoiding distractions that take founders away from understanding customers and improving the product.
Protect time for questions such as:
- What are customers struggling with?
- Why are deals being lost?
- What causes churn?
- Which product assumption is uncertain?
- Where is cash constrained?
- Which decision would make the next month clearer?
If all time is consumed by requests, the company can become efficient at reacting without becoming better at deciding.
Match analysis to reversibility
Not every decision deserves the same amount of analysis.
A reversible decision can often be made quickly, tested, and changed.
A consequential or expensive decision deserves more evidence.
Potentially reversible examples include testing a message, changing a meeting format, or running a narrow customer experiment.
More consequential examples may include major fixed-cost commitments, critical hiring, regulated-market entry, or financing decisions.
The classification depends on context. The principle is to match decision effort to downside and reversibility.
Founder attention is scarce
Founder attention is often treated as free. It is not.
When the founder becomes the approval point for dozens of low-consequence decisions, the opportunity cost is the high-value decision that never gets made.
Ask:
"Could a clear rule allow someone else to decide this next time?"
If yes, document the rule and transfer the decision.
If no, determine whether the uncertainty itself is the real problem.
Daily urgency reset
Write three lists:
Must change: what must be different for the business to move forward?
Must decide: which unresolved decision is creating downstream delay?
Must protect: which work requires uninterrupted founder attention?
Then compare the list with the calendar.
If the calendar contains none of the work required to change the business, the day is being run by incoming demand.
Community evidence
Public startup discussions often describe the tension between building, selling, supporting customers, and reacting to requests. They help identify failure modes but do not establish a universal priority rule.
The useful synthesis is that urgency should be evaluated through consequence, reversibility, ownership, and strategic relevance rather than emotional intensity.
Trade-offs
A strict priority system can become harmful if it ignores real emergencies.
A founder who labels all reactive work unimportant can miss customer failures or compliance issues.
A founder who treats every request as an emergency creates permanent context switching.
The goal is not to eliminate urgency. It is to make urgency earn its priority.
Decision framework
Before taking the next task answer:
- What happens if this waits?
- Who is blocked?
- What is the downside of delay?
- Is the decision reversible?
- Does the founder need to make it?
- Does this change a company-level outcome?
- What higher-value work will be displaced?
If the last answer is significant, the task needs stronger justification.
Related SOE Knowledge
Connect this with SOE's founder focus, decision ownership, team structure, and growth strategy material. The common thread is converting repeated founder intervention into explicit operating choices.
Sources and methodology
Y Combinator's published startup guidance is the primary source for early-stage focus and customer learning. Public founder discussions are qualitative context only. The prioritization framework is SOE synthesis and should be adapted to company risk, stage, and obligations.
Final answer
When everything feels urgent, do not ask which task feels loudest. Ask what happens if it waits, whether the decision is reversible, who owns it, and what higher-value work it displaces.
Urgency should be a property of the consequence, not of the notification.
Related SOE knowledge
Take it into your work
Do something with what you just read.
Save it for later, mark the passage that matters, or open your SOE workspace and keep thinking.
Takeaways
What to carry forward
- → Start with the actual founder problem rather than the surface symptom.
- → Use observable evidence to test assumptions and avoid overclaiming.
- → End with a concrete decision or next step.
Urgency should come from consequence and risk, not from the loudest notification.