Library clips

sharing ideas thoughts and feedback

April 27, 2010

“I am knowledge worker”, says the Janitor

On a post from a while back Andrew Gent spoke about the different types of knowledge workers: generators, brokers, consumers. And for the KM strategy to reflect these groups, rather than one-size-fits all. Peer-to Peer-tools for knowledge generators and the assumption of best practices for consumers…Andrew says:

 "The outsourcing of support is an example of the latter, where the assumption is that the knowledge pre-exists and anyone — even someone for whom English is a second language — can be taught to give the right answers. Here documenting the "right" answers is the primary focus."

Where’s there to go next when you have squeezed all the efficiencies you can out of a process…all that’s left is to be able to sell these skill-based processes as a commodity.

Thus KM being about best practices, rather than supporting knowledge generators.

Andrew highlights the problem here:

"But strategy does not equal reality. What happens in the field often does not match the suppositions of headquarters. And unfortunately — or fortunately, depending on your point of view — knowledge management has to deal both with goals and realities if it is to succeed […] management closest to the field demands support for what is and those at a global level demand support for what is desired."

And then gives an example:

"…there is a significant gap between what can be documented and what happens "on the street"…the case of Xerox technicians who were bombarded with printed information (i.e. "answers") but struggled to solve customers’ problems until they were connected through a community so they could exchange tricks of the trade learned through experience. Almost an exact replica of today’s managers pushing "best practices" to the exclusion of other KM activities."

NOTE: Another example is the knowledge economy of the World of Warcraft.

In this black and white view KM supports strategy (and for any social content to be aligned to strategy), rather than the needs of employees…then you wonder why no-one is motivated to share anything.

Andrew warns to not fall for the lure of strategic alignment:

"KM must stick to KM — actually managing knowledge — not falling for the lure of "strategic alignment". By laying the proper foundation of technical support for collaboration, goals and incentives for individuals, and KM policies and procedures that align with business processes rather than specific, short-term business targets…"

I’m not going to get into "best practices" in this post, but I really like how Andrew puts KM into two camps, the new camp being about support, sense-making (also innovation and learning). This is the place where sharing happens due to enabling intrinsic motivation, and a focus on social capital…basically a distributed way for people to source help and connect with others…making the workers life more empowering, less frustrated…and more engaging.

Bas Reus ponders this:

"It can be the manager that tries to make others only work harder instead of really making them really more responsible for what they do, or it can be the employee that feels like not having enough resources or information he or she needs, or to feel more involved."

Emergent practices

And speaking of emergent practices, lessons applied and the importance of context and conversation, have a read of Nancy Dixon’s post on the eradication of small pox.

Agents in the field applying what they learn daily to what needs to be contextually practiced rather than the top-down generic practice, is a great example of perpetually evolving practice. We need to be able to adapt to the complexities of our situation. If this was done today, the agents could report their experiences in the field using blog posts and comments, and the perpetually changing practice can be updated in the wiki…very agile.

The knowledge worker and routine jobs

A while back the Anecdote blog mentioned that we could do without the term knowledge worker, as even routine jobs require some element of dealing with context.

I agree. Yes a brain surgeon may have to improvise a whole lot more, and use their head a whole lot more, and possess lots of knowledge, way more than a janitor…but this doesn’t mean the janitor is a robot.

This thread has picked up again. A post by Joe McKendrick headed me over to a post on the Big Shift blog, called Are All Employees Knowledge Workers?

The authors are saying something similar to the Anecdote blog post on the false dichotomy that the term knowledge worker creates:

“We increasingly group the people in our firms into two classes: those who have knowledge and talent and, by implication, those who do not. This segmentation is misleading and damaging to firms in the long run.”

The authors say that routine jobs still require thinking:

"When executives focus on "knowledge workers", they lose sight of the fact that even highly routinized jobs require improvisation and the use of judgment in ambiguous situations, especially if the goal is to drive performance to new levels. Many of these improvisations require interactions with one’s fellow humans. Consider the company receptionist. When people walk in the door, or "dial 0 to reach an operator," the receptionist has to engage in a delicate and sophisticated "improvisational choreography," one in which professional competence has to come across through "interactional proficiency.""

We are all knowledge workers…we think and improvise, use heuristics, rules of thumb, and workarounds to get things done…humans are great at self-organising themselves around exceptions to processes, and improvising where processes don’t exist.

The example of the Janitor

Even a janitor’s routine work needs some improvising, see the article Turning a Janitor into a Knowledge Worker.

This article is about micro-managing vs autonomy and leadership…giving the worker some decision-making responsibility as they know their context and local conditions best in order to make an effective and timely decision. Not only does it make for a more agile and responsive organisation, but the worker is more engaged as they have impact on how things are done…they are not just a robot.

In this fictional example the routine work of the janitor is not adapting to mess that is being generated of late due to some new work that is being carried out in different frequencies and parts of the building. The CEO tells the supervisor to cut cost costs and improve quality…the building is too dirty.

The supervisor does a clever thing and gives the janitor some decision-making responsibility…to basically give priority to dirty areas on any given day. As a result the CEO is happy because there are less complaints, and it’s due to the janitor following his own practice.

The supervisor also included the janitor in meetings with sales reps. Where the janitor communicated some issues like wax build up in corners and long waits for the floor to dry between cleaning and waxing, which the sales rep could remedy with different products.

In this story we see that top-down rules and micro-managing are just not adaptive enough, and that localised decision-making and improvisation not only improve agility, but also engagement.

The Janitor and social interactions

Barry Schwartz in his TED presentation refers to Hospital Janitors. It really is a brilliant talk.

Below are some of my transcripts, some bits are verbatim:

Janitors job duties involves no social interaction

Yet when a psychologists interviewed Janitors, they were surprised to hear these contrasting anecdotes:

  • Mike stopped mopping the floor as Mr Jones was out of his bed getting exercise, building strength walking up and down the hall
  • Charlene ignored supervisor orders and didn’t vacuum the visitor lounge due to family members taking a nap
  • Luke washed the floor in a comatose young mans room twice because the mans father who had been keeping a vigil for 6 months didn’t see Luke do it the first time, and his father was angry

The discretion and autonomy of local decision-making of the janitors role improves the quality of patient care.

These janitors think these human interactions (kindness, care, empathy) are an essential part of the job, yet their job description does not reflect practice (reality).

These janitors have the moral will to do right by others, and moral skill to figure out what doing right means.

A wise person knows when and how to make the exception to every rule…janitors knew when to ignore their job duties in the service of others.

Janitors say is takes lots of experience to learn the human interaction part of their job. Experience and time spent with people is important, learning to improvise, try new things, occasionally fail and learn.

"Real word problems are often ambiguous and ill defined, and the context is always changing. A wise person is like a jazz musician, using the notes on a page, but dancing around them, inventing combinations that are appropriate for the situation and the people at hand."

I’m going to revisit this presentation on a future post about excessive rules, best practices and incentives which decrease the quality of moral skill.

More

Michelle Martin reviews Matthew Crawford’s book, which poses whether white collar works get to be creative and think as much as they think they do:

"Ultimately, Crawford maintains,  we are blinded by the idea that freedom to make small decisions–deciding which letter to send to a disgruntled customer or which medication to prescribe after following the decision-tree–is somehow real "thinking," when in fact these merely give us the illusion of problem-solving and independent decision-making. In reality, many knowledge workers are as bound by  quotas, rules, policies and procedures as any factory worker. True creativity, innovation and problem-solving has been leeched out of many of these jobs. At best, creativity for most knowledge workers occurs on the edges."

Mark Gould also posts about Matthew Crawford’s work, which gets into the difference between manuals and practice. The context of situations call for hunches, heuristics rather than rules.

This post was meant to be about knowledge workers, but as you can see it gets into territories such as leadership, autonomy, decision-making, engagement, best practice, context…

Mark Gould’s perspective that I’m sure we all agree with:

"Perhaps knowledge work is actually too easy for people to engage with it properly. By documenting processes in excruciating detail, organisations have simultaneously suppressed creativity and innovation, and created the conditions for inadvertent (but inevitable) error and failure."

Let’s finish off with this quote by Marshall Goldsmith that perhaps encapsulates this whole thing:

"Knowledge workers can be defined as people who know more about what they are doing than their managers do."


April 13, 2010

The fallacy of know-how recipes and hoarding

Filed under: km

The adage "Knowledge is power" makes sense, especially in the context of hoarding in organisations where reward is based on individual action. In a past post I contrasted sharing behaviours in two law firms, the one that rewarded based on the performance of the group as a whole showed much more knowledge sharing, as it was crucial to rewards.

But I think the act of knowledge hoarding can also be a disadvantage to an individual regardless of their reward system.

Know-what

Sure you may withhold some information "know what" about something. The fact that you controlled this information by withholding it, or perhaps controlling it’s flow may benefit you. So sometimes withholding facts benefits us, giving us an edge over others.

But it depends, sometimes sharing some breaking news, or finding something out can get you kudos. Especially in new social online environments where what you say is documented and timestamped…you can never be robbed of being an idea’s person, or robbed of your contributions, if you share them online.

Or in an ironic way you may not disclose to prevent hurting others, or just postpone sharing as letting others in too early may provide a headache.

This is all acceptable.

But the knowledge hoarding we often refer to in KM is about "know-how".

Know-how

The fact that I have the know-how or skill in doing something makes me unique, and I don’t want to share my secrets otherwise I’ll lose my edge.

But is this really true.

I could tell you all I know about running online Communities of Practice (in fact I do both internally and externally), but just because you have all this accumulated information doesn’t mean you know how to do it.

Sure, if I blog about CoPs, my successor is going to have it easier as they can refer to a diary of my experience. Even better that it’s in the context of our company, rather than a generic text book. And even better that it’s in fragments, rather than a manual. Firstly a manual is daunting and you can’t ask it questions, secondly blog posts are raw experiences, whereas documents may leave out juicy peripheral information, and thirdly there is much better recall when capturing as it happens in a blog post.

But the fact that I share is not risky for me, hopefully it can build a reputation, get me noticed by people I don’t know, and get me other places I haven’t even thought of…as I do know stuff that’s beyond my job title :D

I didn’t see that coming

BUT, what could happen in times of trouble is that if the firm considers KM as the same as informal Information Management, they may decide that you are no longer unique now that you have shared, and can get someone else at a lower cost to follow your recipes and be just as proficient.

We know this is untrue, but even so, the firms ignorance coupled with your sharing is the reason you have been replaced…yes you are still unique, but you are left without a job.

Happy ending…the company cannot afford the learning curve, the new hire is hopeless, even with your book of spells, and realises informal information management is not the same as KM, and hire you back as a consultant for double the salary :D

Even if people are able to follow your thought logs and raw documented experience and do a good job as a result, they are not you, they are not the guru, they don’t have the reputation yet, they don’t have the contacts, they don’t have your charisma.  I think it’s more complex than just know-how, people that are competent, amicable, demonstrate leadership and passion, are people you want working for you.

And regardless of all this, as I said in a recent post:

"When you share you are not just a dynamic performer, but you are also helping everyone else to be one as well, and that is reason for the company to actually hold on to you"

But keep in mind I do believe in an equilibrium, and that an element of knowledge secrecy may be needed, but just not as your main differentiator. Here’s the quote:

"Now I agree to not share all your intellectual capital, as we need to survive in a economy based on competition. But, it’s important not to just rely on this as your differentiator."

The fallacy of know-how recipes

Chefs share their recipes in books, but will reading one make me a chef. Even when they do demo’s where you can pickup contexual, peripheral and nuances like: what goes with what, acidic’s, timing, seasonal food, temperatures, etc…it still doesn’t mean I can do it, or that I’m a chef. As I said in my recent post, knowledge is not an accumulation of facts, it’s a way of being…Libraries vs Apprenticeship/Storytelling.

Instead I have to practice it and make lots of mistakes. It has to fit in with my style and mindset with the way I do things, etc…we learn iteratively and over time.

NOTE: This also holds at a group level or process level, where there isn’t a universal way, there is just ‘your way’ that encompasses your context (needs, challenges, obstacles, ability, politics, resources). Again we need to Iterate, refine, experiment, and learn.

Assembling ingredients

Further to this I need to be able to flex my skill in assembling my know-how in applied and unexpected situations. Eg we have people over for dinner in an hour and I need to cook dinner with what I have…improvise.

You need to know the fundamentals, this way you can assemble fragements in new ways.

In this respect we can see personal knowledge fragments as ingredients, and when I’m faced with a situation I bring those ingredients together and assemble them into an outcome. The knowledge is in recalling ingredients for the context and assembling them (knowing how they work together and as a whole). In another context some of those ingredients will assemble with others, and also the assembly may be approached differently. To me, this is know-how!

If I read a book on how to do a sales deal in a particular industry, client engagement, how to make a million dollar in 6 months…it doesn’t mean it will happen. These people are not losing their edge due to people like me following their recipes and becoming millionaires. It won’t happen that everyone becomes a millionaire and knows how to become one, and teaches others…in turn the orignial millionaire is no longer unique.

You are not replaceable because you share know-how, in fact it gets you places.

Just don’t immaculately share everything, share in moderation until our current reward structures based on scientific management get more hip.

April 6, 2010

Knowledge as a way of being, not an accumulation of facts!

Filed under: km

In the lunch area the other day my attention was pulled by the words "Knowledge is being".

These words are printed on the cover of the latest issue of a magazine called "Swinburne" (issue 9 March 2010), here’s the online article I’m refering to.

The header of the article by Karin Derkley reads: "A new centre for Indigenous knowledge and design anthropology is set to shape the way knowledge is shared in Western universities"

The university have engaged Dr Norman Sheehan to establish the centre, he says:

"Too much emphasis has been placed on acquiring and mining knowledge and not enough on developing an understanding of knowledge as a way of being, or existing"

"Indigenous knowledge is a discipline that focuses on knowledge not just as an accumulation of facts, but as a way of understanding and living in the world, informing everything we do. For indigenous people this approach to knowledge is fundamental to everyday life"

NOTE: I don’t agree with his use of the word "knowledge", I’d rather "information", as knowledge is an act and these stored patterns assemble in time of action.

This is totally related to my thinking of late on the fallacy of knowledge objects, and the importance of conversation and context. See my posts:

This article also goes hand in hand with a recent post by Steve Barth called Digitizing or Indigenizing Knowledge?.

Dr Norman Sheehan goes on to say:

"Our aim is to use the laws of anthropology to study how people perceive products and services and how they will integrate then into their lives"

Hmmm, now this sounds like what a Knowledge Facilitator should be doing in the workplace…I briefly mentioned that at the end of my Post-KM post and elsewhere.

This observation and co-creation approach is also related to open innovation (with and within the workplace). Recently I commented on Hutch Carpenter’s post on this topic. Here’s an excerpt of what I said about the benefits of customer/client communities, in making products and services more appropriate and usable. The excerpt I posted as a comment on Hutch’s blog, is from my blog post I published on the customer community:

"Both (the vendor) and it’s clients (like me) benefit from this client community.

This blog post is an example. A manual can only know so much up front, it’s not clairvoyant. The more we experience using these tools in various contexts, situations, purposes and by various people, the more we discover good practices, workarounds, lessons, etc…

Blogs and forums allow us to do this. Perhaps some of this content can be fed back into the manual, but a lot of it will exist complementary to the manual…a wiki is a good way to point to all the gems.

In essence community tools are our coping mechanism. Without it I could not sense-make. Thanks to (the vendor)."
 

Dr Norman Sheehan says something that reminds me of my post about the Corporate plot:

"How do you work with or for people unless you understand how they see and experience the world?"

"You have to reinforce a community from within with programs that include that community’s voice and values"

Maybe if we treat companies more like communities we will have a more engaged and relevant workplace.

Reading the next bit has got me wondering if they are employing Sensemaker from Cognitive Edge:

"…develop a a design-based visual and oral research method for collecting and making sense of data across different cultural understandings. The program uses symbols to track movement in a narrative, allowing marginalised groups to create images to represent their community’s journey towards improved wellbeing" "If you can track narratives you can develop deeper understandings of the social forces that influence peoples’ lives"

In all this article was a pleasant surprise. It’s lists the heart of what KM ought to be about, and sheds the notion of KM as information management.

Get free blog up and running in minutes with Blogsome | Theme designs available here

Related Posts Plugin for WordPress, Blogger...