You Don’t Want a High-Performance Team

Core argument (team performance reframed)

• Most people equate a “high-performance team” with task output (fast, reliable, deadline-free).
• The key lesson: task performance ≠ business performance once roles require metric accountability and ultimately strategy/optimization.
• Promotion can fail when the role’s success criteria change, but the employee remains in a task mindset (e.g., a marketing manager promoted to head of marketing).

The 3 types of employees (role-by-role success criteria)

1. Task-oriented

   • Success = “Was the work done?” “Done right?” “On time?”
   • Often uses a binary score: done vs. not done.
   • Frequently performs the actual execution work (e.g., salespeople, surgeons, marketers building pages/emails).

2. Metrics-oriented (performance-oriented)

   • Success = numbers move (leading/lagging indicators on a scorecard).
   • Tasks become levers rather than the goal.
   • Typical roles: managers/directors responsible for results, not just deliverables.

3. Strategy-oriented

   • Success = what the business should optimize and where it’s going.
   • Focus = “Which metrics should we chase?” “Where are we heading?”
   • Usually VP/top leadership / CEO-adjacent roles.

Key warning: Someone can be excellent at tasks yet fail at metrics and therefore be mispositioned in performance roles.

Example case study: “Jim” (marketing manager → head of marketing)

• Jim’s traits: fast, reliable, never misses deadlines.
• Promotion logic: he was great at execution (landing pages, email campaigns, testing more variants).

What went wrong after promotion

• Leads stagnate; sales in place; results do not improve.
• The issue isn’t that Jim “worked worse.” It’s that:
  • evaluation criteria changed, and
  • Jim wasn’t told how success would be judged.
• Jim’s behavior underperforming conditions: “do more of what he already knows” (more tests, more campaigns/emails).

Operational diagnosis tool implied by the narrative

• Ask: “When things go wrong, what do they do?”
  • If they respond by increasing task volume → likely task-oriented in a metrics role.

Framework / playbook: 3-step system to move people up the ladder

Step 1) Diagnose the gap

• Identify which “type” the person truly operates in:
  • task-oriented vs metrics-oriented mismatch is the central issue.
• Clarify that the position indicates role, not inherent ability.
• Outcome: confirm whether you’re seeing capability growth potential or a structural misfit.

Step 2) Have a “4-step” transition conversation (≈10 minutes)

1. Admit your mistake (leadership failure)

   • Start with: “Jim, I think I owe you an apology… I didn’t make this clear…”
   • Principle: business failures are leadership failures (either wrong hire or wrong conditions).

2. Announce the change in success criteria

   • Previously: responsible for tasks (great).
   • Now: responsible for changing scorecard numbers; tasks are secondary.

3. Ask one question, then stop

   • “What do you think needs to be done to change this number?”
   • Silence is a test: observe whether they think beyond their comfort zone.
   • Don’t turn it into a quiz; don’t already know the projects.
   • Hiring parallel: for metrics roles, interview by asking how they would improve specific metrics, not “what can you do?”

4. Read the answer

   • If they propose new approaches/resources/second-order thinking → likely capable of the leap.
   • If they repeat only task-volume behavior → red flag; may require reassignment or exit.

Step 3) Change reporting to lock in accountability

• Implement a recurring leadership meeting (weekly):
  • called the weekly “pulse meeting.”
• Rule: don’t report tasks (“I’m productive”).
  • Report metric status (“red/green” indicators).
• Reframe execution as outcome management with a CEO/leadership question:
  • “What projects do we need to implement to turn these red metrics into green?”
• Jim-specific adjustment:
  • Stop leading with “cool stuff I’m working on.”
  • Report metric status first; discuss actions only as part of moving metrics.

Scorecard requirement (implied metric management system)

• Metrics-driven management requires a scorecard (and weekly tracking).
• Without a scorecard, role expectations and accountability won’t persist.

Leadership & organizational recommendations (actionable)

• Don’t define performance by busy output. Define it by metric movement.
• When promoting:
  • Ensure the employee understands new success criteria (metrics, not tasks).
• When underperformance appears:
  • Investigate whether the person is operating from the wrong “type” mindset.
• Support correctly:
  • If they don’t know what to do, leaders should coach/help—but the organization must still enforce metric accountability.
• Set process, not vibes:
  • Conversation ≠ system; weekly pulse meetings + metric reporting make the change durable.

Metrics / KPIs explicitly mentioned (as examples)

Referenced marketing metrics Jim was responsible for:

• Unique visitors
• Lead velocity
• Conversion rate
• Qualified leads

Also stated generally:

• “leads and sales were stagnant”

The framework relies on a red/green indicator model, but explicit numeric targets/time-bound KPIs (beyond “three months”) are not provided in the subtitles.

Presenter / source

• Ryan Dice