Back to all articlesManager routines

Follow Up on Coaching Without Turning It Into Daily Policing

Alactic Editorial10 min read

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

A coaching conversation ends with an agreement to try something differently. Then one of two things happens: nobody mentions it until the next meeting, or the manager starts asking for updates after every attempt. In the first case, practice disappears into the workload. In the second, the employee spends more energy demonstrating compliance than learning.

To follow up on coaching agreements, agree on three things before leaving the conversation: a real opportunity to practise, a bounded point of observation, and a condition for reviewing the approach. Let the employee choose how to practise within those boundaries. At review, establish whether enough practice happened before deciding whether the approach worked.

The aim is not to monitor every action. It is to create enough shared evidence to decide whether to continue, adapt, or stop a development experiment.

1. Turn the agreement into a testable behaviour

Broad coaching goals are difficult to follow up without becoming subjective. Agreements such as being more confident, taking ownership, or communicating better leave both people guessing what progress should look like.

Translate the goal into something the employee can attempt in a recognisable situation. Identify the trigger, the action, and the immediate sign that the action served its purpose. Keep the focus on something the employee can influence, rather than a result controlled by several people.

Hypothetical example: An employee wants to improve how they delegate work. Rather than agreeing to show more leadership, they agree to end suitable task handovers by asking the recipient to describe the intended result, their next step, and any unresolved question.

The target is not to eliminate every misunderstanding. It is to practise checking shared understanding before the handover ends. That distinction matters: another person may still encounter an unexpected obstacle even when the employee performs the behaviour well.

Keep the experiment narrow enough to interpret. If the employee simultaneously changes their briefing format, meeting length, tone, documentation, and follow-up routine, it becomes difficult to tell what helped or what created friction.

2. Choose the opportunity before choosing the check-in date

A calendar reminder does not create a chance to practise. Before scheduling a review, identify where the behaviour can realistically occur in the employee’s work.

Ask which upcoming situations are suitable, which are too unusual to be useful, and whether the employee has enough control to try the approach. A rare event may require a longer review period. A frequent activity may produce enough useful experience sooner.

The employee should propose the practice method. The manager can clarify the target and discuss risks, but should avoid prescribing every sentence or movement. Otherwise, follow-through becomes an exercise in reproducing the manager’s style.

  • Practice opportunity: A specific type of work situation in which the employee will try the behaviour.
  • Observation point: An agreed occasion or small piece of evidence that makes the attempt visible.
  • Review condition: The amount or kind of experience needed before judging the approach, with a calendar backstop so the agreement is not forgotten.

Include a route for asking for help before the review. A scheduled conversation should not force an employee to continue an unsuitable experiment when a significant problem appears.

3. Use a filled follow-through card, not a surveillance log

The card below is a fictional worked example. All names, quantities, timings, and proposed observations are hypothetical. It shows a recommended working agreement, not a customer result or a product feature.

Hypothetical coaching follow-through card

Employee and manager: Maya, a team coordinator, and Rowan, her manager.

Development aim: Make delegated work clearer at the point of handover, without taking the work back when questions arise.

Target behaviour: At the end of a suitable handover, Maya asks the recipient to explain the intended result and their next step in their own words, then invites questions. She resolves any mismatch before closing.

Employee-chosen practice: Maya will try this in three routine handovers over the next two working weeks. She will choose the wording herself and explain that she is checking the clarity of her briefing, not testing the recipient. Urgent incidents and work already familiar to the recipient are excluded.

Manager support: Rowan will help identify suitable handovers, offer one rehearsal if Maya wants it, and protect time for the review. Rowan will not introduce a competing briefing format during the experiment or ask for daily reports.

Observation point: With everyone’s knowledge, Rowan will attend one already scheduled handover. Maya will choose which suitable handover to use. Rowan will observe the agreed behaviour, not score Maya’s overall leadership style.

Review evidence: After each attempt, Maya will note the situation, whether she used the behaviour, any mismatch it revealed, and whether the recipient could name a next step. A short note is enough; no recording or copied conversation is required. Rowan will bring observations from the single attended handover.

Review condition: Review after three suitable attempts, with a calendar backstop at the end of two working weeks. If fewer attempts occur, use that meeting to examine the opportunity gap rather than declare the approach ineffective.

Early-help condition: Maya will raise the issue sooner if recipients repeatedly seem confused by the request, the process causes material delay, or she cannot find suitable opportunities. Rowan will help adjust the experiment rather than wait for the scheduled review.

Adaptation decisions: Continue briefly if suitable attempts reveal useful misunderstandings but Maya still needs practice. Adapt the wording if the check feels like a test. Adapt the opportunity or manager support if practice does not happen. Stop this method if repeated suitable attempts add friction without useful clarification, and choose a different way to check understanding.

Ownership and record: Maya keeps the brief practice notes. Both retain the agreed card. Rowan will not collect wider colleague feedback or add observation points without discussing that change with Maya.

This is more detail than every coaching agreement needs. Its value is that each line answers a likely source of ambiguity: what counts as practice, what the manager will do, what will be observed, and what happens if the plan does not work.

4. Observe enough to learn, not enough to control

Observation is useful when it answers a question the employee and manager already share. It becomes policing when its scope expands without agreement or when every attempt requires managerial approval.

Choose the lightest evidence that can support the review. Depending on the behaviour, that might be a short employee reflection, an existing work output, or one openly observed interaction. Do not gather several forms of evidence merely because they are available.

Employee notes preserve autonomy but may miss things the employee does not notice. Direct observation can reveal details but may change how people behave. Existing outputs can show what was produced, but not necessarily how the employee arrived there. Acknowledge these limitations instead of treating one source as a complete picture.

In the hypothetical card, Rowan observes one handover and Maya reflects on the others. That provides different perspectives without turning every handover into an inspection. Disagreement between those perspectives is a reason to ask a more precise question, not automatically a reason to increase monitoring.

Keep records proportionate and limited to the agreed development purpose. Avoid collecting private conversation details when a brief description of the learning would suffice.

5. Separate insufficient practice from an ineffective approach

At review, do not begin with a verdict. Reconstruct what happened in a consistent order.

  1. Did suitable opportunities occur? Check whether the planned situations actually arose and whether the employee had room to act.
  2. Was the behaviour attempted? Distinguish intending to use it from trying it, without turning the distinction into an accusation.
  3. Was it attempted as intended? An awkward first attempt may reveal a skill gap or unclear instruction rather than a flawed approach.
  4. What happened immediately afterwards? Look for the agreed observable signal, including friction, confusion, or no discernible difference.
  5. What decision does that evidence support? Choose a next step proportionate to what is actually known.

If suitable opportunities did not occur, the experiment has not received a fair test. If opportunities occurred but the employee did not try, explore the reason: forgetting, discomfort, unclear expectations, conflicting priorities, or a concern about the method require different responses.

If the behaviour was attempted repeatedly in suitable conditions but did not help, do not prescribe more repetition by default. Examine the approach itself. It may solve the wrong problem, fit only some situations, or create a cost greater than its usefulness.

Avoid judging the experiment solely by a distant business outcome. In the delegation example, wider workload and task difficulty may affect completion. The immediate review question is whether the check exposed misunderstandings and clarified the next step—not whether it produced a commercial improvement.

6. Make the continue, adapt, or stop decision explicit

A coaching review should end with a decision, not an indefinite instruction to keep working on it.

  • Continue: Use this when practice is happening and the observations are useful, but the behaviour is not yet reliable. Keep the target stable and agree on another bounded review condition.
  • Adapt: Use this when the target still matters but the method, opportunity, support, or evidence needs changing. Where practical, change one important element so the next review remains interpretable.
  • Stop: Use this when the behaviour is sufficiently established, the approach is unhelpful, the cost is disproportionate, or the development need is no longer relevant. State which reason applies.

Hypothetical review outcome: Maya tries the check in two suitable handovers; a planned third handover is cancelled. One attempt reveals a different interpretation of the task. In the other, the recipient understands the task but finds Maya’s wording formal. Rowan also notices that Maya answers her own question before the recipient has time to respond.

That evidence does not establish that the approach is ineffective. They adapt one aspect: Maya will use her own shorter wording and leave space for an answer. They agree on two further suitable attempts before reviewing again. Rowan does not add daily checks.

If the behaviour later becomes useful and routine, they can stop the formal experiment without abandoning the behaviour. If it repeatedly adds friction without useful clarification, they can stop the method without abandoning the development aim.

7. Recover when follow-through slips

When the agreement is forgotten, return to the last clear commitment rather than inventing retrospective evidence. Establish what practice actually happened, what is still worth pursuing, and what needs resetting.

If the manager failed to provide promised support, acknowledge that before evaluating the employee’s follow-through. An unavailable rehearsal, a cancelled observation, or an overriding instruction may have changed the conditions of the experiment.

If the employee repeatedly avoids agreed practice, discuss that pattern directly. Ask whether the goal still makes sense and what prevents action. Renegotiate only if there is a credible change to the conditions. Repeatedly extending an unchanged plan can conceal the fact that neither person expects it to happen.

If monitoring has become excessive, reduce it explicitly. Specify which updates will stop, which observation remains, and when the employee can request help. Do not simply tell the employee to feel more trusted while leaving the reporting burden intact.

Development coaching also should not disguise an immediate operational requirement. Where work needs closer oversight because an error could cause serious consequences, state that requirement separately. Be clear about which actions are mandatory and where the employee has genuine room to experiment.

8. Leave the next conversation with a complete agreement

For your next coaching conversation, use one existing development goal and write a short follow-through card together. Do not redesign the whole management process.

Before closing, ask the employee to describe the next suitable opportunity, the practice they have chosen, and what they will bring to the review. Then state your own support commitment and the limit of your observation.

A measurable next action: End the conversation with one target behaviour, one agreed practice plan, one observation point, and one review condition recorded in a place both people can access. At review, make an explicit continue, adapt, or stop decision—or identify the missing practice needed before a judgement is possible.

That gives follow-through a clear boundary: enough attention to support learning, and enough space for the employee to do the practising.

Manager routinesCoachingEmployee developmentFollow-through

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