The Iterative Roadmap

define and practice a Roadmap based on shorter commitments. To iteratively commit to roughly 4-5 Deliverables with higher certainties, while keeping the Roadmap in mind to avoid Blockages and disappointments.

Detailing Disappointments

In this chapter, we’ll deep dive into the Details themselves. We’ll see why they are another source of disappointments, one out of commitment to content and design; And we’ll see why they are also a source for potential Blockages and inefficiencies. Through both, we’ll learn how to make our Roadmaps even more beneficial.


So far in this series, we’ve talked a lot about Blockages, code and design decisions that later need to be Changed or removed in order to continue to make progress. A source of inefficiency. We’ve treated them as something that is necessarily evil, something non-beneficial. We’ve looked at them as an unwelcomed and unintentional outcome. But using them correctly and intentionally, we can leverage Blockages to our own goals. To use them as a Restriction to others, to prevent them from causing future inefficiencies. And that would be beneficial.

Long Term Roadmaps

In this chapter, we’d wish to apply Restrictions but only with a more product/business perspective. To see what is the Product Roadmap, and how Restrictions would help us achieve another goal we have, to avoid execution of valueless tasks. And lastly, although The Iterative Roadmap is excellent for execution, we’d come up with another kind of Roadmap better fitted and easier for long term planning.