Pros and Cons
The simplest possible way to weigh a decision, a change or the sprint as a whole. The team lists the pros on one side and the cons on the other, making trade-offs visible at a glance. Its bare-bones structure makes it a versatile choice whenever a balanced view is needed quickly.
Arguments for the option — benefits, not hopes
Roman
Ships in two weeks instead of two months
Maria
Uses the stack the team already knows
Costs, risks and what the option locks the team into
Anna
Locks us into one vendor for billing
Daria
Needs a data migration we have never rehearsed
Introduction
- Difficult decisions require taking immediate action
- Quick decisions without considering all alternatives can be avoided by using a Pros and Cons List
Why Use a Pros and Cons List?
- Reduces errors and uncertainty
- Objectives decision-making process
- Supports choice with evidence
- Increases awareness of consequences and consideration of others' perspectives
How to Create a Pros and Cons List
- Write down the decision on a sheet of paper and divide it vertically into Pros and Cons
- List the positive and negative consequences of each decision
- Assign values to each item
- Add up the scores and subtract the total cons from the total pros
- Use common sense and gather ideas from group representatives for strategic decision-making
- Complete a Pros and Cons template for each option before comparing outcomes
Final Reason to Use Pros and Cons List
- Simple tool requiring no special skill or technique
- Important to gather ideas from group representatives for different perspectives
- Collaboration tools can be used for remote team members
Conclusion
- Pros and Cons List is a simple and effective tool for making informed decisions.
Similar templates
Other formats teams pair with this one — open any of them as a board in one click.
Sprint Diagnostics
A diagnostic format that combines a quick rating with focused discussion. The team scores the sprint on dimensions like communication, collaboration, quality and pressure, then names a standout like or dislike and what could be done differently before agreeing on actions. The numbers give an easy way to track how the team's health changes over time.
3 L's
A lightweight three-column retrospective for teams that want quick, honest feedback. Participants capture what they liked, what they learned and what they lacked during the sprint. Stripped down to the essentials, it's an easy starting point for teams new to retrospectives or short on time.
DAKI
DAKI gives the team four clear levers for change in a single view. Participants decide what to drop because it no longer helps, what to add that's missing, what to keep that works well and what to improve. The crisp structure makes it easy to leave the session with a concrete, balanced set of adjustments.
SWOT Analysis
A strategic format borrowed from business analysis and adapted for team reflection. The team maps its strengths and weaknesses against external opportunities and threats to see the bigger picture. It works especially well for longer horizons — a quarter, a release or a project — where strategy matters as much as day-to-day fixes.
The Good - The Bad - The Ugly
A vivid three-part format that makes room for things the team can't simply fix. The good is what worked well, the bad is what went off plan, and the ugly is what lies outside the team's control but still deserves to be named out loud. That third column is what sets it apart, surfacing systemic issues that other formats tend to skip.
Agile Kanban
A retrospective that borrows the familiar Kanban board to review the team's flow of work. Items move across to do, doing and done, making bottlenecks and stalled tasks easy to see. It's a natural fit for teams that already think in terms of flow and want their reflection to mirror how they actually work.
