TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
A little background information first, if you please.
The company that I work for uses Sharepoint to store documents. It uses it
poorly, but uses it nonetheless.
The company has your standard departments Development, Project Management,
Business Integration, Architecture, etc. The sum total of the employees in
those department is ~150.
I was asked to assist a contracted resource in cleaning up our Sharepoint
site. This included creating a document creation/approval process. So that
I did.
My plan was to load all of my document templates onto the Sharepoint site
and allow all employees to create documents from within the site. So, for
example, Ted from Development could create a document and, when he was
satisfied with his draft, could click "Submit," which would forward the doc
to his manager for approval or rewrite. When his manager clicked "Submit,"
it would forward the document to me. I would act as the gatekeeper ensuring
the accuracy of the doc, correct format, and whether or not the document had
already been created. Once I was done with the doc, I would forward the doc
to the respective project manager so that the document could be marked as
completed in the project plan. Once the project manager was done with the
doc, he would submit it to the appropriate business unit for (realistically)
a rubber stamp approval, which would then cause the document to appear in
the Sharepoint site.
Unfortunately, this was shot down. The PMO changed the process so that all
document templates and requests for new documents has to be approved by
them. Once approved, all meetings that the tech writers conduct with SMEs
has to be approved by them also. To top it off, once a tech writer submits
a doc to the PMO, he or she gives up all control of that document, meaning
that I only have read-only access to the documents that I created...unless
special permission is granted.
I understand that a project manager is responsible for the success of a
project, but has anyone heard of a project management office seizing so much
control over documentation?
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
