Chapter 36 — Field or community practice
Lesson map
Lesson 36 published. Map, example, EX106.
flowchart TD
N0["Learning outcomes"]
N1["36.1 Sessions"]
N2["36.2 Desk time"]
N3["36.3 Feedback"]
N4["36.4 Changes"]
N5["36.5 Boundaries"]
N6["Sustaining the work"]
N7["Budget"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX106"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["36.1 Sessions"]
N2["36.2 Desk time"]
N3["36.3 Feedback"]
N4["36.4 Changes"]
N5["36.5 Boundaries"]
N6["Sustaining the work"]
N7["Budget"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX106"]
[Learning outcomes]
|
v
[36.1 Sessions]
|
v
[36.2 Desk time]
|
v
[36.3 Feedback]
|
v
[36.4 Changes]
|
v
[36.5 Boundaries]
|
v
[Sustaining the work]
|
v
[Budget]
|
v
[Worked example] --> [Exercise EX106]
Learning outcomes
You will (1) support Bramley staff directly; (2) teach simple habits; (3) gather feedback.
36.1 Sessions
Aisha runs short sessions on locking screens, reporting lost devices and restart notices.
Each session lasts a few minutes at a team meeting and covers one habit with a Bramley example. Locking screens links to the screen-lock setting in the baseline; reporting lost devices links to the one-page procedure; restart notices link to the forced restart policy. Aisha ends each session by saying what staff should do, not what attackers might do. Aisha keeps each session short because staff attend during team meetings and have tenant visits to make afterwards.
36.2 Desk time
She spends two afternoons at Bramley answering questions.
The afternoons are spent in the office, where staff can ask about restart prompts, the request form or where to keep files. Most questions are about restarts and the new screen-lock delay. Aisha notes each question by topic, not by person, and passes recurring ones to Gareth as possible improvements. Questions she cannot answer, such as when a particular laptop will be replaced, are passed to Gareth the same day. She records how many questions each topic received across both afternoons.
36.3 Feedback
Staff ask for clearer restart messages.
Staff say the restart messages are hard to understand and do not say how long the restart will take. Several staff also ask why the restart prompt appears in the middle of meetings with tenants. Aisha records this feedback by theme and shares it with Gareth, who agrees it may explain some of the postponed restarts measured earlier. Aisha also asks staff what they do when a restart prompt appears, which helps explain why many postpone it.
36.4 Changes
Messages are rewritten.
The new restart message says in plain words what will happen, how long it takes and when the laptop will restart if postponed. Gareth changes the message on the management server, so all 45 laptops receive it at once. Aisha plans to compare the topics raised at her next desk afternoon with the first, to see whether restart questions fall. The rewritten message is tested on the five pilot laptops first, following the same staged approach as the other changes.
36.5 Boundaries
She does not access tenant data.
The agreement still applies during desk time: Aisha helps with settings and habits but never opens tenant files, even when a staff member offers to show her a problem. When a question needs a change to a laptop, she passes it to Gareth. Her notes record topics and counts only, with no names. If she sees tenant data on a screen during desk time, she looks away and does not record it. Gareth confirms these boundaries to staff before her first afternoon.
Sustaining the work
Projects often fade when the student leaves. To avoid this, Aisha hands over everything Bramley needs: the weekly routine, the labs as small scripts with instructions, the role documents, the recovery plan and the decision log. Each document names an owner and a review date.
She also runs two handover sessions, one with Gareth and one with the colleague who covers him. In each session, they perform the routine together while Aisha watches and answers questions. Small improvements to the instructions come out of these sessions.
Six weeks after handover, Aisha checks in: the routine has run every week, and one new laptop was correctly added and encrypted.
Budget
Ongoing costs are small: the existing management licences and staff time of about one hour a week.
Keeping documents alive
Documents are reviewed yearly or after any incident, whichever comes first.
Escalation
The contractor remains the escalation route for server problems.
Measuring sustainability
Aisha defines success after handover as the routine running at least three weeks in four and no unexplained inventory differences for a month. Both are met at the six-week check.
Project log entry
Community practice also means sharing. With the manager's approval, Aisha writes an anonymised two-page guide for other small housing associations on the routine and baseline, using only synthetic examples and no Bramley details that could identify systems.
Review with the tutor
Dr Grant asks how Bramley would notice if the routine quietly stopped. Aisha suggests the manager glances at the saved weekly checklists each month, a two-minute check that makes gaps visible.
Worked example
A staff member reports a lost USB stick; Aisha helps Gareth follow the incident process.
Synthetic case. Synthetic.
Errors and limits
Training without follow-up fades.
Exercises
- EX106 — Topics. What did sessions cover? Rubric: 3 = screen lock, reporting lost devices, restarts; 2 = two; 1 = one; 0 = none.
- EX107 — Feedback. What did staff ask for? Rubric: 3 = clearer restart messages; 2 = partial; 1 = vague; 0 = none.
- EX108 — USB event. What did Aisha do about the lost USB stick? Rubric: 3 = helped Gareth follow incident process; 2 = partial; 1 = vague; 0 = none.
Synthesis
Community practice builds habits.
Continue studying — chapter 36 of 40
← Chapter 35 (draft) · Course chapter index · Chapter 37 (draft) →