-
This is the start of a NOVA special about the life and thinking of Richard Feynman. A fascinating mind worth studying. The best example I know of of where the relentless pursuit of simple curiosity can take you.
Category: Knowledge work
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
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.
Fun with constraints, knowledge, and design
Paula Thornton, my friend and co-blogger at FASTforward, tweeted the following this morning
which reminded me of a little constrained exercise I did back in February. That exercise started with this tweet
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 |
More on management and messiness – video interview from FASTforward’09
Joshua-Mich le Ross did an excellent set of interviews at last week’s FASTforward’09 conference. We talked some more about the challenges of managing innovation. Here’s the video for those of you who might be interested.
FASTforward 09: Jim McGee, Managing Director of New Shoreham Consulting
February 11, 2009 at 11:15 am Filed under FASTforward’09, FFC09 Interviews
Jim s comments focused on two basic themes. On the plus side is the notion that the heavy lifting of search is being hidden from end users who can t/won t learn to do sophisticated search queries on their own. On the mildly troubling side is something that he posted to the blog about this afternoon. As Jim explained, that post addresses the following notion: one of the management challenges being glossed over in the marketing focus of the conference is that managing search implementations and enterprise 2.0 implementations runs counter to the sense of order that makes most managers comfortable.
To manage these changes requires managers to become much more comfortable dealing with a messy environment. More importantly, perhaps, they need be careful lest they cripple innovation and experimentation by imposing an inappropriate level of management overhead and structure on these efforts. Technology management has become gunshy in too many organizations about technology project failure. They need to be careful to not take those lessons over into Enterprise 2.0 or they will kill the necessary degree of innovation we need to see.
BIO: Jim McGee: For over 30 years, I ve helped executives and organizations become more effective by making better use of information and communications technology. I ve attacked these problems as an entrepreneur, senior executive, professor, author, blogger, speaker, systems developer, designer, and consultant. Today, I work with senior executives in organizations to formulate, structure, and solve problems in the effective use of information technology in complex knowledge work settings. I am adept at working with organizations to recognize patterns and make sense of complex situations. My clients and I then collaborate to design and build new business patterns and practices to take advantage of these situations and opportunities.
Podcast Video: Hide Player | Play in Popup | Download (34)
Management and messiness

Image via Wikipedia
[Cross posted at FASTforward blog]
I’ve been mulling over Clay Shirky‘s remarks yesterday at FASTforward09. The bookends to his talk hint at some key challenges to managers contemplating their entry into the world of social media and Enterprise 2.0. Clay’s opening five word summary of Enterprise 2.0 is simply “group action just got easier.” While he shared a number of excellent stories and lessons, it was his closing discussion of how Amazon added social elements to its existing pages that I want to focus on.
By Clay’s count there are some 16 different social elements that are today part of the typical product page on Amazon. Each of these elements became part of the page as the outcome of an individual experiment. Amazon’s approach is to make it easy, and organizationally safe, to run experiments quickly and cheaply. While there is a technological component to making this experimentation cost-effective, it is the management and cultural aspects that are critical to success.
What Clay is calling attention to is the value to be found in encouraging the fundamental messiness and disorder of invention and discovery. Unfortunately, managers generally don’t become managers because they are fond of disorder. Even managers who have long ago abandoned the caricatures of command and control models are likely to find guiding this kind of innovation a source of discomfort. But it is discomfort that is essential to encouraging the sort of retail level innovation made possible in the technology environment that is emerging.
Nobel Laureate Linus Pauling once observed that “the best way to have a good idea is to have lots of ideas.” That’s the mechanism at work at Amazon and with Enterprise 2.0 innovation in general. What Clay skipped over in his remarks was a look at the number of ideas that were tried and never made the cut at Amazon. This is unfortunate because it can encourage executives to ignore the “lots of ideas” prerequisite to “good ideas.” Amazon’s approach is sometimes portrayed as lowering the cost of failure. More appropriately, it is about lowering the costs of all experiments. While the technology environment is one factor in lowering the cost of experimenting, there are also managerial and cultural costs to manage. For example, if you insist on wrapping too much methodology and project management overhead around experimenting that will discourage ideas and fewer ideas implies fewer good ideas.
This is not a suggestion that there is nothing to manage. Instead, it’s about seeking just enough control. It’s also about becoming comfortable with trusting your people and the process of experimentation and learning.
JP Rangaswami on KM … “Clear, Transparent, Searchable, Archivable, Retrievable”
This has been lurking in my RSS aggregator for quite a while, courtesy of Jon Husband. There is really a lot of highly condensed insight in this post.
Thanks to JP Rangaswami for distilling social computing (in the context of work) to an essence.
From his post “Facebook and the Enterprise, Part 5: Knowledge Management“.
.
“More and more, knowledge management is going to be about reducing the cost of, and simplifying the process for, letting someone watch what you do. Nonintrusively. Time-shifted. Place-shifted. Searchable. Archivable. Retrievable.”
.
Via Dave Pollard via Nancy White
Powered by Qumana
JP Rangaswami on KM Clear, Transparent, Searchable, Archivable, Retrievable
admin
Tue, 02 Sep 2008 13:08:06 GMT
Technology Leaders Association presentation
I’m presenting today to the Technology Leaders Association meeting in Chicago on the topic of “Technology for Us.” I’ve uploaded my slides to Slideshare.
I’ve also tagged a number of links at delicious; both of sites we may check out and references to follow up materials. Those links can be found here.
links for 2008-10-01
links for 2008-09-24
-
A thoughtful analysis of the potential limits of SharePoint as a platform for collaboration in enterprises. I suspect that SharePoint is becoming the "safe" choice for a lot of organizations interested in elements of social networking and Enterprise 2.0. This post offers some insights into the risks of that default strategy for enterprises that become more sophisticated in their approach to collaboration over time.
-
Funny bit of video suggesting where viral marketing efforts might take us if we aren't careful. Enough truth in it to be scary
-
An interesting and insightful analysis to remind us that GIGO (Garbage In, Garbage Out) is still a relevant bit of advice to keep in mind as information systems become more sophisticated and more tightly embedded in organizational decision making. No matter how clever the model, if management wants to get a particular answer they can find a way to do so.