Dust a Meeting

Meetings are insatiable productivity black holes that complicate lives and ruin workplace flow. I recently tried a collaborative online system called Basecamp in order to asynchronously develop a software strategy at work. What I wanted and what I observed diverged so thoroughly that there was absolutely no point in continuing with Basecamp as it was just in the way. The entire endeavor made me a little sad, not a huge fan of failure.

Meetings themselves are time vampires. I loathe them with every fiber of my being. They are massively interruptive and obnoxiously presumptive. You set aside a date and time and a place where people have to attend to discuss some topic. A meeting is a monster even when it’s in the cradle, being thought up by someone who desires to meet. Out of their heads pop a snarling tentacled beast with sharp fangs that serves no purpose but to interrupt flow and get in everyone’s way. Even the birth of a meeting is an arduous agony, with each participant (or combatant) the multiplexed temporal complexity grows. Two people can find a time to meet. Three people and it’s an order of magnitude harder. I was attempting to arrange a five-person collaboration and I wanted to avoid a five-person meeting with every ounce of willpower I could muster. My intentions were to establish a five-person collaboration which leveraged technology (Basecamp) to achieve speed and productivity because all five collaborators could function asynchronously. You could contribute what you felt you had to when it was right for you. It respected flow and was not supposed to be interruptive or presumptuous. Alas, the road to hell is paved with good intentions and this particular road lead to the very specific hell of a worthless unwanted but agonizingly unavoidable and loathsome meeting.

So now my efforts to avoid a meeting inexorably landed me right into setting a meeting up. Of course it was obvious that right after the first few responses I could tell the tell-tale sloppy-wet-sucking-sounds of a baby meeting unfurling it’s tentacles in my midst. The first agony of course is finding a time when everyone is free for a meeting. So right off the bat, two weeks went down the toilet as we had to wait for everyone to be ready. Then assembling it was a pain. It used to be easier with Groupwise, as a meeting organizer could see the public calendars of all the participants and select the time that would be best and then send it to all the participants which really reduced the interruption of flow quite a lot. Alas, we led Groupwise out behind the barn and we did-what-must-be-done. After we were done burying the corpse of Groupwise we were back to the way it was before – so A emails B, C, D, and E. Then they all reply, and then A shakes the magic eight ball and everyone agrees that in three weeks, we’ll all have time. It’s a lot of back and forth and this and that and it creates a nasty haze of meaningless email exchanges. So, the meeting is ripe for tomorrow at 3pm. Great.

So now I wait. I have a list of all the software we currently use and instead of spending the past two weeks discussing, asynchronously, the merits and flaws and coming up with a solution in at most a weeks time, this nascent baby meeting will likely take another month before there will be any resolution. Tomorrow is just going to be the First Meeting, where we trot out the new baby time vampire and give it a good feeding.

It’s a terrible way to do work. It trashes flow, it lowers morale, and it sucks time down a toilet drain. At least people aren’t fond of the parliamentary species of time vampire meetings, where you spend the first few iterations of the meeting discussing protocol on how subsequent meetings are to be held. That form of meeting is older, and much worse. I really must count my lucky stars that we usually only have the easier-to-cope-with modern meetings where the first three get-togethers aren’t set aflame with discussions on what words mean, how we are going to proceed, or what the definition of is, is.

There is wreckage however, even with a modern meeting. The person who had a problem and started all of this still doesn’t have what they need to get work done – we’ve been waiting for that special moment to arrive when we all can pet the baby time vampire and let it ruin our working lives. I can’t really get worked up very much, as least not as loudly as I used to a long time ago when I felt I could change things. It was pretty much obvious from the start that when the discussion immediately derailed with that most hated of questions “So, when shall we meet?”, heh, that was it. I knew that asynchronous collaboration was not going to work.

What’s really quite sad is that the technology has developed quite well and very elegantly. You see the edits and the collaboration realtime, there is “What’s new” and “Catch up” features, it’s free for 45 days, all of it – right there. Ready, willing, able, and if used, the promise of reaching a solution sooner-rather-than-later can be realized. Instead of that path however, we are going to have a meeting.

Not that anyones life is on the line for the work that has to be done, just the soul-crushing dread of having to endure another time vampire meeting. Having to go somewhere at a specific time, putting everything else on hold while we all waste our time and energy. The wry humor in the idea that we could have been already in the yea/nay phase and quite possibly be sending orders out to finalize the entire project, it could have been that way.

What have I learned? That I won’t ever do this again. Part of the agony of watching a grand design fail is watching it fail in flames. Modern business culture just isn’t ready for the kind of asynchronous ease and productivity that these tools can provide. I’ve written before, tongue-in-cheek that hateful meetings are like intellectual memetic herpes. It’s a theme that we play over and over again, not because actually having meetings leads anywhere but that instead we’ve always had meetings and our peers seem happy and life goes on, so why seek out anything else? It’s an idea, a meme, that is replayed again and again. The fact that meetings are time vampires that suck all the happiness and color out of life isn’t actually a part of the deal. Nobody seems to notice. Every once in a while one of us wakes up and shakes their head and asks “Why the hell are we having these stupid meetings?” and then tries something novel. Then that detestable question, “So, when are we meeting?”

That question should be engraved on a gun. Instead of asking it, just load one bullet, spin the revolver chamber, clack it home and pull the trigger. So, in the end this is all so much bellyaching over nothing. Asynchronous collaboration isn’t ready yet, or more specifically we aren’t ready for it, yet.

Not every industry has this problem however. You see companies like Automattic, which is the parent company that manages the WordPress technology – they make use of the P2 theme which is a central driver (so they say) in how they manage their projects and such. I’m sure Automattic has meetings, but I suspect that they use asynchronous collaboration a lot more elegantly than is done in higher education or the non-profit sector. When I first started exploring Basecamp, for example, I was blown away. I could collaborate with my assistant and material would build because when we were both working on the project and working together as a team brought a kind of science-fiction cool to the dull things we were collaborating on. There is something quite breathtaking about watching an entire project morph and change and grow as you sit there and watch it. Like timelapse only in real-time. Another little bit that I really found super-compelling was how these technologies enabled asynchronous collaboration and respected workplace flow. There was no interruption, if you were in the middle of a task you could polish it off quickly and confidently because time wasn’t important. The collaboration could occur at any time. It also occurred to me that asynchronous collaboration might also benefit from the differeing themes of cognition during different parts of the day. That you are more clever for some things right after dinner than you are before tea, or if you wake up at 11:30pm with a sudden Eureka moment, you could hop on to Basecamp and share your stroke of genius.

Alas, this is all just prattle against the memetic herpes epidemic that is the meeting.

It warms my heart to imagine a world without telephones and no rooms in which to meet. It would preclude meetings completely and banish them to extinction and force asynchronous collaboration. *sigh* It’s only a dream I suppose.

P2 or Not P2

Today has been an odd silly day. It started out with an odd fanciful notion to investigate WordPress.org and possibly host it on a Mac Mini. My design was to create a workplace blog, theme it with P2 and whip it out on my coworkers and see how it worked for them. It’s not really a Wiki, we have that, and the Wiki software we use is Apple’s own that comes with their Server OSes, but the blogging component leaves something to be desired.

I saw WordPress.com pushing P2, a theme that fits into WordPress.com or WordPress.org and enables Automattic, the company behind WordPress to communicate more efficiently. My interest was piqued.

So I started with that original idea, then my assistant reminded me that I have a huge monster HP 1U server that I never use and it has Ubuntu on it. I had a little Eureka moment and decided I could work with that. I downloaded the WordPress.org software and went over the installation manual. I got everything edited and in-place and looking nice in the terminal window but couldn’t get the wp-admin/install.php screen to appear so I could finish the WordPress.org installation. I futzed and putzed and figured out I was missing some things, like a different kind of PHP, as well as PHPmyadmin. Once I added all of those various bits I tried it again. No dice. I finally figured out that when I created the “wordpress” MySQL database and user that I botched up the name and host information and didn’t see it until I blundered my way into PHPmyadmin. With that tool I fixed the problem and then everything was fine. I installed JetPack Plug-in, which promptly exploded in my face. JetPack needs to chat back and forth between WordPress.com and whatever machine you are installing WordPress.org on. This server here is firewalled on the wire and can’t be seen by any outside-to-WMU system, so that put the kibosh on JetPack. I still wanted to try P2, so I installed it and it worked like a charm. Then I ran into the same headache I always run into with these systems: SMTP. Here at WMU there is a huge barrier to access any network services, especially SMTP. So how could a WordPress.org P2 blog ever really work right if the server it’s running on can’t ever send out email properly? Oh, I tried to be clever and I failed. I tried to forge a CA, I tried lots of hints to try to masquerade into smtp.gmail.com using TLS, and I tried sendmail and postfix. Bloody hell. I would rather eat glass than have to see sendmail.cf again. I’d rather massage the tongue of a rabid wolverine than futz with postfixes main.cf file again! I mashed my head up against that brick wall until I took a step back and asked myself why the hell I was going to these lengths for something so tangential.

So then it struck me, if we’re using WordPress.com for the heavy lifting for most of our content management, why couldn’t I just create a new blog for our workgroup, slap P2 on it and carry on? That had its own problems. In the beginning I set everything up with Western Express and set my “Gravatar” to be associated with my work email address of andy.mchugh@wmich.edu. All fine and good until you try to use that address anywhere else! WordPress is picky. So I logged into WordPress.com thinking I could change my accounts email address in WordPress, as it turns out, you can’t. You have to go to Gravatar and change it there. It’s not so much change as put in a new address, switch it to primary, then rip out the old address. A lot of work for something that was supposed to be easy. Blargh!

So I got everything switched around and freed my work email address then re-approached WordPress as if I was a new user. I logged in using my work address (which is the most appropriate address for this pursuit) and created an account. I got the automated email verification message and clicked on it. WordPress refused with the error: “Could not create user” and so I emailed support at WordPress for help. Still waiting to get some TLC from the support people as of the writing of this blog-post.

Along with all of this I’m wondering if P2 will be well received? Will my coworkers see this as one more silly thing that I’m making them all use? I’ve pounded Wiki use into their heads, I’ve done a lot of things behind the scenes that none of them see now but will that will also radically change their working lives (for the better I assure you) and then I sit and wonder. I wonder if P2 is a solution that could work for us? If it works for Automattic, shouldn’t it work for us as well? I’m on the fence on this. I’ve whipped out so much new technology on these people, will they accept another massive change to how they communicate or will I be facing open revolt? I see this idea of mine shaped this way:

A private group blog that everyone can log into anywhere they are in the world, obviating the need to use any kind of VPN system as WordPress.com is available ubiquitously. It would enable people to hold online communications, post instantly like Twitter, post without limit to text (unlike Twitter), include rich content such as YouTube embeds and such all the while managing the conversations and using categories and tags to track different sections of our communication infrastructure. I imagine using P2 as I would have maybe used Google Wave if it was matured properly and supported by Google and not killed in its infancy. That we’d use several big tags such as “Donors” and “Help Desk” along with a constellation of other tags and not have to struggle with email distribution lists and missing information and delayed communications, all of that could be eliminated. On the flip side of that argument is “This is one more thing that you are forcing on us and making us learn.” I’m struggling with how P2 could fit in with our lives and whether this is a valid pursuit or just so much “chasing after the shiny”.

There are several of my coworkers that I’m nearly certain would go stark raving mad if I whipped just one more thing out on them. I just can’t deny the allure of all of these services, WordPress, DropBox, 1Password, Evernote… that their ubiquity online and their omnipresence in the mobile computing sphere is terribly attractive to me. That a workforce that I deeply suspect will be forced to become more mobile and nimble almost demands that I continue this breathless rush towards the bleeding edge.

So what I really would like is to find anyone other than Automattic who found P2 to be useful. It would gratify me immensely to know that P2 was a ‘game-changer’ and serve also as confirmation that I am on the right path and that this whole charge towards shiny actually serves a true and honest business purpose beyond my wanderlust for novelty.

As always, I would really love people to comment, I’m looking for evaluations, opinions, you name it, every bit helps. I thank you all in advance. 🙂