Higher Performance Insights | WHEN TRUST GOES TO VOICEMAIL

November 4, 2025
higher performance insights

THE MATH THAT DESCRIBES WHY LEADERSHIP TEAMS FAIL UNDER PRESSURE


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


Do this math: 8 cabinet members × 12 meetings × 90 minutes = 144 hours annually with people you call "your team" but wouldn't call if your world fell apart.


That's not a leadership gap. That's a relationship infrastructure crisis.


73% of superintendents in our 987-team study report "plenty of colleagues but no one who really gets it." (Most won't admit this until drink two at the conference hotel bar.)


Here's the pattern: We've professionalized educational leadership so thoroughly that we've accidentally made it functionally impossible to build the one thing that determines whether your cabinet actually works—relationships that transcend the role.


I was recently in conversation with a leader who has navigated both established legacy organizations and complete startups—completely different contexts that require entirely different leadership skills. And he said something that stopped me cold: "I only have 2-5 people max who remain my friends through all the seasons of life. And that's all that really matters."


Two to five people. Not 2000 LinkedIn connections. Not your entire cabinet. Not even your full executive team.


Two. To. Five.


And suddenly, everything about why some leadership teams click and others just... meet made perfect sense.


Let's discuss what most leadership development programs overlook entirely.


LET'S TALK ABOUT THIS LIKE ADULTS WHO'VE SURVIVED MULTIPLE ACCREDITATION CYCLES


Here's what nobody tells you at leadership conferences (because they're too busy selling next year's tickets): The reason your cabinet doesn't function like a team has nothing to do with strategic planning tools or communication protocols.


It has everything to do with whether you've built trust deep enough to survive seasons.


SPECIFIC RECOGNITION:


You know this moment:


It's 11 PM on a Sunday, and the board email just hit your inbox—the one that makes your stomach drop. You scroll through your contacts looking for someone to call.


You pass right over your Assistant Superintendent for Curriculum. Your CFO. Your VP of HR.


Not because they're incompetent. Because you need someone who knows you independent of your title.


(And the person you actually call? Probably doesn't work in education.)


Or this one:


You're in a cabinet meeting debating a controversial policy change. Everyone's nodding. Taking notes. Agreeing professionally.


Then you adjourn, and three separate people text their actual thoughts to someone NOT in the room.


You've built a team that performs trust but doesn't practice it.


Or my personal favorite:


Your Chair gets promoted to Dean—brilliant strategic mind. Everyone's excited.


Six months in, she's technically proficient, but the cabinet dynamics feel off—because she's performing her new role while psychologically remaining in her old identity.


And nobody can talk about it because you've never established the kind of trust where identity evolution is safe.


ROOT CAUSE DIAGNOSIS:


Here's why this keeps happening, and I'm going to be direct because I've spent 25 years in the loneliness of the leadership seat: We've confused competency with capacity.


We hire for IQ. We develop EQ. We measure performance indicators. But we completely ignore the foundation that determines whether any of it actually works: Building Trust.


Not trust as a soft skill. Trust as the oxygen of TEAM INTELLIGENCE.


Research from our work with 987 leadership teams reveals something most leadership development completely misses: Leaders cannot skip competency levels without creating fragility in their leadership foundation. You cannot authentically empower others until you've established trust. You cannot facilitate genuine collaboration without both trust and empowerment. You cannot lead change successfully without trust, empowerment, collaboration, and influence working synergistically.


Yet what do we do? We promote people into complex leadership roles and immediately expect them to manage change, resolve conflicts, and develop others—Level 5 work—when they're operating at Level 1-2 on Building Trust.


That's not a competency gap. That's a developmental logic violation. And it's why 67% of change initiatives consistently fail.


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


💡 "You cannot empower others until you've established trust. You cannot collaborate without empowerment. You cannot lead change without all prior competencies working synergistically."


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


(This is actually why we created the TEAM INTELLIGENCE framework and built it into our TEAM INSTITUTE sessions—to help leadership teams develop sequentially instead of randomly. But I'm getting ahead of myself.)


TQ FRAMEWORK INTRODUCTION:


This is the part where I'm supposed to tell you to "create psychological safety" or "build better relationships." But you already knew that.


The real problem? Most leaders are attempting advanced leadership competencies without mastering the foundational one.


Here's the developmental sequence that actually works, drawn from our Leader Competency Assessment:


Level 1: Building Trust — Foundation for all others


Level 2: Empowerment — Builds on trust foundation


Level 3: Collaboration — Requires trust and empowerment


Level 4: Broadening Influence — Leverages collaborative networks


Level 5: Managing Change — Requires all prior competencies


Level 6: Managing Conflict — Transforms collaborative tension into breakthrough


Level 7: Developing Others — Apex competency synthesizing all others


Your cabinet isn't dysfunctional because people lack skills. It's dysfunctional because you're trying to run Level 5 plays (change management) with a team operating at Level 1-2 trust.


And trust—real trust, the kind that survives leadership transitions and organizational turbulence—isn't built in strategic planning sessions. It's built when relationships transcend the org chart.


🎯 BUILDING TRUST: THE COMPETENCY THAT DETERMINES EVERYTHING ELSE


WHY THIS ALWAYS COMES FIRST (EVEN WHEN WE WISH IT DIDN'T)


Organizations led by leaders who create a psychological safety culture are significantly more likely to foster innovative cultures, with substantially better talent retention and higher stakeholder satisfaction. (That's not motivation-poster wisdom. That's data from institutions that actually work.)


But here's what most leadership development gets catastrophically wrong: They treat trust as a soft skill you sprinkle on top of competence, rather than the foundation that determines whether competence ever becomes performance.


Trust is the oxygen of team intelligence. Without it, every other competency suffocates.

Let me break down the five levels of Building Trust—and show you exactly where your cabinet is probably stuck:


LEVEL 1: DEMONSTRATES INCONSISTENT RELIABILITY


• Communication lacks transparency


• Actions and words frequently misalign


• Tends to blame others for setbacks


Observable reality: This is the superintendent who announces, "My door is always open," but team members never walk through it. Or the cabinet member who commits to the meeting but ghosts on execution. Your team isn't underperforming because they're incompetent—they're hedging because reliability is inconsistent.


Quick gut check: How many times this month has someone on your cabinet surprised you by not following through?

LEVEL 2: SHOWS BASIC RELIABILITY BUT STRUGGLES WITH VULNERABILITY


• Generally follows through on commitments


• Shares limited information


• Hesitates to admit mistakes


Observable reality: This is where most educational leadership teams actually operate. Professional. Polite. Performing collaboration. But when something goes sideways, nobody's texting each other. They're calling someone outside the organization who they actually trust. You've built a reporting structure, not a team.


Be honest: When was the last time someone on your cabinet admitted a mistake before you discovered it?


LEVEL 3: CONSISTENTLY DEMONSTRATES INTEGRITY AND TRANSPARENCY


• Demonstrates vulnerability as a leader


• Advocates for team members even when costly


• Addresses trust violations directly and fairly


Observable reality: This is where the shift happens—from "colleagues who work together" to "people who have each other's backs." Cabinet members start processing real thinking with each other instead of around each other. When one person's worried about something, the team knows about it before it becomes a crisis.


LEVEL 4: CREATES AN ENVIRONMENT OF PSYCHOLOGICAL SAFETY


• Establishes systems that promote transparency


• Creates mechanisms for addressing breaches of trust


• Models reconciliation and repair after conflicts


Observable reality: This is the cabinet that can debate controversial decisions and still go to lunch together afterward. Why? Because they've built systems—not just goodwill—that make trust renewable even when it's damaged. They've moved from hoping trust happens to architecting it into how they operate.


LEVEL 5: BUILDS INSTITUTIONAL CULTURES OF TRUST


• Establishes formal and informal influence channels


• Develops systems for cross-campus knowledge sharing


• Connects the institution to external opportunities


Observable reality: This is rare. This is when your cabinet's trust infrastructure becomes the model for the entire district. When principals start running their teams the way you run yours—not because you mandated it, but because they've watched it work.


THE BRUTAL REALITY CHECK:


We spent this fall running TEAM INSTITUTE sessions with campus leadership teams, and we started every single one with the Building Trust assessment. Want to know the most common result?


Leaders rated themselves at Level 3-4. Their teams rated them at Level 1-2.


That gap? That's your entire performance problem right there.


THE THREE TRUST QUESTIONS THAT REVEAL EVERYTHING:


I learned these from a leader who built multiple teams across completely different organizational contexts. He said the distinguishing factor wasn't competence or chemistry—it was answering three questions honestly:


Question 1: "Who on this team would I call at 11 PM if my world were falling apart?"


If the answer is zero or one, you don't have a team. You have coworkers who attend meetings.


Question 2: "Who on this team has embraced the leader I'm becoming, not just the role I'm performing?"


Leadership transitions require identity evolution. If your cabinet can't hold space for that, people perform their new role while psychologically remaining in the old one. (This is why your brilliant new Dean still acts like a Chair.)


Question 3: "Can I make decisions WITH this team, or do I just announce decisions TO them?"


If you're married, you don't make major life decisions unilaterally and then expect your spouse to get on board. Why do we think that works with leadership teams?


The teams that can answer all three questions affirmatively? Those are the ones where trust isn't a nice-to-have. It's the infrastructure underneath everything else.


CASE STUDY: THE TEAM THAT REBUILT TRUST FROM LEVEL 1


A community college president (let's call her "Maria"—and yes, she knows I'm telling this) inherited a cabinet of seven VPs. All credentialed. All experienced. All completely siloed and performing trust instead of practicing it.


Her first 90 days, she tried what most new leaders try: strategic planning. Vision alignment. Goal cascading. Professional development.


Nothing changed.


Then she did something most leaders won't: She admitted the problem wasn't strategy. It was trust.


She brought in our TEAM INTELLIGENCE assessment. Results showed her cabinet at Level 1-2 on Building Trust, yet they were attempting Level 5 work (managing major institutional change).


The developmental logic violation was obvious.


Here's what she did:


She stopped leading cabinet meetings and started building trust infrastructure.


She asked each VP privately: "Who on this team would you call at 11 PM if something went sideways in your personal life?"


Zero VPs named anyone on the cabinet.


Then she asked: "Who on this team knows what you're genuinely worried about regarding your work right now—not the polished version you present in meetings, but the real anxiety?"


Two had someone. Five didn't.


The gap between "colleagues" and "people who trust each other through seasons" was costing them everything.


Maria created monthly one-on-one conversations where the only agenda was: "Who are you becoming as a leader, and how can this team help you get there?"


Not performance evaluations. Identity evolution conversations.


She stopped managing performance and started shepherding transformation.


Within 90 days, VPs started texting each other their real concerns instead of people outside the room.


Within six months, they'd formed what I call "micro-alliances"—2-3 people who processed real thinking together between formal meetings.


Within a year, the cabinet made a controversial curricular decision unanimously because they'd made it WITH each other.

Student success metrics? Increased 12 percentage points. Faculty satisfaction? Up 23%.


But Maria told me: "The strategy didn't change. The trust infrastructure underneath the strategy changed. Turns out, that's what actually matters."


She rebuilt from the foundation up. Level 1 to Level 4 in 18 months.


That's not magic. That's developmental sequence done right.


📋 HERE'S WHAT TO DO MONDAY MORNING (BEFORE YOUR FIRST CABINET MEETING)


STEP 1: RUN THE TRUST LEVEL AUDIT (20 MINUTES)


Pull out our Leader Competency Assessment—or just grab a piece of paper and be brutally honest.


For Building Trust, where is your cabinet actually operating?


• Level 1: Inconsistent reliability, limited transparency, misaligned words and actions


• Level 2: Basic reliability but limited vulnerability


• Level 3: Consistent integrity, demonstrates vulnerability, advocates for team members


• Level 4: Creates psychological safety systems


• Level 5: Builds institutional trust cultures


Don't rate where you want to be. Rate where the evidence says you are.


Then—and this is the hard part—ask 2-3 trusted people on your team to rate you honestly. (If the gap between your self-assessment and their assessment is more than one level, that gap IS your leadership problem.)


STEP 2: ASK THE THREE TRUST QUESTIONS (30 MINUTES TOTAL, 10 PER QUESTION)


Schedule 30 minutes alone. Write down honest answers to:


1. "Who on my cabinet would I call at 11 PM if my world were falling apart?" (Names, not theory.)


2. "Who on my team knows the leader I'm becoming, not just the role I'm performing?" (If nobody comes to mind immediately, that's your answer.)


3. "Am I making decisions WITH my team, or announcing decisions TO them?" (Check your last three major decisions. How many were truly collaborative vs. performatively collaborative?)


If you can't name at least 2-3 people for questions 1 and 2, you don't have a performance problem. You have a trust infrastructure problem.


(Objection handling: "Joe, this feels soft. We need to focus on results." Fair pushback. But here's the data: Leaders in the top quartile for Building Trust competencies are significantly more likely to achieve institutional objectives. The teams that outperform yours? They already figured this out. You can dismiss it as soft, or you can build the foundation that makes results possible.)


STEP 3: CREATE ONE "IDENTITY EVOLUTION" CONVERSATION THIS WEEK (45 MINUTES)


Pick one cabinet member. Schedule 45 minutes. No agenda except this:


"I want to understand who you're becoming as a leader, not just how you're performing in your role."


Ask:


• "What identity from your previous role are you still carrying that might not serve you here?"


• "What new leadership identity are you nervous about stepping into?"


• "How can this team hold space for who you're becoming?"


Then—critically—share your own answers first. Model the vulnerability you're asking for.


This isn't therapy. This is recognizing that leadership transitions require identity evolution, and teams that can't hold space for that will always underperform their talent level.


(Pro tip: This conversation will feel awkward the first time. That awkwardness is diagnostic. If you can't have this conversation, you're operating at Level 1-2 trust. Which means you can't do Level 5 work. The math doesn't lie.)


⚡ THE MATURITY SHIFT: FROM COMPETENCE WITHOUT FOUNDATION TO TRUST-BASED TEAM INTELLIGENCE


IMMATURE TEAM INTELLIGENCE:


• Promotes leaders based on technical competence, ignores trust capacity


• Attempts Level 5 work (change management, conflict transformation) with Level 1-2 trust


• Believes competence creates collaboration


• Confuses "getting along professionally" with psychological safety


• Optimizes for efficient meetings over authentic relationships


• Measures team health by completed initiatives, not trust infrastructure


• Views vulnerability as weakness rather than foundation


MATURE TEAM INTELLIGENCE:


• Develops leaders sequentially through competency levels starting with trust


• Recognizes you cannot skip developmental stages without creating fragility


• Knows trust creates the conditions where competence becomes performance


• Distinguishes "colleagues who collaborate" from "teams that trust each other through seasons"


• Prioritizes identity evolution conversations over performance management


• Measures team health by the "11 PM phone call test" and vulnerability indicators


• Views Building Trust as the oxygen that makes all other competencies possible


The shift isn't about being less professional. It's about being honest that principles without competencies are wishes—and competencies without sequential development are illusions.


Your cabinet doesn't need another initiative. It needs the foundational competency that determines whether any initiative actually works: Building Trust at Level 3 or higher.


Everything else is decoration on a house with no foundation.


P.S. THE FOUNDATION UNDER THE FOUNDATION


I was meeting with a superintendent recently who said something that's stuck with me: "Joe, I've read every leadership book. Attended every conference. My team is credentialed, experienced, and talented. But we're still not clicking. What am I missing?"


I asked him one question: "On a scale of 1-5, where's your cabinet on Building Trust?"


Long pause. Then: "Probably a 2. Maybe a 1.5 if I'm being honest."


"And what level of work are you attempting?"


Another pause. "Change management. Conflict resolution. Developing future leaders. So... Level 5?"


There's your answer.


You cannot skip developmental stages. Leadership competencies build sequentially—each creates the foundation for those that follow.


Attempting Level 5 work with Level 1-2 trust isn't a strategy problem. It's a physics problem.


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

💡 "Principles without competencies are wishes—and competencies without sequential development are illusions."

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


And here's what I've learned after 25 years of this work, grounded in principles that go way beyond organizational theory: The foundation under the foundation is actually faith.


Not faith as religion forced on secular space. Faith as the recognition that we're building something bigger than our own ambition. That how we lead matters as much as what we achieve. That trust isn't a technique—it's the recognition that we're all navigating uncertainty together, guided by principles beyond self-interest.


I know I'm among friends here who share those values. Who understand that excellent leadership flows from internal alignment with something transcendent. Who get that Building Trust isn't manipulation—it's stewarding relationships with the care they deserve.


This fall, we ran Team Institute sessions with campus leadership teams focused specifically on this: Building Trust as the foundational competency that determines everything else. We used the Leader Competency Assessment to help teams see where they actually are (not where they think they are), then gave them sequential tools to develop from Level 1 to Level 4.


The feedback? Teams are finally addressing the real problem instead of decorating around it.


If your cabinet is talented but underperforming, you don't need another strategic planning session. You need to build the trust infrastructure that makes strategy actually work.


New campus teams enroll in the Team Institute each month. We start with Building Trust. We develop sequentially through the seven competencies. We use the Team Intelligence framework to multiply individual development into collective performance.


Want the full Leader Competency Assessment to run with your team? Message me directly or email info@higherperformancegroup.com and I'll send it to you. No cost, no strings—just a tool to help you see where you actually are versus where you're attempting to operate.


If you're interested in what Team Institute might look like for your team, let's have a conversation about where your team is and where sequential development could take you.


But even if you never reach out, do me one favor: Before your next cabinet meeting, honestly assess—Where are we on Building Trust? And what level of work are we attempting?


If there's a gap of 2-3 levels, you just diagnosed your entire performance problem.


The question is: Are you willing to go back to the foundation and build it right?


ONE MORE THING...


If this resonated, I need your help with three things:


1. Repost this with your honest answer: "Where is my team on Building Trust (Level 1-5)? And what level of work are we attempting?" Tag me so I can see your assessment. (The gap between those two numbers tells you everything.)


2. Tag someone on your leadership team who's committed to building from the foundation up—not just decorating around dysfunction. Tell them specifically why you're tagging them.


3. Comment below with this: What's one moment when you realized your team's performance problem was actually a trust problem? What did you do about it? (I read every single comment because your reality shapes what we build next.)


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


And if you're serious about moving your team from Level 1-2 to Level 3-4 trust, message me about TEAM INSTITUTE enrollment. New cohorts launching monthly. Or email info@higherperformancegroup.com to get the full Leader Competency Assessment for your team.


Most important question: Who on your cabinet would you call at 11 PM? If you can't immediately name 2-3 people, you just found your starting point.


NEXT ISSUE PREVIEW


"The $847,000 Meeting Tax: Why Your Cabinet Is Bleeding Budget in 90-Minute Increments"


You know those weekly cabinet meetings where everyone reports out, but nothing actually gets decided? I ran the numbers. For a typical superintendent cabinet, those meetings cost $847,000 annually when you calculate salary, prep time, and opportunity cost.


That's not a meeting problem. That's a TEAM INTELLIGENCE deficit costing you nearly a million dollars a year.

(Spoiler: The highest-performing cabinets meet half as often and decide twice as fast. We'll break down exactly how they do it.)


See you next week. Keep building from the foundation up.


—Joe



P.S. - If this issue helped you see something differently, take 10 seconds to repost it with your biggest takeaway. Your network needs this too.


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 September 15, 2026
Not the parking-lot kind. The kind that happens in the room. I want to say something that will get me uninvited from a few conferences this year: the calmest cabinet meeting in your building this month was probably the most dishonest one. Nobody lied in that meeting. Everyone in the room agreed to something nobody actually believed, and called it professionalism. There's a scene near the start of 12 Angry Men where eleven jurors vote guilty in under two minutes. Nobody's examined the knife. Nobody's questioned the witness. They just want to make the four o'clock ballgame, and a fast unanimous vote looks exactly like agreement. Patrick Lencioni named the real version of that back in 2002, and the label still fits: artificial harmony. Your cabinet runs its own eleven-to-one vote most weeks, and it doesn't need a jury box to do it. Here's the uncomfortable part. A cabinet with zero visible conflict almost always has the same explanation: something real never got said out loud. THE DIAGNOSIS Let's talk about this like adults who've sat through a “great meeting” that solved nothing. You know the meeting where the budget gets flagged as a concern, everyone nods that they'll “look into their numbers,” and six weeks later the same number resurfaces, because nobody said out loud whose number it was to fix. You know the one where two VPs have been quietly furious with each other since March over a staffing decision, and you can feel it every week in how carefully they avoid each other, and you've decided not to name it because naming it feels like starting something. You know the one where a board member's pet initiative gets full-throated public support in the room, then gets picked apart, sentence by sentence, in the parking lot the second the meeting adjourns. That parking lot conversation is where your cabinet's real meeting is actually happening. The one with the agenda is theater. We call it Consent Theater: everyone performs alignment in the room, and almost nobody in the room actually feels it. I know the exhaustion of being the only person who can feel the thing nobody's saying. It's a specific kind of lonely: watching six capable adults nod in unison at a decision you already know three of them will quietly work around by Thursday. (This is the exact gap THE TEAM INSTITUTE was built to close: the collective architecture that makes disagreement safe enough to happen in the room, in real time, instead of surfacing later in a one-on-one, a group text, or the parking lot. Most leadership development still trains individuals to argue better. This trains the room to hold the argument without breaking. More on that in a moment.) Here's the diagnosis. This is an EQ problem, specifically the part of EQ nobody trains: the capacity to host real disagreement without the room falling apart. Most leadership development sharpens IQ. Almost none of it builds a team's tolerance for productive friction. TQ = IQ × EQ × PQ. Skip that capacity, and you're not getting a calmer team. You're multiplying by something close to zero. THE REAL-FIGHT LITMUS (Or: How to Tell a Real Fight From a Tantrum, in Under Ten Seconds) Call this the Real-Fight Litmus. Or don't — it'll still explain why your cabinet's least professional-sounding argument last year was probably its most valuable ten minutes, while last month's perfectly polite meeting produced exactly nothing. Not all workplace drama is the same. There's melodrama, and there's the real thing, and most leaders never learned to tell them apart, so they shut down both the same way. Three checks separate them. The Stakes Check. Is this about the mission, the budget, the students, the decision, or is it about who gets credit and whose feelings got bruised three weeks ago? Real conflict is anchored to something the institution actually needs solved. (IQ's job: knowing whether the fight is even worth having.) The Address Check. Is it being said to the person it's about, in the room, right now, or about that person, to someone else, later? Real conflict happens at the table. Manufactured drama happens in the parking lot, the group text, the hallway pull-aside that somehow never includes the actual person. (EQ's job: whether the team has the nerve to say it to the face instead of the back.) The Landing Check. Does it end with a decision, an owner, and a next step, or does it just end, unresolved, waiting to resurface next month wearing a different disguise? (PQ's job: reading the room accurately enough to know when the real issue has actually surfaced.) Miss any one, and per the formula, you're multiplying by something close to zero: all the emotional energy of a real fight, none of the resolution. THE CASE STUDY This is a composite, drawn from patterns across our work with 987 leadership teams , not one specific superintendent's story. Picture a seven-person cabinet known among peer districts as “the calm one.” Internally, two departments hadn't fully trusted each other in over a year, since a staffing reallocation neither side felt was handled fairly. Nobody had said that sentence out loud with both of them in the room. Instead, it surfaced everywhere else: in one-on-ones with the superintendent, in the politely cold exchanges in shared meetings, in a joint enrollment-outreach grant the two departments had quietly stopped planning together — fourteen months and counting. The turning point came in one meeting when the superintendent named it directly: “I think there's an unresolved staffing decision between these two departments, and I'd rather we have that conversation here, today, than everywhere else.” Twenty-five uncomfortable minutes followed, then something the cabinet hadn't had in over a year: a resolution, with an owner and a next step, that both departments could name identically when asked separately. The grant application was back on both departments' calendars within three weeks. Six months later, joint planning had gone from an occasional truce to a standing agenda item. Same seven people. One real fight, finally allowed to land where it belonged. THE APPLICATION Here's what to do Monday morning (assuming you're not already mid-crisis, in which case, do this Tuesday): Step 1: Run the Litmus on Your Last Meeting (15 minutes). Pull last week's cabinet agenda. For each item that generated any friction at all, ask the three checks: was it about the mission, or about ego? Was it said in the room, or about someone elsewhere? Did it land on a decision, or did it just stop? If most items pass all three, you have real conflict already, and you're ahead of most cabinets. If most items fail the Address Check, you have a parking-lot cabinet, and the real meeting is happening somewhere you're not. Step 2: Name One Unresolved Thing, Out Loud, In the Room (20 minutes at your next meeting). Pick the one disagreement everyone already knows about but nobody has said directly to the people involved. Say it plainly, the way the superintendent did above: name what you've noticed, and invite the actual conversation, in the room, this week, not “offline.” This will feel like the least professional five minutes you've had in months. It's also the most useful. Step 3: Build a Team Norm for the Address Check (ongoing). Agree, as a cabinet, on one rule: disagreements about a colleague's decision get raised to that colleague, not about them. Practicing this once doesn't undo a year of parking-lot conversations. Practicing it every week, for a few months, does. “We don't have time for this.” You're already spending it. The latest workplace research puts the average manager at over four hours a week managing workplace conflict — more than 230 hours a year. That number doesn't change based on whether you have the real fight or not. It just changes whether that time produces an actual decision, or more meetings about the meeting. “This will make our meetings feel less professional.” Maybe for the first few. But Google's own multi-year Project Aristotle study found one trait separated its highest-performing teams from the rest: psychological safety, the freedom to disagree openly without fear of looking bad in the room. Politeness never made the list. You've been chasing the wrong variable. THE MATURITY SHIFT Immature leaders think: “A good meeting is one where nobody gets upset.” Mature leaders think: “A good meeting is one where the real thing finally got said.” Immature leaders protect the room from conflict, and call it culture. Mature leaders protect the room's capacity to have the conflict, and call it trust. The gap runs deeper than temperament. Somewhere along the way, we convinced an entire generation of leaders that a quiet room is a healthy room. Lencioni named the pattern in 2002. Twenty-four years and a mountain of team-performance research later, most cabinets still run on the original assumption: calm equals healthy. Every eleven-to-one vote your cabinet takes without a single dissenting question is a choice, made weekly, about whether the real disagreement happens in the room or goes and finds somewhere else to live. Your turn: think of the disagreement your cabinet is currently avoiding in the name of staying “professional.” Where is it actually living right now? A one-on-one? A group text? Somebody's resignation letter draft? Name it in the comments. I'll wait. If artificial harmony has been running your cabinet's meetings, and after this issue you don't believe “calm” and “healthy” are the same thing anymore, then what's missing is architecture: the collective skill of hosting real disagreement without the room, or the relationships in it, falling apart. This is what THE TEAM INSTITUTE builds. It's an eight-month program for full leadership cabinets — superintendents and university presidents and the people who sit across the table from them — built around exactly this kind of collective muscle: knowing which fights are real, having them where they belong, and landing them on an actual decision. Across 987 leadership teams, cabinets that did this work saw performance improve roughly 3x and engagement rise 29%, without an increase in burnout, which is usually the quiet cost of every other leadership initiative that just asks people to try harder. Start with the Team Intelligence Assessment. It'll tell you, plainly, whether your cabinet's calm is real or borrowed: https://www.higherperformancegroup.com/tq-assessment Whether or not this is the season for that step, here's a smaller one that costs nothing: repost this with the disagreement your cabinet has been calling “fine” for longer than it should have, tag the colleague who already knows exactly which one you mean, or drop your own version in the comments. Somebody else's cabinet needs to hear that they're not the only one avoiding the same conversation. Follow DR. JOE HILL and Higher Performance Group | THE TEAM INSTITUTE
By HPG Info September 7, 2026
Fluent. Confident. Wrong. In that order. Every cabinet meeting I've sat in since the second week of June has opened with some version of the same sentence: "The board wants to know our AI plan." Nobody's arguing AI matters. That fight's over. What almost nobody's asking is the question underneath it: the one that actually decides whether this fall helps your cabinet or quietly wrecks it. Before you put a machine on the payroll as your cabinet's newest ghostwriter, have you checked what it already believes about you? Here's what nobody tells a team of senior leaders walking into its first AI rollout: the tool doesn't create your team's judgment. It ghostwrites it, fluently, into every board memo and parent email and strategic plan you hand it, sounding exactly as confident in the ones that are wrong as the ones that are right. Two stories explain what's actually at stake this fall. One's old. One's brand new. Together, they're the whole problem. THE SENTENCE In third grade, a teacher tried to stop a boy from getting bullied. He'd been held back in reading, had migraines nobody diagnosed, and needed things repeated more than his classmates did. So she stepped in, pointed at him in front of the whole room, and said the thing she thought would protect him: "Leave that kid alone. That's the boy with the broken brain." She meant it kindly. He heard two words. Broken brain became the sentence he ran, silently, for the next decade: every time he wasn't picked for a team, every time he failed a test, every time he took the back-row seat hoping nobody would call on him. That kid grew up to be Jim Kwik, now one of the most recognized names in learning and memory training on the planet, the guy Fortune 500 companies and elite athletes call when they need to think faster under pressure. He told the story in a conversation earlier this year, and the line that stopped me wasn't the injury. It was what he said actually held him back: "Under stress, we don't rise to the level of our aspirations. We fall to the level of our stories, our systems, and our self-image." Not his intelligence. Not his skill. His self-image, inherited from a five-second sentence somebody else said, replaying under pressure for ten straight years. Now sit with the version your own cabinet is running. Maybe it's a board comment from three budget cycles ago that nobody's repeated out loud since, but everybody still quietly believes. Maybe it's a single paragraph an accreditation team wrote four years back that's still deciding what your provost thinks she's allowed to propose. Maybe it's simpler: a founding leader who once told this team they weren't ready for something, and nobody has tested whether that's still true. Here's the part that should actually worry you. Kwik didn't get better at learning by treating the injury. He got better by finding, and rewriting, the sentence. Your cabinet's talent isn't the variable in question here. It rarely is. The sentence running underneath the talent is. THE TURN Here's why this matters more this fall than any fall before it. For every year of your career until now, your cabinet's inherited sentence stayed mostly contained. It shaped a meeting here, a hesitation there, a proposal that quietly never got made. Slow damage, spread out over years. That containment is gone. Kwik, talking about the exact tools your board is asking about, put it plainly: "AI can scale and amplify. But it can only scale and amplify what a human brings to it." Feed it a clear, tested, collectively-owned judgment, and it multiplies your best thinking across every email, every plan, every decision your cabinet touches. Feed it an untested inherited sentence, and it does the exact same thing to that. (This is the exact gap THE TEAM INSTITUTE was built to close this fall: surfacing what the room already believes before the tool starts repeating it back at scale, which is different work than training your cabinet on the tool itself. Every vendor already offers that part. More on that in a moment.) TQ = IQ × EQ × PQ still holds. What's new is the multiplier. A cabinet with strong IQ and an untested self-image used to produce one flawed decision at a time. The same cabinet, with AI in the loop, can now produce that flawed decision a hundred different ways before lunch: in a strategic plan draft, a parent email, a board memo, and every version will read as confident, because the tool can't tell the difference between confidence and an old wound. THE OLD PLAYBOOK If you want proof this isn't just a Higher Performance Group observation, change management researchers are already redrawing the map. Kotter's 8-Step Change Model has run more transformations than any framework in modern management: create urgency, build a coalition, communicate the vision, empower people to act, anchor the gains. It's built for change that holds still long enough to sequence. A comparative model published this year in the Journal of AI, Robotics & Workplace Automation puts Kotter's eight steps next to a proposed AI Adoption Change Model, and the contrast is the whole argument in one picture. Source: Journal of AI, Robotics & Workplace Automation, Vol. 5 (2026), Henry Stewart Publications. Look at where each model starts. Kotter opens with urgency and a coalition, top-down, already decided. The AI model opens with exploring potential and discovering champions, bottom-up, still being tested. Kotter ends with anchoring the change in culture. The AI model ends with "cultivate AI-driven culture" and loops straight back into exploring again, because the tool never stops shipping new capability long enough for anything to get anchored. That's the structural version of what Kwik is describing at the individual level. AI adoption isn't a project you finish. It's a loop you run, and every pass through that loop amplifies whatever judgment your cabinet brought to it, tested or not. Which is exactly why the next five steps matter more than the eight above them. BUILD BEFORE YOU BORROW Kwik teaches a five-step discipline for exactly this problem, built for one person working with AI. It translates almost perfectly to a cabinet. You just have to run it as a room, not as one person with a laptop. Brainstorm first. Before anyone opens a tool, the cabinet talks through the problem out loud, together, with nothing feeding them an answer. This has nothing to do with whether the tool can be trusted. A room that's never practiced thinking together won't notice when the tool starts thinking for it instead. Understand the real problem. Most cabinets solve the presenting problem (enrollment's soft, a program's underperforming) instead of the one underneath it. Kwik's rule: spend the bulk of your time understanding what's actually broken before anyone reaches for a fix. AI is exceptionally good at answering the wrong question with total confidence. Imagine your own solution before you borrow one. Draft the cabinet's own answer first, even a rough one, before any tool sees the problem. This is the step almost every cabinet skips under deadline pressure, and it's the one that actually builds Team Intelligence. Skip it enough times, and the room stops being able to do it at all. Leverage the tool to stress-test, not to think for you. This is the one step where you deliberately fire the ghostwriter. Kwik's own practice: ask AI to argue against what the room already believes, to name the room's blind spots, to poke holes. Not "write our plan." "Tell us what's wrong with our plan." Different question, completely different outcome, and the only one of the five steps where you want the tool talking back instead of taking dictation. Decide, because the tool never has to live with it. AI has no stake in your decision. It doesn't sit in the parent meeting when the plan fails, or defend the budget line to the board. That accountability doesn't transfer, no matter how good the draft looks. Somebody in the room still has to own it. Five steps. None require new software. All five require your leaders to still be doing the thinking it's currently outsourcing, to the tool, or, just as often, to whichever one of you has quietly become the only person who does the real thinking before anyone else weighs in. (Kwik teaches this in far more depth than one newsletter can hold: his book Limitless and his Kwik Brain podcast go deep on the underlying discipline. No affiliation here, just work worth pointing you to.) THE CASE STUDY This is a composite, drawn from patterns across our work with 987 leadership teams , not one specific president's story. A university cabinet spent the spring drafting its first AI use policy the way most do: one dean built a draft using a chatbot over a weekend, and the cabinet spent forty minutes debating word choices in a document none of them had actually thought through together. The policy read confidently. Nobody in the room could say, if asked directly, what problem it was actually solving. Before the fall rollout, the cabinet ran Build Before You Borrow on that same policy, live, in one meeting. Brainstormed first, out loud, no laptops. Named the real problem: not "we need an AI policy" but "we don't yet agree on what we're willing to let a machine say on our behalf." Drafted their own answer as a room, in plain language, before any tool touched it. Only then brought a draft to AI, and only to argue against it. The resulting policy was four sentences shorter than the first one and, according to the cabinet, the first draft everyone in the room could actually explain from memory without looking at it. Same five people. One real conversation, finally had before the tool had it for them. THE FIRST MEETING You don't need a retreat for this. You need one meeting, early in the semester, run differently than the ones you've been running. Name the sentence (20 minutes). Ask your cabinet directly: what's something this institution believes about itself that nobody's tested in years? Write every answer down without editing them. You're not solving anything yet. You're finding out what you've all been quietly agreeing not to say. Run one live decision through Build Before You Borrow, out loud, before anyone opens a laptop (30 minutes). Pick a real one: the fall enrollment message, the AI policy itself, whatever's actually on this week's agenda. Brainstorm together first. Name the real problem. Draft your own answer as a room. Only then bring in a tool, and only to argue against what you just built. Agree, as a cabinet, on one rule for how AI gets used this year (10 minutes). Not a policy document. One sentence everyone says out loud and means: something like "nothing this tool wrote goes out first without a human draft underneath it." Whatever you land on, make it specific enough that you'd notice the day you broke it. If your first objection is that you don't have sixty extra minutes this month, you're already spending more than that reworking decisions that got made too fast, by whoever talked first in the room. This isn't additional time. It's the same time, spent before the mistake instead of after it. If your second objection is that your team will treat this as one more initiative, they're already operating under an initiative. It's just an unspoken one, and it's been running since before you took the job. THE MATURITY SHIFT Immature leaders think: "We need to move fast before we fall behind on AI." Mature leaders think: "We need to know what we actually believe before we teach a machine to say it for us." Immature leaders let the tool draft first and edit for tone. Mature leaders draft the room's own answer first and let the tool argue with it. Kwik calls the difference between these two postures victim mindset and heroic mindset: whether you let your hardest chapter keep narrating you, or you use it as fuel. It's a private decision about your own institution's story, one nobody else can make for you, and this fall, a machine is about to say that decision out loud, on schedule, to everyone. YOUR TURN Your cabinet is about to find out, in public, at scale, which story it's been running. No scandal required. A machine is about to say it back to everyone, fluently, on schedule, forever. Name it. What's the sentence your cabinet has been running that nobody's tested? Where did it come from, and is it even still true? You don't have to post the answer. But if you're willing to, I'd genuinely like to know what you find. If you already suspect which sentence it is, and you're wondering whether it's about to get amplified before you've even chosen a vendor: that's precisely what the TEAM INTELLIGENCE Assessment is built to surface. Fifteen minutes, no pitch, just a clear read on what your cabinet is actually working with before you put a machine in the room as your ghostwriter. higherperformancegroup.com/team-intelligence-assessment Across the 987 leadership teams we've studied, the cabinets that did this work before scaling anything (a new initiative, a new tool, a new plan) outperformed the ones that scaled first and diagnosed later, by a wide enough margin that "later" stopped being a viable strategy. The point is simple: make sure what gets sped up is actually worth repeating. If this is useful for someone else's first fall cabinet meeting, send it their way before their board asks the same question yours did. Tell them which sentence you found. Somebody in your network is about to let a machine ghostwrite a story they've never actually tested, and this might be the newsletter that stops them in time. Follow DR. JOE HILL and Higher Performance Group . — Dr. Joe Hill, Higher Performance Group | THE TEAM INSTITUTE
Show More