TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
But that pigeonholes you into being a communicator.
What I'm trying to get at is skills that might transcend that, but use pieces of what we know and can do from the foundation of our roles.
If you take your skills from the role, some of them, when combined in certain ways, can be used to attack problems at a much higher level.
And the end result might have nothing to do with communication.
Steve
On Tuesday, September 06, 2016 3:42 PM, mbaker -at- analecta -dot- com wrote:
I would explain the curse of knowledge.
Communication is about figuring out the right thing to say and the right way to say it to achieve a specific behavioral objective. That matters to just about everyone in business and certainly to a VP of anything. VPing is all about changing people's behavior, and communication is the number one way you go about it.
The curse of knowledge is why it is hard.
Mark
On Tuesday, September 6, 2016 6:19 PM, Janoff, Steven wrote:
Apologies if this has been dealt with before.
If you wanted to educate a VP, or someone from the C-suite, as to what "abstract" skills a Tech Writer has that could be applied to their own challenges, what would you list?
This is for the purpose of leveraging existing skills into the needs of a larger department.
I think these folks tend to think of writers as people who "write," and that's it -- if even that. Lot of examples lately of stereotyping as "making things look pretty," or just typing, or whatever.
For me the first things that come to mind are information architecture and the organizing of information. What comes to mind for you?
So if you're sitting talking with a VP and you want to think of how you could plug into his or her agenda, how would you characterize the highest level, most abstract version of your skills?
You wouldn't say things like, "I can write stuff for you," or "I can make your reports look pretty."
What would you say?
Thanks,
Steve
PS - This is *not* where you're sitting there trying to pitch yourself as a Technical Writer. What you're trying to do is pitch a way that you could approach one or more of their highest challenges for which you have skills that could be applied. Process improvement is an example, but not just Technical Writing process improvement or necessarily anything related to Tech Writing -- it's just that your skills as a Tech Writer, in some abstract form, at the highest level, might be able to be applied to their problem/challenge/opportunity, whatever you want to call it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
