Home › Platform › Situation Debrief
Situation Debrief

“That Went Badly and I Do Not Know Why.”

One sentence from a phone in a corridor gets a real read: what most likely happened, what else it could be, and the specific thing to do before the end of the day — while the situation is still recoverable.

Book a Demo →Next: Daily Dispatch

The Twenty Minutes After

The Meeting Ended Badly and You Have Twenty Minutes to Work Out Why.

Preparation covers the meetings you saw coming. Most cross-cultural damage happens in the ones you did not: the corridor comment, the sudden silence, the client who agreed to everything and then went quiet for a fortnight. Situation Debrief is the coach you can reach in the twenty minutes afterwards, while the detail is still fresh and the situation is still recoverable.

🤔
What just happened
Describe it in your own words. No forms, no framework to learn first.
🔍
The likely read
Two or three plausible explanations, ranked, with what would distinguish them.
⚡
What to do today
The specific next move, in the right channel, with the words to use.
📈
What it tells you
The pattern behind it, so the same situation is not new again in six weeks.

Live Debrief

“Everyone Went Quiet When I Asked for Objections”

An assignee will not open a training portal to look this up. They will type one sentence into their phone on the walk back to their desk, and if the answer is generic they will never type a second one. So the debrief starts from what they actually said, asks at most one clarifying question, and gives them something to do before the end of the day.

It is deliberately not a therapist and not a decision-maker. It reads the situation, offers the competing explanations, and hands the judgement back — because the assignee has context the platform does not, and because a coach who tells you what to do stops you learning to read the room yourself.

  • One-sentence input from a phone, mid-corridor, in any of four interface languages
  • Competing explanations rather than one confident answer — with the evidence that would tell them apart
  • A concrete repair move with the actual wording, in the channel that fits the culture
  • Draws on the counterpart map, so the read is about these people, not the country
  • Flags when the honest answer is “this is not a cultural problem”
See Counterpart Intelligence →
Debrief — 14:20, Stockholm
You: “I presented the plan, asked if anyone objected, nobody said anything. Two hours later my manager forwarded me a long email from someone who was in the room.”
Most likely: the objection was real and the room was not the place for it. Asking for objections publicly, in front of a manager, made agreement the only low-cost answer available.
Also possible: the plan is fine and this is one person routing around you. What tells them apart: whether anyone else replies to that thread by tomorrow.
Today: reply to him directly, not to the group. Thank him for the detail and ask for fifteen minutes. Do not reference the silence in the meeting.

Coach, Do Not Act

The Platform Never Sends the Email

It would be easy to build a tool that writes the reply and sends it. We deliberately have not. An assignee who outsources every cross-cultural judgement to software is no more capable in month twelve than they were in week one, and the first time the tool is wrong they have no way of knowing.

Every output is framed as a read to test, not an instruction to follow. The assignee decides, acts, and reports back — and that loop is what turns a twelve-month assignment into durable capability the company keeps after they repatriate.

  • Recommendations, not actions — nothing is sent, posted, or scheduled on the assignee’s behalf
  • Reasoning is always shown, so a wrong read is visible rather than invisible
  • Confidence is stated plainly, including when the platform does not have enough to go on
  • Capability transfers to the person, not to a subscription
How Outputs Are Constrained →
Response Framing
Offers a read to testAlways
Shows the reasoningAlways
States low confidence out loudAlways
Sends messages for youNever
Invents a custom the source does not supportNever
Answers a medical, legal or HR questionNever

Why It Matters to the Programme

Every Debrief Is a Data Point Nobody Else Collects

A debrief is the moment an assignee voluntarily describes a real friction point, in the field, at the time it happens. De-identified and aggregated, that is the sensor layer the mobility industry has never had — and it is why programme analytics built on Bearings show root causes rather than ticket counts.

Programme Analytics & ROI Data & Confidentiality

Support at the Moment It Is Needed, Not the Month Before.

Book a 30-minute demo and bring a real situation from your programme. We will run it through live.

Book a Team Demo → See Pricing

FAQ

Common Questions

How fast is a debrief?
Seconds. It is built for a phone between meetings, not a desktop session at the end of the week. One sentence in, a read and a next move out.
Does it store what the assignee describes?
The assignee’s account keeps their own history so coaching compounds. Programmes only ever see de-identified, aggregated patterns — unless the assignee explicitly chooses to escalate a specific issue.
What if the answer is wrong?
Then the assignee should be able to see that it is. Every read comes with its reasoning and a stated confidence level, and the platform offers competing explanations rather than one confident answer — because a coach that is confidently wrong is worse than no coach.
Is this replacing an EAP or counselling?
No, and it refuses to try. Situations that are clinical, legal, or formal HR matters are routed to the right human channel rather than coached through. That boundary is enforced in the product, not left to judgement.
Can the assignee use it about their own manager?
Yes — and they frequently do. Nothing an assignee describes is visible to their host manager or their mobility team.