Podroll: PETALS, Spotify or Atlassian?
This is a sample episode from Si’s latest side project PETALS where he shares insights to his continuous improvement team health framework.
Transcript
This is the 10th Petals snapshot of a spring 2024 and today I want to talk about the difference between Petals and other team health frameworks. So the other day we were talking.
Speaker B:About team health across an organisation and.
Speaker A:Which framework to use petals KB, which was great, the Spotify squad health check.
Speaker B:And at Latissons team health books.
Speaker A:That is also quite a well known standard for me. I'm obviously a little bit biased, but I did say it depends on the situation.
Speaker C:I find petals is really useful for.
Speaker B:Getting more regular pulse because it's very quick.
Speaker A:You can complete the data in minutes, you can discuss within a few more minutes and then you're done. Whereas the other two frameworks, the Spotify and the lattice and ones are quite comprehensive and detailed, they are touching on some elements of what petals covers, but there's a lot more deep rooted conversations required for those frameworks as well.
Speaker C:For example, there are certain areas around.
Speaker A:Team vision and purpose and what our.
Speaker B:General approach is going to be and.
Speaker A:Specific ways of working as well as a team. Those things aren't covered in petals, we just catch it all together under teamwork and productivity around those areas. But the other two frameworks, because they're quite comprehensive, with 13 or eight different metrics to go through and discuss, you will need a lot more time, generally around an hour or two, depending on the size of your team.
Speaker C:Those frameworks are quite good for new.
Speaker A:Teams, they're quite good for quite old teams and, you know, long lasting teams storming, performing, norming, all those things as well. So I'd suggest those things are discussed on a less frequent basis, maybe every quarter, six months or year pedals, though that can be done daily, weekly, fortnightly, monthly, whatever your preference.
Speaker C:That's where I see the difference.
Speaker A:It's not necessarily a competition, it's just two depends on the circumstance and how much data you want to play with and how regularly you want to iterate. And again, going back to my roots, I like more faster feedback. I like it to be more regular and more simpler.
Speaker C:That's why I prefer petals, because it.
Speaker A:Just gets a really rapid response and easier, quicker conversation.
Speaker C:All the preferences aside, let me know what you think.
Speaker A:I would love to hear if you've.
Speaker C:Tried petals, or if you want to.
Speaker A:Know more about petals, or how to best use it as well. Reach out in the comments or reach out on email, whatever your preference, and I'll be back next week with some more petals snapshots.
This is a sample (bonus) episode of Si’s latest side project called PETALS. It’s a framework for helping teams continuously improve their health with quick and regular metrics to discuss.
To demonstrate the power of PETALS and how to think about the five key factors, Si reflects daily on some tips and advice for other teams to hopefully benefit.
Follow the journey in your preferred podcast app - all links at https://petals.team/snapshots/
——
Today, we talk about the differences between PETALS, Spotify Health Check and Atlassian's Health Monitor along with when you might use them.
Spotify Squad Health Check https://engineering.atspotify.com/2014/09/squad-health-check-model/
Atlassian Team Health Monitor https://www.atlassian.com/team-playbook/health-monitor
Support Make Life Work by contributing to their tip jar: https://tips.pinecast.com/jar/make-life-work
Find out more at https://make-life-work.pinecast.co
This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-b0b82e for 40% off for 4 months, and support Make Life Work.