Articles

Wednesday, October 18, 2006

Dispelling Collaboration Myths: Is Your “Team” An Impediment To Content Management Success?

By Emma Hamer, eHamerAssociates, Ltd., special to TheContentWrangler.com

In conversations I’ve had recently with TechComm Managers and Content Management Consultants, as well as with individual technical communicators and instructional designers, one question keeps coming up: How are we going to cope with the changes brought on by the implementation of a content management system? The response to my question: “What changes are you worried about” varies tremendously:

  • Enforcing the discipline of structured authoring
  • Identifying enough reusable content to make it all worth while
  • Repositioning our team to the other departments: less service group, more expert advisors
  • Getting SME’s to understand how this system impacts their contributions
  • Getting my team to collaborate at all, let alone better

Although each of these points deserves an article to itself, this article will tackle the last point: collaboration – we know we need more of it, but do we even know what it looks like? And how do we get there? Is it even possible with the people we have now? And how will we know we’ve succeeded?

First of all, it’s time to dispel some myths. Many of these points are held very dear by technical communicators and their managers alike, but that still doesn’t make them sustainable in a Content Management environment. They are “the old” that must go:

  1. A group of people performing similar tasks in similar circumstances does not a team make; it’s still a group.
  2. It’s not “your” document; it’s the company’s.
  3. Working roughly in the same area, but each in their own cubicle is not conducive to collaboration.
  4. Privacy and quiet are overrated; if you want privacy – don’t come to work. Collaboration is about looking over the fence, not at it.

Allow me to elaborate a bit on each point:

1) A group is not the same as a team.

It has become fashionable to speak of one’s staff as “my team”, or “our team” and of its members as “team mates”. Calling it so, however, doesn’t make it so. There’s more to teamwork than numbers. The key difference is in the level of interaction and interdependence of team members. For a group of people to become a team, their work behaviors must change, in the understanding that they need each other’s contributions to successfully complete the tasks at hand. Writers and illustrators, editors and SME’s, illustrators and information designers, and any other combination of disciplines, must increasingly become interdependent to meet the needs of the organization and its customers.

For this interdependence to take hold, and for interdisciplinary teams to function, barriers must come down, territories must be relinquished, and frank and open discussion must replace the often defensive responses to feedback – whether on content or style.

What used to be a key positive quality in technical writers: the good ones felt a sense of ownership for their documents, is rapidly becoming a liability. See also my next point:

Image
© Dennis Cox - FOTOLIA

2) It’s not your document, it’s the company’s.

Since one of the key rationales for a CMS is the ability to reuse and repurpose content, chances are that new information products (and these do not have to be documents) contain 60, 70, sometimes even 80% content that already exists. Only the “really new” bits and pieces are added or substituted.

Some of the new content will be an adaptation or improvement of previous versions, some of it will be created specifically for a new product. Some of it may be in the form of text, some of it may be a new graphic, or a QuickTime movie, or an audio component. My point is: it is no longer possible to “own” a document, firstly because it may not necessarily “be” a document, and secondly, because in a CMS, a product does not actually exist until it is assembled from new and repurposed “chunks” of information. Which chunks get assembled, in which order, defines which information product emerges: a web page, a brochure text, a training module, a user manual, a packaging label, etc.

Understanding that many contribute to this information product, and that each contribution is critical and valuable, will help a sense of collective ownership grow. Everyone involved in this production is responsible for the end result; it’s everyone’s responsibility to catch mistakes others may have overlooked.

Of course, this may involve an illustrator reviewing a written procedure, and saying: “You know, I think we can get this point across more easily with two or three simple diagrams” without the author of the procedure getting defensive or upset. And vice versa, naturally. It also involves a writer telling a SME that while this procedure may sound logical to the SME, it needs to be rewritten for it to be useful, without the SME pulling rank and/or getting upset.

Image
© Dennis Cox - FOTOLIA

3) Working in the same area, but each in their own cubicle is not conducive to collaboration.

As a method to maximize the number of people per sq. ft., the cubicle has no equal. As a method to shut one’s self off from one’s surroundings, to barricade one’s self within a cocoon of “this is my space”, complete with the trappings of home (photos of loved ones, be they children or pets, strings of Christmas lights, humorous figurines, in short “personality”) the cubicle has no equal, either.

I’m going to say it as plainly as I can: in an interconnected workplace, where collaboration is the goal and the norm: the cubicle has had its day; it must go.

Frankly, cubicle-dwelling discourages and even stifles the kind of cross-over involvement necessary for collaboration. To collaborate with others, you need to know what they’re doing; you need to be able to eavesdrop on their telephone conversations, you need to be able to pull up a chair and join a discussion taking place between a colleague and a SME. For the creative potential of collaboration to be realized, you need to be facing one another, not holed up in a box, with your backs turned to each other.

The good news: this is easy to do: have all the hutches, panels and dividers removed, and group desks in threes and fours. Shove all the storage and filing cabinets to one or two of the outside walls of the area. Create a reference library area (bookshelves) with a table and some chairs somewhere in the middle, and designate this area as the collaborative meeting area, as well. And close your ears and minds to the deafening howls of protest. Just do it, make it a group activity, with everyone pitching in, and explain why. Explain often, and praise everyone for trying hard. Encourage discussion about the pros and cons, and point out the benefits whenever you can. Do what you need to do, but don’t back down. This is the layout of the collaborative team – the team of the future.

4) Privacy and quiet are overrated; if you want privacy – don’t come to work. Collaboration is about looking over the fence, not at it.

Technical writers have maintained that – in order to write – they need privacy and a quiet environment. Perhaps because the profession has an overrepresentation of people with an MBTI preference for introversion, this line has been swallowed like the gospel. Strange, then, that journalists – writers, too – can function perfectly well in a noisy newsroom, with phones ringing off the hook, printers whirring away, people walking by their desks talking, and assorted deadline-driven mayhem around them.

Certainly, there are times when a writer needs some distraction-free time – but that’s not all the time. In the new world of collaboration, a distraction-free zone may only be necessary for a few hours per week. For instance: to work out a rough first draft of notes taken during a content development meeting – perhaps for 3 hours. And perhaps once again, if a final – definitive – edit needs to be done, maybe another 2 hours?  In other words, instead of ‘leaving the work area’ to ‘go to a meeting with your team’, you will temporarily ‘leave your work area’ to ‘work on your own for a few hours’.

The legitimate need for a distraction-free zone is equally easy to address. Create one or two areas, set back from the main hustle and bustle area, where one can temporarily sit and work in relative quiet and isolation, until the task is done. Don’t create too many of these areas – they need to be a scarce commodity that your writers must share. No need for any kind of storage capability in these areas – no-one will stay there long enough to need storage. Just a desk, a chair, a computer. Simple.

Collaboration is more than working together; it is more than sharing resources. True collaboration involves getting to know all aspects of the work, your own, and those of your collaborators. And thinking about, commenting on, and contributing to areas that are not within your primary scope of expertise – simply because you are a collaborator , and therefore it’s your work, too.

How will you know when you’re there? When your people comment freely and constructively on each other’s work, when a SME offers to come and sit with a writer during an editing round, when an illustrator offers to go down to the assembly floor to see and capture with her own eyes how the product is manufactured. The key words are: “freely” and “offer”.

Collaboration is the strategy to develop self-directed and self-managing multi-disciplinary teams: the multi-talented work teams of the future.

About the Author

Emma Hamer BASc, is the founding principal and senior associate at eHamerAssociates, Ltd., Career & Performance Consultants. Her field of practice is human performance improvement, both for individuals and for corporations; her passion is doing things right the first time around. All are firmly founded on in-depth analysis of performance gaps and the design of creative interventions to close the gap.

Introducing and implementing new systems—whatever their complexity—means changing how people contribute to and use the systems. Matching new tasks to the right people with the right critical skills is a key area of concern. Emma provides change management support during all phases of the selection and implementation process, helping the contributors and users close the gap between intent and actual impact of the changes. Emma is an acclaimed and internationally active speaker and presenter on performance management and leadership challenges. She has presented and published on the topic of content management from the human performance and organizational development perspectives.

© 2006 E. Hamer Associates Ltd.

Filed under: Content ManagementChange ManagementTechnical Writing

Comments

By Holly on October 19, 2006 -- 11:27am

Provocative article with many good points.

I’ve always found that when a tech writer’s documentation is not up to snuff, 9 times out of 10, the reason is that they didn’t collaborate very well with the developer, the SME, or another necessary contact.

I totally agree on the “it’s not your document\” point.

I’m of two minds on the “no cubicles” argument. Working together in the same room can be invigorating, but it can also be stressful. Private, quiet, alone time is a good way to alleviate stress. Not having your own space to retreat to, can cause dissatisfaction. Working from home may not be an option in some situations.

People have different work habits. Some like to socialize and joke around. Others are heads down, always focused. These two types can work together, but I wouldn’t put them in the same room.

You can force people into common areas and maybe get some quick wins, but will you retain those employees in the long run? Will your employees recommend your company to their friends and acquaintances? You have to think beyond the immediate project.

By ScottAbel on October 20, 2006 -- 5:52am

Thanks for sharing your thoughts about this important topic, Holly. We expect to see many more articles on change management in our trade and industry publications as businesses around the globe move away from managing content inefficiently. We also expect to see resistance to change.

Those organizations that succeed at adopting collaboration will hopefully continue to share their stories with us so we can learn from their expereinces. Those that fail, well, we’ll point and laugh at as we say, “We told you so.”

Of course, there are both pros and cons to making your office environment collaboration-friendly. And there are also some unanswered questions: What about those who work from home or remotely. How do we bring them into the mix? And, are there any web-based technologies that may be able to connect remote workers so they are able to collaborate in a similar manner as if they were working at the office.

Lots to thinks about. That’s for sure. Thanks again for your thoughtful comments.

Scott Abel
The Content Wrangler, Inc.

By Barry Schaeffer on October 20, 2006 -- 6:41am

Good points but a little heavy on the “what” describing the goal without providing the “how.” Particularly liked Emma’s focus on the human and organizational impediments to true collaboration and team-building.  Unfortunately, the software industry tends to couch these problems as stemming from a lack of proper CM software and IT support (wonder why,) leading many organizations to buy things that don’t address their problems and limp along without much improvement. This is a failing in many areas of IT-related operations and until it is dealt with, we won’t see that brave new world that IT keeps telling us about.

Actually, there is a pretty extensive library of techniques for building the multidisciplinary team contained in the literature around “Concurrent Engineering” or CE.  This philosophy, articulated in the 80s by the DoD and designed to bring together the often antagonistic relationships between design and process engineering in the manufacturing world, addresses most if not all of the points in Emma’s article and is equally applicable to information projects.

Emma’s piece contributes to the sometimes painful realization that the only core players in the information life-cycle are the SMEs who know things and the consumers who need and are willing to pay for those things.  Everyone in between, however capable, and that includes tech writers, IT, etc., are carrying water for the these key players.  Until everyone accepts that fact and understands his or her role, we won’t see the kind of progress the world needs.

By holmesd on October 20, 2006 -- 12:17pm

I agree with most of the article - but I’m a little hesitant to get on board for item 4. I’ve always been of the school of thought that knowledge workers - whether they be developers, authors, artists, or scholars - need quiet, personal space to work.

Many of these workers have to ‘get in the zone’ before they can produce their best work or before they can be their most efficient. The downside is that it takes time to get into the zone (typically between 5 and 15 minutes) and it’s very easy to get knocked out of the zone by outside distractions. The example that’s most often given is a worker that gets interrupted every 20 minutes by someone else’s conversations or phone calls. For this person, only 15 minutes of every hour are spent in productive work, while the other 45 are spent attempting to ‘get back to work’ or rechecking their notes to make sure they didn’t miss something.

From my own personal experience, I can say that the difference between an open and a closed office environment is about a 10% reduction in productivity. If it’s a noisy environment, that number is probably closer to 20%. Assuming that I average 30 hours a week of production time (time spent actually making something), this might mean an overall loss of 6 hours a week of labour.

I guess my hesitation here is that I know that moving to an open, collaborative office environment will definitely mean a reduction in my personal productivity. What I’m curious about is if the net gains are worth it. Will the loss in individual productivity in each worker be offset by the improvements to group productivity that come from collaboration (and of course, the infrastructure savings of the new office environment)?

By Kristy on October 20, 2006 -- 1:29pm

This article is so very true. My workgroup was a collaborative team until end of last year. While we were technically in cubicles, they were essentially in a circle around a central table. It was very easy to discuss policies, procedures, and materials we were working on individually, which spilled over into other materials and work classifications. This was often how we found out about projects that were indirectly related to our tasks. We called it “stoop time” when we rolled out and had these informal meetings.

Then we were moved physically to another part of the building, with normal cubes in rows and other Employees. That’s where we began to fall apart, and we could see it happening. After much discussion, we were able to get half-walls put in between the cubes, so we could at least discuss with our closest neighbors. While this has helped, it is not nearly as collaborative as what we had. There is a definite possessiveness now, which was never there before. The pride we used to have in our group is also gone.

While in the circular environement, it was never completely quiet, but quiet enough that you could concentrate (and I like it quiet). Conversations were also easier to filter because you could tell if it would effect your taks or not. The new environment is much louder, and much harder to filter through the non-work-related conversations, making it harder to stay on task.

My workgroup is also attempting to make the transition to single-sourcing and using a content managment system. The transition has nearly stopped (after making great strides) since the move. This is partly because work is taking longer to complete now that we are separated.

It is pretty amazing to see this process in action. Collaboration makes work much easier, the People happier, and management of projects less stressful. Everyone is at least aware of everything that is going on, and able to give some direction to those external to the group.

Emma’s article should be read and taken to heart. She has really captured the main pieces to having a collaborative team.

By ScottAbel on October 22, 2006 -- 7:39am

Thanks for the great comments everyone. We’ve asked Emma to continue exploring this topic—including ideas for how to overcome some of the issues our readers have identified. Look for some personal responses from Emma on this page and expect to see more change management articles by Emma on this weblog soon!

By Emma on October 22, 2006 -- 11:35am

Thank you all for your comments - and criticisms. I knew when I submitted the article that it would trigger debate, but I confess I had no idea that the debate would be of such high quality. Holly’s concern that a “barrier-free” workplace (literally and figuratively) may drive away some writers who cannot - or will not - make the transition, is a legitimate one. I believe that as the profession changes, it will also draw new people to it, who are perhaps better suited to work collaboratively. In the short term, yes, some tech writers may opt to walk away, or work for companies that are more traditional.

In the longer term, I do believe that the increase in the group’s productivity will more than compensate for the short term drop in personal productivity for some, as writer holmesd suggests. The response from Kristy certainly indicates how quickly things can go down-hill when a collaboration-friendly workplace is suddenly pulled back into the CubeWorld… Kristy’s experience is very near proof of my position that until the walls come tumbling down, collaboration will remain a lofty goal.

For Barry, and others like him, who would like to read more on how to foster and encourage collaboration, I can promise you that I intend to deepen the discussion around this particular topic, and share some success stories with the community. There are more barriers to effective collaborative team work, besides physical conditions, and I will present articles on these barriers regularly on The Content Wrangler - stay tuned for more.

Leave a comment

Name:

Email:

Location:

URL:

Remember my personal information

Notify me of follow-up comments?

Please enter the word you see in the image below:


Subscribe: Direct Inbox Delivery

Get The Content Wrangler Newsletter delivered straight to your home or work Inbox. It's full of content goodness.

sponsors Image Image Image Image Image Image image Image Image Image Image Image Image Image Image Image