Some years ago, I wrote a 400-page book (Downloads a 4MB PDF file).
This book was hopelessly naive, and isn’t something that I am currently pushing, but it was where the term “MAGNAWS” was born. “MAGNAWS” stands for “Making A Great NA Web Site”, which was the title of the book.
The Beanie was a character that I introduced on Page 13. This was The Dreaded Propeller Beanie of Death. Here is the text that I used to describe The Beanie:
Allow me to introduce you to a character that many people who work in the technology industry will find quite familiar: The Propeller Beanie of Death (also known as the Bastard Operator From Hell). “The Beanie” is an addict with complete control of every aspect of the Web site, and that uses this control to enforce their own will. No one else can get a word in edgewise, and no one can wrest control of the site from this person. “The Beanie” has all the passwords, registered the domain names under their own name, and has complete control over all of the site’s source code. The Beanie may even be paying for the hosting out of pocket, or may own the servers.
In true addict fashion, they have taken the site hostage. The only content that goes on the site is that which The Beanie has vetted or created, and the site often becomes a soapbox for The Beanie’s own viewpoint. Even worse, the content contains material taken from other sites that would object to having their content displayed outside of their control (for example, copyrighted N.A. literature, or copyrighted images).
Sound far fetched? It shouldn’t. This is a very real danger in service. N.A. history is rife with service committees gone wild. Addicts tend to have…how shall I put this?…an excessive need to be in control. We’re funny that way. The Beanie’s motives may actually be very noble and good. However, there’s a road leading somewhere that is said to be paved with good intentions…
An unfortunate and very serious reality is that failure of the N.A. message is not just an inconvenience. It can result in terrible tragedy. The Disease is extremely serious. The almost certain result of The Beanie is someone, somewhere will suffer terribly. This is serious. All N.A. service is lifesaving service. When we allow our egos or personal obsessions to interfere, we can cause awful damage.
The message of this page is: Don’t be The Beanie. Also, don’t suffer The Beanie. If the site won’t get constructed unless you let The Beanie have control, then don’t do the site. The bad far, far outweighs the good. Make sure that the Groups always have complete and final control of the site.
The relevant concepts here are:
- (The Groups Own the Service Structure -Non-negotiable);
- (The Groups are the boss);
- (Authority comes from The Groups, and The Groups can rescind said authority);
- (If The Groups put The Beanie in charge of their site, it’s their fault);
- (There needs to be someone who will take the rap -”accountability” is the operative word here);
- (God’s in charge);
- (Everyone gets a say, and this implies that a Service Body is comprised of multiple members);
- (We need to keep up on current events within our own Service Structure);
- (Again, one person making all the decisions is not always a good thing);
- (We can’t have an absolute dictatorship);
- (N.A. Funds, get it? It is a VERY BAD IDEA to let someone pay for an N.A. service, as they tend to feel as if they own it. As a point of law, it can usually be established that they do, indeed own it); and finally,
- (We’re back to The Groups being the boss, and the Service Subcommittee works for The Groups).
That seems to indicate that The Beanie goes against every single one of our concepts. Take it seriously.
