Protocol

Follow up on whether the problem changed, not whether the meeting happened

The meeting is an intervention; the outcome is what happens afterward.

About 1 min read

Before you use it

Use when
  • A conversation or agreement was completed and everyone assumes the conflict is therefore resolved.

Keep this limit in mind

  • Follow-up should not become surveillance or repeated pressure to declare a problem solved.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

At the agreed review point, check the observable actions, whether the original problem recurred, whether either side still experiences the issue as unresolved, and whether the agreement needs adjustment. Escalate the route when repeated informal attempts do not change the problem.

Steps

  1. Were agreed actions completed?
  2. Did the original problem recur?
  3. Does either side still consider it unresolved?
  4. What changes or escalation are needed?

An example

After two release cycles, the team checks whether late changes are acknowledged within the agreed window rather than merely noting that a meeting occurred.

Check your result

The follow-up produces an outcome judgement and a next action, not only attendance confirmation.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingFollow up on whether the problem changed, not whether the meeting happened

Evidence and sources
Supports

Acas recommends that agreed next steps be clear, specific and measurable and that the parties later check whether the problem is actually resolved.

A measurable action does not guarantee relationship repair or fairness.

Dealing with a problem raised by a worker · Keep a record; Following up

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details