# Transformation often breaks before the work begins.
Canonical: https://social-archive.org/tgroenwals/kaxhMdV4t2
Original URL: https://www.linkedin.com/posts/robllewellyn_transformation-often-breaks-before-the-work-share-7504073800133804032-3dW5/?utm_source=social_share_send&utm_medium=member_desktop_web&rcm=ACoAAAAUj9ABA6XwLJ3RcHE4FACjTijtAT4klvY
Author: Rob Llewellyn
Platform: linkedin
Share mode: full
## Content
Transformation often breaks before the work begins. Roles blur. Mandates get misassigned. Too many treat transformation as a one-off project or programme. Projects and programmes end, including those that deliver transformational change. The mandate to keep transforming doesn't. An organisation must keep transforming to remain relevant. Stop transforming, and it starts losing relevance. But continuous doesn't mean perpetual upheaval. The initiatives inside transformation start and stop. What's permanent is the mandate, not the churn. Some organisations go further. They use project and programme frameworks to govern enterprise transformation. Those frameworks are excellent. They help deliver projects and programmes. Some include a phase to sustain the change. But sustaining one change isn't governing the next. They weren't designed to govern an organisation's ongoing ability to transform. This isn't about titles. It's about what the role must deliver. A project manager delivers a defined scope. A programme manager delivers capabilities that realise benefits. A transformation leader strengthens how the organisation keeps evolving. The skills overlap. The mandates differ. You wouldn't confuse a COO with a CIO. In smaller organisations, one person may hold more than one. That adds risk. Each mandate still needs an owner. Governance follows the same pattern. Project governance is for projects. Programme governance is for programmes. Transformation governance spans them over time. Transformation contains projects and programmes. But the whole shouldn't be governed by the rules of its parts. And a mandate is only as real as its authority. A transformation role that's clear on paper can still collapse when trade-offs aren't made. A transformation mandate needs the authority to fund, sequence, stop and reprioritise across every initiative it contains, anchored to value. Without that, it's a label, not a mandate. That's why many large organisations now appoint permanent Chief Transformation Officers, often reporting to the CEO. Portfolio management matters too. It balances all the organisation's investments. It can include investment in a new operating model, a new business model or an AI-driven one. But it isn't designed to govern those changes. Transformation governance is. Authority isn't the whole answer. Change management, leadership, incentives and trust matter too. But without the right mandate, the rest struggles to take hold. Assign a project mandate, you'll get no more than a project outcome. Assign a transformation mandate, you give the organisation the means to keep evolving. Use project frameworks for projects. Programme frameworks for programmes. What are you using to govern transformation? LinkedIn limits posts to 3,000 characters. There's a lot to add to this. So go ahead and include it in the comments. Get The Boardroom Brief Insights for leaders shaping transformation https://cxo.fm/news
## Media
1. image: https://social-archiver-api.social-archive.org/media/archives/tgroenwals/zG8cbJ1Uol/media/0.jpg