Elevating Change to a True Business Role
Change Managers often find themselves treated as task takers. In this conversation, the focus is squarely on shifting that perception and practice. You hear a pragmatic pathway from being seen as generic project resources to operating as trusted partners who protect business value, shape decisions, and ensure adoption. The speaker grounds every point in lived experience from a multi-site ERP implementation in a manufacturing environment, including what worked, what faltered, and how to embed partnership as standard practice for future initiatives. From Change Delivery to Partnership – a mindset shift to secure a seat at the table.
Why Partnership Matters
The central argument is simple: delivery is not the finish line. Benefits are only realised after go live, once people can reliably execute work in the new way. Change exists to mitigate risk to business outcomes and to champion quality and benefits while time and cost remain under intense project control. Treating change as a partner ensures:
- A shared plan where business, change, project and programme voices determine activities and sequence
- Clarity on outcomes and benefits beyond cutover
- Aftercare, embedding and handover to BAU as explicit success criteria
This reframing elevates the change function from a downstream communicator to a co-owner of adoption and benefits.
Principles That Set the Mandate
A key unlock is agreeing principles that define what change does and does not do. These principles give the mandate to lean into decisions that affect adoption and benefits, and to flag risks early. Examples include:
- Change is here to ensure benefits and outcomes are realised
- Change practitioners are responsible for stakeholder engagement, communications and learning, business benefits and adoption metrics
With principles in place, when decisions threaten adoption, you can place the issue on the risk register and mobilise support to revisit it.
Becoming the Trusted Adviser to Business and Project
The advised posture is to serve both sides. Change is described as an internal assurance function:
- Protecting the business from risks that projects introduce
- Protecting the project from risks that business behaviours can create
This relies on strong interpersonal skills, emotional regulation under pressure, and relentless optimism. It also requires a strong executive change sponsor, ideally at the enterprise level or formally assigned alongside the project sponsor. Positioning change activities as risk mitigations secures attention from outcome-driven leaders and opens doors to steering groups and sponsors. Direct access is essential, balanced with transparent alignment to programme and project leads.
Give Change a Seat at the Table
Critical success factors include:
- A clear change voice at the steering table
- Pre-go-live data and reporting that evidence risks and progress
- Direct channels to sponsors and an understood pathway to escalate
Raise issues first with delivery leadership. If they remain unresolved, escalate through a parallel stream that keeps you aligned with project leads while ensuring the right executives are engaged, often in partnership with the GM of People and Culture for people-related risks.
Bring the Business In: Representation That Carries Weight
When one change practitioner faces a room of project professionals, the business voice can feel outnumbered. Establishing a business representation forum counteracts that dynamic. Senior business nominees represent groups of 10, 20, 50 or more, so the case for adoption is carried by weighty, credible voices. This approach:
- Turns recommendations into collective positions anchored in operational realities
- Shortens the distance between project and business decisions
- Improves prioritisation and sequencing in the plan
In the ERP example, this was part of achieving a nine-site simultaneous go live, returning to full production within four weeks and avoiding business-critical outages. The result becomes a benchmark for future change, not just a one-off success.
Create Local Momentum: The “Change Chains”
Champion networks anchor adoption in the everyday. After risk, impact and stakeholder assessments, individuals are selected for influence, mindset and positional leverage. Each site forms a small cross-functional group. The change team:
- Produces regular briefing packs
- Briefs each site’s leader to cascade and close the loop
- Ensures sites own their readiness tasks
This dual strategy of top-down communication and direct engagement at the coalface preserves message fidelity and builds site accountability for adoption.
Plan Together, Own Tasks Transparently
Partnership shows up in planning discipline. The practice recommended is to co-author the plan and resist unilateral task assignment. Practical steps include:
- A work breakdown structure that traces from the adoption goal back to tasks
- Joint capacity checks with communications, learning and operational teams
- Quick resource estimates to expose gaps early
- A clear path for resourcing decisions when internal capacity is insufficient
If internal teams cannot pick up critical tasks, bring sponsors into the resourcing conversation. Every project is different, so start with collaborative conversations, then escalate as needed.
Measure What Matters: Adoption and Business Metrics
Metrics are most powerful when they resonate with the business owner’s accountabilities. The guidance is to begin with a simple dialogue:
- Which business metrics could this change put at risk
- What evidence would give you pre-go-live assurance
- What signals will tell you post-go-live that performance is stable or improving
Potential measures include training completion and competence, adequate practice time, go-live readiness surveys, log-in and usage patterns, and targeted pulse checks. The change practitioner facilitates, but the business owner must care enough to co-own the measures, since their KPIs are on the line.
Use Risk Registers Wisely
The preferred model is a single, shared project risk register that includes adoption risks. That said, there is pragmatic acknowledgement that some people-sensitive risks are better managed privately with the change team and business sponsor until they can be mitigated. The guiding principle remains unity of delivery responsibility across all dimensions, including adoption.
Build Enterprise Change Maturity
Lifting maturity is presented as a two-lens effort:
- Change as a capability developed through learning, communities of practice and formal training
- Change as a structured process represented by a toolkit or set of consistent outcomes
Maturity assessments can demystify the journey and identify starting points. The same ingredients that help on large projects apply at enterprise scale:
- An active sponsor
- A shared plan
- Business engagement focused on benefits, efficiencies and cost effectiveness
There is a cost to prepare people well. It is typically a fraction of the cost of cleaning up after poor adoption.
Partner From Discovery Through Hypercare
Being invited in just before cutover is too late. Partnership means change runs alongside the project from inception:
- Stakeholders included in requirements and testing
- Core change events integrated with the organisation’s delivery methodology
- Visible milestones for risk assessment, impact assessment, stakeholder mapping, engagement, communications, learning, adoption and benefits realisation
Overlay your change milestones with the project’s phases to keep alignment tight from design to hypercare.
Clarify Accountabilities Across Overlapping Functions
Where communications, learning and capability intersect, clarity, ownership and accountability are the levers. Start with the outcome and the risk statement, then map mitigations into the plan. Practically:
- Co-assess operational capacity with each function
- Estimate effort at task level to surface constraints
- Agree ownership in open conversation before escalating to sponsors for resourcing decisions
The consistent theme is partnership behaviours before escalation, then principled escalation when needed.
Institutionalise the Model
When partnership delivers, leaders notice. The path to standard practice involves:
- Securing executive endorsement to make partnership the baseline
- Finding the owner of project delivery standards and codifying change milestones and requirements within them
- Persisting through the long game of integrating change into project delivery norms
A useful tip surfaces with a smile: never waste a good crisis. Post-incident retros are opportunities to confirm the value of earlier engagement, more practice time, or stronger change events, without the unhelpful energy of I told you so.
Lessons That Refine the Approach
Not everything lands first time. One example was a train-the-trainer model tied to QR-code confirmations. Completion data fell below 10 percent, undermining readiness insight. The team adapted by calling sites directly to verify training outcomes. The takeaway is to keep the learning loop active and change the tactic when the data source is not working.
A Single View of Change Without Central Control
For organisations with distributed change teams, a hub-and-spoke philosophy is recommended. Establish a centre that enables rather than polices, supported by a community of practice. The benefits include:
- Sharing what works and what does not
- Reducing rework on tools and approaches
- Building economies of scale while keeping local ownership
The outcome is capability uplift across the network, not central gatekeeping.
The Mindset Shift for New Change Partners
If you are stepping into a programme and want to be a partner, start here:
- You work for the business, even if you report into the project
- Your mission is to prepare the business to adopt the output, not simply to help the project meet its internal milestones
- Build close relationships with business owners early, because their continuity is what success looks like
That mental model guides everyday decisions and conversations toward adoption and benefits.
Actionable Takeaways
- Establish explicit change principles that define remit and value
- Position change activities as risk mitigations to secure senior attention
- Create a business representation forum to amplify the operational voice
- Build champion networks that combine top-down messaging with on-site ownership
- Co-author the plan, validate capacity and make resourcing gaps visible early
- Co-design adoption metrics with business owners and use readiness data to inform go-live decisions
- Keep one shared risk register for delivery, with pragmatic handling of sensitive people risks
- Start partnership at discovery and overlay change milestones with delivery phases
- Enable a hub-and-spoke community of practice to lift enterprise maturity
- Hold the mindset that you work for the business and measure success by adoption and benefits
Benefits of Further Learning
Exploring the full discussion gives you concrete examples, phrasing for stakeholder conversations, and additional scenarios from Q&A. You hear how to navigate direct sponsor access while staying aligned with project leads, how to escalate to and through, how to course-correct when metrics fail, and how to embed partnership into delivery standards. It is practical, candid and immediately applicable to complex programmes with real operational risk.
🎬 Members can watch the webinar on the MEMBER HUB
🤔 Not a member yet? Now is a great time to JOIN HERE NOW
