Lesson map
Lesson 38 published. Map, example, EX112.
flowchart TD
N0["Learning outcomes"]
N1["38.1 Building the pieces"]
N2["38.2 Distribution"]
N3["38.3 Adapting"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX112"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["38.1 Building the pieces"]
N2["38.2 Distribution"]
N3["38.3 Adapting"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX112"]
[Learning outcomes]
|
v
[38.1 Building the pieces]
|
v
[38.2 Distribution]
|
v
[38.3 Adapting]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX112]
Learning outcomes
You will (1) implement the volunteer guide and reporting route; (2) manage distribution; (3) adapt during implementation.
38.1 Building the pieces
Nadia writes the welcome guide for volunteers and part-time staff: what suspicious messages look like, the three questions to ask, how to report and a promise that reports are welcome and never lead to blame. IT builds a simple web form that anyone with a volunteer code can use from any device, sending reports to the shared mailbox. She tests the form with five volunteers, who find it easy, and fixes one confusing label before launch. The guide is two pages long.
38.2 Distribution
The guide is handed out by the volunteer coordinator at induction and sent by text message link to existing volunteers. Part-time staff receive it with their payslips. Nadia tracks distribution with a simple count of guides given out per branch rather than names. After four weeks, 31 of 40 volunteers and 18 of 22 part-time staff have received the guide, which meets her criterion of two thirds. Tracking by counts respects privacy while showing whether the guide reached people. The coordinator keeps the tally sheet up to date.
38.3 Adapting
During implementation, volunteers at one branch say they rarely check their phones during sessions, so the text link is ignored. Nadia arranges for printed guides to be left at that branch. IT notices that some form reports contain members' personal details, which volunteers included to explain context; the form is updated with a note asking people not to include personal data. Adapting during implementation is normal and is recorded, so that the final evaluation reflects what was actually done. Both changes are logged.
Worked example
Nadia builds a guide and web form, distributes them to 49 of 62 people and adapts for one branch and for personal data in reports.
Synthetic case. The implementation is synthetic.
Errors and limits
Counts do not show reading. Forms can be misused.
Exercises
- EX112 — Form access. How do volunteers access the form?
Show marking criteria
Rubric: 3 = with a volunteer code from any device;; 2 = code;; 1 = staff email;; 0 = none. - EX113 — Distribution share. What share of volunteers received the guide?
Show marking criteria
Rubric: 3 = 31 of 40, about 78%;; 2 = 78%;; 1 = vague;; 0 = none. - EX114 — Form change. Why was the form updated?
Show marking criteria
Rubric: 3 = reports included members' personal details;; 2 = privacy;; 1 = vague;; 0 = none.
Synthesis
Implementation builds, distributes and adapts, with each change recorded.
Continue studying — chapter 38 of 40
← Chapter 37 (draft) · Course chapter index · Chapter 39 (draft) →