Change management skills help people understand a proposed change, identify its practical effects, learn a revised task and decide whether the change is ready to use. Announcing a new process is only one part of that work. A complete plan also needs clear ownership, a way to hear concerns, a bounded check and an authorised decision about what happens next.
This guide follows an original, fictional stock-record exercise. It includes a change brief, stakeholder questions, a training plan, an executed synthetic worksheet check and a proposed release decision. The organisation, people and quantities are invented. No real workplace has adopted this process or achieved a business improvement in this example.
Identify the task that would change
A fictional supplies team has six people who record movements of pens and notebooks. Its current process uses a paper movement record. The proposed change is to use a shared worksheet for a limited practice session. It does not replace the organisation's official records, alter purchasing authority or permit anyone to issue stock without the existing approval.
The supplied problem is narrow: the team wants to check whether a worksheet can make each movement and its status visible in one place. There is no measured error rate, time saving or evidence that the current staff resist technology. Those conclusions would require different information.
Write the scope before choosing a change model. For this exercise, the practice scope is two item types and nine supplied entries. The operational scope, access arrangements and permission to use real stock data are unresolved. A successful synthetic calculation cannot settle those questions.
Practise six connected skills
Clarify the purpose. Explain the problem being investigated and what the change would leave outside its scope. “Use this spreadsheet” is an instruction; “check whether this record makes unresolved movements visible” explains the exercise's purpose.
Identify affected people. The person entering a movement, the person approving it and the person reviewing balances may need different information. Do not assume everyone has the same device, access or responsibility.
Listen to concerns. A concern about accidental edits can reveal a record-control requirement. A concern about access can reveal a practical barrier. Record the question and the answer needed rather than classifying the speaker as unwilling to change.
Teach the revised task. Demonstrate one ordinary entry, one rejected entry and the route for asking a question. A training invitation does not establish that someone attended or can perform the task.
Check results within the agreed scope. Compare the exercise's output with independently calculated expectations. Keep unresolved entries visible rather than forcing the totals to look complete.
Maintain decision ownership. A team member may prepare a proposal, but the authorised supervisor decides whether the practice or rollout can proceed. Approval to practise is not approval to replace a production record.
Make communication useful to its reader
CIPD's public employee-communication introduction identifies line managers, dialogue, planning and tailoring communication as topics in its factsheet. The detailed factsheet requires member access and was not used here. The stock exercise and communication drafts below are independently written; they are not a CIPD tool or framework.
An original unsent briefing can read:
We propose a practice check of a shared stock worksheet using invented pen and notebook movements. The current official recording process would remain in place. Before the session, please identify any access or task questions. We need the supervisor to approve the practice scope and confirm who may enter and review records. The exercise will check accepted entries, held entries and balances; it will not establish a real-world time saving.
That draft names the purpose, boundaries and next decision. It does not claim a meeting occurred, permission was obtained or the worksheet is available to the team.
Turn stakeholder concerns into requirements
Suppose the exercise supplies three questions from fictional team members. One asks whether a repeated request could be recorded twice. Another asks what happens when an outgoing quantity exceeds stock. A third asks who can correct an entry.
| Question | Requirement to check |
|---|---|
| Repeated request | Retain a unique request identifier |
| Too much outgoing stock | Hold the request; retain the current balance |
| Entry correction | Define authorised review and change history |
The first two have explicit rules in the synthetic check below. The third remains an operational design question. The practice arithmetic does not implement access permissions or a correction history.
Maintain that distinction when reporting progress. “We identified a correction-control requirement” is supported. “The new process is secure” is not established by a balance worksheet.
Define the synthetic worksheet contract
Start with 20 pens and 10 notebooks. Process entries in the supplied order. A new incoming quantity increases the relevant balance. A new outgoing quantity is accepted only when enough stock is available. A repeated request identifier is held without applying the movement again.
All quantities in this exercise are positive whole numbers. The exercise supplies no returns, damaged items, transfers between locations or changes to previously accepted requests. Those cases need separate rules before they can be included.
The nine received entries are:
| Request | Supplied movement |
|---|---|
| T1 | Pens: outgoing 3 |
| T2 | Pens: incoming 5 |
| T3 | Notebooks: outgoing 4 |
| T4 | Notebooks: outgoing 8 |
| T5 | Pens: outgoing 2 |
| T6 | Pens: incoming 1 |
| T7 | Notebooks: incoming 3 |
| T8 | Notebooks: outgoing 2 |
| T5 repeated | Pens: outgoing 2 |
T4 is held because only six notebooks remain after T3. The final entry is held because T5 was already accepted. Neither held entry changes the balance.
Check the completed practice result
For pens, the accepted sequence is 20 − 3 + 5 − 2 + 1 = 21. The repeated T5 does not subtract another two. For notebooks, the accepted sequence is 10 − 4 + 3 − 2 = 7. T4's eight-item outgoing request is not applied.
The nine received entries therefore produce seven accepted entries and two held entries, with final balances of 21 pens and seven notebooks. The two held cases have different reasons: insufficient stock and a repeated identifier.
These calculations were independently executed as a synthetic check. They establish the answer for this supplied sequence and contract. No shared application, permission system, staff training, operational deployment or real-stock reconciliation was performed.
A complete exercise report can state the inputs, rules, expected balances and two exception reasons. It should also state the untested cases. That gives the supervisor something concrete to review without presenting a toy calculation as an implemented business system.
Plan training and a bounded pilot
A proposed training session would show the current and proposed record side by side. Use T1 to demonstrate an ordinary accepted movement, T4 to demonstrate a hold and the repeated T5 to demonstrate duplicate handling. Ask each participant to explain which balance remains unchanged and why.
Keep attendance, demonstrated understanding and operational permission as separate records. Six team members exist in the fixture, but no session has occurred. It would be inaccurate to report six trained users because the plan names six participants.
Before any real pilot, resolve who owns the worksheet, who approves movements, which records are official and how the existing process will be retained if the check fails. Obtain the relevant authorisation for actual data and access. Those are practical release questions, not answers supplied by this guide.
Set acceptance conditions before reviewing outcomes
For the synthetic exercise, acceptance means the supplied sequence produces the independently expected balances, duplicate handling and insufficient-stock hold. It also means the report preserves both exception reasons. Those conditions were checked.
For an operational pilot, the supervisor would need agreed conditions suited to the actual task. They might concern record completeness, user access or reconciled balances, but the organisation must define their meanings and evidence. Do not borrow the synthetic pass as an operational acceptance decision.
If a requirement remains unknown, keep the release decision open. A proposed correction-control rule can be documented without claiming it is implemented. A decision to revise the plan is a useful outcome of review, even when it delays rollout.
Describe your contribution honestly
A fictional practice contribution could read: “Prepared a bounded stock-workflow proposal, identified duplicate and insufficient-stock rules, and checked nine synthetic entries against expected balances. Kept correction authority and rollout approval unresolved.”
It cannot read: “Digitised stock management for six employees and reduced errors.” The exercise establishes neither employee adoption nor a comparison error rate.
When building your own evidence, retain the brief, questions, practice inputs, checks and decision record. Change management becomes concrete when another person can see the proposed task, its effects on people, the evidence collected and who can authorise the next step.