Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

True, but hard to adjudicate. The problem is how do you differentiate between people who don't pivot because they think the next feature will make them successful and are justified in doing so, versus people who do the same thing but really should pivot? It's tricky because we have all of the following examples:

- People whose initial idea isn't working, but who pivot and immediately hit product market fit.

- People who launch the exact same thing once a year and it finally becomes a huge hit after the fourth time.

- People who pivot quickly and fail, whereas they would have probably been successful had they pushed the original idea to its logical conclusion.

- People who pivot after five years and become wildly successful, but where it's unclear if they would have been as successful had they had pivoted sooner.

- People who pivot and become successful when they would have been better off shutting down and starting over. (e.g. Derek Sivers)

This hits home a lot for me because I always strongly favor the strategy of building some optionality into the product, both for my own startup and when doing consulting, on the assumption that we're probably directionally correct but may be wrong on some specifics (e.g. how a feature should work, who the early adopters will be, what the economy will be like in the future, what the cash flow of the business will be like on any given day, etc.) And I take a lot of shit both for not committing 100% to one specific product and go-to-market strategy, and also for not pivoting fast enough when something isn't working. Go figure.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: