⚠️ This post links to an external website. ⚠️
Every team has certain characteristics, and some of those really matter when planning your own team traditions.
- Is the team, in general, outgoing or reserved?
- Playful or serious?
- Writing-comfortable or writing-averse?
- Long-tenured vs newly formed or mixed-tenure?
- High-trust vs low-trust?
- Culturally homogeneous or global?
- Overloaded or has a little free time to spare?
- Async-friendly or more synchronous by default?
Traditions work best when they’re aligned with your team’s culture. That’s why personalized playlists worked for the playful, high-trust, close-knit, long-tenured Taz team, but why I never would have attempted it on the reserved, global, mixed-tenure Access team. If you’re not sure what would work for your team, ask them! Send a short survey with a few options and let them vote. Getting buy-in can result in greater support.
When traditions fail, people often internalize it as “my team doesn’t care,” when the real issue is misfit, not apathy.
continue reading on christiecosky.com
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.