One of the most widespread themes in consulting is that there is such a thing as a Best Practice. But deciding what does and does not get that label has often been difficult. I've often avoided using the term myself, preferring instead to simply call my suggestions recommendations instead. By labeling a technique a Best Practice, we are implying that the weight of consensus is behind it, not merely opinion.
So is there such a thing as a Best Practice?
We should not use the term lightly. As discussed by W. Curtis Preston today, it is tricky but not impossible to decide if a practice is truly best. I myself came to the same conclusion through my experience in consulting, and I wrote about the topic in a 2004 column for Storage Magazine.
Curtis defines Best Practice this way:
A technique or methodology that, through experience and research, has proven to reliably lead to a desired result – and should be followed except when there is a valid business or technical reason for not doing so.
Over the years, I've come up with a three-phase test to determine if a recommendation deserves the label, Best Practice::
A Best Practice must meet the following conditions:
- It must be prudent - Nothing should be done unless it is a sensible thing to do!
- It must be widely-used in similar circumstances - Nothing new or untested can be considered Best!
- It must be low-risk compared to alternatives - Anyone telling you to take a major risk with your business ought to take a hike!
I find that my three-part test fits nicely with Mr. Preston's definition. His "experience and research" is a great way of saying "prudent and widely used", and suggests that we should avoid risky moves as well. I don't think I'm going out on a limb to say that we would probably agree on what is, and is not, a Best Practice!
He also points out that we should be careful when applying a recommended practice to our particular situation. Not every best practice is best for you, since every environment is unique. Even if everyone used cloud storage services it wouldn't be the correct choice for every organization and application!
Curtis further states in black and white that we ought to follow Best Practices except if there is a "valid business or technical reason for not doing so". That's a solid point, and goes further than my simple litmus test. Best Practices aren't merely good ideas; they're must-follow directions!
Given this, though, who do we listen to when looking for "best practice recommendations"? Should we just take the word of a vendor, systems integrator, or consultant? These should not be rejected out of hand, but it is up to everyone to apply the three tests themselves when presented with a course of action. Use your gut: If you think it's prudent, widely-used, and low-risk, then go for it!
So Best Practices are much more than just shared opinions. Certain strategies meet the requirements for most situations, and others don't. And we all ought to seek out what's Best, keeping in mind that everyone's situation might negate any one of them.