Project management and change management are sometimes treated as neighbouring disciplines. The project team manages scope, schedule, cost, risks and outputs. The change team manages impacts, engagement, communication, learning and adoption. Both teams can be busy, competent and well intentioned—and still create a gap between a delivered product and a changed organisation.
The problem is not that the disciplines are different. Their difference is valuable. The problem appears when they operate to separate definitions of success, separate plans and separate reporting rhythms. The organisation does not experience a project plan and a change plan. It experiences one change to its work, customers, priorities and capacity.
Two disciplines, one business outcome
Project management creates the structure needed to deliver a defined output: decisions, resources, dependencies, quality controls and a route through uncertainty. Change management focuses on the people who must understand, use and sustain that output. It examines what will be different in their work, what may help or hinder adoption and what support leaders and managers need to provide.
Neither discipline is a substitute for the other. A well-engaged workforce cannot compensate for an unreliable product. A technically sound product cannot realise its benefits if people cannot or do not use it in the intended way. The combination becomes powerful when delivery and adoption are managed as connected conditions for the same result.
Agree what success means before planning activity
A shared plan begins with a shared definition of success. “Go live on 1 March” is a delivery event, not a complete outcome. Ask what needs to be working differently after go-live, for whom, to what standard and by when. Include operational performance and customer experience as well as technical acceptance.
This changes the conversation. The project manager can identify the products and dependencies needed to enable the outcome. The change manager can define the adoption, capability and leadership conditions needed to use them. Operations can describe the service levels, exceptions and workload that must remain manageable while the organisation makes the transition.
Build one integrated plan
An integrated plan does not mean forcing every activity into one enormous spreadsheet. It means making the dependencies visible. A process cannot be taught before it is stable enough to explain. Managers cannot brief their teams before key decisions are made. A pilot cannot provide useful evidence unless participants, measures and support arrangements are ready.
Place important change activities beside the delivery milestones they depend on. Link impact assessment to design decisions, manager preparation to confirmed role expectations, learning materials to tested processes and early-life support to the actual pattern of operational risk. When a delivery date moves, the adoption consequences should move with it rather than being compressed into the remaining time.
Use shared milestones and readiness evidence
Project plans often use milestones for design approval, testing, deployment and closure. Add evidence that shows whether the organisation is becoming ready to use what is being delivered. This could include agreed future processes, named local owners, manager confidence, completed role-based learning, support capacity and successful use in a representative pilot.
Readiness should not become a vague traffic light chosen shortly before launch. Define the evidence early, assign owners and agree what happens if the evidence is missing. That gives sponsors a more honest choice between proceeding, narrowing scope, changing sequence or adding support.
Maintain one view of risks, issues and decisions
Separate logs can hide connected problems. A technical delay may reduce training time. A policy decision may change a workflow that has already been communicated. Low manager availability may threaten both testing and team preparation. These are not purely project risks or change risks; they are risks to the business outcome.
Use one joined-up conversation even if specialist teams keep working records. Show the cause, the delivery effect, the people effect, the operational consequence and the decision required. This makes escalation more useful because leaders can see the whole trade-off instead of receiving two partial accounts.
Make operational capacity part of the baseline
Project and change activity both draw on the same people who run the organisation. Subject-matter experts attend design sessions and testing. Managers join briefings, coach individuals and handle questions. Teams learn new tasks while continuing to meet customer and service commitments.
Treat that effort as real work. Estimate it, sequence it and protect it where possible. If several initiatives need the same group, look across the portfolio. A plan that assumes unlimited attention may look efficient on paper while creating rework, missed learning and declining service performance in practice.
Bring communications closer to delivery decisions
Communication is stronger when it explains decisions that matter to the audience: what is changing in their work, why the sequence has been chosen, what is still uncertain and where feedback will influence the outcome. That requires close contact with delivery, not a late request to announce the launch.
Change insight improves project communication by identifying different audiences, concerns and local contexts. Project discipline improves change communication by providing decision dates, dependencies, ownership and a reliable source of truth. Together they reduce both premature promises and last-minute silence.
Measure delivery and adoption together
Completion measures tell us whether products were delivered. Adoption measures tell us whether people are using them sufficiently and proficiently. Operational and benefit measures tell us whether the new way of working is producing the intended result. Sponsors need all three.
Choose a small set of measures that connect the chain: an output is available, the relevant group uses it, performance changes and the expected benefit begins to appear. If adoption is low, investigate the reason rather than labelling it resistance. The problem may be usability, workload, unclear ownership, weak management support or a product that does not fit the work.
A stronger partnership changes the quality of decisions
The most valuable combination is not a project manager who occasionally updates a change manager, or a change manager who adds communications to a finished plan. It is a working partnership that brings delivery evidence, people impact and operational reality into the same decisions from the start.
If you are shaping a change that needs this joined-up approach, I can help connect project management, change management, internal communication and operations into one proportionate delivery model. I work in interim, consultancy, contract and longer-term settings across London, hybrid and onsite, with travel where required.
About Mark M Barton
I am a Change Management, Change/Internal Communications, and Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
