Running the Shadow P&L

Strategic intent: Give the unit a financial language for its contribution — and give consuming units a mirror — without yet moving any money. This is the constrained-autonomy space where the mindset shift becomes tangible.

#Overview

This is Layer 1 of the Adopting Distributed P&L pipeline. Building on the catalog and cost map from Layer 0, the unit derives prices, runs a shadow P&L (virtual revenue alongside real costs), and issues showbacks to consuming units.

No money changes hands. But the economics become visible for the first time — and visibility alone changes behaviour on both sides. Layer 1 is constrained autonomy: the unit behaves as if it were a business (making portfolio and pricing decisions, responding to showback signals) while the organization retains actual financial control.

#When to use it

• After Layer 0 is complete and validated (prices need a cost map to derive from)
• When the unit needs a financial identity to think strategically about its own portfolio
• When consuming units behave as if internal services are free
• As the trust-building stage before any real chargeback (Layer 2)

#Composition

1. #1. Derive cost-recovery prices

   The initial price for each service comes directly from cost data: a capability that cost $100,000 and produced 10 reports yields a $10,000 report. This is cost-recovery, not market pricing — the goal is equivalence, not margin.

2. #2. Run the shadow P&L

   Maintain a parallel financial view: virtual revenue (prices × volumes) alongside real costs (Layer 0 tagging). The unit can now say: "If we were a business, our revenue would be $X and our costs $Y." Keep the cost-based and price-based views simultaneously — the gap between them reveals inefficiencies and cross-subsidies invisible in either view alone.

3. #3. Issue showbacks to consuming units

   Send virtual invoices: a business line that saw "$0 for finance" now sees "$30,000/yr financial reporting, $22,000/yr statutory compliance, $8,000/yr budget support." No money moves; the information creates symmetry — both sides now see the same economic reality.

4. #4. Run "what-if" scenarios

   Model the consequences of raising a price, adding a service, or dropping one. This is where the unit develops judgment about its own economics — judgment that was impossible without an economic language for the work.

#Inputs

• Required: completed Layer 0 cost map and typed service catalog
• Required: tentative input prices from dependency units (rough estimates are acceptable)
• Recommended: node classification (sets the expected shadow result — breakeven for generic, small margin for supporting)

#Outputs

• Service prices — cost-recovery prices for every catalog item
• Shadow P&L — virtual revenue minus real costs
• Showback reports — virtual invoices for consuming units
• Scenario models — pricing / portfolio "what-if" analyses

#Process heuristics

• Cost-recovery first. Don't chase margin at Layer 1; equivalence is the point.
• Parallel accounting is a feature. The cost↔price gap is the most valuable diagnostic the unit gets.
• Showbacks change behaviour without money. Consumers start weighing what they request; providers start seeing themselves as value-producing.
• Sequence circular prices. When Unit A's price is an input to Unit B and vice versa, set provisional prices, respond, iterate to convergence.

#Validation criteria

• Every catalog service has a cost-derived price
• Shadow P&L maintained (virtual revenue vs real cost)
• Showbacks delivered to all consuming units on a regular cadence
• At least one "what-if" scenario produced
• Incentives tied to operational maturity, not virtual financials

#Common mistakes

• Treating the shadow P&L as real — no money moves at Layer 1; promising otherwise destroys trust
• Pricing for margin too early — distorts the cost-recovery baseline
• Skipping showbacks — without the mirror, consuming behaviour never changes
• Tying bonuses to virtual revenue — invites gaming; reward process maturity instead

#Used in pipelines

• Adopting Distributed P&L — as Layer 1

#Connections

• Requires: Establishing Catalog Visibility — Layer 0 provides the cost data prices are derived from
• Feeds: Reaching Financial Autonomy — the shadow P&L becomes the real P&L at Layer 2

#Related reading

• Boundaryless field methodology "The P&L Adoption Mechanism: From Cost Center to Autonomous Unit" — the parallel-accounting insight and the bidirectional meeting point
• Legacy 3EO Toolkit — the Value Adjustment Mechanism and contract patterns