Back to all articlesManager routines

Use Work Evidence in Coaching Without Reviewing Everything

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A missed handoff is easy to remember. A routine handoff that went smoothly is easy to forget. If you prepare coaching feedback from memory, the most striking incident can become the whole story. Reviewing every piece of work is not a practical correction.

Instead, prepare a small evidence packet around one coaching question. Include ordinary work, difficult cases, and work the employee chooses. For each item, separate what you can observe from what you think it means, add relevant context, and state what remains unknown. Use the packet to decide what to ask before deciding what feedback to give.

The aim is not to prove a general judgment about the employee. It is to make a specific conversation better grounded while keeping preparation manageable.

1. Start with a question, not a character judgment

A useful coaching question names a work behavior and the situation in which it matters. “Is this employee careless?” invites you to collect confirming incidents. “What helps or prevents this employee from making the next owner clear at handoff?” gives you something observable to examine.

Before opening work records, write down:

  • The question: What behavior are you trying to understand?
  • The expectation: What was the employee reasonably expected to do?
  • The evidence location: Where would that behavior normally leave a trace?
  • The boundary: What will this preparation not assess?

Check that the expectation actually existed. A manager’s preferred habit is not automatically a shared standard. If the handoff process never specified how to name an owner, the conversation may need to establish that expectation rather than treat its absence as a failure.

Keep the question narrow enough that a small packet can help. Combining accuracy, speed, tone, teamwork, and initiative creates a general performance review disguised as a coaching preparation task.

2. Select a small set using a visible rule

Choose the selection rule before reading for problems. Otherwise, you can spend the entire preparation period following whichever case feels most concerning.

A practical starting design is to include routine work selected by a neutral rule, difficult work selected by a condition relevant to the question, and an employee-selected example. This is a deliberate mix, not a statistically representative sample.

  • Ordinary work: Use a rule unrelated to whether the result looks good or bad, such as the first eligible completed item on specified workdays. Avoid selecting only work you already remember.
  • Difficult work: Define the difficulty in advance, such as a change of owner, an unresolved dependency, or a request that changed midway.
  • Employee selection: Ask for an example that helps explain how the work happens. Welcome either a success or a case that was harder than the visible record suggests.

Record exclusions. If a case is unavailable, say so rather than silently replacing it with a more dramatic one. If the same case qualifies as both ordinary and difficult work, identify the overlap; do not count it as independent support twice.

Give the employee the coaching question and selection approach. Their contribution should add context and potentially challenge your interpretation, not serve as a test of whether they choose the same incident you would.

3. Record observations before interpretations

An observation describes something another authorized reviewer could locate in the work record. An interpretation proposes what that observation means.

For example, in a hypothetical handoff review, “The handoff note contains a next step but no named owner” is an observation. “The employee avoids accountability” is an interpretation—and a substantial leap. Even “the employee forgot the owner” assumes a cause that the record may not establish.

For each item, capture a brief paraphrase of the relevant work, its location, and any missing context. Then put your interpretation in a separate field. This makes it easier to revise the interpretation without arguing about the underlying record.

Absence needs particularly careful wording. “No owner appears in the shared note” does not establish that nobody assigned an owner elsewhere. Equally, an employee’s recollection of a verbal assignment does not establish that the next person could find it. Both points can matter.

Use only work records you are authorized to review for this purpose. Keep irrelevant customer details, personal information, and unrelated employee material out of the packet. Evidence preparation is not a reason to broaden access or begin continuous monitoring.

4. Filled fictional coaching evidence packet

Fictional worked example: All people, records, quantities, and events in this packet are hypothetical. The packet illustrates a preparation method, not an Alactic customer result.

Purpose and selection record

Employee: Maya, customer operations specialist.
Manager’s question: When Maya transfers an open customer request, can the receiving colleague identify the next action and owner from the shared record?
Existing expectation: The team’s handoff guide asks for the next action and receiving owner. The manager still needs to confirm how the guide applies when the receiving team has not accepted the transfer.
Review period: The previous two working weeks.
Preparation limit: Thirty minutes, followed by employee clarification rather than open-ended searching.

Selection rule: Review the first eligible completed handoff on each of two preselected workdays; add two handoffs involving a changed owner or unresolved dependency; invite Maya to choose one further example. The resulting packet contains five distinct items. It excludes requests Maya handled without a transfer and work outside the review period.

Item A: Ordinary handoff with a clear receiving owner

Work observation: The shared note names the receiving colleague and the next action. A later entry from that colleague records completion of that action.

Employee context: Maya says this followed the usual route and the colleague was available to accept the work.

Possible interpretation: Maya can make ownership and the next step explicit when the route is straightforward.

Alternative explanation: Familiarity between these colleagues may have made this case easier than transfers to other teams.

Question before feedback: Which part of this handoff could be reused when the receiving colleague is less familiar with the request?

Item B: Ordinary handoff with an unnamed owner

Work observation: The shared note identifies a next action but refers only to the receiving team. The visible record contains no individual acceptance before that action is completed.

Employee context: Maya says the team normally allocates incoming work internally. This explanation has not yet been checked with the receiving team.

Possible interpretation: The record may leave ownership ambiguous at the point of transfer.

Alternative explanation: Team-level ownership may be the intended process for this queue; naming an individual could be inappropriate before allocation.

Question before feedback: Does the handoff guide require an individual owner here, or an explicit receiving queue and acceptance state?

Item C: Difficult case with a changed destination

Work observation: The initial note names an owner. After the request changes, a later note names a different team but does not identify who will confirm acceptance. A colleague subsequently asks who owns the next step.

Employee context: Maya says the destination changed after new information arrived and that she sought clarification through a separate work channel.

Possible interpretation: The shared record did not make the revised ownership clear to the colleague who asked.

Alternative explanation: Responsibility for updating the record after rerouting may be unclear. Relevant clarification may also exist outside the reviewed record.

Question before feedback: Who was expected to update ownership after the change, and what clarification was available at that moment?

Item D: Difficult case blocked by a dependency

Work observation: The note names the owner and states that the next action depends on information from another team. The visible record does not identify who should follow up on that dependency.

Employee context: Maya says she expected the receiving owner to chase the information.

Possible interpretation: Naming the main owner may not be enough when a dependency needs separate follow-up.

Alternative explanation: The handoff guide may not explain dependency ownership, leaving colleagues to make different assumptions.

Question before feedback: Was dependency follow-up part of an agreed expectation, or is this a process gap to clarify?

Item E: Employee-selected difficult handoff

Work observation: Maya’s selected case includes a named receiving owner, the next action, the unresolved dependency, and an acknowledgment from the receiving colleague.

Employee context: Maya says she used a personal checklist because the request involved several teams.

Possible interpretation: Maya already has a method that makes a complex handoff more explicit.

Alternative explanation: Extra preparation and an available receiving colleague may have helped; the same approach may need adapting under other conditions.

Question before feedback: Which checklist elements are useful enough to apply to other transfers without adding unnecessary work?

Packet-level limits

This packet cannot establish Maya’s overall handoff quality, the frequency of unclear ownership, a comparison with peers, or the causes of delays. Difficult cases were deliberately included, so their share of this packet is not an estimate of their share of Maya’s work. The packet also does not establish intent or effort.

5. Resolve the questions that could change your feedback

Do not give every unknown equal weight. Prioritize questions whose answers would change the coaching choice.

In the fictional packet, the meaning of team-level ownership matters more than the wording of an otherwise complete note. If a receiving queue legitimately owns allocation, Item B may not indicate a problem. If the process requires an explicit acceptance state, the missing state may become the relevant observation.

Likewise, check whether Maya was responsible for updating the rerouted case before asking her to improve that behavior. A missing record can reflect an individual action, an unclear division of responsibility, or information stored somewhere else.

Use a bounded clarification request: ask for the relevant record or explanation, not a reconstruction of the employee’s entire workload. If an important point remains unresolved, mark it unresolved. You can coach on a clear shared expectation without claiming to know the cause of an earlier event.

6. Choose feedback that matches the evidence strength

The packet should support a decision about the conversation, not automatically produce a criticism.

  • Clear expectation, observable gap, relevant context checked: Discuss the specific behavior and the practical change needed.
  • Expectation unclear: Establish the working agreement before treating the example as a failure to meet it.
  • Conflicting evidence: Explore what changes between successful and difficult cases. Avoid flattening both into a single label.
  • Record incomplete: Ask a question or defer the conclusion. Do not fill the gap with a judgment about attitude.
  • Useful employee method already visible: Consider adapting that method rather than prescribing a new one.

For the fictional packet, a defensible provisional focus is making ownership explicit when a handoff changes or depends on another team. “Maya is unreliable at handoffs” is not supported. Even the narrower focus remains provisional until the manager checks the team-allocation rule and rerouting responsibility.

7. Recover when the packet is skewed or incomplete

A small packet trades breadth for preparation time. Its value depends on making that trade-off visible.

If every item is an escalation, add ordinary work using the original neutral rule or narrow the question to escalation handling. If every item is easy, include a relevant difficult case rather than concluding the behavior works under all conditions.

If employee context contradicts your interpretation, preserve the original observation and revise the interpretation. That is a successful correction, not a loss of managerial authority. If the employee-selected item is unusually polished, keep it: it can still reveal a useful method. Just do not treat it as typical.

When records cannot answer the question, stop searching after your preparation limit. Agree on a prospective work artifact that would make the behavior visible, such as an explicit next-owner field in the existing handoff note. Do not respond to uncertainty by collecting everything.

8. Leave preparation with a testable next step

Finish with one provisional coaching focus, the questions still open, and a bounded follow-up method.

For the fictional example, the proposed next step is to clarify ownership rules together, then try Maya’s checklist on the next three eligible cross-team handoffs. At follow-up, review whether each shared record identifies the next action, the receiving owner or accepted queue, and responsibility for unresolved dependencies. Also ask whether maintaining that record created avoidable work.

Those observations would show whether the agreed practice appeared in those cases. They would not prove lasting improvement or explain every downstream outcome.

For your next coaching preparation, write the question and selection rule before opening records. Build a packet containing ordinary work, difficult work, and the employee’s contribution. End it with two explicit statements: what the evidence supports discussing, and what it cannot establish.

Manager routinesEmployee coachingEvidence preparationTeam development

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications