A Decision Is Not a System
Schools make decisions quickly because problems demand answers.
New policy.
New program.
New procedure.
Problem solved.
Except sometimes:
The decision gets made before the system has been designed.
Who owns it?
How does it work?
How will people know?
What tools are needed?
How will we measure whether it worked?
A decision is not a system.
Before making your next organizational decision, ask:
“What would have to be true for this to work consistently?”
Then design backward from there.
Run one upcoming decision through the High-Performing Systems Cycle:
Learn → Assess → Prioritize → Design → Act → Reflect.
When “Fine” Becomes the Ceiling
Most leaders will address something that is clearly failing.
The harder challenge?
Something that is fine.
Enrollment is fine.
Culture is fine.
Results are fine.
Leadership is fine.
And “fine” becomes the standard.
The greatest threat to Peak Performance may not be unacceptable performance. It may be acceptable performance.
So today, don’t ask:
“What’s broken?”
Ask:
“Where have we accepted acceptable?”
Your next Strategic Gap may be hiding inside something everyone has learned to tolerate.
Identify one area where acceptable performance is preventing desired performance.
The Question Every Leader Should Ask First
Here’s a five-word leadership tool:
“What have you considered so far?”
Someone brings you a problem?
Ask it.
Someone wants your decision?
Ask it.
Someone says, “What should I do?”
Ask it.
You’ll discover what they know, how they think, where they’re stuck—and whether they actually need you.
Every unnecessary answer can create more dependency.
Every good question can build more capacity.
Advice comes later. Thinking comes first.
Use the question three times today before giving advice.
Are Your People Improvising What Systems Should Define?
Every day, people in your school make hundreds of decisions.
The question is:
How many are they being forced to invent from scratch?
Strong systems don’t remove judgment.
They provide enough clarity that people know the standard, the process, and the boundaries.
Strong systems answer questions before people are forced to improvise the answers.
That’s one reason we built the High-Performing School Systems Library™—150+ systems, strategies, assessments, tools and implementation resources across the 12 Core Systems.
Don’t start from scratch every time.
Find the system. Use the framework. Move forward.
Get lifetime access to the HPS Library for $97.
Are You Learning From Your Failures?
Something didn’t work.
Our instinct is often to fix it quickly and move on.
But failure contains data.
Don’t hide the failed attempt. Harvest the lesson.
Ask:
What did we expect?
What actually happened?
What did we learn?
What should change next time?
Failure without reflection becomes frustration.
Failure with reflection becomes experience.
And experience intentionally captured becomes organizational knowledge.
Don’t waste a good failure.
Debrief one recent miss with your team—without blame.
Your Leadership Should Multiply, Not Create Dependence
Sometimes leaders hesitate to release responsibility because they care deeply about the organization.
I understand that.
But developing others doesn’t diminish your leadership.
It multiplies it.
The goal isn’t to make you less important.
It’s to make your organization more capable.
Imagine your team thinking, deciding, solving, and executing at a higher level—even when you aren’t there.
That’s not losing control.
That’s building capacity.
Today ask:
What am I still holding that someone else could be learning to own?
Release one responsibility with clear guardrails.
The Problem Behind the Problem
Enrollment falls.
Revenue tightens.
Programs get cut.
Staff morale drops.
Families become concerned.
Enrollment falls further.
School problems rarely exist in isolation.
The problem you see may not be the problem you need to solve.
That’s why one of the most important disciplines in systems leadership is learning to ask:
“What is this connected to?”
Before attacking the symptom, trace the connections.
Because isolated solutions often fail when the underlying systems remain unchanged.
Take one current problem and trace what happens immediately before and after it.
Are You Solving Problems or Building Problem-Solvers?
Someone walks into your office with a problem.
You know the answer.
Giving it takes 30 seconds.
Coaching them might take five minutes.
What do most of us do?
We answer.
And then wonder why they return with the next problem.
Don’t just solve the problem. Develop the person solving it.
Try this instead:
“What have you considered so far?”
Then listen.
You may spend five minutes today.
But you’re building someone who needs fewer answers from you tomorrow.
Coach one problem instead of solving it today.
The Hidden Cost of Organizational Ambiguity
Many organizational problems aren’t caused by bad people.
They’re caused by ambiguity.
Who owns this?
What happens next?
Who makes the decision?
That ambiguity creates delay, duplication, frustration—and eventually everything gets escalated.
Strong systems create clarity:
Know what to do.
Know who owns it.
Know what happens next.
Pick one recurring process today and ask your team those three questions.
If the answers differ, you’ve found a Strategic Gap.
Clarity creates confidence. Confidence creates action.
Use the HPS Library to find the framework behind the process you need to strengthen.
Don’t Let Experience Become an Assumption
Experience is one of leadership’s greatest assets.
But there’s a trap.
We can start believing:
“I’ve seen this before.”
Maybe.
But your people changed.
The environment changed.
The problem changed.
Relying only on your experience is trying to do today’s job with yesterday’s tools.
Experience should inform your thinking—not end it.
Today ask:
What am I assuming I already know?
Then get curious again.
The strongest leaders I know remain students long after they become experts.
  Challenge one assumption today.
