Chapter 36 — Field or community practice

Lesson map

Lesson 36 published. Map, example, EX106.

flowchart TD
  N0["Learning outcomes"]
  N1["36.1 Working within constraints"]
  N2["36.2 Communicating with staff"]
  N3["36.3 Reflecting on practice"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX106"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["36.1 Working within constraints"]
  N2["36.2 Communicating with staff"]
  N3["36.3 Reflecting on practice"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX106"]

[Learning outcomes]
    |
    v
[36.1 Working within constraints]
    |
    v
[36.2 Communicating with staff]
    |
    v
[36.3 Reflecting on practice]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX106]

Learning outcomes

You will (1) work within a real organisation's constraints; (2) communicate with non-technical staff; (3) reflect on practice.

36.1 Working within constraints

Sofia spends a term working two days a week with the cooperative. She learns its constraints: limited money, volunteers with changing availability, an old office computer and a board that meets monthly. She adapts. Documentation is kept short and printed, meetings are scheduled around the shop's busy hours and changes are bundled into the monthly board meeting rather than requested ad hoc. She learns that security in a small organisation succeeds when it respects these realities, and that recommendations ignoring them are politely accepted and then quietly forgotten by everyone involved.

36.2 Communicating with staff

The shop manager asks why the till sometimes shows a balance that differs from the member's wallet for a few seconds. Sofia explains that the till reads from a validator that may be one block behind, and that the difference resolves quickly. She suggests a small message on the till screen. Explaining in plain words, with an everyday comparison to a bank card payment showing as pending, builds trust. She keeps a list of questions staff ask and turns the most common into a one-page frequently asked questions sheet kept beside the till.

36.3 Reflecting on practice

Each week Sofia writes a short reflection: what happened, what she learned and what she would do differently. She notices that her early recommendations were too technical and that people engaged more when she began with the problem they experienced. She also reflects on ethical moments, such as declining to look at a member's transaction history out of curiosity. Reflection turns experience into lasting learning. Dr Asante reads the reflections monthly and comments on them, and they become part of her assessed portfolio for the field practice module.

Worked example

Sofia adapts to monthly board cycles, explains till lag with a pending-payment comparison and records weekly reflections.

Synthetic case. The placement and conversations are synthetic.

Errors and limits

Recommendations that ignore an organisation's constraints are accepted and then forgotten.

Exercises

• EX106 — Till difference. Why does the till briefly differ from the wallet?
  Show marking criteria

  Rubric: 3 = the validator may be one block behind;; 2 = lag;; 1 = theft;; 0 = none.
• EX107 — Explanation comparison. What everyday comparison does Sofia use?
  Show marking criteria

  Rubric: 3 = a bank card payment showing as pending;; 2 = pending payment;; 1 = a recipe;; 0 = none.
• EX108 — Reflection insight. What did reflection show about early recommendations?
  Show marking criteria

  Rubric: 3 = they were too technical;; 2 = too technical;; 1 = perfect;; 0 = none.

Synthesis

Respecting constraints, communicating plainly and reflecting turn practice into learning.

Continue studying — chapter 36 of 40

← Chapter 35 (draft) · Course chapter index · Chapter 37 (draft) →