[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: A technique to get on development's good side

Subject: Re: A technique to get on development's good side
From: John Bartol <johnbartol -at- shaw -dot- ca>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 13 May 2005 08:44:18 -0700


Mike O. wrote:

You know, this list offers so much good advice on how to overcome the
divide between tech writers and developers. I too have my techniques.
But did you ever ask yourselves why that divide exists in the first
place? Why do tech writers, of all other people on the team, have to
overcome this artificial barrier placed in their path?

As one who "came over from the dark side" a couple of years ago, I think I can comment on this objectively.

Unfortunately, it is all too common that the various groups in a company are stratified, each responsible for accomplishing their own goals without considering the (ack, I'm using a term from the closing session of the conference) 'user experience' as a whole.

In terms of the TW/Developer divide, this is manifested in the assumed roles of TWs and Devs as a whole: the TW is an advocate for the user, the Dev is responsible for implementing functionality.

From the developer's point of view, they are required to get, and keep, the system working properly, continually adding new functionality. All too often, they are operating to tight timelines and are constrained by the capabilities and limitations of existing systems and the requirements of new functionality. What this means is that developers will often have far more time to discuss and explain things with other developers *because* they don't have to waste time leading them by the nose. Like it or not, this is how TWs (and marketing people, and pretty much anybody who is *not* a developer) are viewed - they don't understand the developer and are more often than not going to want things done that will impact the project timeline negatively.

So... the TW has to make the effort to show that they are involved and *understand* the issues that impact the developers. If the TW does *that*, the developer will see the TW more as a peer than a nuisance.

As for why tech writers have to overcome this barrier, it's simple (imho)... no other group of people sit so firmly on the invisible fence that exists between the producers of a product and the users of the product.

(Note: yes, I've made many broad statements, but I think the core points hold. I've known *many* exceptions to these, but I've known far more that adhere to these statements)

John


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New from Quadralay Corporation: WebWorks ePublisher Pro!
Completely XML-based online publishing. Easily create 14 online formats, including 6 Help systems, in a streamlined project-based workflow. Word version ships in June, FrameMaker version ships in July. Sign up for a live, online demo! http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.


Follow-Ups:

References:
Re: A technique to get on development's good side: From: Mike O.

Previous by Author: RE: Help vision?
Next by Author: Re: A technique to get on development's good side
Previous by Thread: Re: A technique to get on development's good side
Next by Thread: Re: A technique to get on development's good side

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

What this post helpful? Share it with friends and colleagues:

Sponsored Ads