Bottleneck

Core Idea

Every system has a constraint. One thing that limits the output of the whole.

That’s the bottleneck. And until you fix it, nothing else matters.

Most teams waste time optimizing around the constraint instead of fixing it. They add features, hold meetings, throw more people at the problem yet throughput stays the same.

This model forces you to ask: What’s the one thing holding this back?
Because progress depends on fixing that, not everything.

Practice

1. Map the system. Write down the main steps or parts, high-level only.
2. Spot friction. Where do things stall, pile up, or depend on others?
3. Isolate the bottleneck. What limits speed, output, or clarity?
4. Fix that constraint. Don’t polish other steps. Reinforce or redesign the weakest point.

Example 1 - Writing Consistently

• System: From idea to published post. Notes – >Draft – > Edit – > Format – > Publish
• Friction: I keep “starting” posts but never finish
• Constraint: Drafting. I overthink sentence 1 and stall for hours
• Action: New rule: rough draft in 30 minutes, edit later.

Example 2 - Weekend Planning with Partner

• System: From idea to shared plan. Suggest – > Check availability – > Decide – > Confirm
• Friction: Weekend plans always feel last-minute or mismatched
• Constraint: No shared time to coordinate expectations
• Action: Added 10-min Friday check-in. Small ritual, major clarity.

Example 3 – Home Workout Routine

• System: From waking up to actually working out. Wake up – > Dress – > Stretch – > Exercise – > Cool down
• Friction: I skip workouts half the week
• Constraint: Getting out of bed and dressed feels like a wall
• Action: Set the alarm, prepare clothes + playlist the night before and take a cold shower to activate in the morning.

Other Considerations

• Bottlenecks are often emotional, not technical. What looks like a resourcing issue might actually be avoidance, indecision, or fear of confrontation.
• The constraint is rarely where you’re looking. Most people focus on visible effort, not limiting factors. The loudest pain isn’t always the tightest choke point.
• Fixing a bottleneck can feel disproportionate. Small changes at the constraint often produce massive gains elsewhere. Don’t confuse effort with leverage.
• New throughput reveals new limits. Solving today’s constraint creates tomorrow’s. That’s the point. Systems evolve by cycling through constraints.