Business, Projects and Management
Organisational change and transformation
Organisations are good at deciding to change and poor at changing. A new system, a restructure or a merger can be delivered on time and still fail if people keep working the old way. Organisational change management is the discipline of preparing, persuading and supporting people through a shift until the new way becomes normal. It runs alongside the project that delivers the change, not after it has finished.
Why this topic exists: Making a change stick in an organisation is its own discipline (SFIA Change planning: organisational change management and enablement; PMBOK's stakeholder and uncertainty domains).
Organisational change management deals with the human side of a move from one way of working to another. A project delivers the new system, structure or process; change management makes sure people are ready for it, able to use it and still using it once the project team has left. SFIA 9 divides the work in two. Organisational change management plans and runs the transition itself, with readiness assessments, communication plans and tracking of impact. Organisational change enablement works on the cultural and behavioural side, helping teams take up the new habits and keep them.
PMI's PMBOK Guide approaches the same ground from the project side. The stakeholder and uncertainty domains of its seventh edition ask a project manager to engage the people affected and to plan for outcomes nobody can predict with confidence. Neither framework prescribes a particular change model. Both treat the people affected as something the delivery plan must account for from the beginning, rather than an afterthought once the system works.
Why delivered change fails to stick
Resistance is rarely stubbornness. People resist change they do not understand, change that makes their work harder in the short run, and change that takes away something they valued, whether status, autonomy or a hard-won skill. Most change models, from Kotter's steps to Prosci's ADKAR, address those causes in order: explain why, build the desire to take part, teach the new way, support people while they practise and reinforce it until it becomes routine. In practice that means five things.
- Sponsorship. A senior leader who visibly owns the change and keeps asking about it after launch day.
- Impact analysis. Group by group, what exactly changes in their daily work.
- Communication. Early, repeated and two-way, carried by the managers people already trust.
- Training timed to use. Delivered close to go-live, not months before anyone can apply it.
- Reinforcement. Measures, recognition and retirement of the old way, so that reverting takes more effort than continuing.
The beginner's error and the neighbouring fields
The beginner's error is treating change management as a communications task scheduled for the final month: an announcement, a training session, a launch email. By then the design decisions that affect people most have been taken without them. Change work starts when the project starts and feeds back into it. Project change control is a smaller cousin with another job, approving changes to agreed scope, whereas this topic manages the change that scope delivers; stakeholder management is the skill both share. No single credential dominates the field. Practitioners usually arrive from project management, HR or leadership roles, and the work leans heavily on business communication. In technology programmes it pairs with business analysis, which defines what the future state has to do. Good change managers also know when to slow down: a readiness assessment showing that a group is not prepared is a reason to adjust the plan, not to push harder.
Next to this topic
- Project management fundamentalsCharter, scope, schedule, cost, risk and stakeholders: the predictive vocabulary of PMBOK 7's performance domains and the PMP ECO's Process domain, tested by CAPM, PMP, PRINCE2 and IPMA.
- Agile, Scrum and KanbanThree accountabilities, five events, three artefacts and the empirical pillars of the 2020 Scrum Guide; Kanban's flow; the PSM and PSPO exams and PMP's agile half.
- Business analysis and requirementsElicitation, requirements life cycle, strategy analysis, solution evaluation: BABOK v3's six knowledge areas, the discipline between the business and the build (SFIA Change analysis).
- Product managementDiscovery, roadmaps, prioritisation, metrics and the product owner's accountability: where business analysis, agile and strategy meet (Scrum Guide's Product Owner; SFIA Product management; PSPO).
- Leadership and people managementRunning a team: delegation, feedback, performance, hiring, motivation (SFIA People management; PMP's People domain; Udemy's largest business shelf).
- Business strategy and planningBusiness models, competitive position, planning and the numbers behind a decision (SFIA Strategic planning; Udemy Strategy; the business model canvas).
- Operations, Lean and Six SigmaProcesses, quality and waste: Lean, Six Sigma's DMAIC and the belts, supply chain and operations management (SFIA Business process improvement; Udemy Operations).
- Entrepreneurship and small businessStarting and running a small business: idea to model, funding, legal basics, first customers (Udemy Entrepreneurship; the site's own small-business and freelance readership).
- Sales and negotiationProspecting, discovery, closing, key accounts and negotiating: the revenue side of every business (Udemy Sales; SFIA Selling).
- Business communication and presentingWriting, presenting, meetings and public speaking: the skill every other business skill is delivered through (Udemy Communication; SFIA Relationships and engagement).
- Freelancing and independent workBriefs, statements of work, day rates, retainers and scope creep: how independent work is scoped, priced and agreed (the site's freelancing concepts and the /freelance/ silo).
Concepts to know
Glossary entries with the reason each one matters here.
- Stakeholder Management
Change lands with people or not at all.
- Change Control
Project change control is the small cousin of organisational change.
Frequently asked
- What is the difference between change management and change control?
- Change control is a project mechanism for approving or rejecting changes to agreed scope, cost or schedule. Organisational change management helps people adopt what a project delivers. The words overlap while the jobs barely do, and IT service management uses the term in a third sense, for controlled changes to live systems.
- Is digital transformation just a bigger change programme?
- Largely, yes: several changes to technology, processes and roles at once, spread over years. What makes it harder is that the changes interact, fatigue sets in, and each new initiative meets people still absorbing the previous one.
- How can you tell that a change has stuck?
- When the old way has disappeared without anyone enforcing its absence. Measure use of the new process some months after go-live rather than on launch day, and look for workarounds that have grown up around it.
Courses in the directory
43 courses are filed here; the top 2 by our ranking, details and the provider link on each course page.
Last reviewed 26 September 2026 · Getting Digital