Distinguish an Observation, an Interpretation and a Transferable Lesson

Separate what a fictional activity record shows, what the team thinks it means and a conditional lesson another team might use.

Three Different Claims

An observation describes what was seen, recorded or reported, with its source and scope. An interpretation explains what that evidence may mean. A transferable lesson proposes a useful implication for another situation and states the conditions under which it may apply. Moving from one to the next requires reasoning; a confident sentence cannot supply missing evidence.

UNDP's How to do After Action Reviews, three pages, supports structured team reflection and recommendations. The distinctions and event below are original teaching material, not a finding from an actual project.

Use One Completed Fictional Activity

An NGO planned a routine staff learning session for 09:00 at a community venue. The final notice gave the correct place. The facilitator's log records a 09:20 start and says the room key arrived at 09:15. The venue custodian recalls delivering it before 09:00, but has no contemporaneous receipt. Some staff say the earlier notice named another room. No complete record of everyone's arrival or reading of the notices is supplied.

StatementTypeWhat Makes It Appropriate or Overstated
The facilitator's log records a 09:20 startObservation about a supplied recordIt states source and event; the log is not independently verified
The key arrived at 09:15Unqualified factual claimToo strong if only one disputed account supports it; attribute the account
An unclear key handoff may have contributed to the late startInterpretationPlausible, but competing accounts and other explanations remain
Late keys caused all participants to arrive lateUnsupported causal/general claimNo complete arrival evidence and no basis to attribute every delay
For sessions needing controlled room access, confirm the key handoff and backup before the eventConditional lessonConnects a feasible practice to a relevant dependency, without promising punctuality

Keep Rival Explanations Alive

The late start could involve room access, setup time, inconsistent notices or another missing factor. A team may favor one explanation without having enough evidence to exclude the others. Record why it favors it, what contradicts it and what remains unverified.

The custodian's recollection should not be silently converted into a confirmed timestamp, nor dismissed merely because a manager prefers the facilitator's account. A dated record is useful evidence but can contain mistakes. Seek proportionate clarification if the distinction matters to the decision.

Make the Lesson Transfer With Its Conditions

"Always distribute keys the day before" is too universal. Some venues cannot release keys then, and some sessions have no controlled-room dependency. A better lesson identifies the requirement: someone must confirm authorized access and a workable backup in time for setup. The actual method depends on the venue and responsible owner.

Try a contrast: an outdoor meeting has no key and starts late because transport is disrupted. The room-key lesson does not explain that delay. A broader lesson about confirming critical dependencies may be relevant, but it still needs a concrete local application. Transfer is a reasoned possibility, not proof that one solution fits every team.

State What Will Change

For the next fictional venue session, the coordinator proposes an explicit key handoff and check before the event. The manager must arrange the necessary time and valid venue agreement. Implementing that change is one fact; whether it improves access or start time is another.

Use AAR limits before claiming cause or effectiveness, and the changed-practice guide to carry an accepted lesson into work. An observation, interpretation and conditional lesson can all be useful while their uncertainty remains visible.