LEARN THE MOVE
False Assumptions
In our work and life, we often operate on unverified beliefs that we treat as facts.
The crocodile relies on your assumption that calm water equals safety. False Assumptions forces you to question that 'calm' so you aren't caught by what's lurking beneath the surface
EXAMPLE
A team is launching a new software feature. The "calm water" is the fact that their beta testers haven't reported any bugs.
EXAMPLE
Assumption: "No feedback means the software is stable and easy to use."
EXAMPLE
Why do we believe this: "We sent it to 50 power users and haven't received a single support ticket in two weeks."
EXAMPLE
What happens if this isn't true?
What if the silence isn't because it's stable, but because the interface is so confusing that testers haven't even figured out how to start using it? Or what if the notification system is broken and their feedback isn't reaching us?
EXAMPLE
The team could use this to explore further or maybe even explore watching users interact with it to observe potential issues instead of waiting for feedback.
By questioning the assumption, you explore opportunities and think more innovatively.
Ready for your first False Assumptions?
False Assumptions
Creative
Created on April 21, 2026
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Essential Business Proposal
View
Project Roadmap Timeline
View
Step-by-Step Timeline: How to Develop an Idea
View
Artificial Intelligence History Timeline
View
Mobile Phone Call
View
Momentum: Tools Tutorial
View
Momentum: Onboarding Video
Explore all templates
Transcript
LEARN THE MOVE
False Assumptions
In our work and life, we often operate on unverified beliefs that we treat as facts.
The crocodile relies on your assumption that calm water equals safety. False Assumptions forces you to question that 'calm' so you aren't caught by what's lurking beneath the surface
EXAMPLE
A team is launching a new software feature. The "calm water" is the fact that their beta testers haven't reported any bugs.
EXAMPLE
Assumption: "No feedback means the software is stable and easy to use."
EXAMPLE
Why do we believe this: "We sent it to 50 power users and haven't received a single support ticket in two weeks."
EXAMPLE
What happens if this isn't true?
What if the silence isn't because it's stable, but because the interface is so confusing that testers haven't even figured out how to start using it? Or what if the notification system is broken and their feedback isn't reaching us?
EXAMPLE
The team could use this to explore further or maybe even explore watching users interact with it to observe potential issues instead of waiting for feedback.
By questioning the assumption, you explore opportunities and think more innovatively.
Ready for your first False Assumptions?