📖 Business
Diagnosing Why Projects Stall
Projects don't fail because the code is hard — they fail because of humans and organizations. Reilly identifies the most common patterns that cause cross-team initiatives to grind to a halt, and provides diagnostic frameworks for identifying and unblocking each one. The key insight is that the stated reason a project is stuck ("we need to refactor the API first") is almost never the real reason. The real reasons are organizational: missing decision-makers, unclear ownership, unresolved disagreements, misaligned priorities, or missing context. Staff engineers who can accurately diagnose stall patterns and apply the right fix are worth their weight in gold.
2
Minutes
2
Concepts
+45
XP
1
How It Works
Five common stall patterns and their fixes:
- Missing Decision-Maker — Nobody has the authority (or willingness) to make a call, so the project spins in circles. Design reviews end with "let's think about it more." PRs sit unreviewed. The fix: identify who actually owns the decision. If nobody does, escalate to someone who can assign ownership. Sometimes just asking "who decides this?" in a meeting is enough to unstick things.
- Unclear Ownership — Multiple teams each think someone else is responsible. Classic: "I thought your team was handling the migration." The fix: write down who owns what in a RACI-style document. Make it public. Review it in the kickoff meeting. Ownership gaps become visible immediately when you force people to put names next to tasks.
- Technical Disagreement — Two valid technical approaches, passionate advocates on each side, no resolution mechanism. The debate becomes the project. The fix: time-box the discussion (one week to present both proposals), define evaluation criteria upfront, then have a designated decision-maker choose. Document the decision and rationale so it doesn't get relitigated.
- Misaligned Priorities — Your project is priority #1 for your team but #5 for the team you depend on. They're not blocking you maliciously — they just have different priorities. The fix: make the dependency visible to leadership. Escalation isn't failure — it's the organizational mechanism for resolving priority conflicts. Sometimes the answer is "your project is less important" and that's useful information too.
- Missing Context — People are blocked because they don't understand why this matters. They're executing tasks without understanding the goal, so they can't make good decisions when they hit ambiguity. The fix: share the why, not just the what. Write a one-pager on the project's purpose and impact. Present it at the kickoff. Repeat it regularly.