A lot of companies experiment with ways of measuring and visualizing how their teams are doing (KPI’s; ROV’s, NPS, etc.,) looking for areas where there are opportunities for improvement. The general idea being ya can’t improve what ya don’t measure. And without some sort of systemic approach with clear visualization – things would very much be a guessing game.
Two questions often come up when discussing team engagement and morale:
- What are things I can do to impact team happiness (positively)?
- Can I really measure happiness?
First the Bad News
Without some magic pixie dust, you just can’t make someone happy. You can, however, create the conditions that are conducive to happiness. These conditions can be things like practices, resources, and environments.
Management 3.0 provides a great place to start, with 12 things you can put in place to “manage for happiness”:
Now the Good News
You can experiment with any or all of these 12 things and then monitor the results. Which answers the second question.
There are many great visualization models out there. Let’s start with one that Spotify (Henrik Kniberg & Kristian Lindwall, Sep 2014) created and recently refined.
How the Spotify Team Health Check Works
The Spotify health check looks at approx 10 areas of inquiry, each with three possible “ratings,” and columns for each squad aka Product Team.
For each area of inquiry, each team is asked to rank where they are and what the trend is (stable, improving, or getting worse.) Color coding and arrows helps visualize things:
- Green – Awesome (or damn near!); doesn’t necessarily mean things are perfect. It just means the team is happy with this area, and see no major need for improvement right now.
- Yellow – There are some important problems that need addressing, but it’s not a disaster.
- Red – This is really crappy and needs to be improved.
- Up arrow – Things are getting better over time
- Down arrow – Things are getting worse over time
- No arrow – Things are pretty much stable
Areas of Inquiry
The areas of inquiry are chosen to cover a wide range of different perspectives. Following are my suggestions, based off of the Spotify’s model, along w benchmarks for ratings:
Area of Inquiry
Example of Awesome (Green)
Example of Crappy (Red)
|Easy to Release||Releasing is simple, safe, painless & mostly automated.||Releasing is risky, painful, lots of manual work, and takes forever.|
|Suitable Process||Our way of working fits us perfectly||Our way of working sucks|
|Health of Codebase / Quality of Work||We’re proud of the quality of our work and with what we are producing! It is clean, easy to read, and has great test coverage.||Our code is a pile of dung, and technical debt is raging out of control. We are not meeting our own expectations.|
|Delivering Value||We deliver great stuff! We’re proud of it and our stakeholders are really happy. We have a good balance between working on “Capabilities” (Value for Stakeholders) and working on “Chores” (Value for Team)||We deliver crap. We feel ashamed to deliver it. Our stakeholders hate us. We never get to our chores.|
|Speed||We get stuff done really quickly. No waiting, no delays. We make at least 80% of our sprint commitments.||We never seem to get done with anything. We keep getting stuck or interrupted. Stories keep getting stuck on dependencies. We make our sprint commitments less than 25% of the time.|
|Mission||We know exactly why we are here, and we are really excited about it. The territory we cover is “just right” for our team size and mix of capabilities.||We have no idea why we are here, there is no high level picture or focus. Our so-called mission is completely unclear and uninspiring. The ground we are required to cover is way too large.|
|Fun||We love going to work, and have great fun working together||Boooooooring.|
|Learning||We’re learning lots of interesting stuff all the time!||We never have time to learn anything.|
|Support||We always get great support & help when we ask for it!||We keep getting stuck because we can’t get the support & help that we ask for.|
|Pawns or Players||We are in control of our destiny! We decide what to build and how to build it.||We are just pawns in a game of chess, with no influence over what we build or how we build it.|
|Teamwork||We are a totally gelled super-team with awesome collaboration||We are a bunch of individuals that neither know nor care about what the other people in the “team” are doing.|
Other Agile Team Health Check Tools
The Gallup Group offers a Fortune 500 Employee Engagement Tool:
Q12: Gallup Employee Engagement Center, for small-to-medium sized businesses, is your solution to measure what matters, strengthen your workplace, and boost your bottom line by accessing the same powerful engagement tools used by leading Fortune 500 companies, from $15 per employee.
The Q12 is a baker’s dozen:
- How satisfied are you with your company as a place to work?
- I know what is expected of me at work.
- I have the materials and equipment I need to do my work right.
- At work, I have the opportunity to do what I do best every day.
- In the last seven days, I have received recognition or praise for doing good work.
- My supervisor, or someone at work, seems to care about me as a person.
- There is someone at work who encourages my development.
- At work, my opinions seem to count.
- The mission or purpose of my company makes me feel my job is important.
- My team members are committed to doing quality work.
- I have a best friend at work.
- In the last six months, someone at work has talked to me about my progress.
- This last year, I have had opportunities at work to learn and grow.
MoodApp was designed and built by Atlassian to capture their teams’ feedback. It allows employees to provide feedback daily, and gives the company the opportunity to respond and adapt immediately if there is a problem brewing. It’s free. Not much is terms of analytics or a dashboard, but you can export cvs data files and roll your own. If you go down the MoodApp route, maybe start w the following five questions:
- How fun was this week?
- How satisfied are you with *your* performance this week?
- How do you rate your team’s ability, collaboration and joint efforts this week?
- Did we do adequate planning in advance of our work this week?
- How was your ability to focus this week?
New to the scene is TeamMood.com – which provides daily email prompts and a most excellent analytics dashboard!
Net Promoter Scores are typically used at the organizational level to assess the effectiveness of operations or strategies. But the approach could easily be adapted to teams:
- Survey your teams as well as organizational leadership on issues such as trust, ownership, and dealing with ambiguity.
Comparative Agility Survey
Comparative Agility™ is an assessment tool created by Mike Cohn of Mountain Goat Software and Kenny Rubin of Innolution to help teams compare their use of Agile against others and help determine actionable next steps in their own agile improvement efforts. It’s free. Not directly a happiness metric… but I suspect there’s a nice correleation between agility and morale…
Nöjd Crispare Index – The Crisp Happiness Index
Open source approach http://dna.crisp.se/docs/happiness-index.html with 3 main questions in the survey:
- How happy are you with being at Crisp? This is the main overarching happiness index.
- How happy are you with your tasks in Crisp? This means internal work such as board meetings, conference facilitation, or creating this Crisp DNA site. This is especially relevant for our office team, who do most internal work and have no external clients of their own.
- How happy are you with your current client, or your bench situation? We measure this separately, because sometimes a person could be really happy with Crisp, but sad about the current client. Or vice versa. For people who are on the bench (= no client at the moment), this can express how they feel about that (sometimes people WANT to be on the bench).
The scale is:
- 5 = Super-happy! Don’t want to change anything!
- 4 = Pretty happy, but there are some things that need to be fixed.
- 3 = I can live with this, but there are many things that need to be fixed.
- 2 = Not feeling so good about this right now.
- 1 = This is crap! I want out.
“The barometer is executed as a survey in a workshop. The survey consists of 16 team characteristics, packaged as a deck of cards. Team members vote green, yellow or red for each card in the meeting (or before the meeting as an anonymous survey). Once all cards have been run through, the team reflects and discusses the results.” Takes 30-50 minutes. Click here to download the cards. (Full overview w variations)
The Team Morale metric is a modified version of the UWES by Wilmar Schaufeli and Arnold Bakker, a psychometrically validated and reliable metric to assess work and well-being.
TeamMetrics was created and shared by Christiaan Verwijs as a “hobby project.” (Thanks Christiaan!) It is a simple, free survey tool to help Agile teams improve by gathering objective data about key team factors such as team morale and interpret the results with the help of benchmarks. Christiaan also has a great post on “health” vs. “morale” – Agile Teams: Don’t use happiness metrics, measure Team Morale – a nuanced and meaningful distinction…
Who A Health Check / Moral Metric Model is For
There are two stakeholders for this model:
- The team itself. While discussing the different indicators (red/yellow/green, improving, deteriorating, stable), the team get the chance to build up awareness and discuss what’s working and what’s not. The right (and broad) selection of questions will help expand their perspective without being exhausting. (Perhaps they were focusing on code quality issues, but hadn’t really thought about the customer value perspective, or how fast they learn.) This visualization model also provides a balanced perspective, showing the good stuff as well as the pain points.
- People supporting the team. Sponsors, Product Owners, Managers and Coaches that work outside (or partly outside) the team will get a high level summary of what’s working and what’s not. This stakeholder group can also see patterns across multiple teams, e.g, by looking across rows, or by noticing how many arrows are pointing up vs down.
What It is Not
- A health check model is not a competition nor a comparison across teams. If team A is mostly green and team B is mostly red, that doesn’t mean team A is “better”. It could just as well mean that team A has a simpler context or a more optimistic outlook, or that team B is more honest about their struggles. Either way, the model and visualization tool is about support and improvement, not judgement. The organization’s attitude should be “how can we help?” and not “why are you guys worse than the others?”
- This is not an incentivized model – there’s no reason for a team to want to game thing just to “look good.” Our teams intrinsically want to succeed, and will perform as well as they can under given circumstances. This model is meant solely as a tool to help boost and focus team improvement efforts, for the sake of improvement alone.
- “Done.” Like everything we do, inspect and adapt. If this model helps teams, keep doing it. If there are ways to make the model more useful, try them. If a team find no value in this, stop it.
As George Box said, “all models are wrong, but some are useful.”
Technical Health Metrics
There are many other lenses to look through to get a glimpse of “how the team is doing.”
For a few dozen ideas the team might consider related to process, release, product, and technical / code metrics, see: Understanding Agile Team Metrics
Managing for Happiness
I personally have experimented with most all of the above on various teams over the year. Will any of them work for you? I honestly can’t tell you. But what I can tell you is that it is worth trying something.