Attrition
6 of 7 individual contributors departed in 12 months. Replacement cost, lost expertise, ramp time, and delivery disruption were never consolidated into project economics.
Strategy
The engagement mandate, operating scale, and intended risk control.
The Mandate
A Risk Control Built for Global Scale
A custom risk control application was commissioned for an organization of 30,000 global engineers to inform capital projects exceeding $100M and help prevent $500M in operational risk: $300M in lost production and shutdowns and $200M in penalties and lawsuits.
The mandate was straightforward: build and launch software engineers would trust while coordinating a complex delivery model spanning multiple continents.
Success depended on more than shipping software. It required accurate requirements, meaningful user involvement, stable expertise across functions, change readiness, and governance capable of identifying and correcting execution risk before it reached launch.
Theory vs Reality
The Plan and the Operating Reality
| The Plan Required | Operating Reality |
|---|---|
| Product users inform definition | User research dismissed |
| Stable cross-functional expertise | 6 of 7 individual contributors departed |
| Change readiness before launch | Change management vacant 11 months |
| Coordinated delivery | Project manager position vacant for 11 months |
| Requirements continuity | Business analyst departed after 3 months |
| Early validation before build | User experience expertise excluded from planning and forced to justify basic methods |
| Governance corrects execution risk | ~36 problematic meetings witnessed before intervention |
| Product earns user trust | Users reject product near launch |
Execution
How the team, delivery model, and economics shaped the work.
The 3 Ways Value Was Lost
Leakage, Erosion, Foregone Creation
The Environment
A Team Built to Comply, Not Contribute
From the outside, the project looked functional: a defined scope, a named leader, a delivery timeline. The stakes were anything except ordinary. Built for an organization of 30,000 global engineers, the software existed to inform capital projects exceeding $100M and prevent $500M in operational risk: $300M from lost production and shutdowns, plus $200M from penalties and lawsuits. The product was a risk control, and the quality of its build determined the quality of the organization's downside protection.
Embedded inside the product team, a different picture emerged within weeks. The product owner operated as the singular authority on every decision. Her background was project management, a discipline of schedules and dependencies, and the project demanded product leadership, a discipline of users and evidence. The difference surfaced in how she ruled: through certainty, through criticism, through penalty for disagreement. The team learned quickly that pushback was costly and silence was safe. The people most capable of flagging problems early held the least political safety to do so.
The delivery model split across continents: 7 North America-based roles carrying salaries north of $140K, a 30-engineer offshore team working through a global systems integrator, and senior oversight from the product owner's manager and a local portfolio lead. Product design maturity across the wider organization was low, turnover was already high, and the project carried both conditions into a single room every week.
The people most capable of flagging problems early had the least political safety to do so.
Estimated Delivery Run Rate
The Economic Scale of the Operating System
NA-Based Team
$1.3M – $1.5M / yr
7 roles at $140K salaries, loaded to $180K–$220K each
Offshore Engineering
$2.4M – $3.9M / yr
30 engineers via integrator at $80K–$130K blended
Senior Oversight
6-figure add-on
Partial allocations, manager and portfolio lead
Estimated Delivery Run Rate
$4M – $5.5M / yr
Operating scale before a single change order
This figure represents the estimated annual delivery run rate, not value destroyed. It establishes the economic scale of the operating system experiencing these conditions every week.
Divergence
Where governance, staffing, and decision patterns pulled the work away from its purpose.
Supervision Without Correction
The Manager in the Room Who Said Nothing
The product owner's direct manager attended week after week. She watched the adversarial meetings, the public criticism, the us-versus-them dynamic hardening between employees and contractors. She was never rude herself. She simply allowed it, and the conduct was filed internally under excellence, perfectionism, and high standards, which gave the damage a vocabulary that made it unactionable.
Nine months passed between the first visible weekly harm and formal accountability. When accountability arrived, it attached to the project. The 6 departures attached to nobody. An organization that assigns no owner to attrition has priced attrition at zero, and a cost priced at zero recurs indefinitely.
9 months between first visible harm and intervention. ~36 witnessed meetings. Zero corrections.
The Vacancies
What Left and Was Never Replaced
Change Management: 11 months absent
Absent for 11 months of active build on a transformation that would land on unprepared users.
Project Manager: 11 months unfilled
Lost and never replaced, leaving coordination duties distributed informally across a multimillion dollar annual operation.
Business Analyst: 3 months, then gone
Lasted 3 months. The project ran its final 9 months without one. Business requirements knowledge left with the person, politically maneuvered off the team under a move framed as resourcing, which is why leadership never questioned it.
6 Individual Contributors: 12 months
Six individual contributors departed within 12 months. The last to leave was the product designer, after a year of being undermined, underutilized, under-resourced, and shown no career trajectory.
What Was Visible From Inside
The Signals Nobody Surfaced
User research dismissed
The product owner held that her subject matter expertise superseded the voice of end users, and nobody with authority disagreed out loud.
Hostile team meetings, weekly
Meetings ran adversarial and draining, eroding cohesion, productivity, and psychological safety in front of a manager with the power to stop it.
Contractor divide calcified
Eroding the cross-functional trust a split-continent delivery model depended on.
Every layer filtered upward
Managers managed up, individual contributors protected themselves, and the metrics leadership tracked captured none of it.
Unmeasured Exposure
What Leadership Never Quantified
The project tracked spend. It did not track the economics of execution failure.
Vacancy Drag
Project management and change management remained vacant for 11 months. Business analysis disappeared after month three. The economic effect was absorbed across the organization rather than attributed to the project.
Rework
User feedback arrived after build, when changes triggered contractual change orders. The cumulative cost of discovering requirements late was available in vendor and change order records but never analyzed as a single source of value leakage.
Governance Latency
Approximately 36 weekly meetings occurred across nine months before management intervention. Nobody calculated the cost of allowing known operating conditions to persist.
Risk Control Degradation
Users ultimately rejected a tool intended to help protect against $500M in operational exposure. The organization never quantified how deteriorating adoption affected the efficacy of the control itself.
The numbers existed. The analysis didn't.
Stakes
How the operating conditions affected launch readiness and economic exposure.
The Consequence
Rejection at Launch
Near launch, users rejected the product. The feedback was predictable to anyone who had watched the process: the people who would use the software had never been meaningfully consulted about it. The rejected tool was intended to inform $100M+ capital projects and protect against $500M in operational risk across a global engineering organization.
By then the project was fully coded. Every edit triggered a change order, every change order meant rework, delays, and contract modifications against a vendor baseline already north of $2M, layered on top of a $4M to $5.5M annual operation.
When change management was finally reintegrated after 11 months, their first observation was the obvious one: the transition was going to be difficult. The conditions making it difficult had been compounding, undisturbed, for nearly a year.
The scale at stake
$100M+
Capital projects informed by the application
$200M
Penalty and lawsuit exposure the control helped prevent
$300M
Lost production and shutdown exposure
$500M
Total operational risk the custom application was built to prevent
Insight
The final finding connects visible operating behavior to economic exposure and gives leaders a practical screen for detecting it earlier.
The Structural Finding
The Problem Was Never Invisible
One difficult leader makes a convenient explanation, and the explanation conceals the finding. The structure made truth-telling costly and silence rational, then placed a supervisor in the room every week with full visibility and no mechanism converting observation into correction.
Information was never the missing ingredient. The warning signs were present, early, and witnessed. What the organization lacked was a channel that moved evidence from the people close enough to see it to the people positioned to act on it, before the cost embedded itself in the contract.
The most expensive problems in an organization are rarely invisible. They are simply never surfaced to the people who could do something about them, and a diagnostic exists to build exactly that surface.
The Screen for Any Portfolio
Three Questions Every Leader Can Ask This Week
Leakage
What did attrition cost in the last 12 months, and which leader is accountable for that number?
Erosion
What institutional knowledge left the company this year, and what walked out with it?
Foregone Creation
Whose documented input is being dismissed in the rooms where the product gets defined, and what would the end users say if anyone asked?
Findings of this kind require no projection and no benchmark. They are documented from internal systems, validated with the CFO, and produced in weeks. The pattern appears in nearly every organization that has never assigned these costs an owner.
If you are ready to maximize value creation, correct value leakage, and optimize operations, schedule a conversation.