AKMA's Random Thoughts

April 10, 2003

Blogging Jim McGee

Jim McGee has come to Seabury tonight to talk with us about “knowledge management”; I’ll be live-blogging his talk, of course. You, in turn, will be stuck with my notes.

Jim begins by citing (and showing a clip from) John Cusack in The Sure Thing; a young woman tries to stop him from entering a room, saying, “You can’t go in there,” to which John Cusack replies, “Of course I can — This is America. I can go anywhere.”

Jim argues that most people in organizations have been trained not to think, and especially not to think in public, whereas seminarians are presumably being prepared to go out and preach week after week. But Jim points out that in organizations, the system gets clogged if everyone tries to think; much of the same applies to the educational system in general. Jim asserts that now, increasingly, it’s imperative for people to know how to think in public.

“When is thinking important in organizations?” Jim asks. Why is that? Because they need 5% making decisions about where the ship is going, and everyone else pulling on the oars.

Jim asks what happens to the guy who thinks up the sail; in this system, thinking upsets the established order. The system as designed works as long as everything remains stable, but when the oar-powered boat shows up to fight a sail-powered boat, the old system breaks down.

The time balance the modulates from innovation to a new system has compressed considerably. Much of twentieth-century economic growth has come from (Taylorism, Fordism) extracting more productivity out of a single factory model. That’s reached its limit; now we have to learn what to do when everyone in the organization thinks. We now live in a world where innovation has to fit in as a part of the economic process.

Jim poses the question of what’s real thinking and what’s people pretending to think. He instances political talk shows; someone suggests business staff meetings, and Jim cites Jack Valenti on DMCA, and promotion committees in academic settings. A lot of things pass for thought, but not much thinking; we have, largely, forgotten what thought looks like.

More people in the organization need to be thinking, through the whole organization. Jim’s next example seems to come from a Back to the Future movie, where one character expects another character to write his reports for him.

Jim asks, “Should we talk about knowledge workers or about knowledge management in organizations?” He argues against the idea that only the elite in an organization should do all the thinking, bringing a clip from the Hepburn/Tracy film Desk Set (which according to Jim has some of the sharpest insights into the way that technology intersects with people — Jim laments that hardly anything has changed in the ways technology is marketed and adopted).

Jim cites several illusions expressed in the clip. The first is that knowledge management is about precise answers to exact questions. But knowledge, yoiu can’t touch; you know you’re a knowledge worker if (a) 80% of your time is spent doing things that “aren’t your job”; “It’s not my job” is no longer a reasonable excuse; (c) Your mother doesn’t understand what you do; (d) Your boss doesn’t understand what you do; (e) You don’t understand what you do. Knowledge workers don’t fit onto an assembly line.

But Jim says we all live in this world. How do we even begin to observe what we’re doing in order to improve it under these conditions? What we typically do is to measure productivity with knowledge workers in the same way that we measure the productivity of industrial workers. Can you walk into an organization and see somebody of importance reading a book? Reading a book doesn’t look like you’re busy; we can’t measure the output.

Jim presents a big schema for process in knowledge work. Sorry, no way can I even begin to describe this diagram here. There aren’t very many boxes in knowledge work, and they’re all connected in feedback loops. Well, okay, here’s a try:

Indetify and Frame Problem
Specify Stopping Criteria
Select Appropriate Tools - - Identify and Collect Data
Create Work Products and Deliverables
Evaluate and Assess

(and all these are connected with interwoven arrows)

Douglas Adams’s definition of understanding technology:

1) It’s everything that’s invented before you’re born;

2) anything that gets invented between then and before you turn thirty is incredibly exciting and creative and with any luck you can make your fortune out of it;

3) anything that gets invented after you’re thirty is against the natural order of things;

And Jim changes the slide before I can get number four.

He’s modulating to blogging, now. Weblogs make the process of thinking visible. They’re chronologically ordered, relatively short, categorizable, and available for others to react to. This technology introduces the possibility of beginning to narrate work in project settings that opens up thinking within organizations.

Jim suspects that we have a set of illusions about what thinking looks like. For instance, maybe we get a bright idea and instantly turns into a Harvard Business Review article. Jim applies a business model to his experience of writing a book; the writing process involves experimentation, deletion, reconsideration, and so on, in ways inimical to a linear business plan.

What about blogs in, for instance, parish administration? Jim observes that blogs open up and build community in a new way. They contribute to building a trusted persona; it adds depth and texture to your persona, especially in a parish environment. They offer a way to discover commonalities, shared interests, and make possible personal and community links.

Jim also cites news aggregators as a connection device. Aggregators are the secret amplifier: they bring the new materials all to one spot, and Jim can track his organization as his workgroups split off and tackle various aspects of a problem.

Blogs constitute a tool for an individual knowledge worker: they’e a contemporaneous account of knowledge work activities, a way to increase personal visibility in knowledge work. They make a sharable space for making knowledge public, eliminating barriers to publishing to the web, so that sharing becomes the trivial byproduct of doing. They make a natural fit with communities of practice; weblogs plus aggregators support self-discovering and self-organizing communities of practice.

At this point, the presentation shifted toward a free-for-all discussion. Trevor, in one comment, describes Jeff and Tripp as “the two über-bloggers of the Seabury blogging movement.”

Posted by AKMA at April 10, 2003 07:45 PM | TrackBack
Comments

Thanks for the summary of a talk I hated to miss. It gives me the same feeling as reading Small Pieces Loosely Joined: Gee, I would really like it if the world did change in that way. Do you think it might? To have organizations that could stand for everyone to be thinking and sharing thoughts-- it's like something out of Fast Company (my favorite and only business magazine). To have curiosity recognized as a working asset, outside of academia or even inside? To have parish settings reward an open, trustable, thoughtful persona, rather than wondering why their clergy wasted time dinking around on the Internet? Ya think it's coming?

If I sound wistful, chalk it up to ten years of office work followed by three and a half of studenting. I fear graduation will mark the end of my license to think, and I've really been enjoying it.
lwj

Posted by: Laura Jackson at April 11, 2003 10:37 AM

uber-blogger?

Wow. Who knew?

Laura is on to something and I remain a little cynical. I think that those of us who blog constantly or live on some edge of technological innovation (do we?) are more rare than we know. The pastors at my church recently learned how to do things like attach word documents to email. They have two teen-age daughters, so it is not like they were not exposed on some level.

The church aquired (sp) a network system recently. Very snazzy for 8 computers. At any rate, there is a shared drive, yet these 40 and 50 year old people still insist on giving the secretary paper printouts of letters they type for her to edit and retype. What happens to the original? Well, they delete it after they print it up.

I fear that if this is any indication, that blogging may be far in the future for such people. I worry that some think it strange and a little inappropriate to put one's faith out there to be seen by "just anyone."

I am reminded of Catherine Wallace's remark to us once upon a time at SWTS: "Welcome to seminary. Your faith is no longer private."

Too many thoughts...

Posted by: Tripp at April 12, 2003 07:48 AM

I suppose that one of my questions is, “granted that some people aren’t on board the Cluetrain, do we then simply refuse to board it ourselves? Don’t we rather work all the more hard to do well what we know to be possible?”

Posted by: AKMA at April 12, 2003 10:13 AM

This will allow us to use a few functions we didn't have access to before. These lines are still a mystery for now, but we'll explain them soon. Now we'll start working within the main function, where favoriteNumber is declared and used. The first thing we need to do is change how we declare the variable. Instead of

Posted by: Lucas at January 13, 2004 02:08 AM

The rest of our conversion follows a similar vein. Instead of going through line by line, let's just compare end results: when the transition is complete, the code that used to read:

Posted by: Daniel at January 13, 2004 02:08 AM

Seth Roby graduated in May of 2003 with a double major in English and Computer Science, the Macintosh part of a three-person Macintosh, Linux, and Windows graduating triumvirate.

Posted by: Cesar at January 13, 2004 02:08 AM

Inside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.

Posted by: Joshua at January 13, 2004 10:37 AM

When a variable is finished with it's work, it does not go into retirement, and it is never mentioned again. Variables simply cease to exist, and the thirty-two bits of data that they held is released, so that some other variable may later use them.

Posted by: Barnard at January 13, 2004 10:38 AM

Let's see an example by converting our favoriteNumber variable from a stack variable to a heap variable. The first thing we'll do is find the project we've been working on and open it up in Project Builder. In the file, we'll start right at the top and work our way down. Under the line:

Posted by: Vincent at January 13, 2004 10:38 AM