The Unreliable Narrator Series
Your Dashboard Is an Unreliable Narrator
4 min read · Innovation Tax
Every metric is green. Every SLA is met. Sprint velocity is up 23% quarter-over-quarter. And yet—nothing meaningful ships.
If this feels familiar, you're not failing at execution. You're living in a movie with an unreliable narrator.
The Green Light Theater
Imagine a dashboard. It looks like this:
None of these are lies. They're all technically accurate.
That's what makes an unreliable narrator so effective.
What the Dashboard Can't See
Dashboards are measurement systems, and every measurement system has a boundary. What falls inside that boundary gets reported. What falls outside doesn't exist.
Here's what typically falls outside:
What Gets Measured
- Test coverage percentage
- Build pipeline status
- Sprint velocity trend
- Uptime and SLA compliance
- Deployment frequency
What Doesn't Get Measured
- Critical path fragility
- Linguistic Debt across teams
- Knowledge silos and key-person risk
- Context decay over time
- Semantic drift between Product and Engineering
The first column is your dashboard. The second column is your Innovation Tax—the hidden maintenance burden that compounds every quarter, consuming capacity that should go to building what's next.
The Rashomon Problem
In Akira Kurosawa's Rashomon, four witnesses describe the same crime. Each account is internally coherent. Each is completely different. The audience never learns what actually happened.
Engineering organizations have the same problem. Ask three people about the state of a project and you'll get three convincing but contradictory narratives:
ENGINEERING
“The architecture is fundamentally broken and we're just layering hacks to hit a date.”
PRODUCT
“We had to drop 40% of the scope, but we're framing it as a V1 optimization to stay on roadmap.”
EXECUTIVE
“The team is showing great velocity and we're confident in the Q3 market launch.”
The dashboard confirms all three. That's the problem.
The Question That Changes Everything
Next time you're looking at a green dashboard, ask this:
“What would this dashboard look like if we added the things we chose not to measure?”
What if it showed the semantic distance between what Product writes in specs and what Engineering builds? What if it showed how many hours engineers spend excavating context from old PRs, Slack threads, and docs? What if it showed the ratio of maintenance work to innovation work—the actual Innovation Tax?
At Beyond The Alignment, we've found that engineering teams spend an average of 72% of their time excavating context rather than building. We've found that when the Innovation Tax crosses $2 of maintenance for every $1 of innovation, organizations hit a tipping point where adding more engineers actually makes you slower.
Your dashboard won't show you any of this. It wasn't designed to.
The Narrator Isn't Lying. It's Partial.
The challenge isn't eliminating the unreliable narrator. Every measurement system is partial by design. Dashboards show what's measured. Roadmaps reflect what's been agreed on. Retrospectives surface what feels safe to share.
The challenge is remembering there is one.
Once you see the narrator, you can start asking better questions. You can measure the gap between the story and the territory. You can surface the Innovation Tax before it compounds into a crisis.
That's what we built our methodology to do. Not to replace your dashboards, but to show you what they can't see.
Go Deeper
Experience the full interactive version
The Unreliable Narrator—a cinematic exploration of organizational dysfunction through the lens of film.
View the interactive experience →See It In Your Codebase
What's your Innovation Tax?
Run your repos through the BTA platform. See what your dashboard isn't showing you.
Try It YourselfNEXT IN THIS SERIES