Prosci puts the split plainly: project management handles the technical side of a change, change management handles the people side, and a change only succeeds when both are done well.
What each discipline owns
- Project management — scope, plan, budget, schedule, resources, risks and deliverables. Its question is: is the solution built and delivered as specified? Its bodies of knowledge are PMI's PMBOK and PRINCE2.
- Change management — sponsorship, communication, readiness, capability building, resistance and adoption. Its question is: are people willing and able to work the new way, and are they actually doing it? Its frameworks include Prosci/ADKAR and the ACMP Standard.
Why you need both
A project can hit every milestone and still fail to deliver value if the people side is neglected — the system goes live but staff quietly revert to the old way, and the benefits never materialise. Equally, enthusiasm for change without disciplined delivery produces motion without a finished solution. The return on a change investment comes from the two working in step: the project delivers the what, change management delivers the adoption that turns it into benefit.
How they work together
On a well-run programme the two are planned as one. Milestones on the project plan (design, build, go-live) each have matching change activities (readiness, communication, training, reinforcement). CCG's System7™ methodology was built to integrate change and project management in exactly this way — providing a single structure that maps, plans and risk-assesses both the technical and the human aspects of a programme, rather than treating them as separate workstreams.
Next step: need the people side planned alongside your project? Explore CCG Consult.
on