Product development (and by consequence any software-centered development) is a tricky process, in which you always need to make sure that you’re not only adding complexity but you also can control it. When it comes to complexity controlling, we should focus primarily on 3 pillars: Scope of change Change cost Escape options Scope of change When we think about a new feature, or a new data stream that will be added to the product scope, we should take the time to think about the scope of change. Which parts of the product will be affected by that change? It doesn’t hurt to think a little bit on the negative side: What could be broke down by such a change? How this new complexity is going to be integrated? Thinking about such aspects might give you at least high-level perspective on the affected areas, and thus you can pay more attention to those areas to make sure the complexity is still maintained and under control. Change Cost Think about that like you’re going to be wrong, even i...
Where technology, philosophy, and life experiences meet together.