Step 3: Connect Insights to Actions

Time Remaining: 15:00

Avoid Audio Feedback: Lower Volume | Wear Headset | Mute Mic

Mission Retrospective

Step 3 Support Guide

Select the teaming context you want to view. This guide is separate from the collaboration board and does not change it.

Step 3 Guidance Overview

Mission Retrospective

Step 3: Connect Insights to Actions

1. Relate Core Insights: Consider where each core insight from Step 2 shows up in your team’s day-to-day working environment. Reflect on the situations in which it appears, how often it occurs, and the impact it has on the team.

2. Select One Focus: As a team, determine which core insight is most important to focus on right now and take forward into a Plan of Action.

3. Develop a Plan of Action: Build a plan that is clear, timely, and feasible by specifying what the team will do, why it matters, who is involved, when it will happen, where it should show up, and how it will be carried out.

Step 3 Focus

Move from reflection to practical team action in your ongoing work together.

Relating Core Insights to Your Work Environment Reflection guide

Reflection Guide

Relating Core Insights

Situations: In what recurring situations, meetings, workflows, or interactions does this core insight show up in your team’s day-to-day work?
Frequency: How often does this happen? Is it rare, regular, or frequent?
Impact: What effect does it have on team effectiveness, coordination, decision-making, collaboration, or progress?
Patterns: Does this insight point to a broader pattern in how your team works together over time?
Priority: Which core insight feels most important to address now because it would make the biggest difference to the team?

Developing a Plan of Action Action guide

Action Design

Develop Plan of Action

What: What specific action, behaviour, or change will the team implement?
Why: Why does this matter now? What problem or opportunity does it address?
Who: Who owns the action, who supports it, and who else needs to stay aligned?
When: When will the action begin, and when will progress be reviewed?
Where: Where should this show up in the team’s day-to-day work?
How: How will the team put this into practice and make it stick?
Teaming Tip: Keep the output clear, timely, and feasible so the team can act on it quickly and revisit progress.

Developing a plan of action for an intact team

Examples

Example 1 — Introduce a Wisdom Miner Example

In Step 2, the team identified that they often move to decisions too quickly. In Step 3, they reflected on how this pattern shows up in their day-to-day work environment and recognized that time pressure in meetings often leads them to close discussion before they have explored different perspectives or surfaced key assumptions.

Plan of Action Example — Introduce a Wisdom Miner

What: Introduce a rotating “Wisdom Miner” role to prompt deeper inquiry before important decisions are finalized.

Who: The role rotates across team members so responsibility for deeper inquiry is shared.

When: Use it immediately in the next team meeting when a significant decision is being made.

Where: Apply it during team meetings, especially in moments when time pressure could cause the team to rush.

How:

Pause for 5–10 minutes before finalizing the decision.
The Wisdom Miner asks questions such as:
- “What might we be missing?”
- “What assumptions are we making?”
- “Have we heard from everyone?”
- “What could go wrong if we decide now?”
Capture any unresolved issues for follow-up.

Why: To improve the quality of team decisions, make better use of collective expertise, and reduce rework caused by rushed judgments.

Example 2 — Use a Shared Action Tracker Example

In Step 2, the team identified a recurring lack of clarity about ownership and follow-through. In Step 3, they connected this to their day-to-day work environment and recognized that action items are often discussed but not clearly assigned, which creates delays, duplication, and missed commitments.

Plan of Action Example — Use a Shared Action Tracker

What: Use a shared action tracker to record decisions, owners, and deadlines.

Who: The meeting note-taker maintains the tracker, while all team members confirm their assigned items.

When: Start in the next team meeting and review the tracker weekly.

Where: Use it in all team meetings where actions or decisions are agreed.

How:

Record action items before the meeting closes.
Assign each action to a specific person.
Add a clear deadline or review point.
Keep the tracker accessible to the full team.

Why: To increase clarity, accountability, and follow-through in how the team works together over time.

Example 3 — Create a Round-Robin Format Example

In Step 2, the team identified that some voices are regularly overlooked during important discussions. In Step 3, they linked this to a broader pattern in their ongoing work environment: more assertive voices tend to dominate, especially when the team feels rushed, which limits the range of perspectives considered.

Plan of Action Example — Create a Round-Robin Format

What: Introduce a structured round-robin format during key discussions.

Who: The meeting facilitator runs the round-robin and ensures everyone has an opportunity to contribute.

When: Begin in the next team meeting for important discussions or decisions.

Where: Use it in meetings where the team needs a broader range of input.

How:

Introduce the topic clearly.
Go around the table or virtual room to hear from each person.
Allow someone to pass and return to them later.
Conclude with an open floor for additions or clarifications.

Why: To ensure broader participation, improve shared understanding, and make better use of diverse perspectives within the team.

Step 3 Guidance Overview

Mission Retrospective

Step 3: Translate Insights into Teaming-on-the-Fly Practices

1. Relate Core Insights: Consider where each core insight from Step 2 might arise again in future Teaming-on-the-Fly situations where people need to work quickly with others they do not normally work with.

2. Select One Focus: Choose the core insight that would be most useful to convert into a practical protocol, behaviour, or action for future fast-forming collaboration.

3. Develop Agreed Protocol(s) / Action(s): Turn the selected core insight into something specific enough to apply, simple enough to remember, and useful in helping people coordinate, contribute, and adapt more effectively in future Teaming-on-the-Fly contexts.

Step 3 Focus

Move from reflection to practical actions that can support future fast-forming teams.

Relating Core Insights to Future Teaming-on-the-Fly Situations Reflection guide

Reflection Guide

Relating Core Insights

Situations: In what future Teaming-on-the-Fly situations might this insight be relevant?
Frequency: How often might this type of situation arise across short-term projects, crisis response, cross-functional work, ad hoc problem-solving, or unfamiliar partner environments?
Impact: What effect could this have on team effectiveness if it is handled well or poorly?
Transferability: Is this a lesson that could travel well across different fast-forming teams and unfamiliar collaboration contexts?
Priority: Which core insight would be most useful to convert into a practical protocol or action that people could apply again in future contexts?

Developing Agreed Protocol(s) / Action(s) Action guide

Action Design

Develop Agreed Protocol(s) / Action(s)

What: What agreed protocol, behaviour, or action should people apply in future Teaming-on-the-Fly situations?
Why: Why would this improve future fast-forming team performance?
Who: Who needs to apply this action? Is it something everyone should do, or should one person prompt it?
When: When should it happen? At the start, when new information appears, before a decision, or when coordination starts to break down?
Where: In what kinds of Teaming-on-the-Fly contexts would it be most useful?
How: How should people introduce it, remember it, and put it into practice under pressure?
Teaming Tip: Keep it specific, simple, and portable so it can be applied across different fast-forming teams and changing contexts.

Developing agreed protocols or actions for Teaming-on-the-Fly

Examples

Example 1 — Start with a Rapid Role Clarification Example

In Step 2, participants identified confusion about who was doing what when the team formed quickly under pressure. In Step 3, they reflected on how this could easily happen again in future Teaming-on-the-Fly situations where people come together without established roles, routines, or shared expectations.

Agreed Protocol / Action Example — Start with a Rapid Role Clarification

What: Begin fast-forming teamwork with a brief role clarification to surface who is leading, who is supporting, and who is tracking key information.

Who: Whoever initiates or convenes the team starts the clarification, and everyone confirms their role or contribution.

When: At the start of the team’s work, or as soon as the team composition changes.

Where: Use it in ad hoc teams, crisis response, cross-functional collaboration, and short-term project work.

How:

Take 60–90 seconds to clarify who is doing what.
Ask: “Who is leading this?”, “Who owns what?”, and “Who is tracking the bigger picture?”
Reconfirm roles if the situation changes or new people join.

Why: To reduce confusion early, speed up coordination, and help people contribute effectively even without prior shared experience.

Example 2 — Use a Quick Check-In Before Deciding Example

In Step 2, participants noticed that the team moved too quickly to action without confirming whether everyone had the same understanding of the situation. In Step 3, they identified this as a portable lesson for future Teaming-on-the-Fly situations where shared understanding can be fragile.

Agreed Protocol / Action Example — Use a Quick Check-In Before Deciding

What: Use a short shared-understanding check-in before making an important decision or committing to action.

Who: Anyone can prompt it, though the person leading the task or discussion may do so most often.

When: Right before a key decision, especially when the team is moving fast or information is changing.

Where: Use it in unfamiliar collaboration settings, cross-functional work, and time-pressured problem-solving.

How:

Pause briefly and ask: “What problem are we solving?”, “What do we know?”, and “What are we assuming?”
Invite one or two additional perspectives before deciding.
Confirm the intended next step in one sentence.

Why: To strengthen shared understanding, reduce avoidable errors, and improve coordination when teams do not have established routines to rely on.

Example 3 — Make Speaking Up a Normal Prompt Example

In Step 2, participants identified hesitation to speak up when concerns emerged. In Step 3, they recognized that this is especially risky in Teaming-on-the-Fly situations where people may not know one another well enough to challenge, question, or clarify naturally.

Agreed Protocol / Action Example — Make Speaking Up a Normal Prompt

What: Establish a simple verbal prompt that makes it easier for anyone to flag a concern, question, or uncertainty.

Who: Everyone is expected to use it when needed; the team lead models it early.

When: Any time someone sees a risk, has conflicting information, or feels unsure about the direction of the team.

Where: Use it in short-term teams, operational handovers, unfamiliar partner settings, and high-pressure collaboration.

How:

Agree on a simple prompt such as “Pause — I may be missing something” or “I have a concern.”
Normalize brief interruptions for clarification when risk or confusion is present.
Respond by listening first before resuming action.

Why: To increase adaptability, surface concerns earlier, and help fast-forming teams coordinate more intelligently under pressure.

Mission Retrospective

Team Collaboration Board

Click to minimize

Use this collaboration board to capture the analysis, insights, and agreed actions from your Mission Retrospective.

Connecting…

—

Team

—

Team Scribe

Not set

Participants Present

Shared board active

Opening Context Not started

Capture your teaming context and confirm whether you are working as a stable, intact team or teaming together for the first time (on-the-fly).

Mission

Organization Name

Team Name

Step 1 — Review the Mission Timeline Not started

Review the mission timeline to build a shared understanding of what happened.

Pivotal Moments

After reviewing the mission timeline, identify 2-3 Pivotal Moments that would be worth analyzing in Step 2.

Pivotal Moment No content yet Empty

Moment

Why it may matter

Pivotal Moment No content yet Empty

Moment

Why it may matter

Pivotal Moment No content yet Empty

Moment

Why it may matter

Step 2 — Examine a Pivotal Moment Not started

A. Select a Pivotal Moment

Choose one pivotal moment from the list above to analyze.

Selected pivotal moment: —

B. Identify Insights

Not started

Using a series of probing questions - both broadening & deepening - capture insights about your team’s dynamic.

Insight No content yet Empty

Theme

Name Insight

Describe Insight

Insight No content yet Empty

Theme

Name Insight

Describe Insight

Insight No content yet Empty

Theme

Name Insight

Describe Insight

Insight No content yet Empty

Theme

Name Insight

Describe Insight

Insight No content yet Empty

Theme

Name Insight

Describe Insight

C. Synthesize Core Insights

Not started

By reviewing the insights identified above, synthesize them into 2-3 Core Insights that capture what mattered most to your team.

Core Insight No content yet Empty

Name Core Insight

Describe Core Insight

Core Insight No content yet Empty

Name Core Insight

Describe Core Insight

Core Insight No content yet Empty

Name the Core Insight

Describe the Core Insight

Step 3 — Connect Insights to Actions Not started

Relate Core Insights

Consider where each core insight shows up in your day-to-day working environment. As a team, reflect on which insights are most relevant to your ongoing work together. Then choose one that your team believes is most important to focus on right now to build your plan of action around.

Core Insights	Situations in which they occur	Frequency of occurrence	Impact on team	Select Plan of Action focus
Core Insight
Core Insight
Core Insight

Develop Plan of Action

No plan of action focus selected

From the Core Insight selected above, develop a Plan of Action for your team. Keep the output clear, timely, and feasible.

What

Why

Who

When

Where

How

Retrospective complete

Capture your team’s report

Your team has now identified its pivotal moments, key insights, and agreed actions. Download the report to save a summary of your work.

After your team has completed Step 3, proceed to the Conclusion of the Mission Retrospective with the Team Lead clicking the button on the right.