Skip to main content

What the Blue Jays taught us about a high-performing team culture (Part 1 of 3)

What were you doing Saturday night? I was watching the Blue Jays play in the World Series at Pearson airport.  I am still in shock but it got me thinking, there’s something deeply important worth paying attention to: Great teams reveal their behaviours long before the scoreboard does.

And that’s why the Blue Jays are such a powerful example of what a high-performing team looks like.

In this three-part series, we’ll unpack how this year’s Jays demonstrated the same principles that drive elite delivery teams: clarity, cohesion, accountability, adaptability, and continuous improvement.

High-performing teams build culture on purpose

You can’t fake culture, you can’t buy it and you cannot “announce” it. You earn your culture through shared identity, consistent behaviours and accountability to something bigger than yourself. 


This season’s Blue Jays were defined by chemistry, not just talent. From dugout energy to post-game conversations, you could see their team dynamics and the amount of fun they had together. Those interviews also revealed how much they valued simply coming to work with each other every day. These guys actually liked working together.

High-performing software delivery teams operate the same way. When individuals shift from “my tasks” to “our outcome,” velocity becomes a by-product. Average teams wait for a crisis to teach them while high-performing teams learn while they’re winning.

This is why Socrates Advice focuses on the team as the unit of change, not the individual.

They treat improvement as a habit, not an event

High-performing teams don’t wait until the end of the season or the game to improve.  Coaches adjust strategy from the dugout in real time, preventing small issues from becoming costly.

Delivery teams need the same continuous steering. Waiting until the end of an iteration or sprint means blockers can potentially compound.

This is why our platform delivers a Daily Shift for behavioural guidance that interrupts unproductive patterns as they happen.

Elite teams don’t passively hope to improve, they actively integrate improvement every day. 

Psychological safety shows up in performance under pressure

The Jays showed their trust when the stakes were high as they gave the ball to rookie Trey Yesavage in the World Series and trusting him to face Shohei Ohtani. That decision wasn’t luck, it reflected a culture where players are prepared, supported, and trusted to perform under pressure. 

Great delivery teams operate the same way.  They escalate blockers early, ask for clarity, challenge assumptions respectfully, and address quality concerns before they become outages.

When the pressure hits, high-performing teams tighten, they do not crumble. Clear roles, visible ownership, and aligned priorities reduce friction, prevent bottlenecks, and keep momentum. Safety enables contribution; clarity converts it into execution.

Reflection over regret

Loss hurts but high-performing teams turn emotion into information. After setbacks, they ask: Where did our system break? Which habits helped or hurt? What change can help us win tomorrow? 

Delivery teams should do the same day-to-day. One behaviour at a time. Not in panic but with intention. That’s why coaching accelerates growth: it turns every iteration into an opportunity to learn and improve.

How you can apply this for yourself

Whether you lead a squad or contribute to one, try these:

  • Audit your rituals:  Are they reinforcing learning, or just tradition?
  • Clarify ownership: If multiple people “own” something, nobody does.
  • Strengthen psychological safety:  Ask yourself, “What is the one thing that made it harder than necessary for team members to contribute?” Then listen.
When teams choose to turn emotion into information, they become dangerous the next season.

Stay tuned for the next parts in this series where we will look into turning talent into teamwork and how to sustain momentum.

If you’d like your team to see their habits the way sports teams do:

👉 Take the 10-minute Team Health Check in Socrates Advice.  One insight can change your season.


Comments

Popular posts from this blog

The Power of Coaching: Unlocking My Potential

Over the last three years, I've been on a journey and it has challenged me in so many ways both professionally and personally.  Deciding to leave my corporate job forced me to really reflect on my passions while at the same time trying to find a way to be paid for it.   When it came to entrepreneurship, I needed a different level of assistance as I could no longer rely on my corporate leaders to help navigate an area that they had not been exposed to. As an entrepreneur, I recognized that my journey was going to be very different from my former colleagues and my friends. As such, I needed to make an investment (time and money) to really unlock the potential that I knew was within me.   They [Coaches] hold up a mirror so we can see our blind spots and they hold us accountable for working through our sore spots.  - Adam Grant Coaching has pushed me to challenge my thinking and really approach situations differently. Coaching has provided me with the tools to ...

No more transactions: how do we build an environment for growth?

If the transactional model is a dead end 🔗, what's the alternative? It’s about creating an environment where teams are empowered to own their work and are given the safety and space to improve it. It's about shifting their focus from "how fast can we close this ticket?" to "how can we deliver the most value?". This doesn't happen by accident. It requires a deliberate shift in how leaders lead and how teams are structured. From assignments to ownership The first step is to stop treating teams like ticket-takers and start treating them like owners. Instead of assigning individual tasks, give a team full responsibility for a product, a service, or a specific customer outcome . When a team owns something, their perspective changes completely. They are no longer just fixing a bug; they are improving their product. They benefit directly from their own improvements: less rework, fewer emergencies, and happier users. This is the essence of a team-centric view,...