
The Uncertainty List is a straightforward but powerful tool that can transform the way your team works. With just a few tweaks to your routine, you'll see big benefits like:
- More confidence in how your team handles changes.
- Better estimates that are closer to reality.
- Smoother execution and fewer surprises.
- Stronger trust across the entire business.
All these add up to a team that's more adaptable, reliable, and ready to tackle whatever comes next.
How It Works
Step 1: Talk About Uncertainty, Every Day
Every team has some form of a regular meeting, whether it's a daily standup or a weekly catch-up. Start using this moment to ask a simple question:
“What’s your biggest uncertainty right now?”
Encourage each person to write down their top concern or question that's making them feel unsure in a centralised shared list. If you can clear it up right away, great! If not, decide where and when to tackle it:
- Is it something that needs a bit more discussion? Schedule a separate time to dive in.
- Does it need broader input or a formal plan? Bring it up during planning, estimation, or even retrospectives.
Step 2: Make Uncertainty Part of Planning
When it's time to plan, look at your list of uncertainties and ask: “What can we do to reduce these?” The goal isn't to solve everything at once, just to chip away at it bit by bit.
Step 3: Use Retrospectives to Spot Patterns
During retrospectives, review the full list of uncertainties that came up in the last week or month. Ask yourselves:
- Are there recurring themes?
- Do certain types of uncertainties keep popping up?
- Can these be solved by adding context, talking to other teams, or aligning better?
Step 4: Bring It Into Your Estimates
Now let's add some structure. When estimating projects:
- For small projects, identify one key uncertainty.
- For medium projects, name the top three.
- For large projects, call out the top five.
Capture each one as a separate ticket or task aimed specifically at reducing that uncertainty.
Extra Boosters: Questions and To Figure Outs (TFOs)
Want to supercharge this process? Try these two playful rules:
- Phrase uncertainties as questions. It's easier to tackle an issue when it's framed as a question. Try using "If/then" or "Will/when" formats.
- Turn todos into "To Figure Outs" (TFOs). Instead of listing generic tasks, label them as something "to figure out," starting with a Why, How, What, or When question.
Step 5: Share the Lessons Learned
After working through your uncertainties, capture what you've figured out. Creating a shared "Lessons Learned" list means everyone benefits from what each person has discovered.
Why Does This Matter?
Building great products isn't just about having the best ideas or the most talented team. It's about learning fast and adapting. The faster you can turn uncertainty into knowledge, the better your outcomes.
The Uncertainty List gives your team a safe space to surface these unknowns, talk openly about them, and turn confusion into clarity.
Key Takeaways
Step 1 (Daily): Ask "What's your biggest uncertainty right now?" in standups and capture answers in a shared list; decide immediately if resolvable or if it needs scheduling.
Step 2-3 (Planning & Retrospectives): Use uncertainties to guide what to work on next, spot recurring themes, and identify gaps in context or support from leadership.
Step 4 (Estimation): For projects, identify 1–5 key uncertainties as separate tickets ("To Figure Outs"/TFOs); prioritize based on unknowns, not just scope.
Step 5 (Lessons Learned): Share discoveries from resolved uncertainties so the entire team benefits; celebrate learning and watch knowledge velocity accelerate across the organization.
Related articles
Keep reading

From Writing Code to Validating It: The Engineering Manager's New Job
When AI writes the code, your job becomes proving it works. Testing, security, and quality move upstream. What AI Slop costs teams that don't adapt.

Unwinding the Fidelity: How to Review AI-Generated Prototypes Without the Chaos
AI prototype reviews collapse into chaos because every layer of feedback arrives at once. A 5-stage technique to give human cognition the structure it needs.

AI Is a Magnifier, Not a Magic Wand
AI coding doesn't fix bad codebases, it accelerates them. What pace layers, the simplicity cycle, and cognitive debt teach us about scaling under AI.
Get Product & Tech clarity in one day
200+ assessments. Same-day results. Built by operators who've been on both sides of the table.