Monday, August 30, 2010

Define "Best Practice"

I especially like when we can determine a process which is "best practice"

What does that mean though?

I generally assume people identify this through various degrees of understanding other options, trying lesser performing things and landing upon the "best practice." This is also generally based upon sound, fully vetted research and practically exercised by leading (read: large, profitable enterprise) organizations.

Although, often times it's complete horeshit. It's a way for others to rally around the idea of being "best practice" or "best-in-breed" despite the trueness and/or validity of the claim.

Also, my best practices are not necessarily yours, nor should they be. Context is forgotten and we're blanketed with the assumption of conformity. In Software, it's all about lead gen, sales tools and development methodology. I can sell you on a agile methodology and why it's critical and provides the best output and product in a lean organization. Although, it may not work "best" for you, in your world, with your product, challenges and people.

So, in the end - while the idea of nominating and classifying things, practices and products as "best" is a good idea. Context is crucial. Don't get sold by the color of the paint.

Like the army preaches - be the best YOU can be.

0 Comments:

Post a Comment

You've selected the option to respond to this post:

Subscribe to Post Comments [Atom]

<< Home