From Field Notes to Staff Development, Without Surveillance

The notes already exist. The picture does not.

Walk into almost any hospital ward, school, call centre or field team and you will find someone writing notes about how people work. A coordinator records a visit. A coach jots down what happened during a shift. A supervisor writes a line after a difficult conversation with a client.

These notes are some of the most honest information an organisation has about its frontline staff. They are written close to the work, by people who saw it. Yet they rarely become anything. They sit in notebooks, chat threads and shared folders. Six months later, when someone asks how a person has grown, the answer comes from memory and impression.

Nobody is short of observation. What is missing is the step that turns it into evidence.

We design Reflection around the coordinator as a living model. Coordinators remind colleagues of the right practice through how they speak and how they work, with them and in front of them. Their notes are the trace of that work. When the notes go nowhere, the work leaves no trace at all.

What research says about feedback and coaching

Feedback is powerful, in both directions. In their widely cited review, John Hattie and Helen Timperley describe feedback as one of the strongest influences on learning, but note that "this impact can be either positive or negative." They frame useful feedback around three questions: Where am I going? How am I going? Where to next? They also distinguish feedback about the task, the process, self-regulation and the self. Feedback aimed at the self, usually praise, is in their words "rarely effective."

Badly aimed feedback can make things worse. Avraham Kluger and Angelo DeNisi analysed 607 effect sizes from feedback interventions. On average feedback improved performance, but over one-third of the interventions decreased it. Their explanation: effects weaken as feedback draws attention away from the task and towards the self. A note that judges the person, rather than describing the work, risks exactly this.

Coaching changes practice. Matthew Kraft, David Blazar and Dylan Hogan pooled 60 studies of teacher coaching that used causal designs. They found an average effect of 0.49 standard deviations on instructional practice and 0.18 on student achievement. They also found that large programmes produced only a fraction of the effects of small ones. Coaching works, but it is hard to keep it working at scale.

Improvement comes from targeted practice. K. Anders Ericsson and colleagues linked expert performance to deliberate practice: "activities designed to improve performance," often set by a teacher between sessions. Later work by Brooke Macnamara and Megha Maitra found practice still mattered, though it explained less of the difference between performers than the original study reported. The useful lesson holds: growth comes from specific practice with feedback, not from general encouragement.

Behaviour depends on the situation. Walter Mischel and Yuichi Shoda showed that people behave in consistent patterns of the form "if this situation, then this behaviour," rather than identically everywhere. A nurse may be calm with an anxious family and rushed during handover. Both are true. A label like "good communicator" hides that.

Six principles for development without surveillance

The research adds up to six rules. They cost nothing except discipline.

• Observe behaviour, not personality. Write what the person did and said. Leave out traits such as "lazy," "confident" or "difficult." Traits draw attention to the self; behaviour keeps it on the task.
• Name the situation. "Handling a complaint at reception" or "first home visit with a new family" tells you where a skill shows up. Over time, the same situation observed several times becomes a fair comparison.
• Separate coaching from evaluation. If every note can affect pay or contracts, people stop taking risks and coaches stop writing honestly. Keep the development record for learning. Make formal evaluation a separate, explicit process.
• Show "not yet assessed" honestly. When there is no evidence for a skill, say so. Guessing a level from one remark, or from silence, invents a judgement no one actually made.
• The person sees their own record. A record written about someone but hidden from them is surveillance. A record they can read, question and add to is development.
• Humans decide. Software can sort, group and count notes. It should not judge people. Decisions about a person's level, role or future belong to people who know the work and can be held to account.

How to write a note that becomes evidence

A useful note answers four questions. It takes under a minute to write.

• Who. The person observed, named clearly so the note can be found later.
• Situation. Where and when, in words the team uses every day. Reuse the same names for recurring situations.
• What they did. Observable actions and words. No adjectives about character.
• What changed. The result, and the next step agreed. This is the "where to next" in Hattie and Timperley's model.

Compare two notes about the same moment.

"Sara was great with the patient today. Very caring."

"Sara, discharge explanation to an elderly patient. She used the medication chart, asked the patient to repeat the timing back, and corrected one error. Next: try the same with a family member present."

The first is kind but empty. It cannot be compared with anything. The second names a situation, records behaviour, and sets a next practice. Ten notes like it, written over three months, show whether Sara is growing in that situation, and where she is not yet tested.

Four habits make a note better. Write it the same day. Keep one note to one situation. Mention other colleagues only when they were part of the moment. Avoid health, family or private details that have nothing to do with the work.

From scattered notes to a picture of growth

Once notes share a structure, the picture almost builds itself. Group notes by person and by situation. Place them in time. For each situation, ask three questions. How many times was this observed? What changed between the first and the latest note? Who observed it?

Gaps matter as much as entries. If a frontline team has many notes about patient communication and none about handover, that does not prove handover is weak. It shows that no one has looked. An honest picture of staff growth shows those blanks openly, so coaches know where to spend their next visit.

Be careful with numbers. A count of notes measures how often someone was observed, not how good they are. Levels should come from a person reading the evidence and deciding, with the staff member able to see the reasoning.

How Reflection does this

Reflection is built on these principles. Coordinators and coaches keep writing the notes they already write. Each note is tied to a named situation, and each situation carries a level, where level 0 means not yet assessed rather than a low score. When a note mentions colleagues, fixed rules propose the names, and a person approves them before anything is linked. Staff can see their own record. Reflection organises the evidence; it never makes an automated judgement about a person.

Sources

1. The Power of Feedback. Review of Educational Research, 2007.
2. The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory. Psychological Bulletin, 1996.
3. The Effect of Teacher Coaching on Instruction and Achievement: A Meta-Analysis of the Causal Evidence. Review of Educational Research, 2018.
4. The Role of Deliberate Practice in the Acquisition of Expert Performance. Psychological Review, 1993.
5. The Role of Deliberate Practice in Expert Performance: Revisiting Ericsson, Krampe & Tesch-Römer (1993). Royal Society Open Science, 2019.
6. A Cognitive-Affective System Theory of Personality. Psychological Review, 1995.

Comments

Your nameYour comment

Comments appear after our team reads them. Please do not include patients' or colleagues' personal details.

Post comment