Collaborating the old fashioned way

When a new director took over our group a few years ago, she assembled us for a getting-to-know-you session where she described her management style (open door, flexible, trusting), her expectations of us, and her long-term goals.

When she opened it up for Q & A, someone asked, “What is your pet peeve?”

The answer came without hesitation: “Endless e-mail chains.”

She decribed the all-too-familar scenario: Employees. who sit in the same building or even the same floor, arguing a question via e-mail, escalating the debate along the way by cc’ing more and more people, higher and higher up the org chart. Tension mounts as everyone copied on the exchange hovers over their Inbox awaiting the next salvo. Newcomers to the debate are forced to read the lengthy chain from the bottom up. Accusations and denials are made. The original thread gets muddled, nothing gets resolved. and little real work is done along the way.

“If you cannot resolve a problem in two rounds of e-mails. Get out of your chair, walk over to your coworker’s cube or office, and settle the dispute. At the very least pick up the phone and call them.”

With all the hype about wikis and virtual teams, are we losing sight of the benefits of face-to-face discussions with our fellow team members? I don’t know the statistics, but I would guess that many of us still primarily interact with coworkers located in the same physical plant. Yet how often do we take advantage of the opportunity to get together in the same room and talk things through.

This is what went through my mind last month when Mike Hughes described how his team at IBM Internet Security Systems talks through the architecture of their online help with the aid of an old-fashioned white board. They pull everyone into a room and examine the product, looking for the rough edges where users might turn to the online help for assistance. They scrutinize the content of the help file to determine what is useful and what is not.

Mike’s presentation was not about collaboration — his primary goal was to demonstrate the value of using “task clusters” in a help file as opposed to a TOC-driven structure. But his description of their collaborative efforts was an eye-opener for me.

My team has always worked on a wide variety of training and documentation deliverables. With rare exceptions, each writer works alone on a document or help file. We collaborate to solve problems, but not to validate our decisions on how to structure a document or approach a topic. As manager and editor, I review the final draft, but I can see the advantage of an earlier discussion. I’d like to experiment with this.

This kind of collaboration can be threatening if it isn’t handled well or if the presenter isn’t adequately prepared. But the benefits could be enormous. Every individual—even the most talented among us—has limitations and blind-spots. Another set of eyes or several sets, can make what seemed impossible, possible. As a team works through problems, they become more cohesive and build trust. Standards are set, innovation happens. The document or help file no longer “belongs” to the individual. It is a joint product.

I believe Mark Wallis (also from ISS)  is going to be discussing this more at next month’s meeting. The information isn’t posted on the chapter site yet, but it will be soon.

Advertisements

4 Responses to Collaborating the old fashioned way

  1. Mike Hughes says:

    Also, catch Miranda Bennett’s presentation at Currents in March. Her presentation focuses on how to plan and conduct such walk-throughs.

  2. Charles says:

    I’ve been known to refer to this as ‘storyboarding’, sort of like the film community does.

    I gave my youngest son a copy of Shrek 3 this Christmas. Within the DVD’s special features were deleted scenes which were shown in raw form, storyboarded in front of many people. The run-through was very educational, and an excellent collaboration / ad-hoc cross-functional team experience (how many more buzzwords could I use…).

    Working with eLearning and using branching has given me a bit more appreciation for how a production team works to bring a movie to life, and I’ve storyboarded documentation through ‘Browse Sequences’ along with the eLearning components.

  3. hharkness says:

    Charles,
    Thanks for your comment!
    Is storyboarding always a group effort?

  4. Charles says:

    Hi hharkness,

    Regarding a group effort: Not always. I started using it as a concept when the company eHelp was first launching a product called RoboDemo that I was the techie in charge of running the Betas with. I was fortunate enough to have a social networking connection to a Director of Photography (DP) up in Hollywood that I ran into one Saturday afternoon while visiting a friend and ran concepts past him.

    What I liked with the demo program was that one limited option was not eLearning, it was Usability / User Experience. You could pop out six to twelve slides of your mouse going somewhere and then mark up the screen with boxes, arrows, all sorts of things, and also annotate it with audio.

    Back then we’d email it back and forth. Nowdays it would be more of a blog insert, with comments in the traditional Web 2.0 format. I call that a ‘DevBlog’.

    So here’s my post on DevBlogs and how I use them with storyboarding is pretty clear:
    http://charlesjeter.com/2007/08/16/best-practices-devblogs-and-elearning-content-development-informal-rapid-elearning-tools/

    If the link gets broken, go to
    http://charlesjeter.com/2007/08/16/

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: