Skip to main content



Because Product is not always a quest for perfection: Advocating "quick and dirty" approaches

  In the last months I have perceived an increasing amount of comments, tweets, etc. about how bad quick and dirty approaches are in the digital product arena. It seems, not quite sure about it, it is part of the anti-agile, anti-lean startup sentiment that is also part of the conversation. As someone who, when leading the presales department of a scale up, pushed the building of a ‘quick and dirty’ culture, I feel pressed to defend it - with some nuances , and even if that means Dijkstra will be on my shoulder my whole life... I mean, if 10 years from now, when you are doing something quick and dirty, you suddenly visualize that I am looking over your shoulders and say to yourself “Dijkstra would not have liked this”, well, that would be enough immortality for me. -- E. W. Dijkstra First of all, it’s clear quick and dirty has no place in mission-critical modules in any sector or industry . I don’t think we are that crazy. Telling a Platform Engineer or Product Manager that they should

Latest Posts

Using a data-driven approach to writing a book