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.
Based on the original post, it seemed to me that there was cognitive disonance occurring. In my personal opinion, the conflict wasn't so much about the job per se, but rather about confidence (stay with me here, I'm flying by the seat of my pants).
This person has been with the company long enough to determine if the work environment appeals to them. I assumed (shame on me) that this person would want the perks that accompany a management position (increased pay, office, etc.).
When the management position was announced, it should've taken .03 seconds to determine "Hey, I've always had my eye on being a manager" or "I'm content where I am." If it's the former, then it becomes a matter of reconciliation, which is what we all do, mostly when comparing a posted job with our skill set. In the case above, this person would simply have to determine if they had enough ambition to say, "Hmmm...I want to be a manager. I can learn XML. Done."
If this person declined the opportuniy (based on the above), then it's time to rethink/reprioritize goals, because they really didn't want to be a manager.
So, if someone chooses not to go into management, and remain a TW
full-time, how do they advance? If they were fortunate enough to be at a company where there were two tracks for management vs. advanced XYZ then there is no issue. But if you're not, how would you feel professionally if others in your department, with potentially less experience, advanced to management and you remained in the same position? Would you rethink your goals if that happened?
If management is not for you, what then?
"technical writing plus" said:
Thing is, staying in a non-managerial role can indeed be a goal. -j
-----Original Message-----
Nope. Not this time, oh guru :^)
'What do you want to do?' should be the easiest question to answer because everyone - EVERYONE - should have short term, medium term, and long term goals in place at all times. Once the OPs Manager described the position
the decision is simply comparing the duties and responsibilities of the position against these goals. Do I want to manage a group of tech writers? Yes or no. Do I want to be writer or a manager/editor?
The only difficulties arise when one has to establish goals first, before considering the job.
From: Gene Kim-Eng <techwr -at- genek -dot- com>
I don't think it's a no-brainer at all. The question asked by the
OP's manager (what do you want to do?) is often the hardest
question there is to answer. Practical considerations aside, if
a possible position is not what one *wants* to do, one's
chances for success and satisfaction in the position are already
handicapped.
> This is a no-brainer.
>
> Your current position is here: (_)
> Becoming a supervisor would put you here: (-)
>
> Take the position. Learn XML. Don't look back, and stop trying to talk
yourself out of it.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
