How prioritize when everything feels urgent

The Real Problem Behind Feels Issues

When everything feels urgent, the problem isn't your priorities. It's that you're operating without a clear understanding of your system's constraint.

Most founders mistake symptoms for causes. You see a dozen fires burning and assume you need better time management or clearer goal-setting. But the real issue is deeper: you haven't identified what actually determines your company's throughput.

Think of your business as a manufacturing line. If one machine can only process 100 units per hour while another can handle 500, the slower machine determines your total output. No amount of optimizing the faster machine matters. Yet most founders spend their days optimizing everything except their actual constraint.

This creates what I call the Attention Trap — where urgent tasks multiply because you're addressing effects, not causes. The sales team needs more leads. Marketing needs better messaging. Product needs faster development cycles. All feel urgent because they stem from the same unaddressed bottleneck.

Why Most Approaches Fail

Traditional priority frameworks fail because they assume all tasks exist in isolation. The Eisenhower Matrix tells you to focus on important-not-urgent work. Getting Things Done organizes your tasks by context. OKRs align your team around quarterly goals.

None of these address the fundamental question: which single improvement would increase your company's overall capacity the most?

Here's why popular approaches miss the mark. Priority matrices rank individual tasks without understanding system dependencies. You might perfectly execute your top-priority marketing campaign, but if your constraint is actually in sales conversion, you've just created more pressure on an already bottlenecked system.

Time-blocking and productivity apps make the same error. They help you execute tasks efficiently, but efficiency applied to the wrong activities is just waste with better organization. I've seen founders meticulously plan their days around activities that had zero impact on their actual constraint.

The goal isn't to be busy efficiently. The goal is to identify the one lever that, when moved, moves everything else.

The First Principles Approach

Start by mapping your value creation process from end to beginning. What's the complete journey from initial customer interest to delivered value and retained revenue?

For most businesses, this looks like: Awareness → Interest → Evaluation → Purchase → Onboarding → Value Realization → Expansion/Retention. Each stage has capacity limits. Your constraint is whichever stage has the lowest effective capacity.

Here's the key insight: your constraint determines your company's growth rate. If you can acquire 1000 leads per month but only convert 50 to customers, your growth is constrained by conversion, not lead generation. If you convert 200 but can only successfully onboard 50, onboarding is your constraint.

Most founders never calculate these numbers precisely. They rely on gut feelings and anecdotal evidence. But you can't optimize what you don't measure. Map each stage, calculate its capacity, and identify the bottleneck with mathematical certainty.

Once you've identified your constraint, everything else becomes secondary. Not unimportant — secondary. This distinction matters because it changes how you allocate attention and resources.

The System That Actually Works

The Constraint-First Priority System works in three phases: Identify, Elevate, and Subordinate.

Identify your constraint by tracking conversion rates and capacity limits at each stage of your value delivery process. Don't guess. Measure throughput over at least 30 days to account for normal variation.

Let's say you're a SaaS company with these monthly numbers: 2000 website visitors, 200 trial signups (10% conversion), 40 paid customers (20% trial-to-paid), and 35 successfully onboarded customers (87.5% onboarding success). Your constraint is trial-to-paid conversion at 20%.

Elevate the constraint by applying focused resources to increase its capacity. In this example, every hour spent improving trial-to-paid conversion directly increases company growth. Everything else is secondary until this constraint is broken.

This might mean redesigning your trial experience, changing your pricing model, or improving your sales process. The specific solution matters less than the focused application of resources to the right problem.

Subordinate everything else to supporting the constraint. This doesn't mean ignore other areas — it means their primary purpose becomes feeding or supporting the constraint's operation.

In our SaaS example, marketing should focus on attracting higher-intent prospects who convert better from trial to paid, not just more volume. Product development should prioritize features that demonstrate value during the trial period. Customer success should document what makes trials convert so sales can replicate it.

When you subordinate all activities to supporting the constraint, you stop fighting against your system and start working with it.

Common Mistakes to Avoid

The biggest mistake is assuming your constraint never changes. As you elevate one bottleneck, another area becomes the new constraint. You must recalculate regularly — monthly for fast-growing companies, quarterly for more mature businesses.

I've seen founders spend six months perfecting their sales process only to discover their new constraint was customer onboarding. They kept optimizing the wrong area because they never reassessed their system.

Another trap is the Complexity Trap — trying to optimize multiple areas simultaneously. This feels productive but diffuses your impact. Human attention and organizational change capacity are limited resources. Focusing on your constraint means saying no to other improvements, even good ones.

Don't confuse leading indicators with constraints either. Website traffic might predict future sales, but if your constraint is sales conversion, increasing traffic without fixing conversion just creates more waste in your system.

Finally, avoid the temptation to work on what's most comfortable or familiar. Your constraint is often in an area you understand least well. If you're a technical founder, your constraint might be sales. If you're a sales-driven founder, it might be product development. Follow the data to your actual constraint, not your preferred problem.