Wild Ideas

What bold, no-limits ideas could we imagine if anything were possible?

What if customers could onboard themselves in under sixty seconds with zero documentation?
Imagine an AI assistant that writes our release notes and changelog automatically.
Let's launch the product on a completely new platform nobody in our space has touched.
Tiny Tweaks

What small improvements could we try quickly and easily right now?

Add a checklist to our pull request template to catch common mistakes earlier.
Move the daily stand-up fifteen minutes later so everyone is fully online.
Pin the most-used links to the top of our team channel.
Opposite Thinking

What if we reversed our usual approach — what would we do instead?

Instead of adding features, what if we removed half of them to simplify the product?
What if customers wrote our roadmap and we just executed it?
Rather than fixing bugs after release, what if we made shipping bugs impossible?
Borrowed Brilliance

What great ideas could we borrow from other teams, industries, or products?

Spotify's 'Wrapped' could inspire a yearly usage summary for our customers.
Let's borrow the airline's clear boarding-group system for our release process.
Amazon's one-click checkout — how do we make our key action that frictionless?
One-Sprint Experiments

What safe experiments could we test within a single sprint?

Trial async stand-ups for one sprint and survey the team on how it felt.
Run a 'no-meeting Wednesday' experiment and measure focus-time gained.
Pair-program on the riskiest task this sprint and compare defect rates.
Future Us

Looking back from future success, what ideas got us there?

A year from now, our onboarding is so smooth that support tickets dropped by half.
Future us invested early in automated testing and shipped twice as fast.
Looking back, the decision to talk to customers weekly changed everything.

What is an Idea Storm session

Idea Storm is a high-energy brainstorming session designed to generate a wide range of fresh ideas in a short space of time. Whether you're tackling a tricky problem, exploring new product features, or simply looking to inject creative momentum into your team, this format encourages everyone to contribute freely without judgement. By focusing on quantity first and quality later, teams unlock unexpected solutions and build on each other's thinking in a collaborative, inclusive way. The session works by guiding participants through structured prompts — capturing every idea, grouping related themes, and then voting on the most promising directions. This separation of divergent thinking (generating ideas) from convergent thinking (refining and selecting) helps teams avoid premature criticism that can shut down creativity. It's a flexible technique rooted in classic brainstorming principles popularised by advertising executive Alex Osborn, who championed the idea that deferring judgement leads to more original thinking. The real value of an Idea Storm lies in its ability to surface diverse perspectives and give quieter team members an equal voice. Running it in TeamRetro means everyone can add ideas simultaneously and anonymously, reducing groupthink and ensuring the loudest voice doesn't dominate. The result is a richer pool of possibilities, clearer next steps, and a team that feels genuinely heard and energised about what comes next.

Idea Storm brainstorming format

Wild Ideas

What bold, no-limits ideas could we imagine if anything were possible?

Wild Ideas is all about removing every constraint and inviting the most imaginative, audacious possibilities. Encourage the team to ignore budgets, timelines, and feasibility for now — the goal is to stretch thinking far beyond the obvious. Remind everyone that 'too crazy' often hides the seed of a brilliant breakthrough, so nothing is off the table at this stage.

Tiny Tweaks

What small improvements could we try quickly and easily right now?

Tiny Tweaks focuses on the low-effort, high-frequency improvements that are easy to implement straight away. These are the small adjustments that don't need a big project plan but can add up to meaningful gains. Encourage participants to think about friction points in their daily workflow and the quick wins that could smooth them out.

Opposite Thinking

What if we reversed our usual approach — what would we do instead?

Opposite Thinking challenges the team to flip a problem on its head and ask what they'd do if they did the exact reverse of the norm. This reversal technique often exposes hidden assumptions and reveals surprisingly practical alternatives. Prompt people to ask 'what's the opposite of how we do this today?' and explore where that leads.

Borrowed Brilliance

What great ideas could we borrow from other teams, industries, or products?

Borrowed Brilliance invites the team to look outside their own bubble for inspiration — other industries, competitors, hobbies, or favourite products. Cross-pollinating ideas from unexpected places is a powerful way to spark innovation. Ask participants what other companies or experiences they admire and how that magic could be adapted to fit your context.

One-Sprint Experiments

What safe experiments could we test within a single sprint?

One-Sprint Experiments grounds the creative energy into something testable within a short, contained timeframe. These are safe-to-fail trials that let the team learn quickly without big commitments. Encourage people to frame ideas as hypotheses with a clear way to measure whether they worked, so the team can decide to keep, tweak, or drop them.

Future Us

Looking back from future success, what ideas got us there?

Future Us asks the team to imagine themselves a year or two from now, having achieved real success, and to reflect on what decisions and ideas made it happen. This prospective hindsight technique helps people think bigger and connect today's actions to long-term goals. Prompt them with 'It's a year from now and we nailed it — what did we do?'

When to use this retrospective

  • When your team faces a problem with no obvious solution and needs a fresh wave of ideas to explore.
  • At the start of a new project or feature when you want to gather diverse possibilities before narrowing down.
  • When creativity feels stale or the same few voices dominate and you want broader, more inclusive participation.
  • Ahead of planning sessions to build a rich backlog of options to prioritise.
  • Whenever you need to break out of conventional thinking and encourage bold, innovative contributions.

Suggested icebreaker questions

  • If you could instantly master any skill to solve a problem at work, what would it be?
  • What's the most creative solution you've ever come up with for an everyday annoyance?

Ideas and tips for your retrospective meeting

  • Defer judgement during the idea-generation phase — no idea should be criticised or dismissed until you reach the grouping and voting stages.
  • Use a clear, focused prompt or challenge statement so participants know what problem they're solving for.
  • Encourage quantity over quality early on; more ideas mean more raw material to build on later.
  • Leverage anonymous contributions so quieter team members and junior staff feel equally safe to share bold thoughts.
  • Timebox each phase to keep energy high and prevent the session from dragging or losing focus.
  • Always close with concrete next steps and owners so good ideas don't evaporate after the meeting.

Frequently asked questions

How long does an Idea Storm take?
A typical Idea Storm runs for 30 to 60 minutes, depending on team size and the complexity of the challenge. Timeboxing each phase — generating, grouping, and voting — keeps the session focused and energetic.
When should I use an Idea Storm?
Use it whenever you need a burst of fresh ideas, such as at the start of a project, when tackling a stubborn problem, or when planning new features. It's ideal for moving teams out of routine thinking.
How is an Idea Storm different from a regular retrospective?
A retrospective reflects on past work to improve future performance, while an Idea Storm is purely generative — it's focused on producing and prioritising new ideas rather than reviewing what already happened.
How do you keep everyone involved during brainstorming?
Running the session in TeamRetro lets everyone add ideas simultaneously and anonymously, which reduces groupthink and ensures quieter voices are heard alongside the most vocal participants.
What makes a good brainstorming prompt?
A strong prompt is specific, open-ended, and frames a clear challenge — for example, 'How might we reduce our onboarding time by half?' rather than a vague 'How can we improve?'

New to retrospectives? Read our guide on how to run a retrospective →