You don’t need to expressly work this stuff out, you just need to have an idea of what you’re about to tackle. And then the next.įiguring out the next most important thing involves the value of the addition/change vs the cost (in time, money, and other resources) of the change. Then when that’s done you can move on to the next most important thing. When you prioritize correctly you’re always working on the next most important thing. Prioritization is a huge part of keeping things simple. That’s where opportunity cost and prioritization come in. When things are a lot of work you have to consider what else you can’t work on because of it. How you handle the “also” is what separates greatness from mediocrity from failure. The first thing you’ll hear from customers that love your product is how they’d love it even more if it did this or that also. This reality reveals itself on release day. A product people can live without can become a product people love, but once you’re at the love stage it can turn around on you just as fast. Then the product people can live with can turn into the product people can live without. Then the product people liked can turn into the product people can live with.
Or worse, something you can no longer manage or control.Ī product people loved can turn into a product people liked. Without a clear understanding of the limits and boundaries of your product, the product will morph into something you no longer recognize. The dilution effect is why maintaining a clear vision for your product is so important. That’s not always a bad thing, just be aware of it. What’s the most ignored paradox in software development? Every time you add something you take something away.
Every time you add something you take something away Jason 103 comments
0 kommentar(er)
