The People Side of Delivery
Step 2 of the CMBOK journey: how change management and project management relate as disciplines, where organizational change ends and individual change begins, the five types of organizational change, and the five roles that actually make a change stick.
Organizational & Individual Change
Every change happens on two levels at once. The organization can approve a change on paper — a new process, a new structure — while the individuals inside it are still working out what it means for them personally. A project manager who only tracks the organizational side is only watching half the change.
- Cultural attributes — could support or block change.
- Prioritization of initiatives — monitor change fatigue & saturation.
- Build change agility.
- Shared vision & strategic reasons for the change.
- New/modified business processes, policies, rewards, performance indicators & procedures.
- Structure & role needed to support & reinforce change.
- Unique perspective, biases, motivation, behaviours, mindset, resistance to change.
- Willingness, ability, knowledge, skills & time necessary to transition to the future state.
- Sponsorship & active leadership needed to ensure successful change.
- Individual coaching through personal transition.
Do not assume that organizational agreement automatically means individual adoption. An organization can approve a change while individuals still struggle to understand it, accept it, or perform successfully in the future state.
Relationship Between Change & Project Management
Reason for change feeds two parallel tracks, each moving Current State → Transition State → Future State: the technical side (project delivery) and the people side (change management). One more way to see the same idea:
Roles & Responsibilities
- Application of skills, tools & techniques on activities needed to DELIVER change.
- Within budget, timeline, scope & quality requirements.
- Delivering solutions, results, outcomes.
- Application of skills, tools & techniques on activities needed to IMPLEMENT & SUSTAIN the planned change.
- Influencing behaviour, culture & facilitating new ways of working.
Keep the scope and focus clearly defined
The scope & focus of these two disciplines should be clearly defined. Overlap/interdependency should be identified & documented. Define how to manage information sharing & decision making between the two.
Methodology & Plan
- Org. & mgmt of resources & activities required to complete the project (delivering the change).
- Specific start & end date.
- Sponsorship & active leadership needed to ensure successful change.
- Focuses on the people side of change.
- Preparing the organization for the delivered change; facilitating transition from the old ways of working to the future state.
- Goal usually continues long after the project is closed.
They should be integrated — the right amount of attention given to both. Plan should be integrated into one comprehensive delivery plan. Project milestones & change activities trigger one another.
Tools & Resources
- Technical resources & SMEs.
- Tools for tracking budget, scope & time.
- Tools for monitoring performance & delivery quality.
- People managers, communication experts.
- Tools for communication, feedback collection.
- Tools for monitoring adoption, knowledge, skills & motivation.
Where common tools exist they should be integrated to increase efficiency. Resource sharing should be done (people, hardware, software) — integrating & sharing resources increases collaboration.
Objectives & Outcomes, and Risk
- Deliver the planned change (scope).
- Deliver predefined goals & objectives.
- Ensures the adoption of delivered change.
- Ensures long-term realization of goals & objectives.
Common objective for both is to add value to the organization. They are uniquely contributing to the realization of benefits.
Risk
- Risks related to delivery of the project goals, objectives.
- Focus on scope, time, cost & quality.
- Risks related to adoption of change.
- Threats to the realization of the expected benefits; risks & threats to making the change.
Integrate the risk views
Change management could have interest in project-related risks. Change management can support mitigating project risks & vice versa. Integrated risk management will lower the overall risk impact & probability.
Types of Organizational Change
Before deciding how to manage a change, it helps to know what is initiating or triggering it — internally triggered, or externally triggered from the market. Five recurring types of organizational change:
- Restructuring
Changing organizational structure & reporting lines. - Reengineering
Changing processes, the way work is done. - Mergers & Acquisition
Changing the identities of the organization. - Strategy Change
Changing priorities, ultimate direction & purpose. - Cultural Change
Changing values, attributes & behaviours.
Roles & Responsibilities
Five roles show up again and again in any change effort — each with a different kind of authority, and a different job to do.
Sponsor
Responsible for: accountable for realization of benefits; ultimate decision-making & funding authority. Defines and champions the change goals, scope & definition of success.
Main duties: securing resources; influencing peers & senior leaders; building a coalition; providing leadership; removing obstacles.
Change Management Lead
Responsible for: developing the overall change strategy & vision. Key role in decision making, setting priorities, aligning change with org. strategic objectives.
Main duties: assess the change, define the change plan & implement change management; direct day-to-day control over the change team, budget & resources; align with senior executives.
Change Management Practitioner
Responsible for: hands-on professional who implements the strategy & plans developed by change leaders. Not responsible or accountable for the change strategy.
Main duties: coordinating, applying & tracking change-management tools/activities; day-to-day execution — communication, training, stakeholder engagement.
Change Management Team
Responsible for: group that works together to deliver the change. Composition varies depending on the size & nature of the org.
Main duties: planning, implementing & managing the change. Usual members: change analyst, consultant, communication specialist, training specialist, stakeholder engagement specialist, project manager, continuous improvement specialist.
Change Agents
Responsible for: social leaders, middle managers, SMEs — trusted by colleagues, stakeholders & executives. Selected for their informal network & influence in the org.
Main duties: model the desired behaviour; provide feedback on change initiatives; communicate the vision & benefits; offer support for skill gaps; empower colleagues to take ownership.
Change Management & Organizational Change — Project Manager Mindset
A project manager should never think of change as “delivering a new solution.” The real objective is to move the organization from the current state through the transition state to the future state, and ultimately realize the intended value and benefits. Eight ideas that reframe the job accordingly.
The Big Picture
That requires two connected disciplines: Project Management — deliver the change (scope, schedule, cost, quality, resources, technical solution) — and Change Management — enable people to adopt and sustain the change (engagement, communication, knowledge, skills, motivation, behaviors).
A project is not successful simply because the solution was delivered. Success occurs when the solution is delivered AND the organization is prepared and able to adopt it so that the intended benefits can be realized.
1. Think “Delivery + Adoption,” Not “Delivery vs. Change”
Project management and change management have different primary focuses, but they are interdependent. The project delivers the solution. Change management enables people to use, adopt, and sustain it.
Project Management asks: what needs to be delivered? What is the scope? When must it be delivered? What resources and budget are required? How will quality be ensured? What technical risks could prevent delivery?
Change Management asks: who is affected by the change? Are people ready and willing to change? What new knowledge and skills are required? What resistance might occur? How will people be engaged and supported? How will the new way of working be reinforced?
PMP takeaway: when a scenario involves organizational change, look for an answer that connects the technical delivery with the people side of the transition. If the project delivers perfectly but nobody adopts the solution, the project has not achieved its full organizational value.
2. Integrate the Two Plans
Do not create a project plan and a change-management plan that operate as unrelated activities. They should be integrated into one comprehensive delivery approach, because project milestones and change activities can trigger one another:
- System development completed → training can begin
- Training completed → users can participate in readiness activities
- Go-live approaching → communication and stakeholder engagement intensify
- Go-live completed → hyper-care, feedback and adoption monitoring become important
Plan the technical transition and the human transition together. The objective is not to blur responsibilities — it is to ensure that the two disciplines work toward the same outcome.
3. Look at Change at Two Levels
A project manager must understand both the organizational impact and the individual impact.
Culture · strategic reasons for the change · shared vision · prioritization of initiatives · change fatigue and saturation · new or modified processes, policies and procedures · rewards and performance measures · structure and roles · change agility.
Perspectives and biases · motivation · mindset and behaviors · willingness to change · ability to transition · knowledge and skills · time and capacity · resistance · individual coaching and support.
Do not assume that organizational agreement automatically means individual adoption. An organization can approve a change while individuals still struggle to understand it, accept it, or perform successfully in the future state.
4. Keep Your Eye on Benefits and Value
Project management primarily focuses on delivering the planned change and achieving project objectives. Change management focuses on adoption and the continued realization of the intended goals and benefits. Both ultimately contribute to the same thing:
A project can be on time, within budget, within scope, and technically high quality — and still fail to deliver the expected organizational value if the change is not adopted.
Have we delivered the solution, or have we actually enabled the organization to realize the intended benefit? That question captures the mindset.
5. Treat Change Risk as Part of Overall Project Risk
Risk does not stop at project delivery.
Threats to: scope, schedule, cost, quality, project objectives, delivery.
Threats to: adoption, readiness, knowledge, skills, motivation, new behaviors, benefit realization.
These risks influence one another
Poor technical delivery → reduces confidence → increases resistance → reduces adoption → threatens benefits.
Poor stakeholder engagement → increases resistance → delays decisions/training/readiness → creates project delays → threatens delivery.
Think about the overall risk to project success — not just the risk to the project schedule or technical solution. Integrated risk management can reduce both the probability and impact of threats to successful change.
6. Understand the Source and Type of Change
Before deciding how to manage a change, understand what is triggering it. Change may be internally triggered or driven by external factors such as the market.
The nature of the change influences how you should think about its impacts, stakeholders, risks, communication, readiness and adoption.
7. Know Who Is Responsible for What
Do not automatically assume that the project manager owns every aspect of organizational change. Recognizing roles, authority and accountability is one of the most important mindset skills.
- Sponsor — accountable for benefits. Champions the change; defines the goals and vision; provides funding and authority; secures resources; builds the coalition of support; removes obstacles. Think: who has the authority and accountability to make this change succeed?
- Change Management Lead — leads the strategy. Develops the overall change strategy; aligns the change with organizational objectives; directs the change-management effort, team, resources and budget. Think: who is setting the direction for how the organization will transition?
- Change Management Practitioner — executes. Coordinates change activities; applies change-management tools; supports communication, training, and stakeholder engagement. Not accountable for the overall change strategy. Think: who is executing the change activities?
- Change Management Team — delivers the change work. Change analysts, consultants, communication specialists, training specialists, stakeholder engagement specialists, project managers, continuous improvement specialists. Think: what capabilities are required to make the change happen?
- Change Agents — influence & model. Trusted individuals with strong informal networks who model desired behaviors, communicate the vision, provide feedback, and empower colleagues to take ownership. Think: who has influence even without formal authority?
8. The Project Manager's Change Checklist
When you see a scenario involving organizational change, mentally walk through this sequence:
- Understand the why
Why is the organization changing? What strategic, internal or external factor is driving it? - Define the future state
What does success look like? What organizational outcome and benefits are expected? - Understand the impact
What changes for the organization and for individuals — processes, roles, culture, behaviors, knowledge and skills? - Identify the people
Who is affected? Who has authority? Who has influence? Sponsor, leaders, practitioners, team members, stakeholders, change agents. - Assess readiness & resistance
Are people willing and able to transition? Look for motivation, knowledge, skills, capacity, communication gaps and resistance. - Integrate delivery & change
What technical milestones and people activities depend on each other? Do not manage them as disconnected efforts. - Manage both types of risk
What could prevent delivery? What could prevent adoption? Consider the combined impact on project success and benefits. - Measure success beyond go-live
Was the solution delivered — and is it being used and adopted? Use → Adopt → Sustain → Realize Benefits.
The Golden Project Manager Mindset
Don't just deliver the change. Enable the change to succeed.
A strong project manager sees the project as more than scope + schedule + cost. The project manager connects:
When faced with a scenario, avoid thinking: “What action gets the project delivered fastest?” Instead ask: “What action best supports successful delivery, stakeholder adoption, sustainable change, risk management, and realization of the intended benefits?” That is the Project Manager Mindset.
Practice Quiz — 100 Questions, Live-Graded
100 questions, blending Step 1 and Step 2: 20 straight-recall, 20 PMI/PMP-style situational case questions, 10 multiple response (select all that apply), 10 fill-in-the-blank, 10 match-the-following, and 6 extended case studies with 5 questions each (30 total) — case-study project managers: Urjita, Nivedita, Ayushi, Kajal, Ayesha, Srini.
Every single-best-answer question has been checked so the correct answer's position rotates evenly across A/B/C/D and is never the conspicuously longest, most wordy option — so you can't guess from position or length. Questions marked Tough are the harder, more nuanced items (about 31% of the set).
Click an option (or fill in / match / check the boxes) to see it graded instantly, with the explanation underneath. Your running score for each section — and the total — updates live in the sidebar (or the 🏆 Scores button on mobile).
Before choosing an answer, ask yourself:
- What is the question really testing?
- Delivery or adoption?
- Technical problem or people problem?
- Current state, transition, or future state?
- Who is affected?
- Who has responsibility, authority, or accountability?
- Project risk or change/adoption risk?
- Organizational issue or individual issue?
- What is driving the change?
- Are project and change activities integrated?
- Does the solution actually get adopted and sustained?
- What happens to benefits and organizational value?
- Am I confusing delivery with success?
- Does the answer consider the bigger picture?
- Which option best supports delivery + adoption + benefits + value?
Section A — Straight Recall choose the single best answer
Section B — PMI/PMP-Style Situational Case Questions
Section C1 — Multiple Response select ALL that apply
Section C2 — Fill in the Blank
Section C3 — Match the Following
Section D — Extended Case Studies
Project Management vs. Change Management
Two disciplines · different focus · one successful change.
| Dimension | Project Management — Delivery | Change Management — Adoption |
|---|---|---|
| Primary focus | Deliver the planned change — the technical/project side. | Enable people to implement, adopt and sustain the planned change — the people side. |
| Core question | “What must we deliver, and how do we deliver it successfully?” | “How do we prepare and enable people to adopt and sustain it?” |
| Role in the change journey | Moves the organization from the current state → transition state → future state through solution delivery. | Moves people from the current state → transition state → future state through engagement, preparation and adoption. |
| Activities / methodology | Applies skills, tools and techniques to organize and manage the resources and activities required to complete the project. | Applies skills, tools and techniques to prepare the organization and facilitate transition from old ways of working to the future state. |
| Time horizon | Has a defined start and end date and generally concludes when the project is closed. | The adoption and sustainment objective can continue long after the project is closed. |
| Key constraints / measures | Scope · Schedule · Cost · Quality | Readiness · Adoption · Knowledge · Skills · Motivation · Behaviors |
| Resources & expertise | Technical resources, SMEs, project resources and delivery expertise. | People managers, communication experts, training and stakeholder-engagement expertise. |
| Tools | Tools for tracking budget, scope, schedule, performance and delivery quality. | Tools for communication, feedback, adoption, knowledge, skills and motivation. |
| Objectives & outcomes | Deliver the planned change, predefined goals, objectives, solutions, results and outcomes. | Ensure adoption of the delivered change and the long-term realization of goals and objectives. |
| Risk focus | Risks affecting delivery of project goals and objectives — particularly scope, time, cost and quality. | Risks affecting adoption and benefit realization, including threats to making the change successfully. |
| Contribution to benefits | Creates the solution and planned change that enables the intended benefits. | Enables people to use, adopt and sustain the change so benefits can be realized over time. |
| Ultimate objective | Deliver the change successfully. | Make the change work and last. |
| Shared objective | Add value to the organization and contribute to realization of benefits. | |