I suspect the essay itself might be an example of worse-is-better principle applied in practice. :)
My first impression was that author basically recommends quickly releasing ‘minimal viable products’ and expands on what should be considered ‘minimally viable’ for some specific kinds of software.
‘Worse is better’ is an interesting way to put it, though. I think it can be applied widely.
One way to avoid perfectionism is to constantly remind ourselves what's important, what's in MVP. Sure, there are a lot of things that are important for good product, but some are more important and we should focus on them first.
On the other hand, we can just remember that ‘worse is better’. No need to make yourself focus on what's important—it will come naturally once you label everything else ‘worse’.
It's hard to explain and I may have missed author's point, but that was one of takeaways for me.
Comments
I suspect the essay itself might be an example of worse-is-better principle applied in practice. :)
My first impression was that author basically recommends quickly releasing ‘minimal viable products’ and expands on what should be considered ‘minimally viable’ for some specific kinds of software.
‘Worse is better’ is an interesting way to put it, though. I think it can be applied widely.
One way to avoid perfectionism is to constantly remind ourselves what's important, what's in MVP. Sure, there are a lot of things that are important for good product, but some are more important and we should focus on them first.
On the other hand, we can just remember that ‘worse is better’. No need to make yourself focus on what's important—it will come naturally once you label everything else ‘worse’.
It's hard to explain and I may have missed author's point, but that was one of takeaways for me.