Hiring decisions change along with process maturity
The ways that companies hire technical writers changes as companies mature. I stumbled across an article by JoAnn Hackos who talks about what we in the technical communication industry have discussed amongst ourselves for as long as I can remember. The difference is that Hackos articulates it will and puts the discussion into the framework of a process maturity model.
Briefly, the steps go like this:
- Level 1: Do it ourselves. The developers put together some documentation as time allows.
- Level 2: Do it yourself. The development manager hires a self-starter who understands the technology can operate without much supervision, and hopes the writer knows how to creating content.
- Level 3: Do we know a writer? The technology team realizes that, like an accountant needs to know about accounting principles rather than the company’s technology, a technical communicator needs to know about content development models and have solid abilities in that field.
- Level 4: Hire team members. The management team shifts to realize that content is an integral part of product development, and the writer becomes more of a developer whose development area is content instead of code.
- Level 5: Look for contributors. The executive team recognizes the critical value of content to the success of the product and makes room at the table for someone who can make strategic decicions around how content can contribute to product value, be leveraged for additional purposes, and drive development efficiencies.
Where is your organization on the process maturity scale?
Comments
Leave a Reply
Recent Posts
- Public-sector content, web development and content strategy, and career cautions for writers
- The ROI of content
- Is it time for a content strategy maturity model?
- Getting ROI by Using Lean in Content Production
- Defining Content in the Age of Technology
- Turning Copy into Content
- Copy and content: a tale of two realities
- Content that RAITES
- The Brief Content Audit
- Why content strategy: explaining its value proposition
Categories
Tags
accessibility ann rockley career development CMS content as asset content convergence content lifecycle content management content strategy convergence deliverables DITA Duo Consulting experience design Flash integration intelligent content interaction design management marketing mentors open standards plain language politics processes professional development ROI search section 508 services single-sourcing social media STC structured content syndication taxonomy TechCraft translation Twitter usability user-centered design user-generated content user experience value XMLPopular
- Using topic-based writing to meet aggressive deadlines
- Content strategy and the new face of documentation
- Flash pages, skip intros, and other annoying content
- A practical definition of content
- Content strategy includes convergence, integration, and syndication
- Why social media seems easy but is (evidently) harder than it looks
- Abilities and aptitudes for a content strategist
- Redefining content strategy
- Strategies for adopting structured content
- CMS selection practices need maturation
Random Posts
- The Bailie Daily is out! http://t.co/8Cfucuyt ▸ Top stories today via @doriantaylor 59 mins ago
- The Bailie Daily is out! http://t.co/8Cfucuyt ▸ Top stories today via @michaelseidel @markhurst @danielgm @jlegon @boxesandarrows 1 day ago
- The Bailie Daily is out! http://t.co/8Cfucuyt ▸ Top stories today via @monstro 2 days ago
- Meetings are work, too. Meetings are work, too. Repeat as needed. 2 days ago
- More updates...















Latest Tweets
RSS feed
Twitter