Another dot in the blogosphere?

Beware of “best practices”

Posted on: June 27, 2015

There are a few of my blog entries that seem to get hits every day even though they are a few years old. One of them is “Alternative to ‘best’ practices?“.

That particular reflection was a series of a few. To provide some context, I am listing my thoughts on this contentious issue in today’s entry.

  1. 15 Sep 2012: There is no BEST practice (Contexts may not transfer)
  2. 17 Sep 2012: Alternative to “best” practices? (Contexts are different; best implies there is no need to get even better)
  3. 22 Jul 2014: Can practices be transmitted? (There is signal loss; not all signals are relevant or timely)
  4. 24 Sep 2014: Be wary of “best practices”: Slides 5-9 (Best for whom? Have you considered all contexts?)


Just Beware by MTSOfan, on Flickr
Creative Commons Creative Commons Attribution-Noncommercial-Share Alike 2.0 Generic License   by  MTSOfan 

I was not the first to write against “best practices” and I will not be the last. Here are a few other bloggers or authors who have been more articulate than me with their thoughts about this issue.

  1. The Sham of Best Practices by Larry Cuban
  2. Why Best Practices Don’t Work for Knowledge Work by Luis Suarez
  3. On Best Practices by Shelley Blake-Plock
  4. “Best Practice”—The Enemy of Better Teaching by Bradley Ermeling, James Hiebert, and Ronald Gallimore

2 Responses to "Beware of “best practices”"

KH Yeo: RT @ashley: Beware of “best practices”…



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Click to see all the nominees!

QR code

Get a mobile QR code app to figure out what this means!

My tweets


Usage policy

%d bloggers like this: