Resources
Recording workplace observations: Build context for your next one-on-one
Turn workplace observations into context for feedback and development, with a note template, wording examples, research limits and a fictional conversation series.
MarkusJust before your next one-on-one, a difficult project meeting comes to mind. What exactly happened? Which information was missing? And what had the same person contributed successfully in the preceding weeks? A strong impression does not answer those questions.
Notes about workplace observations can preserve specific situations for later feedback and development conversations. They give you an example to return to, help you identify unanswered questions, and let you examine your interpretation with the person involved. Even a carefully written note represents a selected perspective. Documentation does not guarantee objectivity.
Our guide to running effective one-on-one meetings covers the wider conversation process. This article focuses on the work between meetings: what is worth recording, how to phrase it appropriately, and how an observation becomes a development topic.
Memory and perception have limits
You see only part of your employees' work. Even within that limited view, the order of events can affect your assessment. In experiments, students evaluated recorded lectures. Depending on the experimental conditions, a particularly good or poor performance at the end carried greater weight in the overall rating (Steiner & Rain, 1989). This demonstrates a possible recency effect, but does not establish its general strength in management practice or a rule that the latest event always dominates.
Writing things down does not remove these influences. In a laboratory experiment, an initial impression of a lecturer affected the behavioral incidents recorded later. The study found a contrast effect: subsequent behavior was interpreted differently against the initial impression (Balzer, 1986). This was a simulated appraisal setting, not an ongoing working relationship.
The practical implication is to examine your selection: Which situations are missing from my notes? Am I looking for examples that challenge my current impression? A collection of only supporting evidence can reinforce a premature judgment, even when every individual incident really happened.
What structured notes can help with
Research suggests potential benefits, while distinguishing memory from judgment. In a study of notes taken during recorded employment interviews, taking notes improved recall accuracy, but did not automatically improve judgment accuracy. Reviewing notes improved judgment accuracy for the group using conventional notes (Middendorf & Macan, 2002). These findings have limited direct applicability to ongoing employee conversations.
Structured diaries and structured recall procedures were studied in two organizations. Following the interventions, raters recalled more performance information and produced lower, more differentiated ratings (DeNisi & Peters, 1996). Less generous or more differentiated ratings do not independently establish objective accuracy, however. The studies examined formal performance appraisal, not today's one-on-one note templates.
The practical recommendation is to record relevant situations soon after they happen and review your notes critically before the conversation. The template below is an editorial resource for everyday use. These studies do not establish an optimal note-taking frequency or guarantee improvements in conversation quality, trust or long-term development.
Separate observation, interpretation and evaluation
On September 7, Lea presents a new start date during an internal project meeting. She mentions a pending supplier approval after someone asks a follow-up question. The team postpones confirming the date to the customer. Milan attends the meeting.
The note can distinguish three levels:
| Level | Meaning | Example from the fictional situation |
|---|---|---|
| Observation | Specific behavior or an outcome, with context and a source | “September 7, project meeting: Lea presented the new start date. She mentioned the pending supplier approval in response to a question. Confirmation of the date was postponed. Observed directly.” |
| Interpretation | A possible explanation that still needs to be checked | “Perhaps Lea assumed everyone already knew about the pending approval. I do not know yet.” |
| Evaluation | An assessment against an explicit expectation | “Before confirming a date, we need a clear view of unresolved dependencies. We need to discuss whether that expectation was sufficiently clear for this presentation.” |
Separating these levels makes statements easier to examine. It does not remove all subjectivity: choosing a situation and describing its impact already reflects a perspective. An assumed intention such as “She wanted to hide the risk” therefore does not belong in the observation field. An impact should only be described as having occurred when it is known. “Could prompt further questions” describes a risk, not an observed consequence.
Specific wording and premature judgments
Positive labels can be vague too. The examples below all refer to Lea; the later situations reappear in the conversation sequence.
| Premature judgment | More specific and open to discussion |
|---|---|
| “Lea is unreliable.” | “In the meeting on September 7, the pending supplier approval went unmentioned until someone asked. I do not yet know who had been informed beforehand.” |
| “She doesn't think things through.” | “The proposed start date depended on an approval that was still outstanding. What assumptions informed her plan?” |
| “She's a natural leader.” | “On September 14, Lea opened with the unresolved dependency and an alternative date. The team then decided how to proceed.” |
| “She contributes little outside meetings.” | “I have seen little of the preparation between meetings so far. I want to ask about specific contributions and working documents.” |
Which observations are worth recording?
Make a deliberate selection. Before writing a note, consider:
- Relevance to work: Does the situation relate to a task, an agreed goal, collaboration, a strength or a need for support? A manager's personal preferences are not performance criteria.
- Significance: Will this example be useful for recognition, clarification, feedback or learning? Not every everyday remark warrants an entry.
- Traceability: Can you identify the date, context, behavior and source? Label someone else's account as such and check it before making an assessment. Several accounts of the same incident are not independent observations.
- Appropriate scope: Record only the context needed for the conversation's purpose. Private details, speculation about health and judgments about someone's character do not belong in a development note.
- Need for clarification: Is a conversation needed soon? Urgent feedback should not wait until you have collected enough examples or the next regular one-on-one arrives.
If you reconstruct a situation later, record both the event date and the date you wrote the note. Mark gaps in your memory. A precise-looking date or an apparently verbatim quotation adds little value if you are only guessing.
Include positive, difficult and less visible contributions
If your collection contains only mistakes and exceptional successes, it misses contributions that sustain everyday work: careful preparation, dependable routine work, knowledge sharing and support for colleagues. Before the conversation, consider which work you actually had a chance to observe. Few notes about someone initially tell you that you have little documented insight.
Visibility can itself introduce bias. A qualitative study and an experiment found that simply being seen at work could prompt inferences of dependability or commitment (Elsbach et al., 2010). The research examined office presence, not the effectiveness of digital notes in today's hybrid teams. It does not establish a general rate of disadvantage for remote workers.
As a practical response, ask about outcomes, preparation and collaboration you have not seen. Use relevant examples of work and the employee's perspective. Time in the office, speaking time or message counts should not stand in for someone's contribution. A fixed quota of positive and negative entries is no substitute either: aim for an appropriate selection of relevant work, rather than a numerical balance.
A compact observation note template
For an everyday note, a name, event date and a few specific sentences are enough. Optionally tick what the note is for and what it is based on. You can select more than one option; name the source in the text when recording someone else's account. If something remains unclear, add a question for your next one-on-one. Fill in, copy or print the note here; build a shared understanding during the conversation.
Quick observation note
Note written on
Not saved here. Please copy or print your note.
Keep the note in your organization's designated system with appropriate access controls. An update after a conversation should make clear when an assumption was corrected. Do not retain disproved judgments about a person as though they were still valid findings.
From one situation to a development topic: three fictional conversations
First one-on-one, September 9: add context
Milan brings his observation from September 7: “You mentioned the pending approval after someone asked. How did that come about, and what did the team already know?”
Lea explains that she had flagged the risk in the project channel on September 4. They look at the entry together. Milan had missed it. Lea had assumed the date would be discussed with that information in mind. They had not previously agreed to restate unresolved dependencies in every presentation.
Milan updates his note: “Reviewed the September 4 risk update together; my assumption that Lea had not prepared was unfounded. The expectation for presenting information in the meeting was unclear.” The postponed decision remains a fact. Their understanding of the situation has changed.
They agree on an experiment for the next two planning meetings: Lea will open with unresolved dependencies, decisions needed and a possible alternative date. Milan will clarify who can obtain the outstanding approvals. They also agree that he will briefly record relevant situations for preparation and discuss his interpretation with her.
Second one-on-one, September 21: include contributions and counterexamples
On September 14, Milan directly observed Lea presenting the pending approval and an alternative at the start of the meeting. The team was able to decide how to proceed. He records this example as specifically as the difficulty on September 7.
In their second one-on-one, Lea adds a less visible contribution: before the next planning meeting on September 18, she had worked with Sales and Engineering to prepare the information needed for the decision. Milan had not been involved. They discuss the overview she prepared; his note labels the source as “reported by Lea, discussed using the overview.”
They can now articulate a useful focus: Present dependencies and decisions needed early enough for the people involved to act. Lea wants to become more confident at this because she would like to take on larger projects. Her strength in preparation is part of the topic. Milan takes responsibility for clarifying how decisions are made. They agree to use the next conversation to review which information was available in time and where a decision was still missing.
Third one-on-one, October 5: distinguish progress from working conditions
During planning on September 28, Lea had again raised the risk early. An approval nevertheless remained outstanding for two days because Milan had not yet clarified who was responsible for the decision.
They record that the agreed communication had happened, while the decision process remained unclear. Milan takes responsibility for resolving this before the next planning meeting. Lea will continue using the short overview. Their next review will examine whether preparation and clear decision ownership work together as intended.
The initial situation has become a development topic they understand together. It rests on specific examples, a corrected assumption, Lea's own development ambition and the manager's responsibility. These few situations do not justify a blanket conclusion about Lea's overall performance.
Only describe something as a pattern after examining comparable situations, counterexamples and working conditions. The cited studies do not establish a minimum number of observations. Several notes may describe the same unresolved process issue. Our one-on-one agenda template can help you bring a selected topic into the conversation.
Take the employee's perspective seriously and protect trust
Ask for more than agreement with your version. “What is missing from my description?”, “What could you see at the time?” and “What support from me would have made a difference?” create room for corrections. If your views still differ, record the difference and the next step for clarification. A development conversation does not require forced agreement.
A meta-analysis links participation in performance appraisal with more positive reactions, particularly satisfaction. Having one's voice heard mattered (Cawley et al., 1998). This does not establish that every self-assessment is accurate or that reading notes together automatically increases trust.
Documentation may provide reassurance by keeping agreements accessible. It may also feel like a means of control, particularly if employees only discover a long-standing collection of notes during an appraisal. The studies reviewed here do not directly establish the effects of this note-taking practice on trust. A meta-analysis of electronic performance monitoring found associations with higher stress and more favorable attitudes when monitoring was more transparent and less invasive (Ravid et al., 2023). This is a related research context; its findings cannot be applied directly to individual conversation notes.
As an organizational practice, managers should explain the purpose and handling of notes: what is recorded, who has access, how information is used in conversations and how errors are corrected. Also clarify whether and how information may later inform a formal review. Keep discussed agreements accessible to both participants. Distinguish their purpose from that of private working notes; calling notes “private” does not replace a data protection assessment.
HR can provide clear standards, training and points of contact. Data protection principles include purpose limitation, data minimization, accuracy and storage limitation (European Commission, n.d.). Clarify the specific use, access and retention with the responsible privacy specialists and, where applicable, employee representatives. Our article on a privacy- and works-council-friendly rollout offers an organizational starting point.
How riteful supports conversation context
In riteful, observations can be recorded as journal entries. Journal entries, goals, open actions and previous conversations can provide context during agenda preparation. riteful supports AI-assisted observation analysis and agenda creation, as well as a joint development and conversation plan. The one-on-one software page explains the process.
Notes are private. HR can see whether one-on-ones take place, but cannot access conversation content or private notes. People develop a shared understanding through dialogue. AI outputs assist people; riteful does not make autonomous employment decisions.
Check AI suggestions against the original observation and the additional context too. A convincing analysis cannot turn missing information into established facts. The studies cited here examine other approaches and are not evidence of riteful's effectiveness.
Start with one concrete step for your next one-on-one: choose a relevant situation, fill in the template briefly and mark what you do not yet know. Invite the other person to add their perspective. Then record the interpretation you discussed together and the next step.
References
Balzer, W. K. (1986). Biases in the recording of performance-related information: The effects of initial impression and centrality of the appraisal task. Organizational Behavior and Human Decision Processes, 37(3), 329–347.
Cawley, B. D., Keeping, L. M., & Levy, P. E. (1998). Participation in the performance appraisal process and employee reactions: A meta-analytic review of field investigations. Journal of Applied Psychology, 83(4), 615–633.
DeNisi, A. S., & Peters, L. H. (1996). Organization of information in memory and the performance appraisal process: Evidence from the field. Journal of Applied Psychology, 81(6), 717–737.
Elsbach, K. D., Cable, D. M., & Sherman, J. W. (2010). How passive ‘face time’ affects perceptions of employees: Evidence of spontaneous trait inference. Human Relations, 63(6), 735–760.
European Commission (n.d.). What data can we process and under which conditions? Retrieved October 6, 2026.
Middendorf, C. H., & Macan, T. H. (2002). Note-taking in the employment interview: Effects on recall and judgments. Journal of Applied Psychology, 87(2), 293–303.
Ravid, D. M., White, J. C., Tomczak, D. L., Miles, A. F., & Behrend, T. S. (2023). A meta-analysis of the effects of electronic performance monitoring on work outcomes. Personnel Psychology, 76, 5–40.
Steiner, D. D., & Rain, J. S. (1989). Immediate and delayed primacy and recency effects in performance evaluation. Journal of Applied Psychology, 74(1), 136–142.