Gay

Chaos Monkey with People Instead of Software

The Seahorse writes code for a living so, in the same way that I am obliged to follow sports ever so casually (for instance the Chicago Cubs have hired a new, adorable player) I follow some software/dev/tech blogs so as to be able to hold my own in conversation–at least enough to return the ball back over the net (see? sports metaphor!) So a big h/t to Jenn Webb at O’Reilly who clued me in to the notion of using Chaos Monkey on people.

Kind of Like a Fire Drill
Software isn’t one thing, it’s a lot of inter-connected little ecosystems that all communicate with each other. Chaos Monkey randomly selects one of these systems and terminates it. This happens during the normal work-week, not at 3 a.m., so presumably you have the staff available to troubleshoot and correct the problem. It’s a way to force weaknesses to the surface so that you can plan to mitigate them when you are fully-resourced and at your best.

People are Interconnected Too
So what happens if you send somebody (anybody?) from one of your teams away on short notice? Would the team figure out how to fill the gaps? Could you test this tomorrow? What would happen if you picked someone at 9:47 a.m., whispered in her ear, “Take the rest of the day off without pay. Do not respond to any messages from anyone at work. See you tomorrow morning.” What would happen if you whispered the same thing in a second person’s ear at 10:32 a.m.?

This Sounds Terrifying
I know, right? And yet doesn’t that point to the need to actually try it?

 

Internal Resistance

It’s all so much, isn’t it? The waking up, then making a pot of coffee without aligning the carafe properly so as to cause the whole mechanism to distribute a slurry of hot water and coffee grounds throughout the device.

This is what Sisyphus did, if I’m remembering this correctly, he labored to rinse out the wet coffee grounds from every orifice of the goddamned coffee maker and yet there were still tons of wet coffee grounds lurking everywhere like I haven’t been doing anything.

Also one of my socks is developing a hole in the toe even though they cost almost $9 and are less than one year old. 

Worse, the sun is incredibly bright, making it uncomfortable for me to sit at my favorite spot at the dining room table, forcing me to choose a different chair, one slightly farther away from the electrical outlet thereby causing the cord of my a/c adapter to extend more than I am accustomed to therefore possibly creating a scenario where The Seahorse will come along and, in his haste to kiss me on the forehead, trip over the cord and send the Chromebook crashing to the ground.

So you see, it’s the combination of terrible things that have happened, along with the terrible things that could happen, that are preventing me from making any forward motion on my important-but-not-urgent-quadrant.

PMBOK and Boy Bands

PMBOK stands for Project Management Body of Knowledge and folks tend to pronounce the acronym as PIM-bawk.

It’s all captured in a book full of jargon, diagrams, and math formulas. In other words, it’s kind of intimidating.

The best approach I’ve found is to pretend that PMBOK is like a fussy baby, a scared dog, or other savage beast that might be soothed by singing to it.  Fortunately Hanson is here to the rescue!

You’ll find that singing  PMBOK to the tune of “Mmmbop” will soon have your computations of earned value, planned value, and actual cost moving forward in harmony.

Self-Organizing Teams and a Magic Question when you Get Stuck

I’ve been reading Galina’s post about self-organizing teams, and while she illustrates her thoughts with a picture of a unicorn, she has several thoughtful ideas about self-organization, including a realistic appraisal of what is reasonable and what is unreasonable to expect from a self-managed team.

Ever been in a romantic relationship? Congratulations; you’ve been on a self-organized team of two. Did you guys magically achieve consistent harmony, no matter what the situation, through the sheer force of your luuuuuuv? No, of course not; you had to communicate, and you had to rehash familiar territory over and over again.

That last part sucks, no? Here’s a tip for when when you are feeling stuck and keep talking past each other:
I’m concerned that I don’t fully understand your point-of-view, so I’m going to say what I think your p.o.v. is and I’d like you to please correct me where I’ve gotten it wrong. Then we’ll trade places.

Here’s why this works:

  • We repeat ourselves because I want to hear you but I want to be heard first. Making the turn-taking explicit (and giving them the first opportunity to be understood) breaks that cycle.
  • We repeat ourselves because we fear we aren’t heard, so the reflecting makes your listening tangible.
  • We repeat ourselves because we fear we aren’t understood, so accepting the correction (I assumed you were concerned about the budget, but it sounds like the deadline is a much bigger concern for you. Do I have that right?) helps us to move from adversaries who have opposing points of view, to allies searching together for a win-win solution.