I am a passionate hobby runner. Every week I run between 20 and 40 kilometers. Sometimes on short 5-km routes, in between times 10 or 12 kilometers and a few weeks ago I even contested my first half marathon. (No it was not a competition, but a private run and the time was not overwhelming).
Some days I run very flat trails and others I decide to do more elevation or a trail run, which then really gets into the legs.
Each run has its own pros and cons and I’m glad for the variety. However, when I would like to do a long run but have little time, it usually goes wrong. Then I’m stressed while running, I start too fast, I’m quickly out of breath and all in all it goes rather crappy then.
Often it is the same for me (and certainly for many other people) at work. We have little time and want to accomplish way too much at once in these short time frames.
Developing new features is usually a good example of how the time factor is often underestimated.
- Research? We know our users.
- Brainstorming? We already know what we want.
- Sketching, wireframes and iterations? Takes too much time.
If you hear this a lot too, maybe design sprints could be a solution for you and your team when starting to work on bigger features.