Documentation Managers

Add a Comment

8 Comments

Comment by Chris Bridgen on June 13, 2008 at 9:44pm

Suzi, how did you get started with Wikis for your business unit?

Comment by Suzi Magill on June 3, 2008 at 7:15am

Hello!
I just joined after attending Scott's STC session yesterday. I am a fairly new manager, I've been a team leader for my group for about a year. I love having my feet in both pools--I still write but manage other writers too. My company is moving to blogs/wikis in a big way and I am leading the effort for our business unit. Gulp. Have a feeling I'll be scouring this site for tons of information and advice. :)

Comment by Timothy B. Tanner on May 25, 2008 at 9:19am

Hello to all!
It is great to discover this group. It is amazing how easy it is to get buried in a stack of paper docs or to recreate the wheel in developing training materials for example. Lots of knowledge and sometimes not enough time and resources to streamline. I look forward to learning and sharing ideas with this you.
Have a great weekend!

Comment by Nikki Bridwell on April 17, 2008 at 1:39pm

As a new manager (1 year in) of a Technical Publications department, my biggest frustration is proving my department's worth. It has been very difficult to get new software approved and buy-in from upper management for new projects. I'm slowly breaking down the barriers between us and other departments by producing new types of documents. In the last year, I've been a big advocate of the phrase "it's easier to get forgiveness than permission." It's working!

Comment by Chris Bridgen on April 12, 2008 at 4:24pm

I like to talk the language of my client groups. The telecom hardware and software development team talks in terms of cost and scope -- so my documentation plans highlight the same data.
For example, if software talks scope x head count effort in person months, use the same formula. Do the plans list work by feature number or module name? Define your work exactly the same.
I find it helpful to review past software plans or budgets, and then use the same language in my plans.

Comment by Brian Winter on April 8, 2008 at 3:52pm

Joel, in my experience the language the adminsphere understands best is Return On Investment. Rather than being a necessary expense, try to get them to think of doc as very cost-efficient 24/7 onsite support for your users. It may help if you can draw the picture of better documentation = fewer $$$ spent answering support calls, and more satisfied, loyal users who become repeat buyers and references.

Comment by Mike Wethington, CSP on March 27, 2008 at 11:00am

Joel:

I have found it effective to come up with an implementation plan prior to presenting to management. That way you can show not only the benefits of the new technology/process but how you would go about implementing it, being sure to show how it will increase productivity, not affect currently deliverables, and if necessary be implemented via a phased approach.

When you answer the pain-points up from, you can circumvent a lot of the opposition.

Comment by Joel Butts on March 25, 2008 at 10:00am

Hi Scott,
I have a BIG hurdle to get over. Before implemeting all these great ideas I have for our documentation team I'll have to get management to understand the concept that our content is avaluable business asset. Everyone complains about how hard it is to up-to-date business and product info that's accurate. So ideas about getting them to buy-in? Anybody? Lauds, praises, curses? -jb