Change management is the discipline of handling changes deliberately. A change may be a new process, revised document, software update, supplier change, pricing change, scope change, policy update, or operational adjustment.
The purpose is not to slow every decision down. The purpose is to make important changes visible enough that people understand what is changing, why it matters, who approved it, and what needs to happen next.
A simple change process includes a request, reason, impact review, decision, rollout plan, communication, and follow-up check. For small changes, this can be lightweight. For high-impact changes, the process may need more evidence and approval.
Good change records answer practical questions later. What was the old state? What changed? Who reviewed the risk? Which files, tasks, training, customers, suppliers, or deadlines were affected? Did the change work as intended?
A change process can combine change notes, a register, rollout actions, implementation dates, approved records, and a process map. Keeping those elements connected is often more important than making the process heavy.
Related: Approval Workflows, TaskBoard (WSO ↗), WorkFlow (WSO ↗).