Charter school leadership case study
The wildfire was exceptional. The pattern underneath it was not.
A real account from inside a public charter organization about what happens when unspoken expectations around responsibility, authority, family and support become operational problems.
Written for Chiefs of Schools and charter-network leaders dealing with recurring conflict, parent escalations, staff friction, and problems that return with different people.
7 pages · ≈8-minute read · Includes the 10-minute Cultural Tension Read
Cover of the released edition.
Two pages from inside it
Page 2 · What pressure exposed
Page 6 · The Cultural Tension Read
Four things a network leader can use
The situation
How a catastrophic disruption exposed expectations that had been operating quietly underneath the organization.
What Andre actually owned
A clear responsibility map separating direct site-level leadership from shared organizational authority.
What the recovery required
The operational decisions, communication changes and leadership tradeoffs the team had to keep making.
The field diagnostic
Page 6 · 10 minutes · Use it with your own network
A 10-minute Cultural Tension Read a Chief of Schools can use to identify recurring patterns inside their own network. Six prompts, each with what is said above the line and what is usually operating beneath it.
This is the page most leaders come back to.
You do not need a crisis for this to apply. You need a repeat.
- The same conflict keeps returning with different people.
- Parent and teacher disputes repeatedly reach central office.
- Principals are carrying relationship problems that rarely appear in formal reports.
- Different campuses mean different things by “professionalism,” “respect,” or family partnership.
- Staff turnover is happening without a satisfying explanation.
- Professional development makes sense in the room but changes little in the building.
None of these are unusual. The case study is about what produces them.
Five fields, then the document
No phone number, no organization size, no message field. We ask enough to know who is reading it.
Forward it freely once you have it.