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.
Subject:Re: Formal vs. informal organizations From:David Farbey <dfarbey -at- BAAN -dot- NL> Date:Mon, 8 Mar 1999 14:53:32 +0100
I have to agree with Steve. From my experience the problems of too little
structure are far more frustrating than those caused by too much structure.
There's a trite piece of office humor about a job given to four characters
named Somebody, Anybody, Everybody, and Nobody, which actually has a point.
If work and responsibilities are not properly allocated and demarcated, some
work is done twice, other work is ignored, and everyone is unhappy.
Of course successful organizations benefit from the informal networks of
contacts built up by the people in it, but there has to be some framework.
Otherwise, who's going to pay the bills?
dfarbey -at- baan -dot- nl
> -----Original Message-----
> From: Steven Jong [SMTP:SteveFJong -at- AOL -dot- COM]
> Sent: Monday, March 08, 1999 3:38 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Formal vs. informal organizations
> In response to Andrew's posting, I started to lay out the opposite
> but it's too embarrassing to list the problems I've encountered in
> and companies that lack organization and structure.
> Rather than stake out a contrary view and work back toward the
> middle, let me
> just point out that without some level of organization, you can run into
> trouble with as few as two people, if one disagrees with the other on how
> proceed. Without process, every problem, even the one that crops up every
> release, is a crisis. Without standards, you end up with nonstandard
> Without management support, you can run into trouble over something as
> as two assignments for two clients if both of them demand you make them
> top priority. Without hierarchy, an "entrepreneur" can steal your
> for his projects. And without standards, good work is not repeatable.
> Having seen each and every one of these situations in my career, I
> would say
> that I wouldn't work in a place without some structure.
> -- Steve
> Steven Jong, Documentation Team Manager ("Typo? What tpyo?")
> Lightbridge, Inc., 67 South Bedford St., Burlington, MA 01803 USA
>mailto:jong -at- lightbridge -dot- com -dot- nospam 781.359.4902 [voice]
> Home Sweet Homepage: http://members.aol.com/SteveFJong