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.
Okay, now we've lost sight of reality. Come on. Of COURSE it happens!
Projects DO fail due to lack of skill (or go over budget, or get delayed, or
alienate customers - which are all failures according to one VP or another).
Coding, writing, or whatever example you'd like to use - there are people
out there who simply are not good at what they are trying to do. You can't
Plan and Standardize an unintelligible sentence into helpful instructions;
you've gotta have someone at the keyboard who can write.
Tony, you claim you've NEVER seen a project fail due to lack of skill. Have
you never, in 15 years, had to let someone go or transfer them to another
department because they couldn't keep up? Have you never given someone a
below-satisfactory performance evaluation? Have you never watched a software
implementation fall behind schedule because every round of testing uncovers
new bugs in the code? Or, more to the point, have you *never* seen a single
publishing deadline missed due to doc errors that had to be fixed before
shipping? That was lack of skill.
From: Anthony Markatos [mailto:tonymar -at- hotmail -dot- com]
..When was the last time you heard of a development effort failing because
of a lack of knowledge of coding technique - it never happens. Development
projects fail for the same reasons as TW do - inadequate analysis,
estimating, organizing, and standardization.