The 4-minute mental model behind Staying curious.
The idea in one line
On the surface, Staying curious can look like a single technique you either know or you don't.
Why it's worth your time
Tools and frameworks change; mindset is what makes a developer adaptable and trusted with ambiguity.
How to recognise it in the wild
1. Spot the moment. Notice when *staying curious* is the move the situation is asking for — usually when it's tempting to skip it. 2. Name the goal. Say, in one sentence, what a good outcome looks like here. 3. See the core move. The heart of Staying curious is simple: ask 'why' five times on something you assumed you knew. 4. Know you're done. You've got it when this stops feeling like a technique and starts feeling like instinct.
What "good" looks like
- You move forward without waiting for perfect clarity.
- You treat the goal — not the ticket — as the job.
- You stay curious instead of defending what you already know.
Next: try the step-by-step tutorial to actually run the rep.