Skip to capability
Tree of ManagementE
Your tree
Managing a team route · Step 8 of 11

Teams & Culture

Norms, incentives & culture

Shape the behaviors the system actually rewards.

Why now Turn values into observable working agreements and repair moves.

Essential question

Which repeated behaviors does this system actually reward, tolerate, and punish?

Build the capability

Practices to build

  1. 01

    Working agreements

    Turn assumed norms into revisable commitments.

  2. 02

    Leadership signals

    Notice what leaders repeatedly attend to, tolerate, and fund.

  3. 03

    Incentive alignment

    Check whether measures reward the intended behavior.

  4. 04

    Culture diagnosis

    Compare stated values with recurring lived experience.

Put it to work

Fieldwork

Create a team charter with observable norms, decision conventions, repair moves, and a monthly review ritual.

Go deeper

Field guide

Edited by Ethan Hussong · Last reviewed

Culture is not the values page. It is the pattern people learn from what leaders attend to, what peers repeat, what systems reward, and what the group tolerates when pressure makes trade-offs real.

Norms make those patterns local and observable. They answer practical questions: How do we disagree? When do we escalate? What deserves a meeting? What happens after a missed commitment? Who is expected to make the decision?

Diagnose the lived system

Begin with repeated behavior, not aspiration. Ask:

“We value collaboration” says little if incentives reward individual rescue work and planning hides dependencies. A culture diagnosis compares the stated principle with the behavior the system makes rational.

Write agreements around moments of friction

Generic agreements such as “communicate openly” cannot guide action. Write norms for situations where reasonable people make different choices.

Examples include:

Each agreement should name the trigger, behavior, and owner. If no one can tell whether it happened, it is still a value statement.

Read leadership signals literally

Teams watch what leaders do when the agreement becomes inconvenient. A leader who requests focus and then adds urgent work every day teaches that priority language is theater. A leader who asks for dissent and argues with every challenge teaches that agreement is safer.

Inspect your calendar, questions, funding choices, praise, exceptions, and responses to bad news. These signals often shape culture more strongly than the message used to announce it.

When you violate a norm, name it plainly. Leaders do not protect an agreement by pretending their exceptions are invisible.

Align incentives with the behavior

Formal and informal measures can make the wrong behavior rational. A response time target may reward premature closure. Individual delivery goals may punish helping a constrained team. A utilization target may create queues and eliminate learning time.

For each important norm, ask:

Do not assume the answer is another metric. Sometimes the right move is to remove a target, change a decision right, or stop celebrating a harmful form of heroism.

Make repair part of the norm

Every team breaks its agreements. A workable culture defines how to notice, name, and repair those breaks without turning every miss into a moral trial.

Use a simple move:

We agreed to raise dependency risk before commitment. We did not do that here, and another team absorbed the recovery. What made the agreement hard to use, and what will we change before the next commitment?

The review should be able to change either behavior or the agreement. A norm that repeatedly fails may be unclear, unrealistic, unsupported, or no longer useful.

Review norms as an operating system

Keep the charter short enough to use. Review it monthly at first and after material changes in team composition, scope, or pressure.

Retire agreements that have become ordinary behavior. Revise those that create unintended costs. Add a new agreement only when a repeated friction deserves one. A long charter that no one can recall becomes another statement of intent without operational force.

Practice with a team charter

Facilitate a session that compares stated values with recurring lived experience. Choose three to five moments of friction and write observable agreements for them. Include decision conventions, escalation, participation, missed commitments, and repair.

For each agreement, name how the team will know whether it helped. Review the charter after one month using real examples, not a satisfaction vote alone.

Use resources for practice and system design

The working-agreements guide provides a ready-to-run facilitation pattern. Scaling People offers broader context for the recurring mechanisms through which leadership choices become organizational culture.

Reading can help you design the charter. Evidence comes from whether repeated behavior and outcomes change.

Evidence of Practice

You may be ready to record Practice when you can:

These prompts inform an explicit proficiency decision; they do not complete it automatically.

Continue through the tree

Trust, psychological safety & inclusion makes it possible to name what the culture actually rewards. Goals, planning & operating cadence gives agreements a recurring place in the work. Measurement & operational learning helps inspect whether incentives and outcomes match the intended behavior.