DropRegion · Lessons from Different Escaping the Competitive Herd · Youngme Moon

What Leaders and Managers Can Learn from Different: Escaping the Competitive Herd

You're reviewing your team's quarterly goals against two peer teams in the org, and the slides could be swapped without anyone noticing. Same velocity metrics, same "customer obsession" language, same list of process improvements borrowed from the team that presented first. Your director nods along, unable to say what makes your group different from the other two competing for the same headcount next cycle. You built this plan by making sure you weren't missing anything the other teams had. Walking out of the room, you realize that being thorough and being distinct are not the same thing, and that the safest-looking plan in the room was actually the least memorable one. Something has to change about how you frame your team's value.

01 · The Book in One Minute

The whole book, compressed

01When Every Team Looks

02The Trade-off Behind Real Distinction

03Committing Your Team To One

04Defending Your Team's Difference Over

This edition works through 4 core lessons — take them one at a time, not all at once.

02 · Where Are You Now?

What's different for your conditions

Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.

You're judged relative to peer teams inside the same company, so convergence happens faster than in an open market — everyone reads the same internal playbook.

You don't set final strategy alone; a distinct choice has to survive review by people who reward familiar-looking plans.

Your "customers" are often internal stakeholders whose preferences are easy to poll and imitate, which makes copying peer teams tempting and cheap.

Team turnover means a hard-won distinctive practice can quietly erode as new hires default to whatever looks normal elsewhere.

You have less room to be "worse" publicly, since underperforming on a visible metric can look like managerial failure rather than strategy.

0 of 5 selected

03 · Core Lessons

The core lessons, applied to you

When Every Team Looks

When Every Team Looks the Same on Paper

The idea

Benchmarking your team against every other team's best practices feels responsible, but stacking up all of their strengths turns your team into an average of everyone else, with no clear reason to exist as a separate unit.

What it looks like

A support manager adopts the fastest team's response-time targets, the friendliest team's satisfaction scripts, and the most technical team's escalation process, all in the same quarter. Six months later her team hits none of the three benchmarks particularly well, and leadership still can't describe what her team is uniquely good at. Trying to match every strength borrowed none of the coherence.

Try this

List the three practices you adopted most recently because another team used them, and drop the one that fits your team's actual constraints worst.

The Trade-off Behind Real Distinction

The idea

A team that stands out usually accepts being slower, less polished, or less broadly capable in some area so it can be clearly excellent at the one thing its stakeholders actually need most from it.

What it looks like

An engineering lead wants his team known for both shipping speed and rigorous code review, so he refuses to loosen either standard. Reviews stack up, releases slip, and the team ends up mediocre at both instead of exceptional at one. Nobody outside the team can say what they're for.

Try this

Pick one standard your team will visibly relax this quarter, and tell stakeholders directly which standard you're protecting instead.

Committing Your Team To One

Committing Your Team to One Thing

The idea

Rather than positioning your team as capable across every dimension leadership might value, choose the single outcome your team is genuinely built to deliver and repeat that framing until it sticks.

What it looks like

A marketing manager tries to position her team as data-driven, creative, and fast-moving all at once in every steering committee update. Executives remember none of it, because a list of virtues isn't a position. A single, repeated claim would have stuck where three competing ones did not.

Try this

Choose one sentence describing what your team is for, and use that exact sentence in your next three updates without varying it.

Defending Your Team's Difference Over

Defending Your Team's Difference Over Time

The idea

Once your team's distinct approach starts getting attention, other managers will borrow the visible parts of it for their own teams, and leadership will start expecting the same result from groups that copied only the surface. Protecting your team's edge means continuing to explain the underlying trade-off, not just the outcome, and resisting pressure to broaden your mandate back toward the average the moment things go well.

When the clusters compete

Choosing one committed outcome for your team can conflict with the pressure to benchmark against every peer team's strengths. When a skip-level meeting surfaces a gap versus another team, resist immediately closing it; ask whether closing that gap serves your team's chosen outcome or just quiets the comparison for one meeting.

04 · Choose Your Priority

Name one thing, honestly

If someone read only your team's goals, without your name attached, could they tell it apart from the two teams you're most often compared to?

Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.

05 · Put It Into Practice

The practices from this edition

List the three practices you adopted most recently because another team used them, and drop the one that fits your team's actual constraints worst.

Pick one standard your team will visibly relax this quarter, and tell stakeholders directly which standard you're protecting instead.

Choose one sentence describing what your team is for, and use that exact sentence in your next three updates without varying it.

0 of 3 selected

06 · Small Experiment

Run this for seven days

Choose one sentence describing what your team is for, and use that exact sentence in your next three updates without varying it.

07 · Remember This

If you remember only 4 things

01When Every Team Looks. Benchmarking your team against every other team's best practices feels responsible, but stacking up all of their strengths turns your team into an average of everyone else, with no clear reason to exist as a separate unit.

02The Trade-off Behind Real Distinction. A team that stands out usually accepts being slower, less polished, or less broadly capable in some area so it can be clearly excellent at the one thing its stakeholders actually need most from it.

03Committing Your Team To One. Rather than positioning your team as capable across every dimension leadership might value, choose the single outcome your team is genuinely built to deliver and repeat that framing until it sticks.

04Defending Your Team's Difference Over. Once your team's distinct approach starts getting attention, other managers will borrow the visible parts of it for their own teams, and leadership will start expecting the same result from groups that copied only the surface.

08 · Your Next Step

What will you do differently because you read this?

Youngme Moon develops this argument at length in the original book, Different: Escaping the Competitive Herd, worth reading in full.

Also in this series — Lessons from Different Escaping the Competitive Herd

1. Entrepreneurs

2. Leaders & Managers

3. Teachers

4. Parents

5. Students & Young Adults

6. Career Professionals

7. Creators & Innovators

8. Coaches & Mentors

9. Sales & Customer-Facing

10. Everyday Life