Business Problems and Root Causes

Thanks to Jon Husband for pointing this one out. I’ve been a fan of Evelyn Rodriguez’s Crossroad Dispatches for a long while. Her writing challenges me to take risks that I don’t always rise to, but always appreciate.

Business Problems and Root Causes

A delicious discovery whilst browsing this morning …

From Evelyn Rodriguez’ bio on her blog Crossroads Dispatches:

If one could honestly assess the root cause of many business problems – it’d be these intimately related concepts: being open is dangerous and being guided by the echoing fear in our heads is safe.

– Evelyn Rodriguez

Powered by Qumana

A nice substitute for plant tours

One of the enduring benefits of being a consultant over the years has been the opportunity to go on more than my fair share of plant tours. I love the chance to learn about all the ingenuity and creativity that goes into making stuff. If you can’t get to the actual plant tours, here’s one good alternative. Thanks to lifehack for the pointer.

How do they do that?

The National Association of Manufacturing has been posting a weekly video for over two years that shows how things are made. This is a great way to learn new information while being entertained. Some of their past topics are linked below:

The series has been going on for over two years which means there are well over 100 videos available.

How things are made – [Shop Floor]

Indexed – a daily regimen to prevent dumbth

Comparing the average management self-help book to Nigerian spam may be a bit harsh. On the other hand, I’m also finding indexed to be a welcome daily provocation. Makes a point and makes you think. I think of it as a daily dose of insight to help avoid succumbing to what the late Steve Allen described as “dumbth.”

Modern snake oil

card614-1.JPGThis delightful sketch comes from indexed, a blog which is worth a daily feed. Having spent a lot of time in airports recently the sheer number of shelves devoted to simple guru based recipes is scary. Everything is made simple, reduced to simple steps, off the shelf recipes and impossible problems. Snake-oil salespeople have been around for a long time and they persist. Nigerian spam is just a difference of degree from the average self help book.

Strategic sensemaking and Enterprise 2.0 technologies

The increased importance of sensemaking will prove to be one of the central drivers for Enterprise 2.0 technologies adoption. Organizational theorist Karl Weick positions sensemaking as one of the central tasks in organizations. Dan Russell at Creating Passionate Users provides a nice definition of sensemaking that will serve as a useful starting point:

Sensemaking is in many ways a search for the right organization or the right way to represent what you know about a topic. It’s data collection, analysis, organization and performing the task. [Sensemaking 3]

The value of the sensemaking notion in organizational settings is that it highlights the active requirement for managers and leaders to construct sensible accounts out of ambiguous, ambivalent, equivocal, and conflicting data. In a world (imagine Don LaFontaine here) characterized by significant technology, organizational, and strategic change, the problem of sensemaking becomes more acute.

It occurs to me that there is an useful analogy to be made between sensemaking and open source development practices; in particular with the adage that “with enough eyes, all bugs are shallow.” Instead of counting on the insights of a mythological strategic genius, you distribute the problem to the wider organization. Many of the more interesting strategic planning processes (think scenario based planning and future search conferences, for example) are ultimately grounded in that notion.

One of the attractions in Enterprise 2.0 technologies is that they make these strategies more feasible and scalable. Blogs, wikis, tagging, etc. allow participation to scale beyond what face-to-face methods can support. They make it possible to generate and organize more extensive raw materials and inputs to planning/sensemaking processes. Wikis with good version tracking and refactoring capabilities make it both safer and easier to generate and work through alternative representations/sensemakings.

Realizing this sensemaking potential will require brokering some introductions and partnerships. Those adept in the techniques are likely to not be versed in the ways that the technologies reduce or eliminate some of the key barriers to successfully using the techniques. Those who understand the technologies may not be aware that the techniques exist, much less that they could benefit from technological improvement. One starting point I would suggest is for those promoting Enterprise 2.0 technologies to investigate the sensemaking planning techniques and practices and map points where the technologies enable, simplify, or improve the techniques.

A few quotes to ponder

 I found these at a blog I’ve recently added to my news aggregator. Both the quotes and the blog are worth your consideration.

Some quotes I really liked

Found these in a completely different context (a discussion group about Prediction Markets); thought that they were wonderful descriptions of the “provisionality” of blogs. See what you think.

Richard Feynman:

In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth.

Niels Bohr
:

Never express yourself more clearly than you think.

[Confused Of Calcutta]

Actually there is another good Feynman quote in the comments to this post that is also worth calling to your attention:

Richard Feynman

For a successful technology, reality must take precedence over public relations, for nature cannot be fooled

Chuck Frey’s latest mind mapping research project

Chuck Frey is doing a new research project on the uses of mindmapping. If you’re using mindmapping tools take a few minutes to help with his research.

It’s now time for my next research project. This time, I’m focusing on issues like sharing your maps and collaborating with others, exporting maps into other data formats and a “wish list” of future software capabilities. This survey also includes several open-ended questions, where you can share your thoughts and opinions with me and your peers.

Please take a few minutes to complete this brief, 10-question survey:

http://www.surveymonkey.com/s.asp?u=323173213778

I look forward to your thoughts! [The Mind Mapping Software Weblog: Please participate in my latest mind mapping software survey.]

Tips for gaining adoption of Enterprise 2.0 technologies

[cross posted at FastForward blog]

We’ve been challenged to offer tips for gaining adoption of Enterprise 2.0 technologies by  James Dellow and James Robertson. Of the responses so far, I confess that I am most aligned with Euan Semple’s, who suggests that perhaps the call for adoption advice is premature. Here are some thoughts on adopting these technologies beyond the general strategies that apply to any collision between new technology and an organization.

  1. Start with your own learning. You are the target user base. Moreover, these are technologies whose value is not easily understood from casual use or from reading someone else’s account. Set up a blog and start keeping a daily journal with it narrating your work.
  2. Use Enterprise 2.0 tools to do your research on Enterprise 2.0 Get an RSS Reader and start subscribing to blogs talking about these technologies. Use your private blog to post items from your reader with your thoughts and reactions. Set up an account at del.icio.us and start using it to track your web surfing. Use a wiki to start organizing your research into a business case and plan for your organization.
  3. Find and enlist co-conspirators. Ignore the issue of resistance to organizational change. Route around it. Find a handful of other individuals you work with to join you in your efforts. If possible, include collaborators outside your organization as well. Examine and reflect on your struggles and mistakes as you learn.
  4. Ignore the IT organization or co-opt it. These technologies are inherently subversive to the established order of things in most organizations. Don’t fight it, exploit it. Start with services outside the firewall, unless you can find a sympathetic friend inside the IT organization who will help set up a sandbox server to play with. Don’t get caught up in trying to fit in with the existing technology architecture or standards. You’re initial objective is to understand how this class of applications interact with the business processes in your unique organization. Don’t fall into the trap of thinking the problem is about technology.
  5. Fix a broken process. Once you’ve developed some grounded experience with these technologies, you’ll be able to identify the process in your organization that can visibly benefit and that you have the power and authority to fix.  

Absent a specific organizational situation and a specific problem, I fear that most tips will, of necessity, be very generic.

 

Sensemaking practices

There is an excellent discussion of learning as sensemaking going on over at Creating Passionate Users.  Dan Russell has a series of posts (Sensemaking 1, Sensemaking 2, Sensemaking 3) about his thoughts and practices when he takes on a new research based project. In addition to the value of Dan’s thoughts, each post has also sparked excellent discussion threads, which are also worth your time.

Here’s a definition of sensemaking that Russell gets to today:

Sensemaking is in many ways a search for the right organization or the right way to represent what you know about a topic. It’s data collection, analysis, organization and performing the task. [Sensemaking 3]

Sensemaking is a concept I’ve found useful and valuable in much of my work in organizations. I first encountered it in the writings of organizational theorist Karl Weick (e.g. .The Social Psychology of Organizing). Central to Weick and Russell’s thinking is that understanding is something you build over time as an active effort.

My sensemaking practices run along the following lines.

Data Immersion and Convergence. Like Russell and many of the commenters on his posts, immersing myself in the data is a primary component in my sensemaking practices. If I’m doing work inside an organization that includes getting my hands on whatever previous work I can find, public information, interviews, and keeping my eyes and ears open. I am a fan of Yogi Berra’s advice on this; “you can observe a lot just by watching.”

I’ll generally wrap up the initial data collection when things start to converge and get repetitive. Sometimes, this represents a plateau and more data collection will be needed later. More often than not, I have reached to point of diminishing returns and more data by itself won’t help.

Mindmapping and Issue Finding. I’ll draw a variety of mindmaps over the course of most projects. In them, I try out various ways of organizing and relating what I currently know and don’t know. In particular, I’m looking for issues and themes that provide a way to account for the data. With the advent of good software tools for mindmapping (e.g, MindManager), I have started to use my mindmaps as the primary tool to organize and link to the various data I am collecting.

Trip Reports. I’ve mentioned trip reports before as one of my sensemaking habits. At the end of a day collecting data I write myself a memo trying to understand what I might have learned. In my early days as a doctoral student, these were Word documents. They’ve since morphed into private blog entries. They are not transcriptions of my interview notes. Rather, they are first attempts to put my thoughts into story form.

Pictures and Diagrams. Stories are one form of sensemaking, pictures are another. I will play with various kinds of pictures and block diagrams to see what they might reveal about the subject at hand. I almost always start with hand drawn diagrams. If I need to share the drawing, I’ll create an electronic version in Visio. One problem that I sometimes encounter with sharing diagrams in Visio is that they may appear more “precise” than warranted. A partial solution I have had some success with is to use a font called Charette courtesy of the folks at Mindjet. This is a font the mimics the hand-lettering you might see on blueprints and helps convey the notion that what you are looking at should be seen as provisional and subject to revision and elaboration.

Tony Buzan’s advice on how to create mindmaps

This video clip of Tony Buzan on mindmapping is making the rounds. Jack Vinson and Chuck Frey also pointed it out. According to Buzan there’s a right way and, by implication, a wrong way to draw mindmaps. I suspect Buzan would give me low marks on how I make use of his technique. What good is a tool, if you can’t twist it to your own purposes? In particular, I ignore the “one word per branch” guideline in favor of one chunk per branch. Regardless, I am still a proponent of the technique, both manually and with whatever software tools best suit your style. And Buzan’s Mind Map Book remains your best starting point.

Excellent mindmapping video (and a couple of links)

Really great YouTube clip of Tony Buzan holding forth on the features and benefits of mindmapping. Fascinating stuff from the master himself….

Relatedly, for utter information overload, check out this list of mindmapping tools. Or, check out this relatively recent list of narrowed down options. That second list turned me onto Gliffy, which is best described as free Visio in a browser–very excellent tool for diagramming, but I don’t think it’d port well to mindmapping.

Slacker links: Management Craft
Lisa’s blog is full of good advice.

The Procrastinator’s Clock – User-centered design at its best

Now this is the kind of tool that demonstrates a deep understanding of its target users. Probably wouldn’t help me, as being late to scheduled events isn’t my particular procrastination issue, but I appreciate the design insight.

The Procrastinator’s Clock

clock.gif

If you’re a procrastinator, you don’t need a mathematical formula, you know who you are. Worse, the people who work with you know, too. I’ve tried the “set the clock ahead 10 minutes” trick, but it never works because I know that I really have that extra 10 minutes. If you’re nodding, then perhaps you need David Seah’s Procrastinator’s Clock.

It’s guaranteed to be up to 15 minutes fast. However, it also speeds up and slows down in an unpredictable manner so you can’t be sure how fast it really is. Furthermore, the clock is guaranteed not be slow, assuming your computer clock is sync’d with NTP; many computers running Windows and Mac OS X with persistent Internet connections already are.