Values: The Last Piece of the Team Playbook


Over the last several weeks, we have built a team playbook and scorecard piece by piece.

Now we come to the section that is often written first but should often be written last… team values.

Most teams start with values, but healthy teams discover them. If you’ve been using weekly scorecards, you already have the raw data you need. Values show up in what gets:

  • Protected
  • Confronted
  • Praised
  • Repaired

Values only matter if they describe real, observable behavior. They’re not wishes or slogans.

Three Types of Values for Your Playbook

You team playbook should clearly separate values into three categories. Mixing them can create confusion.

Core Values

These are values your team lives by even when it’s hard.

Core Values:

  • Are non-negotiable
  • Cost you something to uphold
  • Show up consistently in decisions and trade-offs

A simple test to evaluate a core value is to ask “would we keep this value even if it made hiring harder, slowed us down, or cost us revenue?”

If the answer is no, it’s not a core value.

Most teams have 3-5 core values.

Aspirational Values

These are values you sometimes demonstrate, but not consistently yet, although you want to.

They represent:

  • Who you want to become
  • Behaviors that would make the team healthier or stronger
  • Growth edges, not the current reality

Aspirational values are powerful when named honestly. If they are stated as core values and aren’t really, they often create cynicism.

Minimum Values

Minimum values are baseline behaviors required to be on the team.

They are often things like:

  • Integrity
  • Respect
  • Professionalism
  • Ownership

These don’t differentiate your team but they do protect it.

If someone violates a minimum value and doesn’t address it, they eventually can’t be a part of the team. Stating this upfront creates fairness and clarity.

How to Determine Your Team’s Values

Use these questions in a team session to help list your team’s values:

  • Who on this team do we most trust? Why?
  • When we’ve handled conflict well, what behaviors made that possible?
  • When something went red on the scorecard and we responded well, what values were on display?
  • When things broke down, what value was missing?

Look for patterns in the answers. Name behaviors, not virtues and be specific.

Now put the values in your team playbook and look for them to show up everywhere, including in:

  • Hiring decisions
  • Scorecard discussions
  • Recognition
  • Hard conversations
  • Promotions and terminations

Values are not poster or fliers. They are standards.

PS: If you’d like help facilitating a values discovery session or turning your playbook into an organizational operating system, we’d love to help. Just reply to this email.

Perry Myers
The Outlier Team

The Outlier Team

We help small businesses with technology, strategy, and leadership and have a passion for sharing what we have learned. Subscribe to our newsletter to get helpful weekly content.

Read more from The Outlier Team

The Cost of Silence Several years ago, I went through one of the most difficult experiences of my professional career. A few weeks before Christmas, our CEO informed my boss that an outside IT consulting firm would be coming in to help evaluate our technology operations. At the time, I was the IT manager. The announcement raised a lot of questions. Why were they being brought in? What were they evaluating? What would happen afterward? Unfortunately, very few answers were provided. Weeks went...

Over the last two weeks, we’ve discussed meetings that run the business and improve the business. Today, let’s examine the third category: meetings that build the team. Before we do, I’d like to share a story. One summer morning at 2:00 AM, our team received an email that would turn into one of the largest technology incidents the world had ever experienced. Nearly every server and computer at our organization and others throughout the world would not power on. As people woke up, they began...

Meetings That Improve the Business Several years ago, our team was dealing with a frustrating login issue. About one person each week would be affected, and the disruption typically lasted only a few minutes. The team responsible for resolving the issue was actively working with the vendor. We held problem-solving sessions, investigated possible causes, and provided daily updates through email and Teams messages. The work was being done. People were understandably frustrated and wanted the...