When you’re on a sprint, you feel a sense of momentum. Momentum is a powerful tool to keep you focused and positive. It gives you energy. It pushes you forward. When you’re walking you don’t feel that same momentum. Or at least, I don’t.
But the thing is, the walks are important too. The walks answers the question, where to next?
If sprints are execution, then the walks are product strategy. You need to figure out where the next sprint will take you.
I’ve found it useful to understand these differences and to acknowledge these two distinct modes up front. I ask myself, am I in a sprint or a walk? Then you can adjust your expectations. In a sprint phase, the expectation is to do as much as possible; to execute.
But in a walk phase the expectation is different. You need time to let ideas germinate, to figure things out.
It’s not just expectations that change but also behaviours. In a sprint phase, behaviours are narrow. As an indie developer, execution boils down to basically one task, programming. Everything else comes at the opportunity cost of time spent coding.
But during a walk phase, the behaviours are broader. You might research a new market. You might talk to potential users. You may read a book to find inspiration or listen to a podcast to nurture some new trail of thought.