Practical Edge Academy
FOR TEAMS

Start a team learning conversation

Teams often sense a problem before they can name it. This page helps a coordinator describe the situation, the task, the people involved and the change they hope for, and shapes it into a brief for a direct enquiry.

Ask about a team learning need

Describe the task, the people involved and what you want to improve. Ask about learning options for your team and any practical arrangements.

A shared outcome
A named actionA clear handoff
A useful review point
Adults reviewing next actions together in an illustrative practice sceneIllustrative practice scene
BEGIN WITH THE WORK PEOPLE ACTUALLY DO

A learning need
has a real context.

Use a specific handoff, decision or recurring task to describe what would be useful. The tools here help a team put that need into words.

Build a team learning brief

From vague frustration to a usable brief

A comment like our handoffs are messy is a starting point, not a learning need. A useful brief gets specific: what happens, who is involved and what would be different if it improved. Writing this down also helps the team agree on the problem before anyone suggests a solution.

The tool asks for four things: the situation, the task affected, the people involved and the desired change. From these it assembles a clear, editable brief you can refine and send.

What a good brief contains

The strongest briefs describe observable moments rather than general complaints. Instead of saying communication is poor, they say that project notes are passed on without the deadline or the open questions. They also name roles, not individuals, and state how the team will know things have improved.

Keeping the brief factual makes the conversation easier. It lets both sides discuss whether a shared resource, a short guide or something else would help, without assuming the answer in advance.

A worked example: unclear handoffs

A coordinator notices that work passed between shifts often arrives incomplete. They enter the situation as shift handover, the task as passing on open items, the people as six team members across two shifts, and the desired change as fewer follow-up questions.

The resulting brief states these plainly and can be edited before use. It gives the coordinator something concrete to send, and gives the reader enough context to respond usefully.

  1. 01

    Describe the situation

    Write what is happening and when, focusing on what can be observed rather than who is to blame.

  2. 02

    Name the people and the change

    State which roles are involved and what would look different if things improved.

  3. 03

    Review and send directly

    Edit the brief, copy it, and send it yourself by email when you are ready to start the conversation.

USEFUL QUESTIONS
Does using this page commit my team to anything?

No. It only helps you write a brief. Nothing is sent from the page, and you decide whether and when to email it. It is simply a way to organise your thinking.

What if we are not sure what the learning need is?

That is a common starting point. Describe the situation as best you can and leave the desired change open if necessary. A clearer picture often emerges once the problem is written down in plain terms.

What should your team be able to do better?

Describe the shared task, the people involved and what you want to improve. Ask about learning options for your team and any arrangements that matter to you.

Start a team enquiry