May 19, 2026
.png)
Most organizations run change governance through a single board. One body assesses the impact, decides whether to approve, and figures out how to implement. Assessment, decision, and implementation collapse into the same conversation, the same meeting, the same people.
Projects overrun budgets and schedules by 30 to 40% on average. A significant contributor? Change governance that blurs assessment, decision, and implementation into a single conversation, so that it is no longer clear where assessment ends and decision begins.
CM2 separates change governance into three distinct functions, each with documented operating standards. None of the three major industries (aerospace, automotive, and medical devices) does this explicitly.
The Enterprise Change Assessment (ECA) compiles the full impact picture before any board convenes. Which configurations are affected, what the downstream consequences look like, and what the technical and business implications are. Without a thorough ECA, the CRB makes decisions on incomplete information. With it, every stakeholder enters the review with a shared, traceable understanding of what the change actually touches.
The Change Review Board (CRB) handles technical governance and the approval decision. It evaluates whether a change is sound, assesses risk, and determines whether to proceed. The CRB maps to the CCB practices in aerospace and medical device contexts. Its quality depends entirely on the ECA. A CRB without a structured assessment is a room full of opinions.
The Change Implementation Board (CIB) handles cross-functional implementation governance. Representatives from every impacted activity prepare detailed plans and assign effectivity.
Three distinct questions. The ECA asks: “What is the impact of this change?” The CRB asks: “Should we implement this change?” and “What happens if we do not?” The CIB asks: “How, when, and where do we implement this change across all impacted baselines?”
Three different competencies, three different sets of people. The engineer compiling the impact assessment is not the executive weighing strategic risk, nor the resource manager who needs to commit to an implementation plan.
This aligns with a broader trajectory. EIA-649C placed greater emphasis on “Implementation Planning” than 649B, a subtle acknowledgment that approval without structured implementation creates risk, not resolution.
Does your organization separate assessment, decision, and implementation? Or does one board try to do all three?
Use code Martijn10 for 10% off training—and don’t forget to tell them Martijn sent you 😉.
Copyrights by the Institute for Process Excellence
This article was originally published on ipxhq.com & mdux.net.
