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 July 14, 2026
The Case for Standards-Based Leadership Think back to tenth grade for a second. The B+ in Chemistry. The C in Algebra II from the teacher who clearly had a grudge against fourth period. The A in gym you didn't earn through anything resembling cardiovascular achievement. Honest question: did that grade measure what you knew — or how well you'd learned to play the game? The extra-credit packet. The teacher you charmed. The final you crammed for at 1 a.m. and forgot by June. Honk once if you believed those grades were objective. Honk ten times if you're being honest. ο»Ώ Most of us spent thirteen years being sorted by a system we now know, as the adults running it, was subjective, inconsistent, and occasionally just vibes. That's exactly why so many of you are doing the hard, unpopular work of standards-based grading right now — proficiency over averages, evidence over guesswork, a report card a parent can actually defend at the dinner table. Good instinct. Now ask yourself the same question about your cabinet. THE GOOD NEWS. THE BAD NEWS. Let's talk about this like adults who've sat through enough grading-policy town halls to know exactly how loud the "back in my day, a C meant something" crowd gets. Here's the good news: you're not imagining the shift. Districts across the country are actively exploring standards-based grading. In pockets — New Hampshire, Maine, Wisconsin, more recently Connecticut, New Mexico, Oregon — it's not a pilot anymore. It's policy. Here's the honest part. Exploring it and doing it are not the same sentence. The most detailed statewide look available — a recent survey out of Wyoming — found that only 10% of middle schools and 5% of high schools had fully implemented standards-based grading. More than half of middle schools had "begun" the shift. Begun is not arrived. Everyone's talking. A tenth of the room is actually doing it. (Sound familiar? It should. You're about to read the exact same gap in your cabinet.) Higher ed's version is smaller, but real. North of 1,500 institutions nationally have built out competency-based programs — concentrated in nursing, computer science, community colleges, the places where "can you actually do the thing" has always mattered more than seat time. Good news: it exists. Bad news: that's a rounding error against roughly 4,000 degree-granting institutions in this country. So both sectors are — unevenly, slowly, sometimes reluctantly — having the standards-based conversation about students. Here's the conversation nobody at either level is having: standards-based leadership. What are the standards for your cabinet? Not the job description HR pulled from a template in 2014. Not the vague "strong communicator, collaborative, strategic" language every posting uses. The actual, observable standards that tell you whether your VP of Instruction is on track, exceeding, or quietly underperforming a competency she's never once been assessed against. If you can't name them, you don't have a leadership standard. You have a job title and a hope. You almost certainly evaluate every cabinet member once a year. If you can't say, right now, which competency each of them is actually operating at — that's not a documentation gap. That's a year of development spent guessing at a target nobody wrote down. TQ = IQ × EQ × PQ. You cannot standards-base a formula you've never written the rubric for. (This is precisely the gap THE TEAM INSTITUTE was built to close — not with another workshop, but with the actual standard, the evidence, and the sequence to develop against it. More on that shortly.) THE STANDARD The IQ Competency Architecture: What Standards-Based Leadership Actually Requires A real standard does three things: it names the competency, it defines what mastery looks like in observable behavior, and it tells you exactly where someone stands right now — novice, developing, proficient, exceeding. That's the whole model your teachers are already using. Nobody had built the leadership version. So we did. HPG's IQ Leader Competency Assessment maps seven leadership competencies in the order they must be built — not the order they appear on an org chart, but the order the science of trust and cognition says they have to develop, or the structure above them stays fragile. Every level, 1 (Novice) through 5 (Expert), is tied to observable evidence. Not a feeling. Not tenure. A standard. 1. Building Trust — the oxygen of Team Intelligence. Without it, empowerment is abandonment, collaboration is theater, and conflict management is suppression wearing a nicer vocabulary. A leader can sit through a dozen workshops on trust and still be demonstrating Level 2 — reliable, but visibly allergic to vulnerability. TQ IMPLICATION → a cabinet stuck at Level 1–2 Trust cannot multiply anything. EQ approaches zero, and the equation collapses regardless of how much IQ is in the room. 2. Empowerment — Trust's direct descendant. This is the superintendent who says "I trust my principals" and still calls three of them before 7:30 a.m. on the first day of school. (In a provost's office, it's the committee that hasn't produced an original recommendation in three years, because everyone knows the Provost overrides anything she doesn't personally like. Coincidence is not a thing.) TQ IMPLICATION → empowerment without trust is distributed responsibility without distributed authority. 3. Collaboration — where individual intelligence becomes Team Intelligence. This is the meeting with the agenda, the nodding, and the parking-lot conversation afterward where the actual decision gets made by the two people who said the least in the room. TQ IMPLICATION → PQ, Perceptual Intelligence, is what separates a high-performing cabinet from high-performing individuals who happen to share a conference room. 4–7. Broadening Influence, Change Management, Conflict Management, Developing Others. Same sequential logic, no exceptions. You cannot broaden influence you haven't collaborated your way into. You cannot lead real change without Trust, Empowerment, and Collaboration already load-bearing. Attempting Level 5 work from a Level 2 foundation isn't ambition — it's assigning calculus to a room that hasn't mastered fractions. The effort is genuine. The outcome is fragile. Let me tell you about a superintendent I'll call Jordan. (Not his real name — but Jordan, if you're reading this, your CFO is reading this too, and you both know exactly which retreat I mean.) Jordan's cabinet of eight averaged eleven years of tenure and four doctorates between them. On paper, a senior, credentialed team. Against an actual standard, a Level 2.5 team attempting Level 4 work — initiatives that launched with real energy and were quietly dead by day ninety, a superintendent who felt, privately and exhaustingly, like the only adult in the room. Nobody had ever assessed this cabinet against anything. They'd been observed, rated on a template, and sent to conferences — never mapped against a sequential standard. When Jordan finally ran the assessment, three of his eight cabinet members tested Level 2 on Trust — the foundation everything else was stacked on top of. His longest-serving Deputy Superintendent, twenty-three years in, tested Level 1 on Developing Others. Not because she didn't care. Because no one had ever shown her what Level 3 looked like. Ten months of sequential development later — Trust before Empowerment, Empowerment before Collaboration, in that order, not the order that felt urgent — Jordan's cabinet averaged Level 3.8 across all seven competencies. I spent six years managing performance I didn't have a standard for. Now I have one. That's the difference between activity and productivity. The higher ed version has a different name and the same root cause. Celeste, a Provost with a national research reputation and a cabinet full of individually brilliant people, ran the most reliably miserable six-week budget cycle in her institution's history — every year — because nobody on that team had ever been assessed against anything more rigorous than a publication count. Same standard. Same sequence. Different letterhead. THE APPLICATION Here's what to do Monday morning (assuming you're not mid-crisis, in which case bookmark this and do it Tuesday): Move 1 — Write the standard down (30 minutes). Pull up the seven domains. For every cabinet member — yourself included — answer one question with specificity: what level are they demonstrating, based on observable behavior in the last ninety days? Not tenure. Not credential. Not potential. (K–12: can your assistant superintendent facilitate real conflict between two principals with competing visions, or does she manage it by scheduling a follow-up that resolves nothing? Higher ed: is your Dean's 24-hour-notice agenda distribution Level 4 Collaboration, or Level 2 coordination wearing the name of the former?) If you can't answer with specifics, that's the finding. You've been developing without a standard. Move 2 — Say the sequence out loud. At your next cabinet meeting, offer one idea: competencies build on each other, and you cannot shortcut Trust and still expect authentic Collaboration to show up. Then ask the room — and actually hold the silence — "Which foundational competency on this team isn't fully built yet, and what have we been stacking on top of it?" Don't answer it for them. The room that discovers its own gap starts closing it. Move 3 — Make growth visible, the same way you're asking teachers to. When someone moves from Level 2 to Level 3 on Conflict Management, say so, specifically, immediately. "I watched you hold that disagreement between your two directors open long enough for the room to find its own resolution. A year ago, you'd have scheduled a follow-up instead." Seven minutes. Highest-ROI leadership move on this list, and it costs nothing but attention. "We already do evaluations. This is redundant." You already did the math on this one two sections ago — you evaluate outcomes, you don't assess developmental competency, and that gap is exactly what's costing you a year at a time. Your evaluation rubric can't tell you whether your CFO is Level 2 or Level 4 on Empowerment, or that Trust is the actual foundation your strategic plan keeps failing to stand on. Your students get a grade and a standard. Your cabinet has been getting only one of those. "My cabinet won't respond well to being scored 1 through 5." Your students didn't respond well to standards-based grading in September either — until they saw their own growth mapped in language that actually meant something. The leaders who resist a standard the hardest are almost always the ones operating at Level 2 while carrying Level 4 expectations. Resistance isn't a personality problem. It's data, telling you exactly where to start. THE MATURITY SHIFT πŸ“„ Immature leaders think: Tenure is mastery. My experienced people don't need a standard. 🎯 Mature leaders think: Experience tells me what someone survived. A standard tells me what they actually built. πŸ“‹ Immature leaders: evaluate performance once a year and wonder why development doesn't stick. πŸ—ΊοΈ Mature leaders: name the standard, assess against it, and benchmark growth — exactly what they're asking every teacher in the building to do for a ninth grader. πŸ”„ Immature leaders: develop cabinet members individually and hope it transfers to collective performance. There is no research universe where this works. βœ–οΈ Mature leaders: build the sequential architecture that turns individual growth into Team Intelligence — because when any factor in IQ × EQ × PQ approaches zero, so does the whole product. You already believe in the research on standards-based grading. You've staked your professional credibility on the idea that averaging a student's journey produces a number that reveals nothing and guides nothing. Your cabinet is still being averaged. Score your own cabinet, right now, 1 through 5, on Building Trust — the one everything else stacks on top of. Drop the number in the comments. No explanation required. Just the number. If the number is a 4 or 5, tell us which competency it took the longest to earn. If it's a 2, you've just found where Monday morning starts. THE TEAM INSTITUTE Most leadership development runs on a theory that is philosophically identical to the grading system you already dismantled for students: assess once if at all, average performance across years of tenure, call the result a measure of competency. THE TEAM INSTITUTE is the standards-based alternative — an 8-month sequential development journey built on the same premise you're building into your classrooms and your credentialing programs: name the standard, assess against it, develop in the order the science demands, and make growth visible enough to sustain itself. Baseline Assessment. Every cabinet enters with a mapped starting point across all seven competencies — an objective level, with observable evidence, for where every leader actually is right now. Sequential Collective Development. Eight months, competency by competency, in the order the research demands — Trust before Empowerment, Empowerment before Collaboration — because you can't build the third floor before the second floor is structurally sound. 90-Day Benchmarking. Growth that's visible, specific, and tied to observable behavior sustains itself. Growth that's invisible gets quietly averaged away and relabeled "still developing." The research anchor, across 987 leadership teams in 43 states, translates to something more concrete than a percentage: cabinets that run this sequence typically move from closing one major initiative a year to closing three — the actual, felt difference between a 3x performance improvement and a strategic plan that reads well but doesn't move. πŸ“ˆ 3× performance improvement πŸ’‘ 29% higher engagement — the gap that used to only surface in an exit interview, closing before anyone's handing one in 🎯 27% better organizational outcomes πŸ”₯ Zero increase in burnout — the sequence works because it replaces guessing with a standard, not because it asks anyone to do more One requirement: full cabinet participation. Partial collective architecture isn't architecture — it's a majority position wearing the name of a team. You don't have to take my word for any of this. If you want to see where your own team stands before you decide anything, start with the free Team Intelligence Assessment — fifteen minutes, no cabinet required, just an honest first read on where your leadership currently sits against the standard: higherperformancegroup.com/tq-assessment If all of this is worth a real conversation, book a virtual coffee (with me 😊) using this link: https://calendly.com/higherperformance/30minutecoffee AMPLIFICATION Found value here? Help another educational leader find it: → Repost with the number you scored your cabinet on Trust, and the one word that number made you feel. → Tag a leader you've watched genuinely move a competency level this year — not sit through something, do something they couldn't twelve months ago. → Comment with the one competency your cabinet is strongest in, and the one an honest 1–5 assessment would sting on. The more educational leaders who move from development activity to development standards, the better our schools and our institutions become. That's not inspiration. That's arithmetic. Follow DR. JOE HILL and Higher Performance Group for weekly Team Intelligence insights.
By HPG Info July 7, 2026
And summer break isn't going to fix it. It's July 5th. You're reading this the morning after fireworks, probably with a cup of coffee you actually had time to finish for once. And somewhere in the back of your mind, you've already decided that this stretch — these six or seven weeks before the building fills back up — is going to fix what's broken in your cabinet. It's not going to fix it. I need you to hear this from someone who isn't trying to sell you on a vacation: rest is not the same thing as repair. Your team can come back in August more tan and less tired and still be carrying the exact same structural weight they were carrying in May. Because the thing that's breaking them isn't a depletion problem. It's an architecture problem. And architecture doesn't rebuild itself while everyone's at the lake. Keep reading. This one's for the leader who knows something's off and has been hoping the calendar would solve it. — — — You Don't Have a Resilience Problem Here's what's actually happening, in plain terms. You've got people on your cabinet — maybe it's you, probably it's you — who are waking up tired before they've even gotten out of bed. Not tired from a long week. Tired in a way sleep doesn't touch anymore. You've got people performing confidence in the 2:00 meeting and sitting in their car afterward wondering if any of it was real. You've got people who used to love this work and now just do it. Same title, same competence, completely different relationship to the job. That's not burnout the way your professional development catalog talks about it — protect your boundaries, try a gratitude journal. That's a measurable force acting on people who were never given a system designed to hold it. πŸ“Š 63% of professionals are showing at least one sign of burnout right now — up from 51% just a few years ago. That's not a vibe. That's a structural shift in working conditions, and your cabinet is standing directly inside it. Burnout doesn't go after the disengaged. It goes after the deeply invested. Here's the part that should unsettle you a little: it's not hitting your weakest people. It's hitting your best ones. The ones who care most are the ones who absorb the most — because they're the least likely to say no without writing a three-page justification for why they're allowed to. Which means the person carrying the most weight on your cabinet right now is probably the one you'd never think to worry about. Because they're still performing fine. TQ IMPLICATION → When the Burnout Force suppresses any one dimension of TQ = IQ × EQ × PQ — and it almost always hits EQ first — eight brilliant people quietly become eight exhausted individuals trying not to show it. — — — Why This Week, Not September If your plan is "we'll regroup over the summer," you're going to walk your team right back into the exact same conditions in August — just rested enough to absorb them a little longer — while your best people quietly do the math on whether this is still worth it. I've watched it happen more times than I can count. The cabinet member who's three months from the door doesn't leave because they stopped believing in the mission. They leave because nobody ever rebuilt the structure that was supposed to hold them up. This window — right now, this stretch between the 4th and the first board meeting of the fall — is the only time your whole team is actually together, away from the daily fires, with enough margin to do something structural instead of something cosmetic. It's short. It's closing. Once the building fills back up in August, this conversation gets ten times harder, because everyone's back in survival mode and there's no room left to rebuild anything. ❌ Immature: "We'll regroup once things slow down." βœ… Mature: "We'll rebuild the architecture while we actually have the room to do it." — — — What Actually Works (And What Doesn't) You can't fix a collective architecture problem by sending three people to a conference and hoping it trickles down. It doesn't trickle down. It just creates one more person on your cabinet who's seen the framework and is now alone trying to translate it for everyone else. That's not a solution — it's a more sophisticated version of the same isolation. What works is your whole team in the room at the same time, hearing the same language, naming the same forces, in the same moment — so the isolation breaks immediately instead of getting passed down secondhand. I had a superintendent tell me, six months after we did this work together: "I feel like I'm leading again instead of surviving." Same district. Same challenges. Different architecture for who's allowed to carry what. (This is exactly the gap The Burnout Force keynote was built to close — not by making individuals more resilient, but by giving your entire cabinet a shared language for the forces acting on all of them, at the same time, in the same room. More on that below.) — — — The Maturity Shift Immature leaders think: "I need to push through this. Resilience is the answer." Mature leaders think: "I need to understand what I'm pushing against — and whether I'm designed to push against it alone." Immature leaders absorb the force as a personal experience and add another morning routine. Mature leaders name the force structurally and build the conditions where it gets distributed instead of concentrated. From our research across 987 leadership teams: 3× performance improvement. 29% higher engagement. 27% better outcomes. Zero burnout increase — when the architecture gets rebuilt instead of the individual. Your turn: Who on your cabinet is carrying the most right now — and does your team even know it? Name them in your head. Then ask yourself if you'd actually planned to do anything about it before August. — — — Let's Get This on the Calendar Before the Building Fills Back Up Here's what I'd want for you if I were your friend: get your whole cabinet — or your whole staff, if that's the room you've got this summer — in front of this before the fall calendar swallows you again. Not a resilience talk. A structural reframe about why the weight keeps landing on the same people, and what it would take to actually distribute it. I built the Burnout Force keynote for exactly this room, this time of year, this exact decision point. I'd rather have this conversation with you now, while you still have a retreat date open, than in October — when your best person hands you their notice and you're trying to figure out what happened. Full cabinet or full-staff keynote experience. Built for leaders done treating a structural problem as a personal failing. If that's the room you're trying to build this summer, let's talk this week — not in the fall. πŸ“… Grab 30 minutes: calendly.com/higherperformance/30minutecoffee πŸ“ž Or just email: βœ‰οΈ joe@higherperformancegroup.com Your people aren't broken. The system they're operating inside is. And you've got about six weeks to do something about it before the building fills back up. — — — Found value in this? → Repost with the one force you watched hit your cabinet hardest this year. → Tag a leader you know is carrying more than they should be carrying alone — over this holiday weekend especially. → Comment with what your summer plan actually was, before you read this. The more leaders who move from individual resilience to collective architecture, the stronger our institutions become. Follow DR. JOE HILL and Higher Performance Group for weekly Team Intelligence insights. ο»Ώ #CancelAverage
Show More