The One-Page That Changes Everything

A Practitioner’s Guide to the PM+CM Integration Reference

At the end of every session, I teach on PM and CM integration, I share one artifact; a single-page reference table that maps every phase of the project lifecycle across three columns: what PM owns, what CM owns, and what they share. No jargon. No framework complexity. One page, meant to be used on your next project, starting tomorrow.

The response is always the same: this is the thing we’ve been missing.

This article is the deeper version of that conversation, not just what the table says, but how to actually use it. The practitioner-level decisions, the common failure points at each phase, and the questions worth asking before you move forward.

Before You Start: The 30-Minute Conversation That Changes Everything

The action I give every audience is deceptively simple: before your next project starts, schedule 30 minutes with your PM or CM counterpart and walk through this table together.

That conversation is doing more work than it appears to. It is establishing that both roles exist and are valued. It is creating shared language before pressure is applied. It is surfacing assumptions about ownership before those assumptions cause conflict. And it is giving both practitioners a chance to agree, upfront, on what integration actually looks like in this project, not in theory.

If you don’t have a PM or CM counterpart yet, that’s the first thing to surface. Use this conversation as the prompt to make the case for the resource you need.

Initiate: Where the Partnership Has to Begin

PM owns: Charter, scope, stakeholder register

CM owns: CM strategy, sponsor brief

Shared: Combined stakeholder register | Change risk in charter

The initiate phase is where the biggest gap exists in most organizations and closing it is where the highest leverage is. When CM is brought in at Initiate, the charter changes structurally. Change risk gets named alongside technical risk. Adoption metrics get defined alongside delivery metrics.

The combined stakeholder register is the most practical deliverable at this phase. Instead of PM maintaining a register of technical stakeholders and CM maintaining a separate impact assessment, you produce one document that captures both; who is affected, how significantly, what their current posture is, and what they need to be ready.

The question to ask at Initiate: Has CM had a seat at the table before scope hardened or are they being asked to wrap around decisions that have already been made?

Plan: Where Shared Artifacts Are Built

PM owns: WBS, schedule, budget

CM owns: Readiness assessment, communications plan

Shared: Integrated PM+CM plan | Adoption metrics defined

Planning is where the partnership either gets real or gets theoretical. The training schedule cannot be designed without reference to the project schedule. The communications timeline cannot be built without knowing when key milestones occur. These are interdependent from the start, not separate workstreams stitched together at the end.

The most important shared deliverable at Plan is the adoption metrics definition. What does 80% adoption look like? Who measures it? When? Who owns the measurement after the project closes? These decisions made at planning are what make post-implementation accountability possible.

The question to ask at Plan: If I removed either the PM or CM from the planning process right now, would the plan fall apart? If not, we’re not integrated yet.

Execute: Where Integration Is Tested

PM owns: Build, test, issue tracking

CM owns: Training design and delivery, communications execution, resistance management

Shared: Shared status report | Training tied to go-live date

Execute is where the quality of your planning becomes visible and where the temptation to de-prioritize change management work is highest. When go-live pressure builds, training gets compressed. Communications get simplified. Resistance management gets deferred.

The shared status report is the single most practical integration tool at this phase. Instead of PM producing a delivery status report and CM producing a separate readiness report, sometimes with different narratives for the same leadership audience, one integrated report carries both. When leadership sees delivery progress and adoption readiness in the same view, they make better decisions.

Unaddressed resistance is a technical risk. It creates workarounds, which create data integrity problems, which create audit findings, which create cost. Name resistance by stakeholder group. Assign accountability. Track it.

The question to ask at Execute: Is change management work being treated as a parallel workstream or as an integrated part of how this project delivers?

Monitor: Where Adoption Becomes Visible

PM owns: Scope control, schedule performance, risk tracking

CM owns: Adoption tracking, feedback loops, adjustment planning

Shared: Combined risk register | Readiness dashboard

Monitor is the phase that most change frameworks underinvest in and it’s the phase where the difference between sustained change and regression is determined.

The combined risk register makes PM and CM partners in risk management rather than parallel risk managers. People risk and technical risk in the same register, with shared escalation paths, means that when a key department head signals resistance, it shows up in the same view as a schedule slippage. The readiness dashboard, the CM equivalent of an earned value report gives leadership a real-time picture of where adoption stands relative to where it needs to be at go-live.

The question to ask at Monitor: If adoption were falling behind right now, would leadership know? Would they know in time to do something about it?

Close: Where Most Changes Die

PM owns: Final delivery, lessons learned

CM owns: Reinforcement plan, value realization check

Shared: Shared close checklist | Reinforcement owner named

Close is the most under designed phase in change management and the one that determines whether everything that came before it produces lasting value.

Two things must happen before anyone walks out the door:

The reinforcement plan must exist and be owned. Not drafted and filed, actively owned by a named individual with authority and accountability. The plan should specify what behaviors are at risk of regression, what signals will indicate regression is occurring, what interventions are available, and a calendar of 30-, 60-, and 90-day adoption checks.

The value realization check must be scheduled. If the business case promised savings, cycle time reduction, or satisfaction improvements, someone needs to be accountable for measuring whether those outcomes materialized, at a defined point in time. That measurement must be designed, scheduled, and owned before the project team is released.

The question to ask at Close: If we walked away today, who would carry this forward? If the answer is ‘nobody’ or ‘I’m not sure,’ the project isn’t done.

Using the Reference in Practice

The table is a starting point, not a finish line. Every project will require adaptations based on scale, complexity, organizational culture, and the maturity of the PM+CM partnership.

What doesn’t change is the underlying principle: integration is not about more documents, more meetings, or more process. It’s about shared ownership of the full outcome; delivery, adoption, and sustained value from the first conversation to the last.

Thirty minutes with your counterpart, a shared table, and an honest conversation about who owns what. That’s where integration starts. And it’s where the change begins to have a real chance of succeeding.