Re: Interesting job description

Subject: Re: Interesting job description
From: "Monique Semp" <monique -dot- semp -at- earthlink -dot- net>
To: "'techwr-l'" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 7 Oct 2016 14:37:18 -0700

The less SME time a tech writer needs, the less impact they have on the critical path of product development.

This is also the basis on which tech writers can negotiate for higher pay. If you can go to the company and say, "I can produce the requisite documentation with less impact on the critical path than the next guy," that is a value proposition that any project manager can understand.

Yes, and yes. But...

This works only if the organization has some semblance of process and change management. If there are no specs, and the software is so buggy that the writer can have no confidence that how it works is supposed to be how it works, then there's nothing the writer can do except take up the SME's time. We cannot read minds (as someone else postulated would be necessary), or predict what amazing new feature the SME might decide to add during the last week of development.

The only way we can do our jobs without SME interaction is if there's something to take the place of the SME. And by "something," I don't mean the old waterfall method of spending years writing specs. But even in Agile, one is supposed to have sprint-related documentation that tells what the product/software is supposed to do.

If there are no design docs, user stories, (Kanban) planning, or anything, and the software is such (either too buggy, or requires test bed setups that writers aren't allowed to access) that the writer can't simply exercise itâand yes, I've been in organizations like thisâthen personally interviewing the SMEs is all that's left.

Visit TechWhirl for the latest on content technology, content strategy and content development |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Interesting job description: From: Keith Hood
RE: Interesting job description: From: mbaker

Previous by Author: RE: Recommendations on Screen Recording and Editing Program
Next by Author: Re: Acrobat Shared Reviews
Previous by Thread: RE: Interesting job description
Next by Thread: Re: Interesting job description

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

Sponsored Ads