Diagnostic workflow
Diagnostic WorkflowBaseline Assessment
Establish current operational benchmarks and the decision frameworks already in use across the organization.
Module Selection
Choose the economic modules that match the tradeoff in front of you, from delay to switching to missed upside.
Comparative Analysis
Model scenarios side by side to compare long-term financial outcomes and the tradeoffs between them.
Decision Synthesis
Produce an executive-ready summary that frames the recommendation and the value at stake.
Analysis Modules
Run a single module or combine several into one C4 strategic report.
Cost of Delay
The financial stakes of time. Quantify value eroded by postponed initiatives and slow decision cycles.
Switching Cost
The friction of transition. Measure operational downtime, retraining, and lost momentum when you change course.
Opportunity Cost
The value of the path not taken. Capture the upside missed when capital and attention are committed elsewhere.
Carrying Cost
The burden of work in progress. Measure the ongoing cost of holding queues, inventory, and unfinished work.
Grounded in Lean Flow Economics
Methodology
The C4 framework does not invent new economics. It applies a well-established body of Lean thinking — specify customer value, make value flow, and price the waste that erodes it — and renders that thinking in currency. Every figure a C4 module produces traces back to public, peer-recognized sources you can read for yourself.
Lean foundation
Customer Value & Flow
Womack & Jones — Lean Thinking
Five principles anchor the discipline, and the first two do the heavy lifting for C4. First, specify value precisely from the end customer’s point of view — value is only what the customer would pay for; everything else is waste. Second, map the value stream: every step from concept to delivery, each one judged value-adding, necessary waste, or pure waste (muda) to be removed. The remaining three — make value flow, let the customer pull, pursue perfection — sustain it. C4 prices four of those wastes.
The Economics of Flow
Reinertsen — Product Development Flow
In knowledge work the dominant waste is invisible: delay. Reinertsen’s contribution is to make it economic — quantify the Cost of Delay, decide on explicit economic trade-offs, and sequence work by CD3 (Cost of Delay ÷ Duration), delivering the most value per unit of time. This is the engine inside the Cost of Delay module.
Lean at Enterprise Scale
Humble, Molesky & O’Reilly — Lean Enterprise
Carries Lean from one team to the whole organization: optimize for outcomes over output, balance exploring new value against exploiting known value, and prioritize the portfolio by Cost of Delay and CD3. The enterprise-scale case for managing the Cost of Confusion across many initiatives at once — the C4 portfolio view.
Four wastes, priced
Lean names categories of waste. C4 puts a defensible price on the four that drain knowledge-work value the most. Each module is one Lean waste, made measurable.
Cost of Delay
Lean waste: delayValue forfeited while an initiative waits. Computed from the value at stake accruing per unit of time across the delay, then prioritized by CD3 — ship the work that sheds the most value per week first.
Source: Reinertsen, Product Development Flow (2009)
Switching Cost
Lean waste: motion / excess WIPProductivity drained by context shifts and handovers. The Lean countermeasure is direct: reduce WIP and move toward single-piece flow. The module prices the drain so the trade-off is visible.
Source: Poppendieck, Leading Lean Software Development (2009)
Opportunity Cost
Lean waste: wrong priorityThe return surrendered by funding a lower-value priority over the market-mover — the profit of the foregone alternative. It is the management science of the losses you can’t see on a ledger: Deming’s “unknown and unknowable” figures, the hidden money latent in nearly any business. Lean optimizes for value delivered, not output; this module names the value of the road not taken.
Sources: Freiesleben (2005); Deming, Out of the Crisis; Wiig, Fix That Business
Carrying Cost · in development
Lean waste: inventoryThe ongoing expense of unfinished work, idle projects, and accumulated complexity — design-in-process inventory that never appears on the balance sheet. In Lean, inventory is waste held on the books; this module will price the carry so it stops hiding.
Source: Reinertsen, Product Development Flow (2009)
How the math is transparent
The Cost of Delay module is the reference implementation. Nothing is a black box — change an input and the math recomputes in front of you.
Your inputs
Weekly value of the initiative, development duration, and expected delay — all set by you.
Delay accrues
Each week of delay forfeits a week of value; the cumulative Cost of Delay is the running sum, shown against the total value at stake.
Prioritize by CD3
CD3 = Cost of Delay ÷ Duration. The initiative that sheds the most value per unit time is sequenced first.
Deterministic & tested
Every figure is a deterministic function of your inputs and is covered by automated behavior tests — reproducible, not asserted.
References
Womack, J. P. & Jones, D. T. — Lean Thinking: Banish Waste and Create Wealth in Your Corporation.
Free Press (1996; rev. 2003). The five Lean principles — beginning with specifying customer value and mapping the value stream to expose and remove waste (muda). The authors founded the Lean Enterprise Institute.
Rother, M. & Shook, J. — Learning to See: Value Stream Mapping to Add Value and Eliminate Muda.
Lean Enterprise Institute (1999). Introduced value stream mapping to the West — the discipline of tracing material and information flow to find waste.
Rother, M. — Toyota Kata: Managing People for Improvement, Adaptiveness, and Superior Results.
McGraw-Hill (2009). The improvement and coaching kata — the routine practice of managing flow and adapting to change.
Reinertsen, D. G. — The Principles of Product Development Flow: Second Generation Lean Product Development.
Celeritas Publishing (2009). Quantifying the Cost of Delay, economic decision-making, and sequencing by delay cost ÷ duration — the basis for CD3. Backs the Cost of Delay and Carrying Cost (design-in-process inventory) modules.
Anderson, D. J. — Kanban: Successful Evolutionary Change for Your Technology Business.
Blue Hole Press (2010). The Kanban method for knowledge work — visualize work in progress, limit WIP, and manage flow. Reinforces the Switching Cost (WIP) and Carrying Cost view.
Kersten, M. — Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework.
IT Revolution (2018). The Flow Framework — tracking business value through delivery value streams and removing bottlenecks. Backs the whole-portfolio Cost of Confusion view.
Poppendieck, M. & Poppendieck, T. — Leading Lean Software Development: Results Are Not the Point.
Addison-Wesley Signature Series (2009). Economies of flow over scale; the waste of context shifts and handovers; acceptance-test-driven delivery. Backs the Switching Cost module and the platform’s test-first discipline.
Freiesleben, J. — “The Opportunity Costs of Poor Quality.”
Quality Assurance Journal 9(1), 3–10, John Wiley & Sons (2005). DOI: 10.1002/qaj.309. Defines opportunity cost as the profit of the foregone alternative — and shows it is quantifiable. Backs the Opportunity Cost module.
Deming, W. E. — Out of the Crisis (1986) & The New Economics (1993).
MIT Press. Running a company on visible figures alone is a “deadly disease” — the costliest figures (the lost customer, the sale never made) are “unknown and unknowable.” The management science of Opportunity Cost.
Liker, J. K. — The Toyota Way.
McGraw-Hill (2004). Codifies TPS, including the 8th waste — unused human potential: the value forgone by not using people’s capability. Opportunity cost of capability.
Wiig, J. H. — Fix That Business: Finding the Hidden Money in Nearly Any Business.
The practitioner case for surfacing latent, forgone value — “hidden money” — which is opportunity cost made tangible. Backs the Opportunity Cost module.
Humble, J., Molesky, J. & O’Reilly, B. — Lean Enterprise: How High Performance Organizations Innovate at Scale.
O’Reilly Media (2015). Lean and Agile at organizational scale; outcomes over output; prioritizing the portfolio by Cost of Delay and CD3. Backs the whole-of-portfolio Cost of Confusion view.
Imai, M. — Kaizen: The Key to Japan’s Competitive Success.
McGraw-Hill (1986). Kaizen — continuous, incremental improvement as everyone’s daily work; the cultural engine behind sustained waste reduction.
Maskell, B. H. & Baggaley, B. — Practical Lean Accounting: A Proven System for Measuring and Managing the Lean Enterprise.
Productivity Press (2003). Value-stream costing — measuring economics by value stream rather than standard unit cost. The accounting backbone for putting a defensible price on waste.
Poppendieck, M. & Poppendieck, T. — Implementing Lean Software Development: From Concept to Cash.
Addison-Wesley (2006). Applies Lean value and economics to software — “concept to cash” value-stream thinking in place of standard cost accounting.
Ohno, T. — Toyota Production System: Beyond Large-Scale Production.
Productivity Press (1988). The origin of muda — the seven wastes Lean sets out to remove — and of the kanban pull signal.