Regular progress and performance meetings are a change-management intervention in governance, planning, and operating model design. Their purpose is not to “keep executives informed” in a passive way. Their purpose is to create a practical leadership rhythm where adoption risks are visible, decisions are made quickly, blockers are removed, and sponsors know what they must do next. PMI describes project governance as including roles, responsibilities, meetings, reporting, risk and issue management, assurance, and control processes [PMI, 2015]. (pmi.org)

This matters because adoption problems often appear first as weak signals: managers delaying briefings, employees not attending training, business units interpreting the change differently, or leaders sending mixed messages. Prosci recommends measuring change through change management performance, individual adoption, and organizational performance, including speed of adoption, ultimate utilization, and proficiency [Prosci]. (prosci.com) A frequent review forum gives leaders a way to act on those signals before they become resistance, rework, or benefit leakage.

This action establishes a recurring leadership review cadence for the change. It usually includes a senior sponsor or sponsor coalition, business owners, the project or product lead, the change manager, and representatives for communications, training, HR, operations, and impacted groups. It works best when it has documented decision rights, a standard dashboard, a short agenda, and a follow-up mechanism.

Use it when the change is cross-functional, politically sensitive, high impact, adoption-dependent, fast moving, or at risk of losing leadership attention. McKinsey describes transformation performance infrastructure as combining people, process, and tools, including a weekly meeting cadence and common tools to gauge progress and results [McKinsey, 2016]. (mckinsey.com) BCG similarly recommends common processes, tools, reporting cadence, and steering committee decision-making in transformation offices [BCG, 2024]. (bcg.com)

Before launching the cadence, clarify what the meeting is allowed to decide. Practical decisions may include approving adoption interventions, reallocating resources, resolving manager resistance, sequencing go-live by business unit, approving communications, or escalating policy and process conflicts. ACMP defines governance as decision-making processes for approving, monitoring, and adjusting change management plan activities [ACMP, 2025]. (acmpmexico.org)

The change manager should prepare a concise dashboard covering solution progress, readiness, stakeholder sentiment, adoption risks, training completion, manager activation, resistance themes, open decisions, and benefits indicators. Include a decision log, action log, RAID log, sponsor activity plan, and upcoming engagement milestones. The cadence should be weekly during design, testing, deployment, and early adoption for high-risk changes; biweekly or monthly may be enough for lower-risk or later sustainment phases. Avoid adding meetings without removing duplicate forums, because MIT Sloan warns that meeting overload can reduce collaboration and focus [MIT Sloan Management Review, 2025]. (sloanreview.mit.edu)

First, charter the forum. State that the meeting exists to protect adoption and benefits, not to replay project status. Confirm membership, chair, quorum, decision rights, escalation rules, and what information must be submitted in advance.

Second, define the measures. Separate delivery measures from adoption measures. Delivery measures show whether the solution is being built and implemented. Adoption measures show whether people are ready, willing, able, and actually using the change. Prosci’s adoption measures of speed, utilization, and proficiency are useful anchors [Prosci]. (prosci.com)

Third, design the agenda around decisions. A practical 45-minute meeting should spend only a few minutes on status. Most time should focus on exceptions, adoption risks, leader actions, decisions needed, and commitments for the next cycle. MIT Sloan recommends being deliberate about meeting purpose, attendees, content, timing, place, and method [MIT Sloan Management Review, 2025]. (sloanreview.mit.edu)

Fourth, facilitate for evidence and candor. Ask, “What are impacted groups doing differently this week?” “Where are managers not yet confident?” “Which decision is slowing adoption?” and “What do we need from the sponsor before the next meeting?” If resistance is high, invite local leaders or change champions to present facts, not filtered optimism.

Fifth, close the loop. End every meeting with decisions made, actions assigned, owners, dates, escalation items, and messages leaders must cascade. Send the action log within 24 hours and open the next meeting by reviewing completion.

A company implementing a new CRM for 3,000 sales and service employees creates a weekly change governance review for the eight weeks before go-live and the first six weeks after go-live. The sponsor chairs it. The sales operations lead reports solution readiness, the change manager reports adoption readiness, and regional leaders report manager activation.

In week three, the dashboard shows strong training attendance but weak manager confidence in two regions. The group decides to pause a nonessential feature, add manager coaching sessions, and ask the chief revenue officer to explain why pipeline discipline matters in the next sales leadership call. This is the action working as intended: the meeting converts adoption evidence into leadership decisions and visible sponsor behavior.

Do not let the meeting become a passive status broadcast. Do not rely only on green project milestones when adoption data is amber or red. Do not invite every interested stakeholder; invite those who can interpret evidence or make decisions. Do not hide resistance, because questions and dissent can reveal real adoption barriers. Do not create a new meeting if an existing executive forum can be adapted with the right agenda, data, and decision rights. Prosci advises change managers to support sponsors with roadmaps, talking points, meetings, and visible engagement opportunities [Prosci, 2025]. (prosci.com)

The cadence is working when decisions are faster, actions close on time, adoption risks are raised earlier, and leaders can explain both solution progress and people readiness. Useful indicators include action closure rate, decision cycle time, number of unresolved escalations, sponsor actions completed, manager briefing completion, training attendance, readiness scores, usage rates, proficiency evidence, resistance themes, support tickets, process compliance, and benefit-leading indicators. BCG notes that effective transformation routines use tools, milestone tracking, portfolio visibility, and executive follow-up to reinforce accountability [BCG, 2024]. (bcg.com)

45-minute change progress and adoption review

Opening, 3 minutes: “The purpose of today’s review is to protect adoption and benefits. We will focus on exceptions, decisions, and leader actions.”

Progress and readiness, 10 minutes: Review solution milestones, readiness, adoption metrics, and stakeholder sentiment.

Risks and blockers, 12 minutes: Discuss the top three adoption risks, root causes, and decisions required.

Sponsor and leader actions, 8 minutes: Confirm what senior leaders and managers must say, do, model, or decide before the next meeting.

Decisions and trade-offs, 8 minutes: Make decisions or escalate with owner and deadline.

Close, 4 minutes: Confirm action log, communications to cascade, and next review focus.