The Future of Work -- High Performance Teams

Talent wins games, but teamwork and intelligence win championships. — Michael Jordan

The most expensive gap in business right now isn’t the AI gap. It isn’t the technology talent gap. It isn’t the strategy gap. It’s the team performance gap. And while everyone argues about the future of work, almost no one is building the teams designed to close it.

Most organizations think about transformation as something that happens to the business — a strategy to execute, a technology to adopt, a model to redesign. The best organizations think about it differently. The transformation itself is the team. Building high-performance teams across the organization — at every level, starting at the top — is not a means to an end. It is the end.

Those teams look different than they did five years ago. They are hybrid by design: employees, contractors, partners, and increasingly, AI collaborators working alongside them. Every team — including, and most importantly, the executive and senior teams. The most consequential team in any organization is the one at the top, and it is the most under-designed of all.

The organizations that win won’t be the ones with the best AI strategy or the proclaimed “best talent.” They’ll be the ones that have thoughtfully built championship teams — at every level — capable of operating at a consistently world-class level and transforming systematically.

Talent Is Table Stakes. Team Design Is the Differentiator.

Richard Hackman, Professor of Social and Organizational Psychology at Harvard, studied what separates high-performance teams from everyone else. His conclusion: 80% of a team’s effectiveness is determined before its first meeting — by how the team is designed. Not coached. Not incentivized. Designed.¹

Google reached the same destination from a different direction. In Project Aristotle — a two-year study of 180 internal teams — they expected to find that performance was driven by talent. What they found instead was that who is on the team matters far less than how the team operates. The specific behaviors, norms, and standards that govern how a team works together account for 43% of the variance in performance outcomes.² Talent is table stakes. Design is the differentiator.

Across every team I’ve been part of, led, and advised, the pattern is consistent: the organizations on the right side of that gap have mastered the same five practices — applied consistently, enforced by peers, and visible in the operating rhythm and culture of every team, at every level.

I deliver this framework as a keynote for leadership teams and company events. Here’s my preview for this keynote.

Practice 1: Start With Purpose, Operate by Principles

Leadership principles and team tenets are the backbone of every high-performance team. They provide the framework that guides how a team operates, prioritizes, and upholds expectations — setting the standard for how people collaborate, make decisions, and hold each other accountable.

Without clearly defined principles and tenets, organizations default to inconsistency, misaligned priorities, and diluted standards. Leaders may set the tone early, but as a team scales — or as a transformation accelerates — informal norms break down. Codifying principles and tenets is not bureaucracy. It is the infrastructure that keeps a team operating at championship level under pressure.

Amazon’s leadership principles are the most studied example of this in practice. They are not aspirational wall art. They are actionable — shaping every decision, influencing every hire, and providing a consistent foundation at every level of the organization. When principles and tenets are embedded into the daily operating rhythm, they act as a compass, not a constraint.

Ray Dalio put it plainly: operate by principles so clearly defined that their logic can be assessed, and others can see whether you walk the talk.

Championship teams codify their principles and tenets. They build mechanisms for communication, training, and accountability around them. They create a common language for evaluating performance and a shared foundation for making tough calls — especially under the conditions that transformation demands.

Critically, principles make team performance durable. As leaders rotate, as new talent joins, as the organization scales, the principles and tenets remain. They become the team’s constitution — the operating contract that doesn’t depend on any single person to hold it together. This is how a high-performance team is built to last: not by talent alone, but by a shared commitment to operate the same way, every day, at every level, regardless of who is in the room.

Practice Two: Customer Obsession — As a North Star, Not a Slogan

Championship teams don’t ask what customers want. They build systems to discover what customers need before they know to ask.

And “customer” means more than the end consumer. For a clinical team, the customer is the patient. For a finance team, the customer is the business leader who depends on accurate, timely insights to make decisions. For an IT team, the customer is every function they enable. Every high-performance team has a customer — the person or team that depends on their capability — and championship teams design around that relationship deliberately.

At the functional level, that means your team has a mechanism, not just an instinct, for staying ahead of the customer. Voice of the Customer programs, correction of error reviews, real-time data on customer experience — these are not nice-to-haves. They are the operating infrastructure of a team that takes obsession seriously.

That mechanism does something else most leaders don’t anticipate: it keeps the team humble. It’s hard to get arrogant about your own capabilities when you’re constantly confronted with what your customers are actually experiencing. External focus becomes the default orientation, not a reminder on a values poster.

This matters especially during transformation. Teams under pressure to execute internally are the most vulnerable to losing their customer orientation. The ones that maintain it — that have built it into their operating rhythm rather than their aspiration statements — are the ones that come out the other side with both the transformation and the customer relationship intact.

The question isn’t whether you care about customers. The question is whether that care is built into how the team actually operates.

Practice Three: Operational Excellence — The Relentless Chase of Perfection

The greatest challenge for “good” teams is that “good” becomes “excellent” — and mediocrity becomes the accepted target. This is how decay happens — not through dramatic failure, but through the slow erosion of standards that nobody explicitly lowered. Championship teams cannot afford this — and will not tolerate it. They are relentless. There is a reason Amazon owns the domain relentless.com.

Chasing perfection as a team practice is built on three disciplines.

1. Stay Humble. Humility is the most underrated driver of operational excellence. It prevents the success trap — the complacency that sets in when past performance becomes the ceiling for future ambition. Teams that stay humble maintain a continuous feedback loop: successes are celebrated, but shortcomings are scrutinized for opportunities to improve.

Humility is not a personality trait. It is a practice — and it has to be designed in. Mechanisms that build humility into the team’s operating rhythm include:

• Voice of the Customer (VOC) — a structured, recurring process for surfacing what customers are actually experiencing, not what the team assumes they are experiencing.

• Correction of Error (COE) reviews — a disciplined post-mortem practice that asks not just what went wrong, but what in the system allowed it to go wrong, and what will prevent it from happening again.

• Peer performance visibility — designing metrics and operating reviews so that performance gaps are visible to teammates before they become problems for leadership.

• External benchmarking — regularly studying how analogous teams, functions, and organizations operate at world-class levels, so the internal standard never becomes the only standard.

These are not signs of weakness. They are the mechanisms of a team committed to getting better — and staying that way.

2. Design the Right Metrics. In God we trust — all others must bring data. Metrics are not merely numbers; they are the critical signposts that tell a team where it excels and where it falls short. Championship teams design metrics deliberately — not to track data for data’s sake, but to measure what actually matters to customers and operations.

Mechanisms that bring disciplined metrics to life include:

• Input and output metrics — tracking not just results but the leading indicators and behaviors that drive those results, so teams can intervene early rather than explain late.

• Weekly operating reviews built around data — replacing status updates and anecdote with structured reviews of metrics that surface friction points, inefficiencies, and opportunities.

• Root cause analysis — when metrics reveal a gap, the discipline to go beyond the symptom and identify the system failure underneath it. A true fix addresses the cause, not the signal.

• Metrics ownership — assigning clear accountability for every key metric so that numbers have owners, not just observers.

When everyone on the team understands what success looks like and how it is measured, accountability stops being a management tool and becomes a shared standard.

3. Design the Machine That Makes the Machine. Most teams focus on the work. Championship teams focus on how the work is designed. Work design is the deliberate process of defining required outcomes and constraints, then structuring activities, workflows, and decision-making frameworks to achieve those outcomes efficiently and effectively. Once the work is designed, technology and AI are applied to scale it, automate it, and continuously improve it.

Mechanisms that build the machine include:

• Zero-based work design — rather than inheriting existing processes, start from the desired outcome and design backward. Question every requirement, every step, every handoff. As Elon Musk put it: delete, delete, delete.

• Written workflow definitions — documenting how work actually happens at the function and task level, so that excellence is repeatable and not dependent on institutional memory or heroic effort.

• Technology and AI enablement — only after the work is designed, evaluate where automation and AI can be appropriately applied to increase speed, reduce variability, and generate the data needed to continuously improve.

• Feedback loops and iteration — building metrics and review mechanisms into every workflow so that the machine improves itself over time rather than drifting toward the path of least resistance.

The enemy of excellence is low standards — bars set too late, expectations negotiated after the fact, and mediocrity that nobody explicitly chose but everyone slowly accepted. Championship teams design against that. Every team. Every level. Every time.

Practice Four: Outcome Orientation — Commit to Results, Not Activity

This is the discipline that creates the most discomfort when I work with leadership teams — because it requires honesty. And honesty, at the leadership level, is not just about transparency. It is about the willingness to make hard choices. To declare what success looks like before you know if you can achieve it. To re-evaluate when the evidence tells you the path is wrong. To stop doing things that are consuming resources but not producing outcomes. Outcome orientation is, at its core, a calculated risk — you are committing to a result, not just a process, and that commitment has consequences.

Ask any executive what their team is working on. They’ll tell you the initiatives, the projects, the milestones. Ask them what outcome their team is accountable for delivering in the next 90 days, and the answer frequently gets complicated. Ask them how they will know — specifically, measurably — when the work is done, and the room gets quiet.

The research is unambiguous. Gallup finds that only 36% of employees have clearly defined team goals — even though 58% have individual goals.³ Goal clarity and commitment accounts for 31% of the difference between high and low performing teams. And individuals with clear, specific goals are ten times more likely to achieve them than those without.⁴

That gap is not a communication problem. It is an outcome orientation problem.

Jeff Bezos identified this pattern in Amazon’s 2016 shareholder letter and called it one of the most dangerous signals of organizational decay — managing to proxies instead of outcomes. He wrote that in large organizations, process can become the proxy for the result you want. You stop looking at outcomes and just make sure you’re doing the process right. It’s not rare to hear a junior leader defend a bad outcome with “Well, we followed the process.”⁵ The process is not the thing. It’s always worth asking: do we own the process, or does the process own us?

Without outcome carefully considered goal and outcome clarity, teams default to activity. They measure inputs instead of results. They report on progress instead of impact. They negotiate expectations after the fact rather than setting them before work begins. This is how organizations become busy without becoming effective — and how transformations stall while everyone insists they are making progress.

Championship teams design their operating reviews around outcomes, not activities. They begin with the end in mind — defining what will be different as a result of the work, not just what will be done. They set the quality bar and the success criteria before work begins. They re-evaluate when the evidence demands it — and they make the hard choice to stop, pivot, or double down based on outcomes, not sunk cost. Performance is measured against results, not effort. And done means the result happened and is confirmed — not that the task was checked off.

Activity without outcome accountability is how busy teams lose. Championship teams are not busy. They are effective. They make deliberate choices and say “no” more than they say “yes”.

Practice Five: Taking Big Bets — The Courage to Transform

Great operations without transformation is a slow path to irrelevance — accelerated by AI. Great transformation without operations is chaos. Championship teams are built for both, and they use AI to do each faster, smarter, and at a scale that was previously impossible.

High-performance teams are not just built to run the business. They are built to change it. Championship teams are not just great operators — they are systematic transformers. They do not get trapped by legacy thinking, by the success of what worked before, or by the comfort of what they already know how to do. The organizations that win over the next decade will be the ones with teams capable of taking on transformational, high-ambition initiatives and seeing them through. Big Bets. And Big Bets require a different kind of team discipline than running the core business.

In Big Bet Leadership, Kevin McCaffrey and I identified three habits that separate the leaders who win at high-stakes transformation from those who don’t.

1. Create Clarity. Big Bets fail most often not because the strategy was wrong but because the team never achieved a shared, precise understanding of what winning looks like. Championship teams define the outcome with enough precision that every team member can make decisions aligned to it without escalation. This is the Big Bet Vector — a clear, directional statement that holds the team on course through the inevitable turbulence of transformation.

2. Maintain Velocity. Bureaucracy is the natural enemy of transformation. Large organizations generate organizational antibodies — processes, approvals, competing agendas — that slow, dilute, and eventually kill high-ambition initiatives. Championship teams prioritize speed and rapid learning over process compliance. They make decisions quickly, surface bad news early, and treat every obstacle as a problem to be solved.

3. Prioritize Risk and Value. Big Bets are not reckless gambles. They are calculated risks rooted in analysis, experimentation, and foresight. Championship teams think big but bet small — testing the highest-risk assumptions early and cheaply before major commitments are made. They explore widely, commit deliberately, and scale what works.

This requires a disciplined portfolio of initiatives at various stages — not betting everything on a single idea, but systematically building and testing a pipeline of transformative concepts. Championship teams do not wait for disruption to force their hand. They are always asking what the next bet should be.

The choice to pursue championships is a deliberate one. This is the hard path, filled with calculated risks and difficult decisions. But teams grounded in the first four practices — purpose and principles, customer obsession, operational excellence, and outcome orientation — are the teams built to absorb the uncertainty that Big Bets demand. They are antifragile. Not just resistant to disruption, but strengthened by it.

The High-Performance Team is the Future of Work

Every organization has a strategy. Most have a technology roadmap. Almost none have deliberately designed the teams that will execute both.

That is the transformation gap. And it is the most expensive gap in business right now — not because it is the hardest to close, but because it is the most ignored.

The future of work is not a destination. It is not a moment of arrival where the transformation is complete, the org chart is set, and the operating model is locked. It is a continuous state of change — driven by AI, by market volatility, by competitive disruption that arrives faster and from more directions than any planning cycle can anticipate.

The half-life of a strategy is shrinking. The half-life of an organization composed of well-designed, high-performance teams is not.

Onward,

John

John Rossman

Author, Big Bet Leadership, The Amazon Way, Think Like Amazon
Your guide to making winning high-stakes decisions in the AI era.

www.johnrossman.com

---

John Rossman is the author of Big Bet Leadership and the founder of Rossman Partners. He advises C-suite leaders and boards on high-stakes decision-making in the AI era.

1. J. Richard Hackman — Leading Teams: Setting the Stage for Great Performances (2002). The 6 conditions account for up to 80% of a team’s effectiveness. https://hbswk.hbs.edu/archive/leading-teams-setting-the-stage-for-great-performances-the-five-keys-to-successful-teams

2. Google Project Aristotle — Two-year study of 180 internal teams; team norms and dynamics are the primary driver of team effectiveness. https://rework.withgoogle.com/intl/en/guides/understanding-team-effectiveness

3. Gallup — Science of High-Performing Teams: 36% of employees have team goals vs. 58% with individual goals; top quartile teams are 23% more profitable and 18% more productive in sales.https://www.gallup.com/workplace/650156/science-of-high-performing-teams.aspx

4. LSA Global Organizational Alignment Research — Goal clarity and commitment accounts for 31% of the difference between high and low performing teams. https://lsaglobal.com/blog/how-to-make-goals-and-accountabilities-clear-to-your-team/

5. Jeff Bezos, Amazon 2016 Annual Shareholder Letter — Process as proxy for results.https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders