The workload has been increasing rapidly and I now deal with
four major tasks at work. One of these has been the first contact with CPI in a
lean environment. Something that has been tricky to say the least. Not having
much experience as a tech writer it´s been challenging working with a project
that changes direction every week and getting larger and larger by the day. However
it´s my project and I´ll be dammed if I can´t make the end result be,
acceptable. By that I mean be outstanding from someone with my limited
experience. Working towards telecom one might guess what companies I write for
in Sweden. The most challenging task aside from getting the right technical
information in time has been starting working with the range of the client’s
tools and accesses. These two factors can probably take up to 50% of my time on
projects. I guess there is just one thing one can do about it. Be a bit of a
bitch and get in people’s faces until stuff happens. Usually literally getting
into peoples face is the best way. Always arm yourself with a good smile and
people skills though. Swedes and I think people in general have a real hard
time saying no to people face to face when they think it´s a reasonable
request.
I think to manage technical writing fast one needs two things: a good feel for structure and a way with technology or academia. One does not need to understand everything and this is where the shoe needs to fit. I think understanding is superfluous at times as a tech writer. It is great to understand, but it´s not always feasible to understand everything for every project. The important thing is to understand enough. I guess this takes one to the old dilemma of the good enough concept.
My approach is much like one would to back in school. Look at examples, analyze and re-engineer. Trying to divide your way of describing things in modules that has been proved to work will minimize chances of getting things wrong and also your creativeness. Then again how creative is a tech writer supposed to be?
It will be interesting to see how a dyslectic like me will fare throughout this project. So far all feedback has been over expectations. If I can manage my projects and my time here with good or great reviews I think I´ll give myself a pat on the back and determining I can do writing as a profession, with a little help from the spell check function and lots of read troughs ;)
I think to manage technical writing fast one needs two things: a good feel for structure and a way with technology or academia. One does not need to understand everything and this is where the shoe needs to fit. I think understanding is superfluous at times as a tech writer. It is great to understand, but it´s not always feasible to understand everything for every project. The important thing is to understand enough. I guess this takes one to the old dilemma of the good enough concept.
My approach is much like one would to back in school. Look at examples, analyze and re-engineer. Trying to divide your way of describing things in modules that has been proved to work will minimize chances of getting things wrong and also your creativeness. Then again how creative is a tech writer supposed to be?
It will be interesting to see how a dyslectic like me will fare throughout this project. So far all feedback has been over expectations. If I can manage my projects and my time here with good or great reviews I think I´ll give myself a pat on the back and determining I can do writing as a profession, with a little help from the spell check function and lots of read troughs ;)