Chapter 17 — Placement project: changes and results
Lesson map
Lesson 17 published. Map, example, EX065.
flowchart TD
N0["Learning outcomes"]
N1["17.1 Changes"]
N2["17.2 Results"]
N3["17.3 Remaining"]
N4["17.4 Staff reaction"]
N5["Talking to each user"]
N6["Checking results honestly"]
N7["Follow-up check and cost"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX065"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["17.1 Changes"]
N2["17.2 Results"]
N3["17.3 Remaining"]
N4["17.4 Staff reaction"]
N5["Talking to each user"]
N6["Checking results honestly"]
N7["Follow-up check and cost"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX065"]
[Learning outcomes]
|
v
[17.1 Changes]
|
v
[17.2 Results]
|
v
[17.3 Remaining]
|
v
[17.4 Staff reaction]
|
v
[Talking to each user]
|
v
[Checking results honestly]
|
v
[Follow-up check and cost]
|
v
[Worked example] --> [Exercise EX065]
Learning outcomes
You will (1) make changes safely; (2) re-measure; (3) report.
17.1 Changes
Extra admin rights are removed after talking to each user, and the self-service catalogue is introduced. Update failures are fixed as in chapter 5. Talking to each user first means nobody loses software they need without warning. The self-service catalogue gives them a way to install approved tools without admin rights. Fixing update failures follows the causes found earlier: spares started weekly, disks cleaned, the broken service repaired and the partner's laptop set to update when it connects. Nadia records each change in the change log with the user consulted, so a later complaint about lost rights can be traced to its decision.
17.2 Results
Extra admins fall from 12 to 0 PCs; updates within 14 days rise from 25 to 29 of 30. Nadia measures again with the same exports and method as before, so the figures can be compared directly. The admin result is complete, since every extra administrator was removed after checking with the user. The update result is close to complete; the one remaining PC is explained. She presents both with the before figures in a simple table, with the export dates. Lena signs the results table, which confirms that the firm accepts the figures as its own record of the change.
17.3 Remaining
One PC stays late because it is a partner's laptop often off; a reminder is set. The partner's laptop is often off for days, so it misses update deadlines even with automatic updates set. A reminder asks the partner to leave it connected overnight once a week. Nadia records the laptop as a known gap rather than a failure of the project, and the supplier checks its status each month. If the reminder does not work, the supplier will contact the partner directly.
17.4 Staff reaction
Most staff did not notice the change; two asked for software via the catalogue. The quiet reaction suggests the change caused little disruption, which matters for keeping it in place. The two catalogue requests show staff found the new way to get software. Nadia asked a few staff directly whether anything had become harder, and nobody reported a problem. She records the reaction in her report, without names, and notes that it covers only the first weeks. Lena agrees, adding that she had expected complaints about losing admin rights and received none in the first weeks.
Talking to each user
Before removing admin rights, Nadia speaks to each of the affected staff. She asks what they use admin rights for, checks those tools are in the catalogue and explains the change. Most used rights only for printer drivers, which the supplier now deploys automatically.
One partner asks to keep rights; Lena decides that partners follow the same rule, and the partner is given a separate admin account held by the supplier for rare needs.
These conversations took about fifteen minutes each and avoided every complaint that Lena had expected.
Checking results honestly
Nadia re-measures with the same exports and steps. She notes that update results can vary month to month, so she will check again next month. She also notes that admin rights could creep back if the supplier grants them for quick fixes, which is why the quarterly check matters.
The report shows both measures with counts, dates and a short explanation of the remaining late PC.
She sends the report to Sam and Lena together, so both readers see the same numbers and caveats.
Follow-up check and cost
One month after the changes, Nadia repeats both measures with the same exports and steps. Extra admin rights remain at zero and updates at twenty-nine of thirty, which suggests the changes are holding rather than being a one-off result. She also records the effort: about twelve hours of her time and four of the supplier's. Recording cost matters for a small firm, because partners decide whether to continue a practice by comparing effort with benefit. Here the effort was modest, and the ongoing quarterly check takes under an hour, which makes the case for continuing it straightforward.
Worked example
The report table shows before and after values.
Synthetic case. Figures are synthetic.
Errors and limits
Removing rights before the catalogue was ready would have caused complaints.
Exercises
- EX065 — Results. State both results. Rubric: 3 = 12→0 and 25→29;; 2 = one;; 1 = vague;; 0 = none.
- EX066 — Ordering. Why set up the catalogue first? Rubric: 3 = alternative before removal;; 2 = smoother;; 1 = vague;; 0 = none.
- EX067 — Remaining PC. How is the remaining late PC handled? Rubric: 3 = reminder;; 2 = followed;; 1 = ignored;; 0 = none.
- EX068 — Reaction. What did staff reaction suggest? Rubric: 3 = low disruption;; 2 = fine;; 1 = vague;; 0 = none.
Synthesis
Small careful changes produced clear measured improvements.
Continue studying — chapter 17 of 18
← Chapter 16 (draft) · Course chapter index · Chapter 18 (draft) →