An open charcoal book beside a cream note sheet and a single speech bubble.
Design & UX,  Productivity & Collaboration

Plan a team learning session with more than one way to take part

You are planning a team learning session. The activity sounds lively: quick answers, a shared whiteboard and a presentation from every group. Before sending the invitation, check what someone must do to participate. Fast speaking and confident presenting may be extra requirements you never intended to teach.

Start with one learning goal, then offer different ways to practise it. A colleague might think quietly, write a response, discuss it or ask the facilitator to read it. The useful question is whether each route gives them access to the same learning.

Product Talk’s 20 October 2026 discussion of team experiences prompted this guide. Its public notes emphasise planning with the team. The exercise below turns that consideration into a small session plan you can adapt for colleagues entering tech or developing product and delivery skills.

Decide what people will practise

A learning goal describes something a participant should be able to do. “Build confidence” is difficult to plan around on its own. “Ask one clarifying question before proposing a solution” gives you a specific behaviour to practise and discuss.

Keep that goal separate from the activity’s format. If the skill is asking a useful question, nobody needs to disclose a personal setback or deliver an impromptu speech to demonstrate it. Use a shared practice scenario that does not depend on private experience.

Choose a small output: one question, a revised explanation or a short comparison. Explain how it will be used. A practice response does not need to become a performance rating or a public ranking.

Prepare participation before the session

1. Make the task available in advance

Purpose: Give people a clear starting point.

Share the goal, instructions, agenda and practice material early enough for colleagues to prepare. Explain unfamiliar words and what prior knowledge is needed. If the exercise changes on the day, make the updated version available to everyone.

W3C’s accessible-events guidance recommends accessible materials and checking the event platform and venue. Apply that to the actual tools you choose: a visual board alone may leave someone unable to read, navigate or add a response. Arrange a usable alternative with them.

2. Offer routes with equal value

Purpose: Keep the learning goal consistent across formats.

Allow time to think before asking for contributions. Offer a written route as well as spoken discussion, and explain how both will receive feedback. Reading silently should not leave someone with a smaller task or no opportunity to practise.

Ask privately what would help someone take part, rather than requesting an explanation in front of colleagues. Confirm practical arrangements such as captions, breaks or accessible documents. Avoid promising that a tool or format will suit everyone before checking it with the people involved.

3. Explain the facilitator’s role

Purpose: Make choosing a route straightforward.

Say how people can pass on speaking, submit a question or contribute later. Do not ask them to justify that choice publicly. If a later contribution matters to the learning, give it an agreed review time and someone responsible for responding.

Describe useful visual information aloud and keep instructions in a shared, accessible place. W3C’s guidance covers these presentation practices. Check that remote colleagues can follow the task and receive the same updated instructions as those in the room.

Example: a 30-minute question practice

Consider this example: Morgan is planning a session for a mixed product and development team. The goal is to ask a clarifying question about a customer’s task before suggesting a feature. The practice material is one line: “After choosing a time, I cannot tell whether my appointment is booked.”

Participants can write privately, add text to the agreed document or discuss the prompt. Morgan can read a submitted response without naming its author. Everyone receives the same prompt and the same feedback questions.

A suggested running order

  • Minutes 0–4: explain the goal, the available routes and what will happen to responses. Nobody has to describe a personal experience.
  • Minutes 4–9: read the prompt and draft one question independently. Keep the instructions available while people work.
  • Minutes 9–17: compare responses through writing or conversation. Ask what each question would help you understand.
  • Minutes 17–24: revise one question. Morgan offers feedback through the agreed written or spoken route.
  • Minutes 24–30: identify one way to use the skill in ordinary work and explain how to submit a later response.

For instance, “Would a bigger confirmation button help?” introduces a solution before establishing what happened. A possible revision is “What did you see immediately after choosing the time?” It asks about the experience the team needs to understand. This is a suggested question, not a customer research finding.

Nadia could submit her revision in writing, while Tess could explain hers aloud. Morgan reviews both against the same criterion: does the question seek information about the task before suggesting a fix? Speaking speed and presentation style are outside that goal.

Adapt the timing with participants. If more thinking time or a break is needed, reduce the number of responses discussed. Keep the learning opportunity available rather than treating the schedule as a test of pace.

Use a small participation plan

  • Goal: what specific skill will people practise?
  • Material: what will they receive beforehand, and in which usable format?
  • Routes: how can they practise and contribute through writing, speech or another agreed method?
  • Feedback: how will every route receive a response against the same goal?
  • Support: who will arrange access needs, breaks and instructions?
  • Follow-through: when and how can people complete the practice or ask a question afterwards?

Before the invitation goes out, ask a colleague to follow the instructions without your explanation. Check what they would produce, where they could contribute and how they would receive feedback. Resolve any missing route with the people who will use it.

Start with one short session. Afterwards, ask which parts helped people practise and which made participation harder. Use that feedback to change the next plan. A useful outcome is a learning activity people can approach in different ways, with clear instructions and a practical skill to carry into work.

This recent-discussion-inspired guide includes an original practice scenario, running order and participation plan. The timings are adaptable teaching suggestions. Accessible-event recommendations draw on W3C guidance.

Leave a Reply

Your email address will not be published.