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.
Yes, but an increase in what you're calling Process Maturity Level
invariably leads to a decrease in what I call "Enjoyable Workplace." When
a company gets too stiff, it breaks, instead of bending. Of course,
that's just my experience, but I prefer companies with fewer processes
and more flexibility. I suppose that's why I tend to work for startups
more than megacorps, higher number of hours and all.
Just one opinion...
----->Mike
On 09/02/1999 6:12 PM, Anthony Markatos (tonymar -at- hotmail -dot- com) wrote:
>It has been my observation that, within the software industry, the average
>total hours worked per week is inversely related to the organizations
>Process Maturity Level. That is, as the Process Maturity Level decreases
>(moving from 5 to 0), the avg number of hours worked increases. Has this
>been your experience also?
