Slide 01

86% Waste Density. Or 14% Value Density. Same Number. Different Board Reaction.

CFO + CTO + Board

Core claim

Would you be surprised if your engineering organization spent less than 20% of its capacity creating customer value? You should not be. Most don't.

Value stream mapping reveals the same number told two ways: value density — aspirational, makes boards feel hopeful — or waste density — visceral, makes boards demand change. Same data. Different emotions. Choose based on whether you need inspiration or urgency. Most organizations need urgency.

Implementation 60 days to map. The number you find will be uncomfortable. That discomfort is the point.

Slide 02

Seven Teams. 24 Weeks. 15 Weeks of Work. 9 Weeks Waiting at Handoffs.

The relay problem

Total elapsed time 24 weeks

One checkout feature. Product → Architecture → Platform → Services → Frontend → Security → Operations. Six months to ship.

Actual work time 15 weeks

Seven teams working their leg of the relay. Each team optimized for their own throughput. Nobody watching total race time.

Waiting at handoffs 9 weeks

Work sitting "ready" while teams finish other priorities. Coordination overhead. Approval queues. Rework from contradictory feedback across boundaries.

You've got world-class sprinters running a marathon relay, and each runner is also doing the pole vault, and on a good day ice dancing training. You're wondering why it takes six months.

The relay problem: seven teams each optimized for their leg while destroying total race time

Slide 03

$1.1M Spent. $154K Created Customer Value. $946K Was Organizational Friction.

The real economics

Where the $1.1M went

14% — Customer value creation: Code that differentiates the product, design that improves experience
38% — Organizational overhead: Ceremonies, coordination, waiting for other teams, approvals
22% — Rework: Contradictory feedback, requirement changes, incident fixes
16% — Compliance theater: Documentation nobody reads, post-hoc reviews, checkbox exercises
10% — Waste in queue: Work sitting "ready" while teams work other priorities

The board framing choice

14% value density — "We're creating some value, we could create more." Feels like an opportunity. Boards respond with measured interest.
86% waste density — "We're burning $946K of every $1.1M on organizational dysfunction." Feels like a crisis. Boards demand immediate change.
Same data. Same truth. Different emotion. Different board reaction. You choose the emotion based on whether you need hope or urgency from your board right now.

Slide 04

Three Days to Map. Then Categorize: Does This Create Customer Value, or Manage Organizational Complexity?

The mapping method

How to run the map

Pick one recent feature — ideally one that took longer than expected. Map every step from "we should build this" to "it's in production." Every handoff. Every wait state. Every approval.

Then categorize each step: Does this create customer value? Or does it manage organizational complexity? Be ruthless. Most approval ceremonies manage complexity. Most handoffs manage complexity. Most documentation at handoff manages complexity.

Timeline Three days to map one feature thoroughly. You will not need a consultant. You will need two engineers who were actually on the team and will tell the truth.

The four categories

Customer value creation — Code that differentiates. Design that improves experience. Decisions that make the product better for users.

Organizational overhead — Ceremonies, approvals, coordination, meetings that exist to manage the organization, not build the product.

Rework — Work that happens because the first version was wrong, feedback was contradictory, or requirements changed mid-flight.

Compliance theater — Documentation nobody reads, post-hoc reviews that do not actually catch anything, checkbox exercises for audits.

Slide 05

Stop Running Relays. Give One Team the Entire Race.

The operating model fix

Old model

The relay

Specialized teams, each optimized for their leg. Platform provisions. Services builds APIs. Frontend implements. Security reviews. Operations deploys. Nobody owns the full race. Total time suffers at every handoff.

New model

Self-contained features

One team owns end-to-end. Conceives the feature. Builds it. Deploys it. Operates it. Measures it. No relay. No handoffs. No waiting for Platform to provision or Services to update an API.

The result

24 weeks → 6 weeks

The same checkout feature, owned end-to-end by one team, at companies that have made this shift. The work does not shrink. The handoffs and the waits disappear. Value density moves from 14% to 45-60%.

What this requires Teams that can do the full relay — product, engineering, security, deployment. AI agents dramatically lower the barrier to full-stack ownership by eliminating the labor cost of cross-domain work.

Slide 06

Open with Waste Density. Close with Value Density Progress. Control the Narrative.

Board narrative strategy

The narrative sequence

Board session one: show 86% waste density. Create urgency. Get mandate for change. Board session two: show 60% value density. Show progress. Build confidence.

Same improvement. Same number told two ways. The framing controls the board's emotional state — and therefore their decision-making. This is not manipulation. This is communication. You are showing them the same reality. You are choosing which emotional frame creates the right organizational response at each stage.

Slide 07

Map One Feature. In 60 Days, You Will Know Your Waste Density. Then You Will Have No Excuse Not to Fix It.

Decision close

The decision in front of you

You either know what your engineering capacity is actually doing, or you don't. If you don't, your board will eventually ask. When they do, "I don't know" is the answer that ends careers.

The SVP Stephen's predecessor was fired not because the question was unreasonable. He was fired because his organization spent a decade building processes that made the answer unknowable — and then systematically resisting change.

Map one feature. Any feature. Three days. The number will be uncomfortable. That discomfort is the point. It is the fuel for what comes next.