For many years now, I've been active in a local group that features sundry activities. An event basically involves a member who is a leader deciding to lead an event and getting it listed in the group's newsletter, and other people reading about it and showing up.
Now, once upon a time, Back In The Old Days, there was a procedure for leaders to send in events: they'd type them up and mail them in. As I understand it, there was (before my time) a tradition of having a planning night just before the deadline for next month's newsletter, and leaders could show up and hand in events to fill in gaps.
There were two club officers involved in the process: the newsletter editor and the activity coordinator. It was more or less customary, if the schedule was sparse, for the coordinator to call around to leaders and solicit events (preferably ones for which the writeups were on hand and could be easily recycled).
Eventually, I started leading events, and then got talked into becoming activities coordinator when the previous coordinator took over the post of newsletter editor. This was about the time that email was becoming common, and we phased in a standard format for writeups-by-email. I also revived, for a time, the monthly scheduling party, though that proved to have limited utility, and eventually reverted to a meeting between myself and the editor, and any leaders who felt like stopping by; this meeting frequently generated phone calls to leaders to resolve conflicts, or to solicit extra events. Then the editor would take the collected material home and spend a few hours in front of his Mac, fitting everything to the template.
After a while, the editor left, and, following what had become tradition, I stepped into his place. By this time, we'd got the process pretty well sorted out, though I had to translate his template from Mac to a cheap desktop-publishing package (Expert Personal Publisher, if memory serves) under Windows 3.1. (I had grandiose notions of using TeX under Linux, but never did make the transition.)
The scheduling process went something like this: leaders would send their writeups (almost always by email by this time), and, as they trickled in, I would update two documents. One was the chronological collection of writeups, with preliminary formatting applied (30 seconds or so of work per writeup); the other was a summary list of event titles and times, which I sent out periodically to the leaders as the deadline approached. After the deadline, I just had to import the writeup collection, and any other material that had come in, into the template; fill in the calendar page by hand; make any necessary formatting tweaks; print and check proofs; print high-quality masters; and drop the masters off at the print shop, whence the guy who ran the mailing party would pick up the printed newsletters a couple of days later.
Typical elapsed time from deadline to mailing party was a week, though if memory serves it was sometimes as little as three days.
Anyway, I passed the torch, the template, and the process along to my successor, who made some tweaks before passing everything along to his successor, who made tweaks....
Then, a few years ago, we got a brand-new executive committee - a Slate organized by a Candidate with Ideas, and made up largely of people with little connection to the group. Only one old-timer was carried over.
The new committee made a lot of abrupt, and often ill-considered, changes. Among them was the replacement of the planning/scheduling process which had evolved over the years with a new, Designed process.
The Leader got someone (an outsider) to throw together a webapp for scheduling. Now, a webapp for scheduling is conceptually a great idea; in fact, I'd been working on one myself, but it was a ways from being ready. Unfortunately, what was got was something that wasn't ready either, but It Had Been Decreed that this was the replacement for the old process that worked.
Well, over the years since then, it's sort of worked, though the newfangled labor-saving system doesn't seem to save labor; elapsed time from deadline to finished newsletter in electronic form (no printing) runs 10-15 days. Thing is, the old process has gotten entirely lost, and now the webapp is suffering from software rot, and frequently just doesn't work at all (as, e.g., today, the deadline for November events). With the wonderful Designed process busted, and the old-fashioned manual process forgotten, we seem to have a problem here.
So what's the point here? Evolution is conservative and decentralized, and this is frequently a Good Thing. Intelligent Design is radical and centralized, and you'd better hope the Designer is omniscient, omniprescient, and omnibenevolent, 'cause otherwise you're SOL.
Recent Comments