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.
Andrew Plato wrote, among other things:
<snip>
A recruiter at my company interviewed a guy the other day for a ColdFusion
position. This applicant raved about how he knew some methodology. The
recruiter nodded and carried on the interview as normal. The guy was
insistent
that his expertise was the sole reason he was qualified and worth more money.
Of course, whenever the recruiter asked about his ColdFusion skills, he just
redirected the question to talking about his amazing ability to implement this
methodology at his last employer.
The recruiter finished the interview, politely thanked him for his time,
showed
him out, and threw away his resume.>
<snip>
HEY! I thought you all were supposed to keep resumes on file for 7 years or
something like that? Or is that IRS records?
In my experience, methodology means squat to a client. They don't care if you
are Ioanian, Freudian or dyslexian (okay, they might care about a dyslexian).
What they DO care about is bringing the project in on-time and on-budget,
giving them a product - online help, user manual, technical documentation etc.
- that is easy to use, easy to understand and meets the needs of the target
audience. If you can produce, and meet or exceed the client's expectations,
you're well ahead of the game. If you're mired in minutae, like the guy who
interviewed at Andrew's company, it doesn't matter what methodologies you know
- if you don't meet the client's requirements you can kiss the opportunity
goodbye.
As for consulting firms that have their own methodology and use only that,
I've seen work that's similar. If it meets the needs of the client, great.
If not, is that consulting firm so big and powerful that it can dictate how
problems are going to be solved and how the final deliverable will look?
Excuse me, but what happened to client's needs?
Just my opinion,
jarnopol -at- interaccess -dot- com