> Markdown version of [/jobs/ext/2918207-head-of-business-change](https://www.wearedevelopers.com/jobs/ext/2918207-head-of-business-change). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Head of Business Change - **Company:** Cornerstone - **Location:** Theale, UK - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Testing (Software), Artificial Intelligence, Data Governance, RAID - **Published:** September 15, 2026 - **Apply:** https://www.collegerecruiter.com/job/2879182531-head-of-business-change ## About the Role * 8+ years in senior change, transformation or delivery leadership (Head of Business Change, Head of PMO, Transformation Director, Programme Director or similar). * Evidence of standing up or maturing an enterprise delivery and change capability: engagement, demand, portfolio, delivery standards, adoption and benefits. Not just running a settled PMO. * Led multi-project or multi-programme portfolios, including capacity, dependency and investment trade-offs. * Solid working knowledge of portfolio, programme and project methods across agile, waterfall and hybrid. * Experience running business engagement / demand models with senior sponsors. * Comfortable with product and service ownership models, and with benefits tracking that continues after go-live. * Used to working with architecture, data, security and operations inside delivery. * Infrastructure, telecoms, asset-intensive or similarly complex environments strongly preferred. * Aware of the UK CNI / telecoms regulatory context and what it means for change control and release. * Strong with senior stakeholders. Able to say no, or not yet, when demand does not fit capacity or strategy. * Commercially aware. Able to recommend investment and prioritisation on value, risk and strategic fit. * Able to lead a mixed team and raise delivery maturity without dropping current commitments. ## Description The Head of Business Change leads the business change and adoption function. You own how change is prioritised, governed, delivered and adopted across the Technology, Data & Digital portfolio, and the business change that depends on it. You are accountable for business engagement and demand management, the investment portfolio, project and programme delivery, business analysis, test assurance, adoption and benefits realisation. This is a build role. We already deliver projects, but the engagement model, demand process, portfolio governance, product and service ownership, adoption and benefits management are not where the strategy needs them to be. You will put that operating model in place, strengthen the team, and keep current delivery under control while you do it. Scope of accountability * How Technology, Data & Digital and the business engage on change: discovery, shaping and agreement. * Single demand intake, triage, prioritisation and the decision forums that sit around it. * The investment portfolio: funding, capacity, dependencies and financial control. * Enterprise PMO: standards, reporting, risk, dependencies and portfolio visibility. * Project and programme delivery (agile, waterfall or hybrid). * Business analysis: requirements, process design and traceability into delivery. * Software / test QA for change delivery. Data quality sits with the Head of Data. * The product and service ownership model: named owners, service catalogue, measures and roadmaps, working with platform and domain owners. * Adoption, business readiness, communication and workforce impact. * Benefits management: plans, tracking, realisation, and recommendations to stop, defer or resequence work. * A governed route for innovation and experiments into the portfolio, Business engagement, demand and portfolio * Define and run the business engagement model, with clear roles for sponsors, outcome owners, engagement leads and design authorities. * Put in place a single demand process so work is shaped against strategy, capacity and risk before it is funded. * Own the Technology, Data & Digital portfolio view: what is in, what it costs, what depends on what, and how delivery is going. * Support the portfolio decision forums with clear options to approve, stop, defer or resequence. * Make sure work entering the portfolio has a sponsor, an outcome owner, a benefits case and named dependencies on architecture, data and security. Delivery governance and PMO * Establish and run the Enterprise PMO: standards, stage controls, reporting, RAID, dependencies and financials. * Set ways of working that cover agile, waterfall and hybrid delivery without adding process for its own sake. * Give executives portfolio reporting they can take decisions from. * Manage cross-portfolio risk, dependencies and resource conflict, and escalate early. Project and programme delivery * Lead delivery for the Technology, Data & Digital change portfolio and the business initiatives that depend on it. * Keep plans realistic against capacity and sequenced to the strategy: foundations first, then connect and modernise, then scale. * Hold delivery to time, cost, quality and scope. * Work with Enterprise Architecture, Data and Security so design and controls are part of delivery, not bolted on at the end. Business analysis, testing and quality * Lead business analysis so requirements, processes and acceptance criteria are clear and owned. * Make sure testing and software QA give a real view of quality before release. * Keep a hard line between software QA and data quality / data governance (Head of Data). Product, service and innovation * Put in place the product and service ownership model the strategy calls for: named owners, catalogue, measures and roadmaps. * Ownership sits with the business or platform lead. This function provides the engagement, portfolio and delivery mechanism around it. * Create a governed path for innovation so experiments can be funded or stopped without bypassing the portfolio. Adoption, benefits and continuous improvement * Own adoption and business readiness for major change: communication, training, cutover and go-live. * Put benefits management in place: baseline, target, who tracks it, and a review after delivery. * Improve how we deliver through better tools, shared playbooks and lessons learned. * Judge change on whether it was adopted and whether the benefits landed, not on whether the project closed. Leadership and stakeholders * Lead the team across PMO, business analysis, project delivery, testing and change / adoption. * Work with senior stakeholders in the business and technology to keep demand aligned to strategy and capacity. * Work as a peer to the Head of Data and the Head of AI, Architecture & Digital Operations, with clear hand-offs between delivery, architecture, operations and data. * Build the team and ways of working needed for Horizon 1 and the later stages of the strategy. Measures of success * Business engagement, demand and portfolio model agreed and in use, with named sponsors and outcome owners on priority work. * One clear view of the Technology, Data & Digital portfolio: priorities, funding, capacity, dependencies and delivery health. * Demand-to-decision time visible and improving. Work that does not fit the strategy is stopped, deferred or resequenced. * Investment mapped to the strategy priorities. Horizon 1 foundation work is protected. * Delivery is predictable: milestones met, risks and dependencies managed, exceptions raised early. * Product and service ownership in place for priority services, with roadmaps and measures. * Adoption and readiness planned for major releases. * Benefits plans on priority initiatives, tracked after go-live. * Sponsors use the portfolio process to make decisions. * Standards and controls that people follow, without excess process, * Happy to build in an imperfect environment: set direction when demand is competing, get hands-on where needed, and put foundations in before scaling. * Own the change agenda end to end: engagement through to benefits. * Enough governance to make safe investment and delivery decisions. No more than that. * Explain portfolio choices to executives in terms of outcomes, capacity and benefits. * Show progress through clearer priorities, more reliable delivery, better adoption and tracked benefits. ## Related Videos - [How Visionary Leaders Drive Transformation](https://www.wearedevelopers.com/videos/1701-how-visionary-leaders-drive-transformation) - [Excellent Software Testing](https://www.wearedevelopers.com/videos/87-excellent-software-testing) - [Data Governance in the Era of AI](https://www.wearedevelopers.com/videos/1622-data-governance-in-the-era-of-ai) - [The user in the eye of the Cargo1492 storm](https://www.wearedevelopers.com/videos/96-the-user-in-the-eye-of-the-cargo1492-storm) - [Dirty Tests And How To Clean Them](https://www.wearedevelopers.com/videos/515-dirty-tests-and-how-to-clean-them) - [AI beyond the code: Master your organisational AI implementation.](https://www.wearedevelopers.com/videos/1248-ai-beyond-the-code-master-your-organisational-ai-implementation) ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Best Companies to work for in London: Top 25 Companies in 2023](https://www.wearedevelopers.com/magazine/187-best-companies-to-work-for-in-london-top-25-companies-in-2023) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [UK Business Culture and Etiquette](https://www.wearedevelopers.com/magazine/326-uk-business-culture-and-etiquette) - [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed) - [Best US AI Conferences for CTOs in 2026: Build vs. Buy, Vendor Evaluation, and Peer Intelligence](https://www.wearedevelopers.com/magazine/736-best-us-ai-conferences-for-ctos-in-2026-build-vs-buy-vendor-evaluation-and-peer-intelligence)