|
|
Monday, January 20, 2003 |
Ernie is on to a nice meme here. Another term to throw into the mix is "ethnography." While usually associated with doing anthropology in the field, it's also become a legitimate research tool in organizational settings. I find an anthropological approach particularly useful in the realm of technology for a couple of reasons. First, technology is too dynamic for a lot of other research approaches. Along a similar line, organizational research is not a place where you get to do controlled experiments. It's either impractical or unethical (sometimes both). That leaves you with observational techniques of one sort or another. One advantage of ethnographic/anthropological approaches is that they explicitly recognize that the anthropologist/observer is part of the system. Another reason that I prefer anthorpological approaches is that technology and knowledge management issues lie in a space that Gerry Weinberg describes as "organized complexity." The following diagram comes from his excellent Introduction to General Systems Thinking:
In that environment you need tools that are robust more than you need tools that are precise. You tolerate fuzziness in the answers in exchange for getting answers that are directionally correct in a manageable amount of time. One consequence of doing anthropology is that you have to develop some sense for who the observer is. You're not doing experimental work that can be replicated. You're doing a certain kind of storytelling that depends on observational skills and narrative skills. Unlike a fiction writer, you aren't using stories for the abiilty to make stuff up out of whole cloth (I suppose fiction writers don't really do that either). You are using narrative as a tool to reveal gaps in the logic, to discover what's missing in the logic of the story that will point you toward new things to look for. |
|
[Point of clarification. The resources listed here were pulled together and organized by Joy London on her excellent blog - Excited Utterances. Although it's cited below, some readers missed that, meaning Joy isn't getting the credit she deserves. I continue to struggle with how best to reference material here. My preference is to post all the material that comes through my aggregator and then to add my commentary. I typically indent/blockquote the posted material and add my comments at the end. Once I have some more time to figure out CSS and stylesheets I can probably figure out a more visual way of setting off quoted material from my own stuff. Anyway, Joy did the heavy lifting here. I just used it as a launching pad for a few observations. I also wanted to make sure that I had all these excellent materials ready to hand as part of my use of this weblog as my backup brain.]
An Excellent collection of resources. The issues of proxemics extend well beyond law firms. When we designed our first office space for Diamond in the Hancock building, we made a couple of interesting decisions with the help of Perkins & Will , our architects. For example, we turned all the corners of the floor into team rooms where project teams could work. That left no corner offices to fight over among the partners. The Hancock has great views and we were on the 30th floor. We designed the partner offices with glass partitions separating them from the inner areas so that those views were available. A couple of partners wanted to restrict use of partner offices, but that lasted about 15 minutes. Partners are on the road most of the time, so partner offices rapidly became yet another meeting room for small teams. One little lesson we learned and applied when we added space. The first offices had lots of power and network connections but they required crawling under credenzas to get to. In the second stage build out, the offices had all power and network connections available at desktop height at the back of the desks. |
Slowly catching up with stuff that came through my aggregator over the holidays. This is some excellent thinking on the right frame of reference for thinking about knowledge management. Some key excerpts:
There's a marketing challenge here. While the answer is decentralized, solutions typically get sold to someone who's been put in charge of the problem. Until you've thought long and hard about knowledge management from an operational point of view, the centralized solutions promoted by technology vendors are certainly going to sound like a faster and easier solution to your (i.e. newly appointed chief knowledge officer or equivalent) problem. That they aren't won't be immediately apparent and won't easily be traced to adopting a centralized approach. Making knowledge management work requires a delicate blend of technology tools, organizational sensitivity, patience, and persistence. A difficult message to get across in a technology marketing environment addicted to peddling instant miracle cures. |



