Why [some] tech writers don’t like content management
Moving to content management means a big shift in the way technical communicators work and the way they think about their work. With some sweeping generalizations (because the very nature of “top ten” lists require such generalizations), here are my five top reasons that technical communicators don’t like content management:
- The personality types drawn to structure, predictability, and stability of technical writing aren’t part of the 15-20% of the population who willingly embrace change.
- Because so much of a writer’s work is carried out using software, one’s feeling of competence is tied being able to use the software on auto-pilot while concentrating on the craft of communication. Messing with that in a major way creates a crisis of confidence.
- Technical writers don’t like the idea of constraints being putting on their writing styles, even though the lack of constraint may be an illusion.
- Technical communication departments tend to be insular, and rather than keeping up with incremental industry changes, technical writers lag behind and then get overwhelmed with having to learn several new concepts, technologies, and tools at once – and then it feels overwhelming and disheartening.
- Technical writers don’t think like business people, and resist the metrics and measurements that reduce their work to units, measurable like so many auto parts, so the language that gets used to sell content management to management, or describe the benefits of content management sounds cold and threatening.
Next, the five top reasons why other technical writers love content management.
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 1 hr 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