Will organizational leaders accept the evidence about incentives and creative work?

Daniel Pink, author of the excellent Free Agent Nation and A Whole New Mind, has a new book coming out in December. Drive: The Surprising Truth About What Motivates Us takes a look at the evidence about the links between incentives and creative, knowledge work. Recently, he spoke about his work at a TED talk in England:

If you’ve been paying any attention at all, his conclusions should come as little surprise. This is simply one more brick in the growing wall of evidence that the fiction of "rational economic man" has long outlived whatever utility it might have had. The evidence boils down to this; if you need creative and original thought out of people, economic incentives don’t work. Creative work comes from internal, self-motivation and requires autonomy, mastery, and purpose.

This is not news. The question that is interesting is whether organizational leaders have finally reached the point where they are prepared to act on this knowledge. If what your organization needs is creative, mindful, independent thought from all quarters and you must finally abandon the pretense that you can elicit that behavior with specific, concrete incentives, then how much harder has your leadership task become? If, to use Pink’s phrase, "sharper sticks and sweeter carrots" won’t work, what will?

The answer comes down to leadership. More specifically, it comes down to the kind of leadership exemplified by Bill Russell of the Boston Celtics. For Russell, leadership was about getting the best out of each of the players on the team more than it was about getting the best out of himself.

Nip it in the bud or wait for the crisis

Twenty five years ago I was running an internal project for the consulting arm of Arthur Andersen & Co, back before it split off to morph into Andersen Consulting and then Accenture. We were creating a system development center to provide all of the development tools and facilities to support large scale information systems implementation projects. This was in the day when serious development was done on mainframe computers and setting up an environment for productive work could chew up a lot of time and fees without adding value for either Andersen or its clients. The centers turned out to be a successful venture for several years.

Setting up the first one was a large scale project management problem in its own right. Some challenges in creating a work plan and work breakdown structure for something that hadn’t been done before, but nothing out of the ordinary.

One odd conversation from that effort still sticks with me. It was early Monday morning, well before 8AM, and I was parked in the partner’s office. I had learned that the only way to guarantee Mel’s attention was to catch him before he got wrapped up in anything else. He rolled in a short time later and the conversation unfolded like this:

Me: I’ve been going over the project plans for the development center. We’re on track, but I’m worried about the scheduled install of the mainframe next month.

Mel: So?

Me: Do we deal with it now or wait until it’s a full blown crisis?

Mel: Wait until it’s a crisis

You need to understand that Mel was and is an excellent manager and leader. But I was certainly greatly puzzled at the time. Isn’t management supposed to be about anticipating problems and dealing with them before they get out of hand?

Consider some of the possibilities at this point, setting aside issues of organizational turf warfare or operating beyond your authority.

  1. Not all anticipated problems materialize. Calvin Coolidge’s observation about problems may apply, "If you see ten troubles coming down the road, you can be sure that nine will run into the ditch before they reach you."
  2. This is a management development opportunity. Someone who reports to you needs to recognize and deal with the problem. It can short circuit or undermine their development if you point out problems before they’ve had an opportunity to see them for themselves.
  3. A crisis can be put to good use. Allowing an issue to become more troubling and more visible may be a necessary step in garnering resources you may need later
  4. You or your organization confuses heroics with effectiveness. This is the dangerous case. If you’re confused, you can either get unconfused or seek out an occupation where heroics are relevant. On the other hand, if your organization (or your client) is confused that can be a serious problem. It takes an astute manager to recognize that "no muss, no fuss" indicates effective management. Or to distinguish between a real crisis and a manufactured one.

In my earliest managerial days, crisis was my too often default mode, out of ignorance and inexperience. Since then, I’ve learned to prefer bud nipping. More importantly, I’ve learned (and continue to relearn) that there aren’t many either/or choices in the real world. What strategies have you chosen when you see a problem on the horizon?

links for 2009-08-11

danah boyd on new habits in a connected world

I have got to meet danah boyd in real life one of these days. Her work, as revealed through her blogging, shows what can happen when you drop a well-trained, smart, and articulate observer into new environments. We all learn from her sharp attention to what is really going on. So much better than listening to what others think is going on.

She’s just posted an illuminating perspective on her recent experience at an academic conference in Italy that brought together a combination of young Turks and old farts. It’s a reflection on the slow emergence of new habits and behaviors in shared public settings; a look at how and why blackberries, twitter, backchannels, laptops, and iphones might actually be making meetings better for all concerned. Here are just a couple of quick excerpts. Go read the whole thing.

There’s no doubt that I barely understood what the speaker was talking about. But during the talk, I had looked up six different concepts he had introduced (thank you Wikipedia), scanned two of the speakers’ papers to try to grok what on earth he was talking about, and used Babelfish to translate the Italian conversations taking place on Twitter and FriendFeed in attempt to understand what was being said. Of course, I had also looked up half the people in the room (including the condescending man next to me) and posted a tweet of my own.

Blackberries and laptops are often frowned upon as distraction devices. As a result, few of my colleagues are in the habit of creating backchannels in business meetings. This drives me absolutely bonkers, especially when we’re talking about conference calls. I desperately, desperately want my colleagues to be on IM or IRC or some channel of real-time conversation during meetings. While I will fully admit that there are times when the only thing I have to contribute to such dialogue is snark, there are many more times when I really want clarifications, a quick question answered, or the ability to ask someone in the room to put the mic closer to the speaker without interrupting the speaker in the process.

My colleagues aren’t that much older than me but they come from a different set of traditions. They aren’t used to speaking to a room full of blue-glow faces. And they think it’s utterly fascinating that I poll my twitterverse about constructs of fairness while hearing a speaker talk about game theory. Am I learning what the speaker wants me to learn? Perhaps not. But I am learning and thinking and engaging.

What will it take for us to see technology as a tool for information enhancement? At the very least, how can we embrace those who learn best when they have an outlet for their questions and thoughts? How I long for being connected to be an acceptable part of engagement.

I want my cyborg life
zephoria
Mon, 13 Jul 2009 18:16:26 GMT

links for 2009-07-07

Bridging analytic and managerial cultures, Part 2

Suppose you buy the notion that management is fundamentally an oral culture and analytics a literate one (see Part 1). How does that influence how you manage analytics? How can you take full advantage of technology?

In an oral culture, what you can think is limited to what you can remember and tell–without visual aids. Oral thinking is linear, additive, redundant, situational, engaged, and conservative. The invention of writing and the emergence of literate cultures allows a new kind of thinking to develop. Literate thinking is subordinate, analytic, objectively distanced, and abstract. It’s the underlying engine of science and the industrial revolution.

Management understands something that those rooted in literate thinking may not. Knowing the right answer analytically has little or nothing to do with whether you can get the organization to accept that answer. What literate thinkers dismiss as "politics" is the essential work of translating and packaging an idea for acceptance and consumption in an oral culture.

The critical step in translating from a literate answer to an oral plan of action is finding a story to hang the answer on. The analysis only engages the mind; moving analysis to action must engage the whole person. Revealing this truth to the analytical minded can be discomforting. It’s equivalent to explaining to an accountant that the key to a Capital Expenditure proposal is theater, not economics. You might want to check out Steve Denning’s book, "The Springboard: How Storytelling Ignites Action in Knowledge-Era Organizations," for some good insights into how to craft effective stories inside organizations.

In addition to helping the analytically biased see the value of creating a compelling story, you need to help them see how and why story works differently than analysis. The best stories to drive change are not complex, literary, novels. They are epic poetry; tapping into archetypes and clich , acknowledging tradition, grounded in the particular. You need to bring them to an understanding of why repetition and "staying on message" is key to shifting an oral culture’s course, not an evil invention of marketing.

Assume you teach the literate types in your analytic organization how to repackage their analyses for consumption. They’ve now learned how to pitch their ideas in ways that will stick in the organization. What might you learn from their literate approach to thought? Is there an opportunity if you can get more of your organization and more of your management operating with literate modes of thinking?

Being able to write things down done permits you to develop an argument that is more complex and sophisticated. On the plus side, this makes rocket science possible. On the negative side, you get lawyers.

On the other hand, if you are operating in an environment whose complexity demands a corresponding complexity in your organizational responses, then encouraging more literate thinking by more members of the organization is a good strategy.

What would such an organization look like compared to today’s dominant oral design? The mere presence of e-mail and an intranet is insufficient. E-mail tends to mirror oral modes of thought, particularly among more senior executives. Intranets tend to be over-controlled and, to the extent they contain examples of literate thinking, are rooted in an organizational culture that strives to confine the literate mind to the role of well-pigeonholed expert. The presence of particular tools, then, isn’t likely to be a good predictor, although their absence might be.

What of possible case examples? A few knowledge management success stories hold hints. Buckman Labs used discussion groups successfully to get greater leverage out of its staff’s knowledge and expertise. Whether this success built on literate modes of thought or simply on better distribution of oral stories is less clear. The successes of some widely distributed software development teams are worth looking at from this perspective.

Although it’s a bit too early to tell, the take up of blogs and wikis inside organizations may be a harbinger of management based on literate thinking skills. They offer an interesting bridge between the oral and the literate by providing a way to capture conversation in a way that makes it visible and, hence, analyzable. As a class of tools, they begin to move institutional memory out of the purely oral and into the realm of literate.

Bridging analytic and management cultures, Part 1

Walter Ong

Have you ever wondered what’s behind the conflict between geeks and suits? Sure, they think differently, but what, exactly, does that mean? A Jesuit priest who passed away in 2003 at the age of 90 may hold one interesting clue.

Walter Ong published a slim volume in 1982 titled "Orality and Literacy: The Technologizing of the Word" that explored what the differences between oral and literate cultures mean about how we think.

Remember Homer, the blind epic poet credited with "The Iliad" and "The Odyssey"? If we remember anything, it’s something along the lines of someone who managed to memorize and then flawlessly recite book-length poems for his supper.

The real story, which Ong details, is more interesting and more relevant to our organizational world than you might suspect. Homer sits at the boundary between oral culture and the first literate cultures.

In an oral culture, what you can think is limited to what you can remember and tell–without visual aids. Ong’s work shows that oral thinking is linear, additive, redundant, situational, engaged, and conservative. The invention of writing and the emergence of literate cultures allows a new kind of thinking to develop: literate thinking is subordinate, analytic, objectively distanced, and abstract. It’s the underlying engine of science and the industrial revolution.

While this may sound interesting for a college bull session, it’s particularly relevant to organizations. For all their dependence on the industrial revolution, organizations are human institutions first. Management is fundamentally an oral culture and is most comfortable with thought organized that way. Historically, leadership in organizations went to those most facile with the spoken word.

At the opposite extreme, information technology is a quintessentially literate activity with a literate mode of thought. In fact, IT cannot exist without the objective, rational, analytical thinking that literate culture enables.

How does the nature of this divide complicate conversations between IT and management? Can understanding the differing natures of oral and literate thought help us bridge that divide?

Technology professionals have long struggled with getting a complex message across to management. In our honest and unguarded moments, we talk of "dumbing it down for the suits." But the challenge is more subtle than that. We need to repackage the argument to work within the frame of oral thought. The easy part of that is about oratorical and rhetorical technique. The more important challenge is to deal with the deeper elements of oral culture; of being situational, engaged, and conservative. The right abstract answer can’t be understood until it is placed carefully within its context.

What management recognizes in its fundamentally oral mind is that organizations and their inhabitants spend most of their time in oral modes of thought. The oral mind is focused on tradition and stability because of how long it takes to embed a new idea. The techniques of change management that seem so obtuse to the literate, engineering mind are not irrational; they are oral. They are the necessary steps to embed new ideas and practices in oral minds.

Repeating a calculation or an analysis is nonsense in a literate culture. Management objections to an analytical proposal rarely turn on objections to the analysis. Walking through the analysis again at a deeper level of detail will not help. What needs to be done is to craft the oral culture story that will carry the analytical tale. It’s not about dumbing down an argument, it’s about repackaging it to match the fundamental thought processes of the target audience.

That might mean finding the telling anecdote or designating an appropriate hero or champion. Suppose, for example, that your analysis concludes it’s time to move toward document management to manage the files littering a shared drive somewhere or buried as attachments to three-year old e-mails. Analytical statistics on improved productivity won’t do it. A scenario of the "day in the life" of a field sales rep would be better. Best would be a story of the sales manager who can’t find the marked up copy of the last version of the contract.

These human stories are much more than the tricks of the trade of consultants and sales reps. They are recognition that what gets dressed up as the techniques of change management are really a bridge to the oral thinking needed to provoke action.

Seen in this light, what is typically labeled resistance to change is better understood as the necessary time and repetition to embed ideas in an oral environment.

Reblog this post [with Zemanta]

Fun with constraints, knowledge, and design

Paula Thornton, my friend and co-blogger at FASTforward, tweeted the following this morning

image

which reminded me of a little constrained exercise I did back in February. That exercise started with this tweet

image

and a blog post that generated some fun discussion.

What I didn’t do was publish the final list of C-words that were ultimately generated in the ensuing discussion. Again, the constraint was C-words relevant to conversations about knowledge. Here’s the list (including "constrain/constraint" that all of you created:

Calculate
Calibrate
Canvas
Capture
Catalog
Categorize
Censor
Certify
Challenge
Change
Characterize
Chart
Check
Cite
Claim
Classify
Cluster
Circulate
Circumscribe
Circumvent
Coalesce
Coax
Co-create
Codify
Collaborate
Collate
Collect
Collude
Combine
Comment
Communicate
Compare
Compile
Compose
Compute
Concatenate
Conceal
Conceive
Conform
Confide
Connect
Connote

Consider Consolidate Constrict Consult
Constrain
Constraint Construct Contribute Converse Convert
Convey
Coordinate Copy
Count
Craft
Cram
Create
Critique
Crystallize Cultivate Curate
Customize
Capital
Case/Case Study
Cause
Channel
Characteristic
Chart
Collage
Community
Compendium
Competence
Component
Concept
Concern
Construct
Content
Context
Convention
Conversation
Culture
Coherent
Complete
Concise
Conditional
Consistent
Contingent
Contradictory
Convergent
Cryptic
Current
Cursory