How to Brief Your Team in 90 Seconds (Without Losing Them)

When it comes to communicating what you’re currently working on, the challenge for most technical specialists is simple: when everything feels relevant, nothing lands.

When you’re asked to brief your team on a project, two assumptions quietly sabotage you:

1. They’re interested in everything
2. They understand your concepts because they’re “technical” too

Neither is usually true.

So you start talking… and suddenly you’re sliding into a black hole of detail while another part of your brain notices your listeners glazing over. Then comes the awkward climb back out.

This structure stops that spiral.

It helps you share your work clearly, concisely, and in a way your team can actually use – even when you’ve only got a minute or two.

(And if you need a format for longer updates, you’ve got this structure here.)

The Situation / Complication / Outcome Structure

A fast, high‑clarity structure for briefing your team on any project — especially when time is tight.

When you only have 30–90 seconds to get people aligned, this structure forces you to cut the fluff and surface what actually matters.

Here we go…

1. Situation: What’s the context?

Set the scene. Limit this to simple bullet points. Not all of these need to be stated: for example, the where might not be necessary. You need only give the minimum viable orientation.

• Who’s involved?
  Key collaborators, stakeholders, or impacted teams. Also: who’s responsible for making it happen?
• What are we working on?
  A short description of the initiative, project, or experiment.
• When and where?
  Timeline, milestones, and relevant locations (physical or digital).
• Why now?
  Strategic relevance, urgency, or opportunity window.

Examples in Context:

✅ Example: FinOps (Investment Banking)

A FinOps engineer has been asked to standardise how the Commercial team communicates financial performance to clients.

They say: “Each client uses different terminology and the Commercial team has its own internal vocabulary. We need to build a shared “translation layer” so everyone is talking about the same elements in the same way.”

✅ Example: Construction Engineering

A construction engineer is coordinating structural, electrical, and mechanical teams on a new commercial build.

They say:  “Each discipline uses its own planning tools, drawings, and naming conventions, and the client expects a unified progress view.”

✅ Example: Pharma (R&D / Operations)

A Pharma operations lead is preparing a new therapy for Phase III trials.

They say: “R&D, Regulatory Affairs, and Manufacturing each own critical components of the Phase III trials – experimental data, compliance documentation, and production protocols – all of which must be aligned before submission.”

2. Complication: What’s getting in the way?

This is where you surface the friction – the thing that slows progress, creates confusion, or introduces risk.

• System‑level challenges
  Bottlenecks, outdated processes, tech limitations, or resource gaps.
• Stakeholder friction
  Misalignment, competing priorities, unclear expectations, or communication breakdowns.

Note that this has two or three sentences:

1. The issue and impact.
2. The analogy (although you can have that at any point if you need to include one)

Analogies are extremely powerful here. They make the friction instantly graspable — especially when the challenge is abstract, technical, or invisible to outsiders.

This post describes how to find the right analogy,

Examples in Context

✅ FinOps Complication

The challenge here is the language inconsistencies between the clients and Commercial.

They say: “(issue) Commercial, Finance, and clients all describe identical concepts using different terms and it’s creating avoidable back-and-forth, slowing reporting cycles.  (analogy) It’s like trying to get three groups to speak Esperanto… except very few people speak Esperanto. (impact) This misalignment slows reporting cycles and creates avoidable back‑and‑forth.”

✅ Construction Complication

The problem here is that the timings are all out of synch.

They say: “(issue and impact) Each team is optimising for its own workflow, which means dependencies get missed, tasks overlap, and critical path items shift without warning. (analogy) It’s like trying to choreograph a dance when every group is following a slightly different version of the music.

✅ Pharma Complication

There’s a regulatory evidence burden in this case.

They say: “(issue) R&D moves fast, but Regulatory needs every claim backed by specific formats, audit trails, and validation steps. (impact) The result is Regulatory lags too behind, slowing down our ability to launch.  (analogy) It’s like having a brilliant chef who can create dishes instantly. The science is ready, but the documentation isn’t submission‑grade.

1. 3. Outcome: What’s the impact?

This is where you show momentum or make a clear ask. Note the WIIFM is included here. That’s the overall benefit of your project, stated in italics below. (You can include them anywhere, but I’ve chosen to include them here.)

1. 1. • What we’ve achieved so far
        Tangible wins, prototypes, insights, or momentum shifts.

Or / and

1. 1. • What we want others to do
        Feedback, decisions, support, or action.
      • What we’re doing next
        Next steps, experiments, or pivots.

Examples in Context

✅ FinOps Outcome

The engineer has adapted the language to build in flexibility.

They say: “The engineer is building automated outputs that adapt to each client’s preferred terminology while remaining internally consistent.
This reduces manual translation work, improves accuracy, and strengthens client trust because reports finally sound like them.

✅ Construction Outcome

The engineer is implementing a shared coordination model

They say: “We’ve integrated a shared coordination model that uses AI to align timelines, dependencies and update cycles across all disciplines. Everyone will be working from the same ‘master schedule’. As a result, clashes drop, timelines tighten, and the client gets a unified reliable view of progress.

✅ Pharma Outcome

There’s now a unified framework to bring together all the elements.

They say: “We’ve made the system more cohesive. It’ll standardise terminology, evidence requirements and version control across all teams.
This reduces submission errors, accelerates trial readiness, and gives regulators a cleaner, more coherent package, ultimately speeding the therapy’s path to patients.

Your Actions:

1. 1. 1. Got a “share your project moment” coming up? Define the ‘Situation’, sticking a few bullet points for Who, What, When, Why (and Where, if relevant)
      2. Do a couple of bullets for ‘Challenge’ – to include issue and impact.
      3. Repeat for Outcome.

WIIFMs need to be dropped in but you can do that anywhere, as with analogies if you decide they’d benefit understanding.

Use this structure and watch your team look at you like you’ve suddenly become the most organised person in the building. (You always were — now they can tell.)

For a quick narrative framework that’s excellent for quick anecdotes, case studies with prospects and clients, as well as those you need to steer to a different course of action, you’ve got the ‘Pain, Pivot, Prize’ structure.

Need more support with your communication skills? Have a look here at how I coach and train teams as well as individuals to become Communication Ninjas.

Get in touch with me here and book a free 15-minute Discovery Call.