Month: June 2009

On Crisis Fatigue

I’m not (usually) horrifically rude, but I happened to glance at the page of the woman next to me on the bus this morning and saw the words “crisis fatigue” at the top of one of her lists. Then I stopped reading and started typing this (honest!) because it got me thinking about the impact of crisis fatigue on geeks.

I don’t know the last time I talked to someone who wasn’t crisis fatigued to some extent. Just think about the news that we see every day:

  • The economy and its parade of tax hikes, layoffs, bankruptcies, and pyramid schemes
  • Swine flu and pandemics
  • Wars and violence–both foreign and domestic

Then add politics, traffic, weather, and the total randomness that folks call news. Now add work. It just seems like, as a society, we’re chronically over-stressed, under-staffed, over-caffeinated, under-funded and just plain tired.

Now think of geeks. Many of them live in environments of almost constant crisis. Servers and switches crash, applications are buggy, and few work environments these days have the staff or budget to fully replace the equipment or fix the problems. Add to that the sheer complexity of the products or systems supported and you can be certain that most of the user community has no idea why there are so many problems and why they’re taking so long to fix.

Are there ways to remedy the geeks’ and users’ stress? Absolutely. I’ve talked about having fun and communication as good remedies. But is it hard to remember to share a joke or communicate properly? Absolutely. There aren’t enough resources–humans, time, money, or hours in the day–to do things perfectly and remember to implement the remedies.

As a leader, it’s my job to be aware of crisis fatigue and attempt to implement remedies despite being crisis fatigued myself. Do I always succeed? Nope. I’m sick, exhausted, and stressed just like everyone else. But I do my best, and I’m glad that my moment of bus rudeness has made me more aware of the problem.

On the Meaning of Leadership

As some of you might know, I’m the point person on publising content for the ILTA ’09 Conference Blog. On Fridays, we publish a “Profile in Leadership” of one of the volunteer leaders of the International Legal Technology Association (ILTA). One of the primary questions we ask during the interview is, “What does leadership mean to you?” This, of course, got me thinking about how I define leadership.

To me, leadership means:

  • People want to follow you
  • You have somewhere to go
  • You can be creative and flexible in defining your goal(s) and how to get there
  • You use your followers’ diverse strengths
  • You admit that you’re wrong when you are (as I always say, “I’m perfectly happy to admit that I’m wrong–after it’s been proven to me.”)
  • You have self-confidence
  • You can be humble
  • You shine the spotlight on your followers
  • You take responsibility when things go wrong
  • You are primarily collaborative, but can be authoritative when the situation demands it
  • You evolve

There are undoubtedly many other characteristics of a leader, but these are the ones to which I aspire. These, however, are the traits that come more naturally to me or that align with my personal values. Others define leadership according to their personalities and values, and may have a vastly different idea of what leadership means.

ILTA’s “Profiles in Leadership”
fascinates me, as many of the people profiled are role models to me in my legal technology career. As I read them each week, my definition of leadership might change, thus fulfilling my last trait of leadership above–I will evolve.