Sparring
Sparring is a short structured peer-review session in which one person brings unfinished work and a small group gives candid, usable feedback on it. It is a play from the Atlassian Team Playbook: the presenter says what kind of feedback is needed, reviewers read and comment in silence, and the group then talks through the themes. The whole session takes about 30 minutes and works for any kind of work, from documents and plans to designs and code.
Facilitation script
- 1
Set the stage: the presenter introduces the work, its goal and audience and states two or three specific feedback questions. Reviewers ask only clarifying questions.
5 min - 2
Gather feedback in silence: reviewers read and annotate strengths, changes and additions, removals and open questions directly on the shared page or printouts.
10 min - 3
Discuss: go through the comments theme by theme, starting with points several reviewers raised. Reviewers explain their reasoning; the presenter listens and asks questions.
10 min - 4
Wrap up: the presenter summarises what they heard, says which points they will act on first and by when, and thanks the reviewers.
5 min
Tips
Ask the presenter to be specific about the feedback they want: 'is the argument in section two convincing?' gets better comments than 'any thoughts?'.
Choose reviewers from outside the immediate project where possible, because people who know the back story fill gaps a real reader would stumble over.
Protect the silent phase; once someone starts talking, the others stop writing and the first opinion sets the tone.
Common pitfalls
Bringing polished work, so reviewers hold back or the presenter resists changes that would now be expensive
A presenter who explains and defends during the discussion, which uses up the time and teaches reviewers to soften their comments next time
Skipping the silent annotation and going straight to talk, so the most senior or fastest voice shapes everyone else's feedback
Not saying what kind of feedback is wanted, which produces comments on wording when the question was about the overall direction
Ending without stated next steps, so reviewers never learn whether their input was used and stop investing effort
Variations
Run it asynchronously by giving reviewers a day to comment in the shared document and using a 15-minute call only for the discussion and wrap-up. As a standing weekly slot, team members sign up to bring work and reviewers rotate. For larger work, split it and spar on one section per session instead of extending the time. In person, print the work large, pin it to a wall and let reviewers annotate with sticky notes.
Where it fits
When to use it
Work is roughly half done and still cheap to change
The author has been alone with a piece of work long enough to stop seeing its weak spots
A formal review or stakeholder presentation is coming and you want the obvious objections found first
Feedback in the team usually arrives late, in passing, or only from the manager
You need input within the week and cannot wait for a full review cycle
When not to use it
The work is finished and cannot change: feedback then only frustrates, so hold a retrospective on how it was made instead
You need a decision or sign-off, not input: use a decision meeting with the people who hold that authority
The presenter needs help with a problem and has nothing to show yet: a Peer Assist or a Peer Coaching Circle fits better
The work is a visual or interaction design that should be judged against user goals in detail: a Design Critique gives more structure for that
More than five people want to comment: use a Feedback Carousel or a Gallery Walk so everyone gets a turn
Related methods
Frequently asked questions
What is Sparring?▾
Sparring is a 30-minute peer-review session from the Atlassian Team Playbook. One person presents work in progress, two to four colleagues comment on it in silence, and the group then discusses the main themes. The aim is honest, practical feedback while the work can still change.
How many people should take part in a Sparring session?▾
Three to five in total: the presenter and two to four reviewers. With more people the ten-minute discussion cannot cover everyone's comments. If more people need a say, run a second session or use a format built for larger groups.
What is the difference between Sparring and a Design Critique?▾
Both are structured feedback sessions on unfinished work. A Design Critique is aimed at design work and evaluates it against user needs and design goals. Sparring is more general and shorter, uses silent written comments first, and suits documents, plans and code as well as designs.
Does Sparring work remotely?▾
Yes. Reviewers comment in a shared document or on an online whiteboard during the silent phase, and the discussion happens on the call. The silent phase can also be done before the meeting, which shortens the live part to the discussion and wrap-up.
What should the presenter do with conflicting feedback?▾
The presenter decides. Sparring gathers input and does not produce a group verdict, so contradictory comments are normal. In the wrap-up the presenter says which points they will follow and, where useful, why others are set aside.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Sparring into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Atlassian Team Playbook.