How Do I Prioritize When Everything in My Business Feels Urgent?
By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.
Key takeaways
- Constant urgency is a routing problem: when all decisions flow through you, they all feel equally critical.
- One named annual bet gives your team a filter to self-sort requests without asking you.
- Written decision-rights thresholds remove you from the majority of day-to-day calls before they reach you.
- A standing weekly triage cadence catches what slips through without turning you into the catch-all.
Why everything feels urgent (and why it is not a you problem)
Here is what is actually happening. Every request that enters your business gets triaged by asking, implicitly or explicitly, 'is this important enough for the founder?' Because the answer is almost always yes, almost everything arrives on your desk with the same urgency tag. The problem is not that your team is bad at prioritization. The problem is that you have not given them a filter they can use without you.
This is the urgency trap. It is a structural failure, not a discipline failure. Founders who try to solve it by getting better at personal prioritization, using a matrix, color-coding their task list, batching their email, are treating a symptom. The volume does not shrink because you got more organized. It shrinks when the work stops routing to you in the first place. If every decision in your business goes through you, that is where to look first.
The fix starts with one named annual bet
Your team cannot self-sort requests without a clear priority anchor. Right now, they escalate to you because they genuinely do not know what the business cares about most this quarter, or what can wait. The first structural fix is a single named annual bet: one outcome, stated in one sentence, with two or three numbers that prove it moved.
A real example: 'Grow net revenue retention from 88% to 95% by December, measured by churn rate and expansion revenue per account.' That sentence alone lets a team member answer 'does this request help that number or not?' without calling you. Anything that does not connect to that outcome is, by definition, lower priority. You still make the call on the few things that are genuinely ambiguous, but the volume of escalations drops sharply because most requests are no longer ambiguous. Setting direction for your team is what makes this work in practice.
Decision-rights thresholds: the artifact that removes you from the queue
The single most concrete thing you can install is a written decision-rights table. For each domain in your business, name who owns decisions and write a threshold below which they act and tell you after, not before. This is not about trust. It is about removing an ambiguous default ('ask Brendan') and replacing it with a clear one.
A real example of what a threshold looks like in practice: any unbudgeted spend under $2,000, the owning person approves it, acts on it, and tells you in the weekly meeting. Any new client commitment that changes scope by less than 10%, the account lead confirms it with the client and logs it. Any hire below a named seniority level, the relevant manager interviews and recommends, and you ratify in a 20-minute conversation rather than running the process. These are not hypothetical. Write them down, share them with the relevant people, and hold the line when someone escalates something that falls below their threshold.
The test of whether a threshold is real: the next time something in that category lands in your inbox, do you route it back or do you answer it? If you answer it, you have just told your team the threshold does not apply. Building this table properly takes an hour and saves you that hour every week.
| Domain | Who decides | Threshold (act and tell after) | Escalate to founder when |
|---|---|---|---|
| Unbudgeted spend | Department owner | Under $2,000 | $2,000 or above, or outside budget category |
| Client scope changes | Account lead | Under 10% of contracted value | Above 10%, or affects delivery timeline |
| Hiring decisions | Relevant manager | Any role below senior level | Senior hire or role is new to the business |
| Vendor contracts | Operations owner | Renewals under existing terms | New vendor, new category, or price increase above 15% |
The weekly triage cadence: the structure that catches the rest
Even with a named annual bet and written thresholds, some things will still slip through. Not because your team is ignoring the rules, but because genuinely ambiguous situations exist. A weekly triage cadence handles those in batch rather than in a stream of interruptions throughout the week.
This is a short standing meeting, typically 30 to 45 minutes, where the team surfaces what is stuck, what is coming up that might need a founder call, and what was decided since last week. You are not running the meeting. You are attending it as the decision-maker for the things that genuinely need you. Everything else gets handled or parked for the following week. Building an operating rhythm around this cadence is what turns it from a good habit into a structural fix.
The cadence does one other thing: it gives your team a reliable window when they know they will have access to you. That alone reduces ad hoc interruptions, because people stop grabbing you in the hallway when they know they have a slot on Thursday morning.
The honest test: what still runs on you?
Take a full week away from the business with no contact. Not a light week, a full week with no calls, no messages, no 'just a quick one.' What stalls is what still runs on you. What moves is what the structure owns. That is your real prioritization problem map, and it is more accurate than any task-management audit.
Most founder-led businesses under about 50 people have a structure gap at the root of the urgency feeling, not a staffing gap. Hiring another senior person into an unstructured business does not fix the routing problem. It relocates it onto them, at a higher cost, and if they leave, it routes straight back to you. Whether to hire or fix structure first is a question worth asking before any senior hire.
What to actually do this week
You do not need a full operating overhaul to start. Three concrete actions this week will move the needle.
- Write your one annual bet in one sentence with two numbers. Put it somewhere your team can read it.
- Pick one domain where you get the most interruptions and write the threshold below which the owning person acts without you. Tell them. Hold the line once.
- Block 45 minutes next week for a standing triage meeting and put your team on the agenda instead of your inbox.
When everything feels urgent, the missing piece is usually a direction everyone shares. The Momentum Engine starts by building that with you, then moves on to decisions and delivery.
See the Momentum EngineCommon questions
Is this really a structure problem, or do I just need better time management?
It is almost always a structure problem. Better personal time management helps you cope with the volume, but it does not reduce the volume. The volume reduces when requests stop routing to you by default, which only happens when your team has a named priority anchor, written decision thresholds, and a reliable cadence to surface the genuinely ambiguous things. Time management tools sit on top of a broken routing system and make it slightly more bearable. They do not fix it.
How specific do decision-rights thresholds need to be?
Specific enough that a team member can apply them without calling you. 'Use your judgment on small spend' is not a threshold. 'Any unbudgeted spend under $2,000, you approve and log it, tell me at the weekly meeting' is a threshold. The dollar number, the domain, and the reporting expectation all need to be explicit. Vague thresholds produce the same volume of escalations as no thresholds.
What if my team makes a bad decision under their threshold?
That is part of the system working. A bad $1,500 decision that your team learns from is cheaper than routing every $1,500 decision through you for the next three years. The threshold is not permission to ignore bad patterns. If someone consistently makes poor calls in their domain, that is a performance or capability conversation. But pulling the threshold back to yourself does not solve the capability gap, it just buries it.
How do I handle genuinely urgent things that cannot wait for a weekly meeting?
Define in advance what counts as a genuine interrupt: a client at risk of churning above a certain revenue threshold, a legal or compliance issue, a delivery failure that will miss a commitment. Write those down. Everything that is not on that short list waits for the weekly cadence. Most things that feel like emergencies are not. The list forces you and your team to be honest about which ones genuinely are.
What if I have tried delegating before and it always comes back to me?
That usually means the delegation happened without the supporting structure. You handed off a task but kept the decision rights, the context, or both. A team member who does not know the annual bet, does not have a written threshold, and does not have a reliable cadence to surface questions will default to bringing things back to you, because that is the only safe move available to them. The fix is not to delegate harder. It is to build the structure the delegation depends on.
How long does it take before the urgency feeling goes away?
With a named annual bet, one or two written thresholds, and a weekly cadence in place, most founders report a noticeable drop in reactive interruptions within three to four weeks. The full shift, where the business runs on its own operating rhythm rather than on you as the rhythm, takes longer and usually requires more structural work. But the urgency feeling is one of the first things to ease because you have given the team somewhere to put decisions that are not you.