Seek Product Blog

Product blog Updates & Insights from the Product & Technology teams at SEEK

Team Health Check for focusing next improvement

18 Jan 2017

Team health and professional fulfilment for individuals within a team is super important to us. The SEEK unified purpose “to help people live more fulfilling and productive working lives and help organisations succeed” stands for us as much as it does the communities that we serve. A number of different team health conversations happen around SEEK. Recently one of our great Data Services team did a follow-up session using the popular Spotify Squad Health Check.

spotify health check cards
Simple yay, urgh, nay rating for team capabilities

The Spotify Health Check has become popular for a few key reasons:

  • the ease with which it facilitates insightful conversations,
  • the simplicity of the language and,
  • the adaptability for team specifics.

If you need to gain insight on what to improve next with your team, I highly recommend the Spotify Squad Health Check for gathering the necessary data and discussions. Pop on over to the spotify health check tools to learn how.

Our team added in some great team themes to their health check. These are values and practices that they feel are important to discuss regularly. The additional themes are:

  • prioritising
  • tools, architecture, environment
  • Feedback
  • Future of the team (certainty)
  • Socialising (within the team)
  • Communication
  • External Support
  • Decision Making
  • Code Standards & Reviews

Custom themes

You might see a correlation and even causation to the topics originally provided and think we’re doubling up. It’s not, it’s good forethought that the team call out what’s important to them so as to better be able to support and hold each other accountable in these areas.

image of health check for data services team
SEEK Data Service Team Trending Up for their valued capabilities.

The primary purpose of the sessions was to see the data on ‘team health’ and have a meaningful conversation about it – and to act more insightfully. As such, be sure to guide the team to agree on at least one improvement action before leaving. The nice bonus from this follow up session is that the team had a trend of improving on the majority of themes since last time. Whether you are better or worse than last time isn’t the primary purpose; however, in this case it was good to see that the team actually were doing better than perceived. Always good to acknowledge your own efforts as a team.

Thank you Tom and the very clever Data Services team for inviting me to host. :)

Written by Stephanie BySouth, Agile Coach