Re: Managed Services

Subject: Re: Managed Services
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Thu, 23 Mar 2017 21:41:21 -0400

On Thu, 23 Mar 2017 17:30:05 -0400, Goertz, Teresa <Teresa -dot- Goertz -at- precor -dot- com> wrote:

I'm curious about Managed Services regarding technical and/or marketing writing and editing documentation. Specifically:
Have you or your company used or thinking about using a "managed services" model vs. the typical contractor/staff augmentation model?
If so, what have you found or what do you think are the pluses and minuses of managed services? The concerns? The obstacles?
In your or your company's view, what does "managed services" even mean? What would be the hallmarks of a managed services content project?

Never heard of it. Sounds like the opposite of the right way to do documentation. My inner curmudgeon hears, "Please send 13 megabytes of documentation by next Friday. Black ink only, do not use Comic Sans."

The best doc teams I've had the pleasure to inhabit have served as an unofficial (and often resented) part of software QC, and occasionally of user-interface design. Only rarely did those teams have to document strictly from the specifications.

On the other hand, there are economic models that work in that latter fashion. At one time, so I've heard, Raytheon would get a military contract, and then design, build and document to the contract with no deviations from the written specs, even if it was obvious that something simply would not work. The Navy would test the result, determine that it did not work, and put out requests for bids for a new contract. The method was predictably good for years of revenue. Any tech writer who tried to improve things rather than following instructions got pushed aside.

In the Raytheon-style military model the "managed services" approach might work well.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

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

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
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


References:
Managed Services: From: Goertz, Teresa

Previous by Author: Re: Which skill to acquire
Next by Author: Re: User Documentation in Agile Development Teams
Previous by Thread: Managed Services
Next by Thread: User Documentation in Agile Development Teams


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

Sponsored Ads


Sponsored Ads