A Work Team Is Defined by Its Work

This is going to sound familiar to most of you. Someone in your company has decided that people need to bond. Create a family. And usually the preferred method for doing so is… EVENTS: off-sites, parties, hikes, concerts, talks, games, birthdays… just to name a few.

The Mission, San Francisco
  1. They don’t engage at all and just go home or do something else. “My laundry and my plants definitely need me more than the company.”
  2. They engage but nothing else happens. They attend the event, they do whatever they are supposed to do, and then they leave, with no practical difference.
  3. They engage TOO MUCH: “I don’t have anything to do today and I’m going to leave these suckers in a couple of months, so I’ll spend the rest of the evening just hanging out and drinking as much as I can on company money.”
  1. Two hours every Friday afternoon, blocked off to do coding katas and present our work to the rest of the team.
  2. A fridge full of beer (sometimes paid for out of my own pocket, something nobody here could possibly believe).
  3. Nerf guns.
  4. A lot (A LOT) of work to be done.
  1. A challenging project with challenging conditions. A project where almost everybody could fail.
  2. Endless learning.
  3. Pride and love for our work.

I’ve been into software engineering for the most part of my life so I have thought long and hard about it. Now I‘m just writing it down.