(Non)predictions for 2012
With 2011 waning, people are contemplating what 2012 will bring for technical communication. Our profession is changing rapidly, so intelligent conversations about the future of tech comm are essential.
All that smart talk has absolutely nothing to do with this post.
Instead, prepare to be underwhelmed by my lack of precognition as I offer these humble (non)predictions for 2012:
- A tech comm team without any budget will implement DITA because it’s “free”—and will spend countless hours configuring (and complaining about) the PDF plugin in the DITA Open Toolkit.
- A technical writer (not communicator) will lose respect by demanding it.
- An IT department will insist that SharePoint is suitable for managing modular XML content.
- If there is a new release of FrameMaker, it will have some promising features—and at least one (non)feature that causes long-time users to howl obscenities.
- A tech comm team will have their request to implement <shiny new tool or technology> rejected because they offer no business case for the change.
- There will be lengthy discussions about punctuation consistency within online help that nobody reads because better information is in unofficial forums riddled with, punctuation inconsistencies.
- Technical writers will cry, “I just want to write!” when faced with the task of compiling metrics that could ultimately justify their jobs.
- A consultant or XML tool vendor will shamelessly peddle DITA as the cure-all for tech comm ills.
- A fervent supporter of a particular tool or technology will take criticism of said tool or technology as an ad hominem attack. (Blame Sarah O’Keefe for this prediction.)
- An article about the power of online media will be distributed in print and a three-column PDF file. (Please mail your comments to Simon Bate.)
- I will write a blog post with nearly toxic levels of snark. (Mission accomplished, and it’s not even 2012 yet!)
What does your crystal ball have to say about 2012? Leave your (non)predictions in the comments section. The person who posts the best (worst?) prediction will receive a free EPUB version of Scriptorium’s State of Structured Authoring report, which sells for $49.99. The contest will close on Thursday, December 8, and I’ll contact the winner the next day.
An influential project manager will resist the mere mention of structured authoring because, y’know, we can’t force writers to give up their creative freedom. It’s socialism, is what it is.
A techcomm team will be replaced by a cheaper source because they could not articulate the business case/ROI for knowledge management of quality user-facing information.
A tech writer will say that they are waiting for the XML tools to be mature before adopting structured writing, by which they will mean they are waiting for them to work just like FrameMaker.
A tech writer will predict the end of technical writing as a profession and demand to be called a Content Manager.
Jennifer O Neill
Take terminology management seriously now that the company is selling worlwide in multiple languages, has outsourced some/all product development to suppliers and whose documents need to be rewritten, and globally dispersed teams means we’ve now two versions of English as well as Chinglish, franglais and Dunglish in the docs? Nah! Let’s discuss line spacing in the templates again.
Vendors who have made $$$ on the donated effort of the DITA Technical Committee and the DITA Open Toolkit will fix and document the DITA-OT PDF plugin.
A tech writer will insist that his or her tool, CMS, or solution (structured or otherwise) is the wave of the future and the answer to every writer’s and product’s tech comm needs.
Bonni Graham Gonzalez
A major new user-facing software project will be launched without scheduling the content team’s time. Odds are it will be “Agile.” Further odds are that the content team will learn of it 2 weeks before launch. Everyone involved will be mystified as to how this happened.
Bonni, you’re the winner of the (non)predictions contest! (Not sure if I should offer congratulations, though!) Expect to get an email from me with a copy of our structured authoring survey report attached.
Executives from various companies will have meetings about content strategy and will chant “optimize the content!”
1. Meeting concludes; self-applause given.
2. Executives give each other raises upon exiting meeting room.
3. Executives dock subordinates for failure to optimize content.
A happily ex-technical writer will thank her lucky stars that she got out of the biz before all this nonsense took firm hold on the industry. 🙂
Paul Di Somma
Organizations will begin rehiring.
A TechComm department will switch from FrameMaker to XML and CMS, based on the business case that it will save money and make the department more efficient. Based on this expectation, enough writers will be ‘let go’ to equal the cost of the new system. Hilarity will ensue.
A company will seek to provide clear, accurate, and complete documentation for its product or service, with the goal of improving the user experience and minimizing costly support calls.
Said company will advertise for and interview technical writers. One of the candidates will exclaim “I’m not a technical writer, I’m a business problem solver!”.
The interviewer will chuckle silently while showing this candidate the door. And the company will hire the professional they need, a technical writer.