Libby Hemphill research and posts on social media, collaboration, and related technologies

27Mar/090

The Wrongheadedness of Best Practice Thinking

I’ve come across a gem of a book introduction, and I’m writing to recommend that you read it. Yes, all of you. The introduction is from the book Strategic Procurement in Construction by Andrew Cox and Mike Townsend, published in 1998. The shelves of bookstores are crowded with advice for practitioners and business owners about the latest “best practices” for their business or for business in general. I have contributed to the best practice literature myself, trying to make my onboarding research findings accessible and interesting. I’ve been troubled by the literature before; something about the idea of a “best practice” made me wary, much like a “Truth” did when I spent more time with philosophy. I noticed this frustration most acutely when teaching master’s students in a professional degree program. So many students demanded that I teach them best practices, that I tell them what to do in their next job. I tried to explain to students that I was helping them acquire new tools for meeting the challenges information professionals face, not giving them step-by-step instructions for how to do their eventual jobs.

Cox and Townsend argue in their introduction, and throughout the book, that best practice thinking is wrong-headed and leaves us playing catch up. One of my favorite bits of the introduction reads:

They will be searching for the ‘Holy Grail’ of best practice. By this one means practitioners are looking for the answer that provides the solution to all of the problems which they face managerially. Unfortunately, this desire to discover the single solution (best practice), that will allow the practitioner to avoid the need for thought and risk taking, is an illusion.

They go on to discuss concepts such as appropriateness and leverage and recognize that many practitioners would call their discussions “common sense.” Their response?

Some of the practitioners who read these pages may accept what has been said, and argue that this is just common sense (which it is), and that they already know this. If that is the case then this book may have little to teach them, however, because experience leads the authors to conclude that such a form of sense (in a business context) does not appear to be all that common.

I wish I’d written something like that in the paper Andy and I submitted recently that was rejected for having results that were not surprising enough. The results we found in our onboarding study were surprising because we found them and not necessarily in their content. For instance, it’s surprising that teams still behave as though new employees will be immediately productive even though the sense that onboarding takes time is apparently common. Much like Cox and Townsend find that strategic procurement is not all that common, neither are teams who smoothly onboard their new members.

My questions as I continue to read Cox and Townsend’s book are really about how one encourages strategic, reflective thinking over best practice thinking and how one should present research results that show just how uncommon common sense can be. See, one can learn things by studying construction projects. This message brought to you by my dissertation, a work in progress.

2May/070

Innovation in Communities of Practice (1)

Over the last few weeks I've been revisiting communities of practice literature, and I'm writing now to see what I think about it. After all, how will I know what I think until I've seen what I said? I'm channeling Karl Weick again there. Bonus points to my 504 students who recognize that logic. Anyway, moving on to what I think.

The NSF project that current pays my rent is ostensibly about facilitating the development of civil infrastructure. When I was first presented with the project, the part that seemed most interesting to me was the 'transfer of practice' (TOP) problem. The TOP problem goes something like 'it's difficult to move practice from research labs to the real world.' Sure is. I looked forward to working on that problem. As I got into the project more, my focus changed. It seems like now the problem is not so much how do we move a practice from over here in research land to over there in construction but rather, how do the practices of civil infrastructure design and construction change when the materials available change?

Engineered cementitious composites (ECC) have the potential to change the practices of civil infrastructure design and construction. (You can read about ECC's revolutionary properties at the University of Michigan news site.) I don't know enough about that design and construction to yet know what the possibilities are, but I get the sense that they are big and dramatic. Iron and steel certainly made a big difference. Concrete, the rigid kind, is sure important. Imagine what happens when you change the tools again! At least, that's what I'm imagining. With a little help from my colleagues, I'll do some more definitive imagining.

So what does any of this have to do with communities of practice (COPs)? The problem of TOP is something like moving a practice from one community to new individuals. Here, I'm describing what happens when new people learn about ECC and start to learn how to work with it. It's tough to make ' the recipe is incredibly precise and the underlying theory is important ' and it's deceptively similar to regular concrete. To solve TOP, you simply send that newly trained person off in to the world, much like a graduate from the lab at Michigan is now off in the world getting his company to use ECC. Obviously I'm oversimplifying here, but you get the idea. By characterizing the problem of developing new infrastructure as a TOP problem, we make the research lab and its practices the goal, and the 'real world' and its practices the target. This could even be a transfer practice from one community to another problem.

However, that's not what I think is going on. Rather, I think the communities of practice involved are a little broader than that TOP conception allows. I don't think the problem is one of trying to ease the problems with throwing ECC over the wall between lab and field. The really interesting problem, I think, is how does a change in practice within the civil infrastructure design and construction community happen? Much of the existing COP literature is about moving practice from a community to an individual. What about changing a practice within the community? How does that happen?

To start to answer those questions, I'm off to explore a variety of literatures including innovation (generally), innovation (in construction), organizational change, apprenticeship, public policy and infrastructure, and standards development and negotiation. That's just to get me started. I'm likely to blog about this quite a bit in the near future as I try to figure out what I think is going on, or rather where I think something interesting is going on. I'd like to figure out how to study that interesting bit and maybe even get a dissertation out of it.