Twitter Status Board

Several months ago, I noticed that one of the nearby offices was using a whiteboard mounted outside their office door to keep people informed of their comings and goings. “That’s good communication!” I thought to myself, “but my team is made up of geeks. Surely we can do something nerdier!”

Thus was born an experiment with Twitter that is yielding some good results. It began with our six-person development team: programmers who were interested in participating set up a twitter account and began posting what they were up to through the day. We subscribed to each other’s updates and easily keep a finger on the pulse of the team’s activity. (This was especially helpful when working off-site or stuck in meetings.) In addition to the standard Twitter functionality, we also wrote a little Rails app that uses Twitter’s APIs to build a replacement for the old-style In-Out board. People can pull up the status screen from a web browser or look at a monitor we stuck in the window of one of our cubicles to see at a glance who was around and what they were up to:

Status Board In Situ

Status Board In Situ

After a month of voluntary participation, we had a meeting to discuss whether it was worth keeping up, and decided that the minimal effort required to improve our communication was well-spent. We’ve been using the system regularly for several months now. (One interesting side-effect that I’ve noticed is that it helps me to keep on task a little better: when I post that I’m working on ticket #726, I feel a little guilty if I’m not actually working on it!)

Of course, people walking by quickly noticed the screen and asked whether it could be expanded to include other people as well. At my boss’ requenst, we put together another status screen for use at the department’s front desk, where the people there can quickly ascertain whether a call can be transferred or a visitor directed back to someone’s office. It looks like this (with strategic blurring to protect the unwitting):

Front Desk Status

Front Desk Status

The color-coding is done by preceding a status update with “IN:”, “OUT:”, or “OFF:” (for those times you’re working but not at your desk), a feature of our status board app. While some of the folks around the department were initially a bit skeptical, they have quickly become enthusiastic once they use it for a day or two. The front-desk folks decided that they’d rather have timestamps than the “x hours ago” notation we’d originally used, so we tweaked the app to better meet their needs.

We’re still refining our software (I need to make the caching smarter), there are at least two other Status Board applications under development in the department (using Javascript and FLEX), and I now quickly hear about it if something goes wrong with the system. It should be interesting to see where this thing goes over the next few months! (If there’s interest, I can clean up the Rails code and open-source it once I finish the caching improvements.)

Comments 7

  1. Adam wrote:

    This is really cool! I would definitely use this. Post an update if you ever make this available to the masses!

    Posted 27 Feb 2009 at 12:16 pm
  2. Scott wrote:

    brilliant. If it serves you in the cubicle setting, just imagine for a more geo-diverse team — couriers, delivery, anything with errands. Come to think of it, I haven’t heard an ad for the ludicrous Nextel walkie-talkie feature in a while. Maybe they fired the VP of Loud Beeping Public-Address Humiliation.

    Posted 01 May 2009 at 12:53 pm
  3. Scott wrote:

    That Nextel diatribe distracted me. I wanted to say also that the account above is good study in change management principles. It’s easy to see the plan-do-study-act cycle at work. Action is purposeful and consensual (uh, can’t say that anymore without the vice squad visiting; good luck with that; what a SHAME about our language); results are assessed, progress is consolidated; improvements made in response; organic growth is growthed, and the passive verb tense is used throughout. Text book stuff!

    Posted 01 May 2009 at 1:42 pm
  4. Adam wrote:

    Any update on releasing this to the world?

    Posted 05 Aug 2009 at 10:53 am
  5. SeanMcTex wrote:

    Hey Adam,

    No, unfortunately not. Some of the optimizations we made for our version make it tougher to distribute in a meaningful way. (We’re running a cron job to collect the data now and then writing it to temporary files which the display application reads. Good efficiency, but raises the bar for setting it up somewhere else!)

    I wish I had the time to clean it up and make it generally available, but for now I’m afraid I can’t swing it. :(

    Sean

    Posted 28 Oct 2009 at 1:19 pm
  6. Brook wrote:

    Are you able to post it as-is? With the full disclaimer mentioned above?

    Posted 29 Jun 2012 at 2:22 pm
  7. SeanMcTex wrote:

    Hey Brook,

    Thanks for your interest. Unfortunately, I think we’ve at a dead end on this for a couple of reasons:

    1. I no longer work at the U, and don’t have access to the source any longer.

    2. Twitter has changed their API since we wrote this thing originally.

    It would be a fun project to recreate, but alas, I don’t have the time.

    Cheers and best wishes,
    Sean

    Posted 02 Jul 2012 at 4:39 pm

Post a Comment

Your email is never published nor shared. Required fields are marked *