Product
Architectural Decisions Without Cost Attribution
Yet none of these costs are tagged, allocated, or attributed. A leader who approved five fast-path features never sees that the sixth now costs more than twice what it should. An engineering manager who skipped interface work never gets a report showing the accumulated extra across the teams that now depend on his module.
The report attributes Vacuum Effort, Sync tax, Domain coupling, Failure risk cost, and What your engineers actually had to do. Make the invisible cost visible, and the people who create it can see the bill.