Step 06 / 06
Underneath
You're always here. This doesn't happen at a moment, it happens underneath.
Some things don't fit in a list because they don't happen at a particular moment. They happen continuously, or they never happen at all.
Waiting
Some things need their time, like a field lying fallow, which looks idle but is actually recovering.
Decisions with no way back need a night in between, and good ideas almost never turn up on the first pass. Going fast has a cost, and it's usually paid in ideas that haven't had time to mature.
With anything that can't be undone I write my answer first, badly, and let it rest. I skip this more often than I should, and it shows.
The rule I use for whether something deserves the wait is simple: if undoing it would cost more than an afternoon, sleep on it.
The notebook
Ten minutes a week: what you decided, why, what you rejected and what would change your mind.
It looks like paperwork and it's the opposite. It's what turns your judgement into something you can consult. While you're the only one who knows why each thing is the way it is, you don't have a system: you depend on being available.
The use that has served me most isn't avoiding repeated arguments, it's telling a bad decision apart from a bad outcome. They aren't the same, and if all you remember is the outcome you'll learn the wrong lesson both times.
Alone or with people
Working alone you're faster and more fragile. You cut without meetings, but nobody tells you when you've spent three weeks on the wrong part.
If you work that way, find somebody outside you can show things to without asking permission, and tell them plainly that their job is to make you uncomfortable. That last part matters: if you don't say it they will be kind, because kind is the default.
With a team you gain friction and lose agility. It's still worth it, because the best thing a team gives you is people who don't think like you. You can always find someone to execute; finding someone with judgement who'll push back is much harder.
That said, every decision needs an owner and not a committee, and the conversation to define something is usually worth more than the definition you arrive at.
What this doesn't fix
It won't tell you whether the problem deserves your time. That isn't a product question and no method answers it.
It doesn't replace having somebody to argue with properly.
And it doesn't cure attachment. In my case it has only moved: I now call something a prototype so I can let myself start it, and then I don't throw it away once it has answered its question. In the end it's the same attachment, just with a different name.
Questions people ask about this
01What order do these steps go in?
No fixed one. You go back to listening after showing it, and back to cutting the day you finally know how to say it. In the end the order comes down to how expensive a mistake is at each stage, and that depends on the project.
02Does this work inside a large company?
The steps do; the timescales don't. All of this comes from small teams with little slack. In an organisation with many people touching the same surface, things that look like overhead here are the only thing preventing chaos.
03Do I need to follow every step?
No. Skip the one your project has already settled. What is worth not skipping is the one you're reluctant to do, because that reluctance usually points at the one you needed.
04How often should I revisit all this?
When something stops fitting. If you revisit it on a schedule it turns into a ritual, and if you revisit it when something breaks, it keeps being useful.
Further reading