EN
Open notebook with cards showing person icons, surrounded by cups and papers on a table.

How to record observations without turning them into surveillance

Recording an observation can improve a development conversation. Recording everything, all the time, changes the relationship: it stops producing useful evidence and starts producing surveillance.

PRYSMAP5 min read

The difference does not depend only on the tool. A notebook can be used invasively, while a digital system can operate within clear limits. What matters is the purpose, the selection of what is recorded, access, duration, and consequences.

This guide offers an approach precise enough to reconstruct a situation, yet deliberately incomplete as a record of the person’s working life.

1. State the decision the note will help review

Before writing, complete a sentence: this observation will support a conversation about ___. If the blank remains empty or accepts any answer, there is no defined purpose yet.

A note may help review a role expectation, prepare feedback, or recognize a practice worth sustaining. Notes should not be accumulated on the chance that they might become useful one day. The minimization principle formulated by the UK data protection authority requires identifying the minimum information necessary for a purpose and retaining only that. This is a specific regulatory reference, not universal legal advice, but it offers a sound design principle: adequate, relevant, and limited to what is necessary.

2. Record situation, behavior, and effect—not an identity

A defensible observation makes it possible to reconstruct what happened. Include the relevant situation, the behavior that could be observed, and the immediate effect when it can be verified.

During Thursday's deliverable review, they explained two assumptions and asked for the third to be validated before committing to the date preserves context. They are cautious and strategic turns an episode into an identity. Interpretation can be discussed later; it does not need to be disguised as fact in the record.

Intent should not be inferred either. An interruption is observable. Disrespect is an interpretation that requires context, the perspectives of the people involved, and probably evidence from more than one situation.

3. Select material moments, not a continuous stream

Recording should be triggered by situations connected to the expectation: a relevant decision, a deliberate practice, a repeated difficulty, or a change worth monitoring. It should not be triggered by every movement in the workday.

The Information Commissioner’s Office guidance on monitoring workers distinguishes occasional from systematic monitoring and warns that even practices with a legitimate purpose must respect data protection principles. Screenshots, keystrokes, web activity, and productivity tools can easily turn a specific need into continuous tracking.

Camera on a tripod beside a square plot marked out on the ground in a meadow.

A simple operational rule is to record according to materiality, not availability. The fact that something can be captured does not mean it contributes to the decision.

4. Preserve evidence that challenges your first impression

A record built only to confirm an earlier conclusion amplifies bias. If the expectation is coordination under pressure, a difficult situation may be relevant, but so is a comparable occasion when the person behaved differently.

The aim is not to manufacture balance or count positive and negative notes. It is to preserve enough variation to avoid turning the most available episode into a pattern. When situations are not comparable, the apparent contradiction may reveal that context changes performance.

5. Make the note reviewable by the person

Purpose The conversation or decision that justifies the record.

Evidence The verifiable situation, behavior, and effect.

Limit Access, expiration, and uses that remain out of scope.

The person described should be able to know what was recorded, add context, and identify a factual error. This opportunity improves accuracy and limits the use of invisible files.

Review does not require accepting every interpretation. It requires separating the facts from the interpretation and acknowledging that the observer has only a partial view. If a note cannot be supported before the person without exposing a protected source or creating a real risk, it needs different treatment and explicit rules; it should not silently enter an ordinary development record.

6. Define access, expiration, and prohibited uses

An observation useful today can become misleading after a change in role, context, or expectation. Every system needs to answer who can read the note, for how long, for which decisions, and under what conditions it will be deleted.

It must also state prohibited uses. A note made to prepare coaching should not automatically feed compensation, disciplinary, or selection decisions. Changing the purpose after the information has been collected alters the original agreement and can create consequences the person never had an opportunity to understand.

A minimum format

Use only the necessary fields:

  • Purpose: the decision or conversation it will support.
  • Date and situation: material context without incidental details.
  • Observable behavior: what the person did or said, without attributing intent.
  • Verifiable effect: what changed immediately, if it can be supported.
  • Context provided: the person’s explanation or correction.
  • Follow-up and expiration: when it will be reviewed and when it will no longer be retained.

The format matters less than its limits. Before adopting one, it is worth testing it with three questions: Does the person understand why the note exists? Can they correct a factual error? Will the organization know when to delete it? If the answer to any of them is no, the record still needs design work.