This sounds like quite the opposite:
> The takeaway? Don't stress over all the things you are not doing but focus on the few you are doing right.
The only advice is to not sweat over things you don't do. Do you suggest one should?
As a business owner, it resonates with me.
To be fair, all startup advice is completely random advice. Really, there's no guaranteed rulebook for success, so everything should be taken with a grain of salt.
So for example "we just used Heroku" might stick in the craw of developers who think AWS Lambda based microservices are the future, but for a small startup with limited resources and time Heroku is probably a safe bet.
You need to stop focusing on all the things you’re doing incorrectly and focus on the things you’re doing well that are working for you.
If you take any of the items they said they didn’t do as a recommendation to not do that thing then you’re missing the author’s point.
But of course this is much easier to say than to put in practice; "what needs to be done" is very hard to know, while random generic advice is always top of mind.
So then we shouldn’t follow the advice in this article either.
Maybe we should just do nothing lest we follow someone’s advice.
Their advice is to not cargo cult. Not to ignore all advice.
What that would mean is that even for the advice that they give, not to cargo cult, you need to examine whether that’s actually good advice or not.
It may turn out that your product is a component library, in which case, being in the spaces the cargo cult tells you to be it may actually make sense for you to follow, because that’s where the largest market would be.
And you don’t have either without some level of traction. Which in turn requires a GTM strategy and money to execute on it.