amen. it's far too easy to get stuck in a rut of just building and not shipping and getting feedback.
this happened to me recently. i kept wanting to add one more little feature and improve efficiency, but all that time could have been used in gathering user feedback. personally, my problem is that i've been trying to build too much at once, which makes the build-and-ship cycle awfully long.
but some days, i love seeing posts like these to remind me of how important it is to avoid obsessing about efficiency or features without adequate feedback. negative feedback is better than none!
I still think that some thinking and planning are important, but I agree definitely that speed of implementation is a critical success factor for startup. The shorter your build-and-ship cycle is, the more feedback you can get. In the worst case, if you build something that is not as useful as you expected or that has a negative impact, you didn't waste a lot of time before correcting your trajectory.
this happened to me recently. i kept wanting to add one more little feature and improve efficiency, but all that time could have been used in gathering user feedback. personally, my problem is that i've been trying to build too much at once, which makes the build-and-ship cycle awfully long.
but some days, i love seeing posts like these to remind me of how important it is to avoid obsessing about efficiency or features without adequate feedback. negative feedback is better than none!