What is the State of Nirvana Futurespective?
The State of Nirvana Futurespective looks forward instead of back. Your team first agrees what its ideal state would look like, its own version of nirvana, then works backward to decide what has to happen by month 1, month 3, month 6 and month 10 to get there. The board has five columns. Our definition of Nirvana holds the vision: zero incidents on deploy, a sustainable pace, customers who recommend you unprompted. The four time columns turn that vision into steps, starting with quick wins in the first month and building to the bigger changes that take most of a year. Working backward from an end state (a planning technique often called backcasting) makes long-term goals feel reachable, because each column only asks what's next. Use it at the start of a planning cycle, before a major initiative, or when the team feels stuck repeating the same sprint and needs a direction to aim at.
State of Nirvana futurespective format
Our definition of Nirvana
The ultimate state we want to be in.
Ask the team to set today's constraints aside and describe the ideal state. Encourage bold answers, but keep them tied to the team's actual work, and finish with a definition everyone agrees on.
1 month
Things to do by month 1
Look for quick wins and groundwork. Ask for first steps that are realistic within a month and that start moving the team toward the vision.
3 months
Things to do by month 3
Look for improvements that build on the month 1 steps. Ask about changes to how the team works, not only quick fixes.
6 months
Things to do by month 6
These are the bigger changes that need sustained effort. Ask what each one depends on and what could get in the way.
10 months
Things to do by month 10
This column is for the changes that bring the team close to its nirvana. Keep them ambitious but believable, and check they follow on from the earlier columns.
When to use this retrospective
- When the team needs to agree on long-term goals and a shared picture of where it's heading
- At the start of a planning cycle or a major new initiative
- When the team feels stuck and needs a direction to aim at
- Before a large change program, to map the steps in order
Suggested icebreaker questions
- If you could instantly master one skill or technology, what would it be and why?
- What's one thing you wish you could automate away in your daily work?
Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →
Ideas and tips for your retrospective meeting
- Treat the vision phase as a space where no idea is too ambitious, so people say what they actually want
- Timebox each column so the later time periods get as much attention as the first
- Write each step as a concrete, measurable action rather than a vague aspiration
- Revisit the plan every month or two and adjust the timeline as things change
- Keep the nirvana definition somewhere the team sees it, so day-to-day choices can point back to it
- Note any outside dependencies that could push a step back
Frequently asked questions
What is the State of Nirvana Futurespective?
What's the difference between a futurespective and a retrospective?
When should a team use this futurespective template?
How long does a State of Nirvana Futurespective session take?
Related templates
Tag-team your sprint review with a wrestling theme.
Working, Not Working Retrospective
Sort what's working from what isn't, then fix it.
Quarterly Retrospective
Step back from the sprints and review the whole quarter.
Baby Steps Retrospective
Pick one small change your team will actually finish.