Higher Performance Insights | GO TO THE ANT, YOU S-WORD?

December 2, 2025
higher performance insights

When Ancient Wisdom Calls Out Your Cabinet Meeting


Three thousand years ago, King Solomon looked at lazy people and said, "Go watch the ants work. Maybe you'll learn something."


Harsh? Maybe. Accurate? Absolutely.


But here's what Solomon didn't know—and what your leadership team desperately needs to understand: The ant's genius isn't that it works hard. It's that the colony has an operating system your brilliant cabinet doesn't.


An individual ant has roughly 250,000 neurons. Your CFO has 86 billion. By any measure, your CFO is 340,000 times smarter than an ant.


Yet somehow, when you put those ants into a colony, they solve complex routing problems, allocate labor dynamically, adapt to environmental changes, and make collective decisions that consistently optimize for survival.


Meanwhile, your cabinet—filled with people 340,000x smarter than any ant—just spent three hours in a meeting and made zero decisions. Again.


Here's the profound part nobody in leadership wants to admit: The ants' intelligence doesn't emerge because individual ants got smarter. It emerges because of how they interact.


Your cabinet? You've hired smarter and smarter ants. Sent them to better development programs. Given them corner offices and impressive titles.


But you've never built the colony operating system.


73% of educational leadership teams in our study have higher individual IQ than collective intelligence. You're paying for genius and getting group project energy where everyone did their part, but nobody read anyone else's sections.


Solomon told sluggards to go to the ant. I'm telling brilliant-but-stuck leaders the exact same thing.


Comment "COLONY" if you've spent the last year hiring smarter ants and wondering why the colony isn't building anything.


THE DIAGNOSIS: WHAT THE ANT KNOWS THAT YOUR PHDs DON'T


Let's talk about this like adults who've survived at least one strategic planning retreat that somehow produced a beautiful vision statement and zero change in how your team actually operates.


You know this meeting. I know you know it:


Your VP of Enrollment presents compelling market data about declining numbers. Solid analysis. Clear recommendations.

Your Chief Academic Officer immediately pivots: "We can't just chase numbers—we need to think about mission alignment."

(Translation: I'm the guardian of academic integrity, and your proposal feels transactional. Also, I went to grad school for this, not to run a business.)


Your CFO is already calculating ROI and asking about costs nobody's thought about yet.


(Translation: I'm the adult who understands we can't spend money we don't have. Also, I'm the only one who actually reads the audit reports.)


Your VP of Student Affairs is thinking about how this affects current students and whether anyone consulted them.


(Translation: While you all strategize in the abstract, I actually talk to students. You know, the humans this is supposedly about?)


Four brilliant perspectives. Each one valid. Each one advocating with genuine expertise.


Zero synthesis. Zero integration. Zero collective intelligence.


The meeting ends with everyone agreeing to "explore this further"—professional code for "we'll have this exact conversation in three weeks, except everyone will be slightly more exhausted."


What actually happened? You had four separate monologues performed simultaneously. Four individual ants wandering in circles, each following their own pheromone trail, wondering why the colony isn't building anything.


The ants don't do this. They can't afford to. A colony that operates like your cabinet meeting would be extinct in a week.


The Loneliness of Seeing the Whole Nest


I know the loneliness of being the leader in this moment.


Of feeling like you're the only one who can see the whole nest while everyone else optimizes their individual tunnel.


Of wondering if you're the problem because surely—SURELY—other leadership teams have figured out how to think collectively instead of just politely taking turns thinking individually.


Of going home exhausted, not from hard work but from the emotional labor of being the only person trying to synthesize perspectives that should integrate naturally if you just had the right operating system.


But here's what nobody tells you at leadership conferences: You're not the problem. You're trying to solve a colony problem with an ant solution.


You keep hiring smarter ants. Sending them to better development programs. But individual ants—no matter how brilliant—can't solve problems that require colony-level intelligence.


Solomon wasn't telling sluggards to work harder. He was telling them to work smarter—specifically, to work like a system rather than as isolated individuals.


(This is actually why I created The GROUP—a free community where insights like this become Leader CORE Lessons you can deploy Monday morning. Because translating the ant paradox into Tuesday's cabinet meeting without an implementation guide is how good insights die in conference rooms. But I'm getting ahead of myself.)


When Individual Genius Meets Collective Mediocrity


Let me tell you about a community college president I'll call Marcus (not his real name, but Marcus, you know exactly which budget meeting made you finally admit your Avengers had never actually assembled).


Marcus had a dream team on paper. CFO with an MBA from a top program. Chief Academic Officer with a track record of innovation. VP of Student Affairs who'd turned around retention twice before.


Individual excellence? Off the charts. Each ant was brilliant—340,000 times smarter than the insects Solomon was watching.

Cabinet meetings? Marcus described them as "watching brilliant people talk past each other in high definition while the institution slowly loses momentum."


Someone would present an idea. Three others would immediately explain why it wouldn't work from their domain perspective. Decisions got made through exhaustion, not synthesis. Implementation was inconsistent because everyone left with different interpretations.


The colony wasn't building anything. The ants were just wandering in increasingly frustrated circles.


Marcus tried what you've probably tried: More communication training. Better meeting structures. Expensive retreat with a consultant who taught them "active listening."


He sent people to individual development programs. Each person came back smarter, more skilled, better equipped—individually.


Nothing changed collectively.


Because Marcus was still breeding smarter ants when he needed to build colony intelligence. He was solving an operating system problem with a personnel solution.


Tag the cabinet member who came back from their last conference excited and exhausted—whose brilliant insights somehow died in your first meeting back.


THE FRAMEWORK: THE ANT PARADOX EQUATION


Call this the Ant Paradox. Or don't. Either way, it'll explain why your brilliant cabinet consistently operates at 60% capacity—and what actually changes the equation.


P = (p - i) (TQ)


Performance equals potential minus interference, X Team Intelligence.


This isn't new-age fluff. This is the mathematical expression of what Solomon observed three millennia ago when he watched ants outperform humans at collective work.


1. Your Potential Is Already There (The Ants Are Already Smart Enough)


Think about your cabinet. Combined decades of experience. Multiple advanced degrees. Proven track records.


Individually? Everyone's operating at 7-8 out of 10.


Collectively? Your team is operating at 4-5 out of 10 of actual capacity.


That 40% gap? That's not a personnel problem. That's the difference between individual ants and colony intelligence. And you can't close it by hiring better ants.


Solomon didn't tell sluggards to become smarter. He told them to observe how already-smart-enough ants become collectively brilliant through their operating system.


Your problem isn't insufficient individual intelligence. Your problem is the absence of protocols that turn individual intelligence into collective genius.


2. The Interference Is Killing Your Colony


Every time your CFO and CAO have their polite disagreement about fiscal sustainability versus academic mission—without any framework for how both can be true simultaneously—that's interference.


Every time someone leaves a meeting unclear about who actually decides what, that's interference.

Every time perspectives collide instead of integrate, that's interference.


Interference isn't drama. It's the friction that happens when high-performing individuals lack the operating system to become a high-performing collective.


The ant colony solved this with pheromone trails—simple communication protocols that turn one ant's discovery into colony-level action.


When one ant finds food, it doesn't schedule a meeting to discuss optimal resource allocation. It doesn't form a committee to study implementation. It doesn't send three follow-up emails clarifying the decision-making process.


It leaves a chemical trail. Other ants follow it. The colony eats.


Simple protocol. Zero interference. Maximum collective intelligence.


You need the human equivalent.


3. Team Intelligence Is the Operating System


Here's where 99% of leadership development completely misses Solomon's point:


They try to make each individual better at communication. Better at strategy. Better at whatever competency is trending. They're breeding smarter ants.


But TQ isn't about making individuals better. It's about creating conditions where your team's collective intelligence exceeds the sum of its parts.


━━━━━━━━━━━━━━━━━━━


"The ant colony has foragers, soldiers, nurses, builders—specialized roles working in concert. Your team needs the same: diverse perspectives with integration protocols."


━━━━━━━━━━━━━━━━━━━


The breakthrough isn't getting your CFO to become more emotionally intuitive or your Student Affairs VP to become more financially analytical.


The breakthrough is creating the operating system where all perspectives integrate into decisions better than any single leader could make alone.


That's what the ants have that you don't: Not smarter individuals. Smarter interaction protocols.


That's what Solomon saw that you've missed: The wisdom isn't in the ant. It's in how the ants work together.


Marcus Built the Colony Operating System


Marcus finally understood what Solomon was saying three thousand years ago: His team didn't need to work harder. They needed to work like a colony instead of isolated individuals.


His team took the Team Intelligence assessment. (Results were humbling. His CFO: "Well, this explains why I leave every meeting feeling like I'm the only one who gets it"—which, plot twist, everyone else was also thinking.)


They were operating at Level 7-8 individually but Level 3 collectively. High individual IQ, catastrophically low team operating system.


They had brilliant ants with no pheromone trails.


Here's what changed:


Communication protocols—not "let's communicate better" platitudes, but actual rhythms for how perspectives integrate before decisions get made. Simple. Clear. Executable.


When presenting a recommendation, include the perspective of at least two other roles. When someone presents, the next person synthesizes before adding. When we disagree, we state what would make both perspectives true before choosing.


Decision rights—so people stopped treating every decision like it needed consensus. The ant colony doesn't vote on where to build the nest. It has clear protocols for when different roles engage.


They mapped their top 10 decision types. Assigned clear rights. Watched 40% of meeting time vanish because they'd stopped having colony-level conversations about ant-level decisions.


Thinking out loud together—not performative agreement, but actual cognitive diversity where "this is financially impossible" and "this is pedagogically essential" became inputs into a solution neither could see alone.


Six months later: Same people. Same budget constraints. Same enrollment pressures.


Cabinet meetings went from three hours of polite disagreement to 90 minutes of actual decision-making. Not because they agreed more—because they'd built the operating system for integrating disagreement into better solutions.


Decisions got made faster, implemented more consistently, and actually stuck. Not because individuals got smarter—because the team got smarter.


Marcus got 14 hours per week back.


They stopped trying to hire smarter ants. They built the colony operating system that turned brilliant individuals into collective intelligence.


They finally went to the ant. Considered its ways. And became wise.


Revolutionary? No. Obvious? Yes, once you see it. Common? Based on 987 leadership teams—absolutely not.


Now, if you're thinking "this makes perfect sense, but how do I actually facilitate the 'build our operating system' conversation with my cabinet on Tuesday without it turning into another meeting about meetings?"—I get it.


That's the gap between insight and implementation.


This is what The GROUP is for.


Each week, I turn the newsletter topic into a Leader CORE Lesson and Guide: facilitation notes, discussion prompts, the Team Intelligence diagnostic, team exercises for building your operating system—everything you need to lead your team through this content without spending Sunday night trying to translate ant colonies into something your CFO won't roll their eyes at.


It's free (because charging you to learn how ants solved this problem 100 million years ago would be peak irony), built for busy leaders who need practical resources, not more theory, and designed for Monday morning meetings when you're already exhausted.


Grab this week's Ant Paradox implementation guide: https://www.higherperformancegroup.com/the-group

But whether you join The GROUP or not, here's what you can implement immediately...


THE APPLICATION: BUILDING YOUR COLONY OPERATING SYSTEM (MONDAY MORNING EDITION)


Here's what to do Monday morning (assuming your cabinet isn't already in crisis mode from the three decisions you didn't make last week):


STEP 1: The Ant Paradox Audit (20 minutes)


At your next cabinet meeting, before diving into the seventeen urgent items everyone brought, put this on the agenda:


"Solomon told sluggards to go to the ant because the ant had something they didn't. I'm going to suggest we have the same problem. Let's run a diagnostic.


On a scale of 1-10, rate two things:


1. How smart is each person on this team individually? 2. How smart are we as a collective when solving complex problems together?"


Write down answers privately. Then go around the room.


What you'll discover:


If Question 1 averages 7-8 and Question 2 averages 3-4, congratulations—you've just discovered you have brilliant ants with no colony operating system.


If everyone rates both questions equally high, someone's lying (probably the person who scheduled three sidebar conversations before this meeting to "align" because they don't trust the group process).


If answers vary wildly, you don't have shared understanding of whether you're even trying to build colony intelligence or just managing individual ants more efficiently.


The diagnostic question: "Are we breeding smarter ants, or are we building a smarter colony?"


If you don't know the answer, you're doing the first thing while hoping for the second. Solomon wouldn't be impressed.


STEP 2: The Pheromone Trail Mapping Exercise (25 minutes)


This one's uncomfortable but worth it:


"The ant colony's intelligence lives in its pheromone trails—the communication protocols that turn one ant's discovery into colony-level action. Let's map our equivalent.


Think about the last major decision we made. How did information actually flow? Who talked to whom? Whose perspective never made it into the final decision?"


Draw it on a whiteboard. Literally map it.


You'll probably discover one of three patterns:


Pattern A - The Hub and Spoke: Everyone talks to you, but not to each other. You're trying to be the central processor for the entire colony. This is why you're exhausted. The ant colony doesn't work this way because it can't scale.


Pattern B - The Siloed Clusters: Your CFO and VP of Operations talk. Your CAO and Student Affairs VP talk. But the two clusters never integrate. You have two colonies pretending to be one.


Pattern C - The Random Chaos: Information flows based on whoever happens to run into whom in the hallway. Your "operating system" is geographic proximity and scheduling luck.


None of these creates colony intelligence. They create very busy, very frustrated individual ants who are each 340,000 times smarter than actual ants but producing worse collective results.


Now ask: "What would our pheromone trails need to look like for information from one perspective to actually inform action across the whole team?"


Don't solve it yet. Just name what's missing. That gap between your current communication pattern and actual colony intelligence? That's your TQ deficit.


That's what Solomon saw three thousand years ago that you're just now discovering.


OBJECTION HANDLING


"But we don't have time to think about ant colonies when we have actual crises to manage."


You have crises BECAUSE you don't have colony intelligence. You're managing the same problems repeatedly because you've never built the operating system that would solve them collectively.


Also, you just spent three hours in a cabinet meeting that produced zero decisions. You have 14 hours per week trapped in meeting cycles that don't work. You don't have time NOT to build this.


The ants figured this out while also building nests, farming food, and defending against predators. You can figure it out while managing enrollment and budgets.


Solomon didn't tell busy people to go to the ant. He told sluggards—people who were working but getting nowhere. That's the diagnostic: Are you working, or are you building?


THE MATURITY SHIFT


❌ Immature leaders think: "I need to hire smarter people." βœ… Mature leaders think: "I need to build the operating system that makes my smart people collectively brilliant."


❌ Immature leaders optimize individual ants. They send people to development programs, hire consultants for better communication, add more expertise to the table, and wonder why team performance stays flat. βœ… Mature leaders build colony intelligence. They create interaction protocols, communication rhythms, and decision-making frameworks that turn brilliant individuals into collective genius.


❌ Immature leaders believe: "If everyone just did their part better, we'd get better results." βœ… Mature leaders know: "If we built better integration protocols, doing our parts would produce exponential results."


The sluggard works hard but gets nowhere. The wise person goes to the ant, considers its ways, and builds differently.

The difference is the difference between breeding smarter ants and building a smarter colony.


One keeps you busy managing individual performance. One makes impossible inevitable because you've unlocked the collective intelligence that was always there—you just never built the operating system to access it.


━━━━━━━━━━━━━━━━━━━


"You have smarter ants than the ants do. You just don't have their colony operating system. And until you build it, you'll keep hiring smarter individuals while getting the same mediocre collective results."


━━━━━━━━━━━━━━━━━━━


The ant paradox isn't a cute nature metaphor. It's a brutal diagnosis of why your brilliant cabinet consistently underperforms its potential.


Solomon saw it three thousand years ago. The ants figured it out 100 million years ago. You're still trying to solve it with better meeting agendas and individual development programs.


That's not a personnel problem. It's an operating system problem. And unlike your budget constraints or enrollment challenges, this one is 100% within your control to fix.


YOUR TURN: THE QUESTION SOLOMON ASKED THREE THOUSAND YEARS AGO


Think about your last major decision as a cabinet. Honest assessment—did you synthesize multiple perspectives into something better than any single view? Or did you average perspectives into a compromise that satisfied no one?


Did you work like a colony? Or like individual ants wandering in circles while calling it collaboration?


Drop a comment with your cabinet's Ant Paradox score: Rate individual intelligence 1-10, then collective intelligence 1-10. Post both numbers.


Let's see how many brilliant leadership teams are operating at ant-level collective intelligence.


Tag the cabinet member who you think sees this pattern too. Or screenshot the ant paradox section and text it to your CFO with the message "We need to talk about Tuesday's meeting."


P.S. IF YOU'RE THINKING "I DON'T HAVE TIME TO TURN THIS INTO A TEAM MEETING RESOURCE"


I already did it for you.


The GROUP is a free community where every newsletter becomes a ready-to-deploy Leader CORE Lesson and Guide. Facilitation notes. Discussion prompts. Team exercises. The Team Intelligence diagnostic that shows your team exactly where their operating system breaks down.


JOIN THE GROUP: https://www.higherperformancegroup.com/the-group

Think of it as the meal kit version of team development. I prep the ingredients and recipe. You just facilitate. Your team gets fed. Everybody wins.


Plus, you get access to hundreds of campus leaders who are also trying to eliminate their performance gaps and understand why their last cabinet meeting went sideways. The implementation guides save you hours. The peer conversations? Those might save your sanity.


FOUND THIS VALUABLE?

The LinkedIn algorithm won't show this to your network unless YOU share it:


→ Repost with YOUR Ant Paradox score (individual IQ vs. collective IQ—be honest) → Tag 3 cabinet members trapped in the meeting cycle → Comment: "COLONY" if you're ready to build the operating system

Tag DR. JOE HILL and Higher Performance Group in your repost.


(LinkedIn's algorithm prioritizes posts that generate tags and reposts in first 2 hours. Help other leaders discover this.)

The more leaders who shift from individual heroics to team intelligence, the better our educational systems become.

Follow DR. JOE HILL and Higher Performance Group  for weekly Team Intelligence insights.


NEXT ISSUE: "Your Cabinet Is The Avengers (If Nobody Watched Each Other's Movies)"

ο»Ώ

We'll explore why your all-star leadership team operates like superheroes who've never fought together—each one brilliant in isolation, each one solving problems with their signature move, but with zero coordination when the real battle starts.

Spoiler: You're not having a talent problem. You're having an integration problem, and no amount of individual superpowers fixes a team that's never learned to assemble.


Do you want more leadership topics and guides?

Join THE GROUP


An online community for higher education leaders, where we offer a library of lessons and guides that can be utilized during your leadership sessions and other resources.

JOIN THE GROUP

Help Spread the Word

If you found value in this post, we’d love your help spreading the word! Please consider sharing this on your favorite social media platform and tag Higher Performance Group and Dr. Joe Hill. Your support helps us reach and inspire more awesome people like you!

Like What You've Read?


Get practical, research-based ideas to Accelerate Higher Team Performance delivered straight to your inbox every Tuesday.

More Blog Articles

By HPG Info May 25, 2026
Note: Your team already knows the answer. Here’s a diagnostic question nobody asks at your strategic planning retreat: When was the last time your stated values cost someone something real? Not a performance conversation. Not an awkward pause in a hiring debrief. An actual consequence — a hire you didn’t make, a promotion you delayed, a departure you initiated — because someone violated the culture, not the metrics. Take a moment. Search your memory. I’ll wait. If you’re struggling to name the instance — not because it was so long ago, but because it genuinely hasn’t happened — then you don’t have values. You have wallpaper. Beautiful, professionally designed, consensus-approved wallpaper. Run a word cloud on the stated values of 500 K-12 and higher ed institutions right now. Integrity. Respect. Excellence. Innovation. Equity. Community. The six most expensive words in educational leadership. Expensive because they cost nothing to claim and prove nothing when violated. Meanwhile, the highest-performing organizations outside education built something structurally different. Their lesson isn’t philosophical. It’s architectural. And the gap between what they built and what most institutions call a values exercise is costing your institution more than your last three failed strategic initiatives combined. The villain here is not your character or your cabinet’s. It’s what happens — reliably, predictably, across 987 leadership teams in 43 states — when values live in the lobby instead of the decision architecture. The Diagnosis: When Values Become Performance Art The décor model is predictable. An institution convenes a committee, runs a facilitated process involving Post-it notes and enthusiastic nodding, and produces a list of virtues nobody could argue with. Respect. Integrity. Innovation. All free. All harmless. All useless as architecture. The problem isn’t the words. It’s what happens next — which is nothing. Values get a design treatment, go on the wall, and actual decisions continue being made by what has always made them: budget pressure, political relationships, and the preferences of whoever has the most tenure and the least accountability. (You know that person. They were in your last cabinet meeting. They’ll be in the next one.) Here’s the diagnostic question that matters: When did your values last make a decision before you did? The pattern across our research is consistent. Institutions with performative values frameworks operate at a fraction of their collective ceiling. Not because the people lack conviction — they don’t. But because when the person who most visibly undermines the stated culture keeps getting promoted, your team doesn’t conclude the values were ambiguous. They conclude the values were theater. And they adapt — rationally, efficiently, quietly — to the system that actually exists. Not the one on the wall. (This is the structural villain THE TEAM INSTITUTE addresses — not by teaching better values, but by building the architecture that makes values operational at the cabinet level. More on that in a moment.) Here’s what makes this urgent: your best people — the ones with options, the ones whose departure would sting — figured this out faster than you did. They’re not disengaged. They’re in values triage. Sorting signal from performance. Deciding how much of themselves to invest in a culture they can’t yet verify is real. What Load-Bearing Values Actually Look Like The highest-performing organizations outside education didn’t stumble into values clarity. They engineered it. And in every case, the thing that made their values real was identical: consequences built into the architecture. Netflix: Adequate Performance Gets a Generous Severance Package That single line — published in Netflix’s culture document, viewed over 20 million times, called by Sheryl Sandberg the most important document to come out of Silicon Valley — is the most load-bearing value statement in modern organizational history. Not because it’s harsh. Because it’s honest. Netflix built the Keeper Test. Managers ask one question, regularly: if this person told me they were leaving for a comparable role elsewhere, would I fight hard to keep them? If the answer is no, Netflix doesn’t wait for performance to deteriorate. They offer a generous severance and open the seat for someone who earns a yes. The question for your cabinet: would you fight hard to keep every direct report? At Netflix, that answer has a documented consequence. At most institutions, it’s just a thought that happens on the drive home. Southwest Airlines: Warrior Spirit, Servant’s Heart, Fun-LUVing Attitude Southwest receives a job application every two seconds. They hire fewer than 2% of applicants. Before any skills assessment, they screen for exactly three things: Warrior Spirit, Servant’s Heart, Fun-LUVing Attitude. Not aspirational nouns. Behavioral filters, observable in a group interview — in how you treat the receptionist when you think no one’s watching, in the story you tell about a time you failed, in whether you laugh at yourself or perform competence. Their motto: hire for attitude, train for skill. Because you can train someone to load a plane. You cannot train a cultural misfit into a high performer. And Southwest measures all three values in annual performance reviews — not just what you produced, but how you produced it. The diagnostic question: do your stated values appear in your hiring rubric, your performance evaluation, or your promotion criteria? If the answer to all three is no — you built values for the lobby, not the institution. Zappos: We Will Pay You to Leave After completing their first week of training at Zappos, new employees received a check to quit. Tony Hsieh eventually raised it to $4,000. Less than 1% took the offer. That’s the point. The check wasn’t designed to thin the herd. It forced a conscious declaration. People who turn down $4,000 to stay are actually here. Everyone else is just present. There’s a difference. Your cabinet can feel the difference in the first fifteen minutes of a cabinet meeting. Hsieh fired people performing their jobs well if they were corrosive to the culture. The question for your institution: have you ever let a genuinely talented person go because of a values call alone? If the honest answer is never — you haven’t yet tested whether your values are real. Patagonia: We Told Our Customers Not to Buy Our Product Black Friday 2011 — the highest-revenue retail day of the year. Patagonia ran a full-page ad in the New York Times: “Don’t Buy This Jacket.” The ad detailed the exact environmental cost of producing their best-selling R2 jacket: 135 liters of water, 20 pounds of COβ‚‚, two-thirds of its own weight in waste. Then asked consumers to think before buying anything new. Revenue grew 30% in the nine months that followed. Not because the ad was clever — because people recognized something rare: an organization that actually means what it says. Patagonia told customers not to buy their product and grew 30%. Because the only thing rarer than an organization that means what it says is the person who doesn’t notice when one finally shows up. The question for your institution: would you take the institutional equivalent of that position? A costly public stand, at an inconvenient moment, because your values demanded it? If that’s hard to even imagine, your values haven’t been tested enough to know if they’re real. The Team Jersey Principle In sports, wearing the jersey means something. It’s not a costume. It’s a declaration of accountability to a shared standard that exists independent of your mood on a given Tuesday. The most impactful leaders don’t just comply with institutional values — they wear them. They reference them in hard conversations. They invoke them when it’s inconvenient. They make the call nobody would hold them to — and they make it anyway. Herb Kelleher worked baggage handling the day before Thanksgiving — busiest travel day of the year, in the rain — because the Warrior Spirit wasn’t a poster to him. Patagonia’s founder eventually gave the entire company to a climate trust. Not a PR move. A leader who decided the jersey was worth more than the equity. The diagnostic question: would your cabinet describe you as someone who wears the institutional values — or someone who administers them? The gap between those two descriptions is the cultural altitude your institution is currently operating at. What HPG Just Did We completed our own 2026–2027 values exercise — the real kind. What we landed on:
By HPG Info May 18, 2026
You believe in your people. Your org chart doesn't. ο»Ώ That's not a leadership philosophy problem. It's an architecture problem. And it's sitting in five questions. The gap between what your cabinet produces and what it's actually capable of isn't a hiring problem. It isn't a training problem. It isn't even a culture problem — though it wears culture's name in most post-mortem conversations. It's a deployment problem. And it has a name: The Deployment Gap — the distance between what your people are actually built to do and what your cabinet architecture is currently asking them to do. You don't have a talent problem. You have a deployment architecture problem. And unlike talent, architecture is completely within your control. The test below takes eight minutes. It will either confirm what you already sense — or surface a gap you've been too busy to name. Either way, you'll know something true by the end of it. THE DIAGNOSIS Why Brilliant People Produce Mediocre Cabinets Let's talk about this like adults who've survived enough strategic planning retreats to know the difference between a cabinet that's functioning and one that's performing. Functioning cabinets execute. They show up, manage their portfolios, hit compliance deadlines, and nod in the right places. (You know the nod. The one that means "I heard you" but not "I'm with you." The one that migrates to the parking lot conversation afterward.) Performing cabinets multiply. They think together. They cover each other's blind spots. They produce outcomes that none of them could have generated alone — not because they're smarter individually, but because the collective architecture actually matches who they are. Here's the uncomfortable truth most leadership development programs won't tell you: The gap between those two cabinets is almost never about talent. It's almost always about deployment. Research across 987 leadership teams tells us the same story in different fonts. High-IQ cabinets underperform not because of individual deficiency but because of structural misalignment — people operating outside their zone of genuine contribution, carrying responsibilities that drain rather than energize, filling roles designed for a generic leader rather than the specific, irreplaceable human being actually sitting in the seat. TQ = IQ × EQ × PQ. The PQ dimension — Perceptual Intelligence, the capacity to accurately see what's actually happening with the people in your system — is the one most cabinet leaders have optimized least. Not because they don't care. Because nobody gave them a diagnostic tool that cut beneath the org chart. Until now. (This is the exact gap THE TEAM INSTITUTE was built to close — not through individual development, but through collective architecture that deploys who your people actually are. More in a moment.) Before you run the test — one quick audit: when did you last ask a cabinet member what they do better than almost anyone? If you're reaching for a specific answer, note that. If you're not — note that too. THE 5-QUESTION CABINET STRESS TEST Run this on your current cabinet. Answer honestly — not as the leader you want to be, but as the one who was in last Tuesday's cabinet meeting. No scoring rubric. What follows each question is a consequence statement. The answer you give is less important than what it tells you about the system you've built. Question 1 If every cabinet member were asked to name their single greatest professional strength — the thing they do better than almost anyone — would their answers match what you're currently asking them to do? If the answer is mostly no — or if you're not certain what their answers would be — you have a Discovery Gap. Your cabinet architecture was designed around roles, not people. The result: capable individuals operating at a fraction of their actual ceiling, not because they're underperforming but because they're misaligned. The tragedy isn't that they're failing. It's that they're succeeding at the wrong things. Question 2 In your last five cabinet meetings, who spoke the most? Who spoke the least? And does that pattern reflect genuine contribution — or organizational hierarchy? Silence in a cabinet meeting is never neutral. It's either the silence of someone who feels safe enough to think before speaking — or the silence of someone who has learned that speaking costs more than it's worth. If the same two or three voices dominate every meeting regardless of topic, you don't have a quiet cabinet. You have a cabinet where PQ has been quietly trained out of most of the room. The ideas you need most are sitting behind the people who stopped offering them somewhere between year one and year two. Question 3 When did you last move someone in your cabinet — not out, sideways — because you discovered they'd be more valuable somewhere else? If the answer is "never" or "not recently," you're running a static architecture in a dynamic institution. The principle of comparative advantage — deploying people based on what makes the whole team better, not just what fills the org chart — requires ongoing recalibration. High-TQ cabinets aren't built once. They're continuously tuned. If your cabinet looks structurally identical to the one you inherited or designed three years ago, it's almost certainly operating below its ceiling — because the people in it have grown, and the structure hasn't followed. Question 4 If you removed yourself from the room, would the quality of your cabinet's thinking go up, go down, or stay the same? This one stops people cold. And it should. The honest answer for most leaders is: it would go down. Not because their cabinet is incapable — but because the cabinet has been architected around the leader's presence rather than the team's collective intelligence. When the leader is the room's primary thinker, the cabinet functions as a reporting structure rather than a thinking unit. High-TQ cabinets are built to think better when the leader steps back, not worse. If your absence creates a gap rather than an activation, the architecture needs attention. → Save this before you keep reading. Question 4 is the one you'll want to bring to your cabinet. Question 5 What is one thing someone on your cabinet is genuinely better at than you — and are you currently deploying that superiority or quietly managing it? This is the question that separates leaders who believe in their people from leaders who manage their people. Believing in people is not a sentiment. It's a structural act. It means building an architecture where someone else's excellence isn't a threat to your authority — it's the mechanism by which your institution actually moves. If the honest answer is that you're managing their superiority rather than deploying it, you're paying the full cost of their talent while capturing only a fraction of its value. The org chart proves it — or it doesn't. THE FRAMEWORK What High-TQ Cabinets Do Differently The leaders in our research who moved their cabinets from functioning to performing didn't do it through better hiring. They did it through better seeing. They stopped asking "Is this person good at their job?" and started asking "Is this person in the job they're actually built for — and is the team architecture drawing out what makes them irreplaceable?" Three specific moves separated them from the rest. Move 1: The Contribution Conversation 30 minutes. This week. Schedule a one-on-one with each cabinet member — not a performance check-in. A contribution conversation. One question: "If you could redesign your role to maximize what you do better than almost anyone, what would change?" Then listen without defending the org chart. You're not committing to restructuring. You're generating intelligence. What you learn in those conversations will tell you more about your cabinet's deployment gap than any assessment you've ever administered. (If you're thinking "I don't have time for five thirty-minute conversations" — you're currently spending far more than that managing the downstream effects of misalignment. The math is not close.) Move 2: The Silence Audit Your next cabinet meeting. At your next cabinet meeting, track — on paper, not mentally — who speaks, on what topics, and for how long. Don't change the meeting. Just observe it. What you'll find almost always surprises leaders: the pattern of voice has almost nothing to do with who has the most relevant expertise on a given topic. It has everything to do with who has learned that speaking in this room is safe. The silence audit isn't about demanding more participation. It's about diagnosing which voices your current architecture has quietly trained out of the room — and what those voices would be worth if the architecture changed. Move 3: The Comparative Advantage Question Standing agenda item. Add one question to your monthly cabinet agenda: "Given what each of us is genuinely best at — are we deployed against our comparative advantages right now, or against our job descriptions?" High-TQ cabinets ask this question continuously. They treat deployment as a living variable, not a fixed structure. The result isn't chaos — it's the opposite. When people operate inside their zone of genuine contribution, the collective architecture stabilizes because everyone is giving what they actually have rather than performing what was expected. THE MATURITY SHIFT IMMATURE LEADER THINKS: "I need to develop my people." MATURE LEADER THINKS: "I need to deploy my people — against what they're actually built for, not what the org chart assumed they'd be." IMMATURE LEADER THINKS: Fills roles with people. Hires for the job description. Evaluates against it. Develops people within it. MATURE LEADER THINKS: Builds architecture around people. Discovers what each person does better than almost anyone. Builds the structure that deploys it. IMMATURE LEADER THINKS: Believes in their people as a value statement. MATURE LEADER THINKS: Believes in their people as a structural act. The org chart proves it — or it doesn't. The gap between believing in your people and building for them is the most expensive gap in educational leadership. It doesn't show up on your balance sheet. It shows up in every cabinet meeting where the room produces less than the sum of the people in it. Your turn: Run Question 1 right now. Name one person on your cabinet whose greatest professional strength is not what you're currently asking them to do most. First name only. One sentence. What would change in your institution if you fixed that one misalignment? Drop it in the comments. The pattern in those answers will tell you something important about how many leaders are sitting on untapped architecture. THE TEAM INSTITUTE Most leadership development programs operate on a theory that is structurally backwards: develop people individually, and cabinet performance will follow. It won't. Not at the level you need. Not consistently. Not without the collective architecture that ensures individual development actually lands somewhere. Here's what the research across 987 leadership teams shows: the cabinets that moved from 60% to 90% capacity didn't get there by becoming individually sharper. They got there by building the collective conditions where each person's genuine contribution could actually be deployed — and protected. That's what THE TEAM INSTITUTE builds. Not better individual leaders. Better collective architecture — the shared language, structural clarity, and trust infrastructure that turns eight individually capable people into a cabinet that genuinely multiplies. 8 months. Full cabinet. Sequential development that builds from the foundations on which everything else depends. From our research: 3x performance improvement. 29% higher engagement. 27% better organizational outcomes. Zero burnout increase. One requirement: full cabinet participation. Partial collective architecture is not architecture. It's a majority position wearing the name of the whole. If you recognized your cabinet somewhere in those five questions, that recognition is data. Not a feeling. Data. The Team Intelligence Assessment is not a self-assessment. It's a whole-cabinet diagnostic — your full leadership team completes it together, and the output shows exactly where your cabinet lands on the spectrum from functioning to multiplying. Calibrated against 987 leadership teams across 43 states. The output pinpoints specifically whether the gap in your cabinet lives in IQ, EQ, or PQ. Most cabinets find the gap isn't where they assumed it was. That surprise is where the real work begins. If there were a way to build the collective architecture your cabinet is missing — without another retreat that returns seven brilliant individuals to the same broken system — would that be worth exploring? → Learn more and reserve your team's assessment window: higherperformancegroup.com/team-intelligence-assessment This is a conversation between people who are done accepting cabinets that function when they could be multiplying. FOUND VALUE IN THIS? Help other educational leaders find it: → Repost this with your answer to Question 4. "If I stepped out, my cabinet's thinking would _____." One word. The leaders who need to read this are in your network right now — and that one word will make them stop scrolling. → Tag a cabinet member who brings something genuinely irreplaceable to your team — and tell them you see it. Seven words. Highest-ROI leadership act you'll do this week. → Comment with your honest answer to Question 1. One name, one sentence. The pattern in those comments will tell you something important about how many leaders are sitting on untapped architecture. The more leaders who move from developing their people to deploying them, the better our institutions become. Follow DR. JOE HILL for the framework. Follow Higher Performance Group for the research behind it. Every week.
Show More