A daily newsletter on building software products for non-technical founders. Give me two minutes a day, and I’ll help you make technical decisions with confidence.
Once your team’s processes are working well, development can sometimes transition into feeling endless. And by contrast, have you noticed how work seems to somehow get done when it’s subject to an immovable deadline? This phenomenon aligns with Parkinson’s Law, which states: “Work expands to fill the time available for its completion.” Without clearly defined time periods, work in progress can become virtually infinite, with no clear sense of when it should end. This is why establishing cycles with fixed time periods is so important. For example, many teams follow these cycles:
(37 Signals use 6 weeks. See their book Shape Up for a detailed description of how they use cycles.) Each cycle has a goal, and the shorter cycles contribute towards achieving the goals of the longer ones. By assigning all work to a specific cycle and its “owners,” the purpose of each task becomes clear to everyone involved. This clarity ensures contributors understand what to prioritise and encourages them to make tradeoffs to fit the scope into the time available. Equipped with purpose and structure, developers can make better decisions that directly benefit your business. The alternative? Developers working on the “fun” stuff instead of initiatives that actually move the needle. Investing in a disciplined, cyclical approach may not sound exciting, but it yields substantial benefits, including:
Ultimately, this structured framework allows your team to thrive - not just deliver work, but deliver meaningful progress. |
A daily newsletter on building software products for non-technical founders. Give me two minutes a day, and I’ll help you make technical decisions with confidence.