There was a post on Reddit the other day about some kid (relatively speaking) who coded a vibe coding app in his spare time and sold it after only four months for something silly like $80 million. Conventional MBA wisdom says you should deep-dive into a market you have at least a decade of experience in, do exhaustive market research, develop an ICP, interview potential customers, iterate, design, overthink…etc. We're told stories about guys like Phil Knight and the nearly two-decade grind to turn Nike into what it is today. What gives? Why do some people struggle where others just... don't?
Sarah and I have been talking a lot about best practices vs antipatterns while working on landing pages and positioning for our tattoo booking platform. The question of mentioning competitors in our marketing came up. The received wisdom is: never mention competitors in your ads. You don't want your brand permanently linked to your competition. But then why does almost every SaaS website have an "us-vs-them" section laying out how their features compare to everyone else's? Working through that question brought us to a few conclusions: blindly following dogma (the belief system, not the film) is a bad idea, best practices should be guides not gospel, breaking too many rules at once tends not to end well, and you, the business owner, need to be the one steering.
My career has given me a front-row seat to some pretty spectacular failures and successes. I know for myself that experience is the best teacher (we'll blame my ancestors and my upbringing for my stubbornness). Somehow, I've learned that there's real value in studying other people's paths. Best practices are where that value lives: not as rigid commandments carved in stone, but as a collection of hard-won lessons you can adapt to your own situation. They're like maps drawn by previous travelers: useful for general direction, but not necessarily the only way to get where you're going.
This still feels uncomfortable. Why did this kid win the game of capitalism? He caught a once-in-a-generation opportunity. He saw the cultural moment around AI-assisted coding, had the right network, the right tools, and hit at exactly the right time. When you dig a little deeper, though, you'll find he still followed a lot of best practices, just compressed into a very short window.
Almost paradoxical, right? Ignore all the rules, but also follow all of them, be lucky, and have rich parents. Done! I think it's more useful to get clear on what you're actually trying to accomplish first. A clear goal makes it easier to know which advice applies and which you can safely ignore. And let's not try to lawyer our way out of this. My daughter is a professional: "I want to make a billion dollars in six months!" Great goal, not very practical.
A clear goal gives you something to measure decisions against. Best practices say never mention competitors in your marketing, but your B2B SaaS clients need to know how you stack up. Do you have the feature they need, and how is it different from the other options? The advice to have a clear goal is everywhere for a reason. North star, guiding light, X marks the spot. It keeps showing up because it keeps being true.
Once you have something to aim for, you can use best practices deliberately, or break from them when it makes sense. Instead of following each one religiously, ask yourself "why does this exist?" and then "does this actually get me closer to my goal?" Sometimes taking only the relevant part of the guidance, or running a small test, cuts through the noise faster than anything else. This is especially true in software, where updating a page or shipping a small change is a lot cheaper than a test run of thousands of physical widgets.
So if a clear goal is your north star, think of best practices as your compass. A compass doesn't tell you about the terrain ahead (the unexpected swamps, the sudden mountains), but it keeps you pointed in the right direction. It's a tool, and its value depends entirely on the person holding it. The kid who sold his app didn't throw out his compass; he just used it to move through a very different, very fast-moving environment than the one Phil Knight crossed. The goal isn't to memorize the map. It's to learn how to read the terrain, trust your compass, and know when to cut your own path because the old roads don't go where you need them to.
With that, go break a few rules, but not too many! And good luck out there.
-Sethers