Home Library Translate
A A A
Share »
Follow us on Facebook Follow us on Twitter Follow us on LinkedIn
Connect »

Blog: Business Communications

Menu

  • This Blog's Home
  • Guest Writer Submissions
  • Policies
  • To Subscribe to a Blog
  • About
  • Feedback

Getting To Know Your Technical Writing Department (Part 1)

By Theresa Pojuner on October 15, 2012

What happens when your new job is to manage or reinvent a Documentation Department? Where do you begin? What do you need to know? Here are some tips on getting to know your Department and Technical Writers without stepping on any toes and without being too forceful. There is a lot to talk about here, so this is the first of two posts. Even two posts may not be enough, but I will share what I can for now. Let’s begin.

During the first meeting with the Technical Writers and team members, let them know why the meeting was called and present your ideas of what makes a viable Documentation Department and simultaneously, gather the following information from each member of the meeting. You can ask the following questions (if the group is small), hand out questions at the meeting (and arrange a follow-up meeting), or email the questions prior to the meeting (if the group is large or global).

By getting to understand the current processes, you familiarize yourself with the team members and you can determine whether or not changes have to be made.

Projects – What projects are the technical writers involved with?

  • Are we included on project plans or charters?
  • Do the writers also create their own project plans?
  • Who sets the writers deadlines?
  • Are more than one writer assigned per project?
  • What projects have they worked on?
  • Estimate how many documents are needed for each project.

Writing – What is involved?

  • What documents are each writer in charge of?
  • Do they write mostly for content or the web?
  • What format are most documents produced in (docx, pdf, html, xml, etc.) ?
  • What departments and whom do they meet with for gathering their information?
  • How often do they meet with others and are they helpful?
  • Is it difficult to set up meetings with Subject matter Experts (SME’s) to get the needed information?
  • Estimate the turnaround time for each new document created.
  • What happens when a document is late?

Collaboration – How well is the department working with others or vice versa?

  • What meetings do the writers attend for gathering information?
  • Are they part of status meetings?
  • Are they given enough time to produce their documentation?
  • Do they attend meetings when a project begins?
  • How are they notified of changes/updates to documents?
  • How are they handling conflicts or bottlenecks?
  • Are they given enough time to make necessary changes to their documents because of a change in process or development or any kind of adjustment that impacts the document?
  • What road blocks or bottle necks do you face daily?- such as – Delays about notification changes or when there is too long of a lag in time between reviews.

When you have gathered all this information, create a mapping or matrix for yourself and try to see the whole picture of how the current Documentation Department operates. See if there are trends or cycles of heavy and light workloads or when more resources are needed.  This should help you get a clearer picture of your Technical Writers functions, the Department performance, and where improvements are needed.

« Previous Next »

Search Our Site

Meet This Blog’s Host

Gail Zack Anderson, President of Applause, Inc., has nearly 20 years experience in training and coaching. She provides individual presentation coaching, and leads effective presentation workshops and effective trainer workshops. [Read more ...]


Theresa Pojuner is a Documentation Specialist with over 20 years of writing experience and is skilled in many areas of documentation, for example, Style Guides, Training Manuals and Test Cases, wth a specialty n Technical Writing and Procedures. [Read more ...]

Recent Blog Posts
Alternate Recent Posts Widget

  • Becoming A Technical Writer-Communicator Review
  • Creating A Knowledge Community
  • Tips for Handling Technical Writer Stress
  • Likeminded Communication
  • A Technical Writer Is Different From Other Writers
  • Involve and Engage Your Audience 20 Ways
  • Tips On Documenting Processes
  • Communicating Technical Writing Review
  • Communicating Via Visual Designs
  • Special Tips for Laptop Presentations

Related Library Topics

  • Body Language
  • Netiquette

Categories of Posts

  • Basics and Overviews
  • Body Language
  • Communicating Change
  • Communication Best Practices
  • Feedback (Sharing)
  • Humor in speaking
  • images
  • Listening
  • Netiquette
  • Presenting
  • slide shows
  • Speaking Skills
  • Team Presentations
  • technical writing
  • Telephone Skills
  • Uncategorized
  • Visual Aids
  • Voice and Vocal Habits
  • Writing

Library's Blogs

  • Boards of Directors
  • Building a Business
  • Business Communications
  • Business Ethics, Culture and Performance
  • Business Planning
  • Career Management
  • Coaching and Action Learning
  • Consulting and Organizational Development
  • Crisis Management
  • Customer Service
  • Facilitation
  • Free Management Library Blogs
  • Fundraising for Nonprofits
  • Human Resources
  • Leadership
  • Marketing and Social Media
  • Nonprofit Capacity Building
  • Project Management
  • Quality Management
  • Social Enterprise
  • Spirituality
  • Strategic Planning
  • Supervision
  • Team Building and Performance
  • Training and Development
About Feedback Legal Privacy Policy Contact Us
Free Management Library, © Copyright Authenticity Consulting, LLC ®; All rights reserved.
  • Graphics by Wylde Hare LLC
  • Website maintained by Caitlin Cahill

By continuing to use this site, you agree to our Privacy Policy.X