Too hard? Take more steps


I’ve been stuck on a few tasks of late. Where to start, how to finish, what finished even looks like, and thinking that middle part is a murky chasm which reinforces procrastination and self-doubt.

Jessica Joy Kerr proposed a solution that seems so friggen obvious with hindsight:

When something gets a little bit hard, I ask: how can I do this in more steps?

It works in code: more lines, more variable names, easier to read and understand later. Walk my future self through the process.

It works in household tasks: making coffee, the beans are on a high shelf. Get a ladder; get the beans; put away the ladder. Each small step is safer than the single hard step of reaching the beans without a ladder.

As my favourite software lecturer used to say, it’s better to be clear than clever. He was talking about code reviews, but it easily applies to tasks you assign yourself. We all think we’re clever, but “do X” in your task manager feels far less intimidating if it has “do A, B, and C” subtasks underneath.

I’ve applied this thinking to a few personal and work problems again this week, and it’s really helped. It also dovetails beautifully with what Merlin Mann discussed in 2013:

Every time you realise a dependency, you get closer to what you need to do.

Author bio and support


Ruben Schade is a technical writer and IaaS engineer in Sydney, Australia who refers to himself in the third person in bios. Wait, not BIOS… my brain should be EFI by now.

The site is powered by Hugo, FreeBSD, and OpenZFS on OrionVM, everyone’s favourite cloud infrastructure provider.

You can leave me a comment by contacting me, and I might publish your thoughts. Please read the FAQs first though.

If you found this post helpful or entertaining, you can shout me a coffee or buy some silly merch. Thanks!