Most programs fail not because the technical solution didn't work — but because the governance was mismatched to the work. Jennifer Jones writes on the risk patterns leaders consistently miss.
"Governance, risk, and compliance — designed for how transformation actually works."
Transformation management isn't a technology function. It's a governance discipline — and most organizations are doing it wrong.
I've spent 20+ years inside complex, matrixed organizations learning why transformation initiatives fail even when the technical solution works. The answer is almost never in the code or the timeline. It's in the governance design, the stakeholder alignment, and the mismatch between how work is managed and what kind of work it actually is.
At Choctaw Nation of Oklahoma, I built the enterprise PMO from the ground up, led a full Oracle Cloud implementation, and developed the risk and governance frameworks that now allow the organization to execute at scale. I've managed $150M+ portfolios, led cross-functional delivery teams, and partnered with senior executives to turn strategy into programs that actually land.
My work sits at the intersection of structural governance, organizational change, and adaptive delivery. I write about this regularly — because the most dangerous risks in a portfolio aren't on the risk log. They're hiding inside the governance structure itself.
Published weekly on LinkedIn. Focused on the governance and risk patterns that determine whether transformation takes hold.
Cost reduction often shifts risk rather than eliminates it. The risk doesn't disappear — it just moves somewhere less visible.
Delayed decisions don't pause programs. They create downstream costs that compound quietly — until the timeline absorbs them all at once.
The most dangerous program I ever assessed was showing all green. RYG dashboards don't lie — they just don't tell the whole truth.
Everything was green. And the program had no viable path forward. The risk wasn't in the work. It was in the culture around it.
Transformation success isn't delivery. It's adoption. The delivery workstream is detailed. The change workstream is an afterthought.
Applying the same governance model to predictable, adaptive, and transformational work doesn't reduce complexity. It hides it.
Some initiatives fail even when the technical solution works. The hardest problem is rarely building the solution.
Adaptive work doesn't fail from lack of effort. It fails from lack of direction — and that's exactly what product management exists to provide.
Not all problems can be planned. Some must be learned — and the governance model has to allow for that.
Some work gets safer with more planning. Apply the wrong model and you introduce instability where none existed.
Consistency feels like maturity. But when fundamentally different types of work are governed the same way, risk visibility deteriorates.
Most program risk plans focus on what could go wrong during execution. Fewer examine what will emerge because of it.
Most program plans assume capacity is elastic. It isn't. Capacity risk rarely appears on dashboards — until burnout forces attention.
When programs struggle, leaders often look at execution. But in complex environments, the issue is frequently structural.
Programs rarely fail because risk was absent. They fail because certain risks were never made visible.
Stakeholder thinking isn't administrative overhead. Ignoring it doesn't remove the tension — it delays it.
Academic papers and practitioner sessions presented at professional and academic conferences. Papers available on request.
Whether you're navigating a complex transformation, building a PMO from scratch, or trying to understand why your programs keep missing the mark — get in touch.