Altitude: Enterprise Diagnostic Frame
The 23 Enterprise Gaps
The strategy was approved a year ago. The initiatives shipped, the number it was meant to move has not moved, and the review blames execution, culture or mindset. The stall has more specific causes, and this page names 23 of them.
What a gap is
A gap is a condition that can stall a result and that you can observe in your own organization: in how work gets identified and funded, which priorities win, where approvals wait, and what gets measured.
The usual explanations for a stalled result give you nothing to observe. “Execution,” “culture” and “mindset” each name a feeling in the room. None of them names something you can change on Monday. So the review ends the way the last one did, with a proposal for another reorganization, another framework or another transformation program.
Read the 23 gaps with your real organization in mind: the one that shows up in meetings, not the one in the strategy deck. Mark every gap you recognize, because you will use the marks at the end.
Two labels on every gap
Every gap breaks one of three things: direction, movement or learning. Its barrier says which.
- Alignment Drift breaks direction. The strategy never reaches the work in a form people can act on.
- Choked Flow breaks movement. More work enters the system than the system can finish.
- Broken Feedback breaks learning. Evidence of what the customer got does not reach the decisions it should inform.
A gap’s tier says how severe it is, most severe first.
- Foundational gaps corrupt your signals.
- Structural gaps cap your speed.
- Frictional gaps drain your energy.
The table shows all 23 gaps by barrier and tier. Each name links to its entry.
| Barrier | Foundational | Structural | Frictional |
|---|---|---|---|
| Alignment Drift | |||
| Choked Flow | |||
| Broken Feedback |
The 23 gaps
Alignment Drift
The compass is broken. Everyone is busy and believes their work is the right work, but customers still don’t get what they need.
1. Incentive Misalignment
Foundational
Leadership says “innovate.” The incentive structure says “no surprises.” Guess which one controls the bonus. Managers caught between the two fund the safe bet and describe every pivot as “staying on plan.” So the portfolio fills with safe bets. A bet that cannot surprise anyone has little downside, and little upside for the same reason.
Go deeper: Incentive Misalignment
2. Language Drift
Foundational
Everyone says “customer value.” Nobody means the same thing. The meeting ends in agreement, because each person agreed to their own meaning. “Done” and “capacity” drift the same way at every layer they pass through. The differences surface later, in execution, and you pay for them in rework.
Go deeper: Language Drift
3. Delivery-as-Success
Foundational
Shipping counts. Learning doesn’t. So teams fake certainty to hit the scoreboard. Success is judged at the end, by one test: was the commitment delivered? Reviews praise the teams that delivered, whatever happened to the customer, and an experiment that disproves an assumption gets labeled a failed project. The result is efficient delivery of the wrong things.
4. Motion-as-Progress
Foundational
The portfolio review opens on the status report. Milestones are complete, burn is on plan and utilization is high. Nothing in the report says whether customers are doing anything differently. Delivery-as-Success is the test applied when work ends. This gap is the test along the way, where activity stands in for progress. So course correction comes late, if it comes at all.
5. Capacity Denial
Structural
Leaders say “do this too,” never “do this instead.” Everything starts. Nothing finishes. Each new opportunity looks compelling on its own, and “we can do both” avoids an uncomfortable conversation about trade-offs. But the portfolio review keeps adding priorities and never removes one. Cycle times inflate, and urgent work queues behind other urgent work.
6. Portfolio Fog
Structural
The dashboard says green. The team is drowning. Aggregation hides the truth: the portfolio roll-up smooths over the teams that are blocked. Then a status flips from green to red with no yellow in between. Until that day, leadership decides on false signals, and teams learn to protect the indicator.
Go deeper: Portfolio Fog
7. Horizon Collapse
Frictional
Tuesday’s data says pivot. The quarterly commitment says stay. The commitment wins. The board needs return expectations and sales needs commitments to close deals, so the quarter locks. But once it locks, the evidence arrives and the decision waits. Teams keep executing a plan they know is outdated, because the answer to any mid-quarter change is “we already committed to the board.”
Go deeper: The Strategic Cadence Trap
8. Strategy Vapor
Frictional
The strategy says “grow market share.” Teams need to know what to build on Monday. Nobody owns the translation between the two. The strategy was written to inspire and align. It excludes nothing, so any work can be justified under it. Each layer guesses what the layer above meant. Decisions turn into contests of interpretation, and delivery idles while they run.
9. Priority Collision
Frictional
The loudest voice wins. Economic reasoning waits. The analysis gets presented, and then an executive’s opinion overrides it. Those opinions were built on successful careers, and they carry that weight into the room. Teams learn the real rule quickly: getting work prioritized takes a sponsor, not a business case. High-impact work waits while preferences get funded.
Choked Flow
The system is full. Starting new work is easy, but finishing anything already started is hard.
10. Project-Funding Trap
Foundational
Every project cycle resets the team to zero. You are paying for amnesia. Project funding persists because it fits the way budgets get built. But every project has to assemble a team, the team spends weeks learning the domain, and the team disbands when the project closes. Knowledge gets rebuilt each time instead of compounding. And while teams keep churning, flow cannot stabilize.
Go deeper: Project-Funding Trap
11. Silo Survival
Structural
Marketing optimizes reach. Engineering optimizes throughput. Operations optimizes stability. Nobody optimizes for the customer. Each leader is doing the job they were given, and each function’s metrics are green. But value has to cross the boundaries between functions, and every boundary becomes a negotiation. Each decision is right for its function and worse for the whole.
12. Decision-Rights Fog
Structural
Nobody knows who can say yes. So everyone waits for the VP. Decision rights were never defined here, because defining them meant an uncomfortable conversation. One team gets praised for a call that got another team reprimanded, and people draw the obvious conclusion. When authority is unclear, the safe move is to escalate. Routine choices go up the chain and queue there.
Go deeper: Nobody Knows Who Can Say Yes
13. Missing Runway
Structural
The “simple feature” needs three weeks of foundation first. You skipped the runway: the capability the feature depends on was never built, because enabling work is invisible to customers and features win when the roadmap is reviewed. The bigger cost comes with the next strategic pivot, which needs groundwork that does not exist.
14. Governance Drag
Structural
Governance was designed for quarterly releases. Teams complete work weekly. The calendar always wins. Finished work waits for the review board, so teams adapt. They batch small changes together to cross the gate less often, but batching increases risk. Teams end up optimizing for getting through the gate, not for learning.
Go deeper: Governance Drag
15. Change Saturation
Frictional
Multiple transformations look like ambition from the top. From the bottom, they feel like chaos. At the executive level, change is a portfolio of separate initiatives. At the team level, those initiatives all land on the same people. Old and new processes run side by side, because nobody has the capacity to finish the switch. Teams never reach stable ground, so quality and learning both slip.
16. Capacity Illusion
Frictional
You added ten engineers. Output stayed flat. The bottleneck was never headcount. The math looked simple: more people, more output. But real capacity is set by the bottleneck, and adding people anywhere else does not shorten the wait in front of it. New hires also take onboarding time from the people already there. The money went to headcount instead of the constraint.
17. Risk-Language Mismatch
Frictional
Leaders say “take risks.” Controls say “wait for approval.” The two instructions contradict each other because they were set by different people, at different times, under different pressures. The controls arrived one incident at a time, and they slow all work, not only the risky work. Faced with both instructions, teams optimize for compliance with the controls, not for strategic outcomes.
18. Hidden Debt
Frictional
Executives see slow teams. Teams see a codebase held together with duct tape. Both are describing the same system, but the reports leadership reads show only the slowness. Each feature takes longer than the last, with the same team. When the team proposes technical work, it cannot state the value in terms leadership recognizes. So the investment goes to the symptoms instead of the cause.
Broken Feedback
You’re flying blind. The dashboards carry plenty of numbers, and the leadership team still cannot agree on what is working.
19. Customer Distance
Foundational
Executives debate customer needs. None of them talked to a customer this quarter. What they know arrived through layers of summary, and each layer removed nuance. The people closest to customers speak cautiously, but the people furthest away speak with certainty. So the debate ends in a confident decision, made on wrong information.
Go deeper: Customer Distance
20. Data Illiteracy
Structural
Usage has been falling for weeks, and the numbers reach the executive meeting. Nobody there can say what the fall predicts, so nobody acts on it. Leadership learned to read financial dashboards, and usage data speaks a different language. Then revenue drops, and the same meeting asks why. Leadership acts on the revenue number, weeks late.
21. Leadership Absence
Frictional
Strategy is broadcast from conference rooms. The constraints live in the work, and leaders have not watched the work in months. They ask “why aren’t we moving faster?” without seeing what slows the teams down. What reaches them is a report with the friction cleaned out of it. Decisions end up fitting the reported reality, not the real one.
22. Evidence Stalemate
Frictional
You need ROI proof to run the experiment that would generate ROI proof. The evidence standard was built for large capital decisions, and a small experiment gets held to it. So the work freezes, and teams spend more time justifying experiments than running them.
23. Experiment Prohibition
Frictional
A low-risk test waits for the same security review as a high-risk change. Teams either skip security or drown in it. The organization demands market speed but never sets security boundaries: no one has agreed in advance where a team may experiment without asking. So every team has to ask for approval, and learning dies in the approval queue.
What your marks tell you
Go back to the table and see where your marks fall.
Where they cluster. If most of your marks sit in one barrier, start your diagnosis there. If they spread across all three, that is a reason to check whether the barriers are feeding each other.
How severe they are. The tier sets the order you look in.
- Foundational first. A fix made on top of a foundational gap does not hold.
- Structural next. Find who owns the constraint, because a structural gap is one the teams cannot remove by trying harder.
- Frictional gaps together. Judge them as a set, because each looks manageable alone and the cost is in the sum.
Now pick one result that stalled and trace it through three stops: where the intended outcome was set, where the work waited, and what evidence came back afterward. At each stop, ask which of your marked gaps was at work.
For example, you may find that the outcome was set as a list of deliverables, which is Delivery-as-Success. The finished work waited on a review board, which is Governance Drag. And the evidence that came back was a summary several layers removed from any customer, which is Customer Distance.
Then check whether the gaps are feeding each other: did what happened at one stop help cause what happened at the next?
Do not fix anything yet. The trace shows which of your marked gaps the work behind this result ran into. It does not yet show which of them held the result back.
This list is our framework for organizing what you observe. It is not a scored assessment, so a cluster of marks tells you where to look, not how bad things are.
Where to go next
If your marks spread across all three barriers, read The Vicious Cycle next. It shows how the barriers can feed each other, so you can check whether yours do.
When you are ready to act, The Value Acceleration Process shows how a diagnosis becomes work that someone owns.
Sources and lineage
The 23 gaps, the Three Barriers and the severity tiers form part of the Applied End-to-End Flow framework developed by Curtis Hibbs and Joshua Barnes. The complete treatment appears in Applied End-to-End Flow: Enterprise. These are authored framework models, not externally validated diagnostic scores.