Best practices, while useful in some respects, are generally “one size fits all” solutions that do not account for the context of unique audiences, products, and businesses. This kills innovation and propels businesses toward a state of mediocrity. To encourage true organic solutions that generate measurable results, businesses should break away from best practices by questioning the status quo and running quantitative tests, talking to users and running qualitative tests, developing multidisciplinary teams, and promoting a culture that embraces risk.
We’ve all encountered “best practices” at one time or another. Be it through a list-style blog post of prescribed industry-standard advice, a how-to speech given to thousands of attendees at conferences across the world, an unsolicited redesign of a popular site, or my personal favorite, a live landing page critique with a panel of industry experts. And yet, while we sit there scribbling down all of this advice, eager to take it back to the workplace, do we ever stop to think about the validity of the advice that we’re being given in the first place?
One of the more abstract and fascinating manifestations of best practices can be found in what I like to call consultant instruction loops. This is essentially where consultants will repackage and resell old advice or flip-flop on conflicting recommendations, where one month they’ll have you doing X, the next month they’ll have you abandon X and do Y, and the next month again, they’ll have you abandon Y and go back to X. And so the cycle repeats itself. The consultant cashes their check while you run your business around in circles like a dog chasing it’s tail. Best practices are not too dissimilar from this. They perpetuate conflicting “one size fits all” advice that is rarely rooted in any actual insight (much less insight that is relevant to your product) and propel businesses toward states of mediocrity.
Of course, there are times where what I’ve just said simply won’t hold true. There are indeed very legitimate, talented, and respectable consultants that would never use consultant instruction loops – and there is no shortage of them. In the same way, there are times when following a best practice is actually the ideal course of action. I myself have benefitted from following best practices many times and I’ve even written about best practices for my readers to follow. In fact, one could argue that what I’m about to give you in this article is essentially a list of best practices for eliminating best practices. The most meta article I’ve ever written. So I fully recognize the exceptions and potential implied hypocrisy. That said, I still take a very large issue with best practices. And I think you should too.
Best practices exist in absence of the context given for your unique audience, product, and business. The data that supports them is not contextual, meaning that best practices are essentially “one size fits all” guesses that try to solve common business problems. The issue with this is that what may have worked great for a business in a different category or even a direct competitor may not work well for your business. It may not resonate with your audience, it may not integrate well with your product, and it may not adequately solve your business goals. Yet we still adopt best practices without much hesitation. Is that really how we should be approaching these matters?
One of the best things about best practices is that they’re universally accessible and applicable. They’re commonly available to the public online and can be immediately applied in the workplace. This is also arguably one of the worst things about them. Because best practices are available everywhere and don’t require much effort to implement, they’re also being used by everyone. This can make it very difficult for businesses that closely follow best practices to innovate and differentiate themselves from the crowd. With a little extra effort and creativity, any organization can break away from best practices, become an innovator in it’s space, and generate true measurable returns. All while their competition chats about the next Hamburger Menu or viral social media trick, only to come up with nothing meaningful. We should all strive to kill best practices.
Being the person that disagrees with and refutes best practices won’t always make you popular. At least, that is for the first few months that you take on the “anti-best practices” role. But with the proper approach, you’ll eventually be able to demonstrate the imperative for organic innovation within your company and truly put the “best practices hype” to it’s final rest.
“But Apple did it…” is not a proper justification for your design decision. Indeed, it can be very tempting to take the easy route and copy a design influencer or even your competitor. Be careful about that. Organizations that truly innovate are the ones that are constantly questioning and challenging the status quo. Just because something appears to have worked for someone else or has always been done a certain way doesn’t mean that it’s the best solution for your company.
I found this out the hard way when I consulted for an eCommerce client that was redesigning their checkout flow. The design that they had was completely outdated; it looked like something from the Windows ’95 era. So, naturally, the designers wanted to bring it into the 21st century and apply Bootstrap styling to everything. Their competition had recently redesigned their checkout flow, so the client took massive inspiration from that and created a new checkout that they were finally proud of. They brought me in to do some final checking on the design, help bring it live, and measure performance afterward.
When I got a first look at the new design, I liked it, but I suggested to the team that we test it against the old design before launching it to the full audience. Unsurprisingly, they didn’t like this idea. It was a shock to them that I had suggested it in the first place. Anyone could see that the new design was clearly superior. But we tested it anyway…and the new design lost. Over time, we were able to iterate on the design and bring it to a point where it was performing better than the original. But that’s not the point here. The point is that our assumptions were wrong. Just because the design was newer, better looking, full of best practices, and a replica of a competitor’s design didn’t mean that it would work for our company. We needed to extrapolate a solution that was unique to our audience, product, and business.
Good designs don’t occur in a vacuum. Or in a boardroom. Or in a best practices post. Good designs have to be cultivated organically. In order to do that, you need to branch out and talk to the individuals that will be using your product. Observe their actions, note their pain points, and identify areas of opportunity. Use this information to extrapolate the optimal solution.
I was recently mentoring a couple startup founders that had put together a new software concept for digitizing certain legal paperwork. As they started to interview potential users and present them with early prototypes, they were able to identify 3 personas for their product. The founders themselves actually fit one of those personas almost perfectly; they were able to conceive the product because they themselves would have benefitted from it. Unsurprisingly, they were also optimizing almost exclusively for their persona because it was the one that they identified with the most. At the same time, however, the other two personas had different sets of pain points and use cases for the product. By focusing on their single persona, they were excluding two thirds of their audience. They needed to remove themselves from the product and gather insight from their full audience (all 3 personas).
Good ideas originate from everywhere. Richard Montañez, Executive Vice President at PepsiCo, was a janitor when he revolutionized the Frito-Lay company and invented their highest selling product, Flamin’ Hot Cheetos. There was nothing in his job description to indicate that it was his responsibility to create a product, manufacture it, market it, and sell it. But he took on that role anyway.
This happens regularly in multidisciplinary teams. Developers will provide input on design, Designers will provide input on code, Salespeople will provide input on marketing, etc. For this reason, it’s important to ensure that you’re working with people that are outside of your job role. Designers should work with Developers, Marketers should work with Salespeople, and so on. When someone has little to no idea of what the industry standard is, they’ll help steer you away from it by introducing their own view of the problem that has nothing to do with how things are always done and everything to do with the best solution for this unique problem.
Matt Rheault, one of my co-hosts on the UX and Growth podcast, recently discussed the concept of Randy Pausch’s “First Penguin Award” and how it can be used to promote a culture that embraces risk. Pausch, a former professor at Carnegie Mellon, developed the First Penguin Award to reward students who took great risks in pursuing their goals, even though they were met with failure. The title of the award comes from the notion that when penguins are about to jump into water that might contain predators, well, somebody’s got to be the first to jump. The First Penguin award is, in essence, a celebration of risk taking.
It is no surprise that companies like Google are adopting First Penguin Awards in the workplace. While not every risk-taking project pans out well, a few that did in the past were responsible for bringing us products like Gmail and AdSense. Rather than focus on sure bets and small wins that force us to resort to best practices, we should embrace risk as a measure of opportunity. While risk may discourage us from taking bold leaps, it should also encourage us to harness opportunities.
While best practices generally aren’t the most optimal solutions, there are times when it makes sense to use them. Certain industry standards and procedures exist for good reasons; they’ve been tested and proven time and time again. Others are simply fads or one-time wins that could never be replicated again, but make for great clickbait headlines. The key is to understand how to separate the former from the latter. By adopting the methodology that I presented above, I would argue that you can do exactly that.
Start by questioning the status quo and running quantitative tests to verify the design changes that you’re making, regardless of whether or not they’ve worked for a competitor. Ensure that you’re talking to users and running qualitative tests that provide insightful feedback, rather than allowing internal stakeholders to dictate the product direction based on opinion or anecdotal experience. When building your team, thrive to hire multidisciplinary individuals from varying backgrounds and pair them with each other so that they can challenge common ideas. Finally, promote a culture that embraces risk and encourages big, new ideas. If you do all of this and still arrive at the conclusion that a best practice is indeed the optimal solution, then it probably is. But you may also discover an entirely new solution that otherwise would have never seen the light of day. Therein lies the true best practice.
