05: The Hidden Systems You're Already Using (Without Realizing It)
Stop building new systems. Find the ones you already have.
📺 Prefer video?
Watch the 3.5-minute version, or keep reading
Where We Are
Last week, we looked at assigning ownership to keep systems from drifting back.
This week is about what’s hiding in plain sight. Because even if you think you don’t have many systems… you do.
Listen to your team for a minute:
“We always announce early dismissals via email the morning of.”
“Every February, department heads submit budget requests.”
“When a new teacher starts, they shadow someone for two days.”
Those aren’t random actions. They’re systems. Just invisible ones: undocumented, unowned, and unmaintained.
Today, I’m showing you how to see what’s already working, and why making it explicit is often more powerful than building something new.
The Problem
When systems are invisible, they drift without anyone noticing.
Nobody owns “we always announce early dismissals via email” because it was never formally established. So when someone starts announcing via text, someone else via website, and someone else via app, the system fragments.
Nobody catches it because there was no system to maintain.
And they disappear when people leave.
The office manager who handles enrollment knows every step. But it’s all in her head. When she leaves, the system leaves with her.
The Power of Making Systems Visible
Here’s the counterintuitive insight: You don’t always need to build new systems. Sometimes you just need to name what’s already working.
When you make an implicit system explicit:
You can improve it (once named, it’s evaluable)
You can transfer it (documentation survives turnover)
You can maintain it (assign ownership, prevent drift)
The shift: From “that’s just how we do things” to “this is our system, and here’s who owns it.”
How to Spot Your Invisible Systems
Step 1: Listen for “We Always” Language
Over the next week, pay attention to recurring patterns.
Any sentence starting with:
“We always...”
“Every [timeframe] we...”
“When [X] happens, we...”
That’s an invisible system announcing itself.
Write these down. You’re building an inventory of what already exists.
Step 2: Map One Pattern
Pick one recurring pattern. Document it.
Answer these questions:
System Name: [What we call this]
What triggers it: [When does this happen?]
Who’s involved: [People or departments]
Current process: [Step by step]
How we know it worked: [Outcome]
Who maintains this: [Even if informally]
Step 3: Decide the System’s Fate
Option A: Formalize it
If it’s working, make it official. Document the workflow. Assign clear ownership. Add it to your Operational Calendar so it doesn’t disappear when someone leaves.
For example: Your athletics director sends tournament travel updates via a WhatsApp group. It works. Parents get info fast. No complaints. Make it the official protocol: who updates it, when, what format.
Option B: Fix it
If it exists but doesn’t work well, now you can improve it systematically.
For example: Your Friday newsletter goes out at 4 PM, and open rates are dismal. Now that it’s visible as a system, you can test sending it Thursday at 8 AM instead, track engagement, and assign someone to monitor what’s actually working.
Option C: Kill it
Sometimes visibility reveals that a system shouldn’t exist at all.
“We always send paper flyers home in backpacks” might serve very few, for the environmental cost it brings. The system exists only because “we always did it.”
Make it visible. Evaluate it. Kill it if it’s not serving anyone.
➡️ Start Here ⬇️
I’ve created an Invisible Systems Mapper (powered by AI) to make this process easier. It walks you through identifying your informal systems, surfaces what’s working and what’s broken, and helps you decide which ones to formalize, fix, or kill. Start by filling in your “we always” patterns and download a .txt file to share with your team.
Real Example: The Invisible Student Events System
A high school administrator told me they “don’t have a clear way to inform students about events.”
But when I listened, I heard:
“Student council always posts on Instagram”
“Advisors always announce it in morning meetings”
“The activities coordinator always sends emails through the LMS”
“Digital signage always shows the weekly calendar”
They had a system. Just not an explicit one, and students didn’t know which channel to trust.
We documented it:
System Name: Student Event Communication Protocol
Process:
Activities coordinator updates master calendar
Student council posts to Instagram
Advisors announce in morning meetings
LMS message goes out
Digital signage updates
Problem identified: Six different channels with no coordination. Students don’t know which to trust. Timing varies. Information conflicts.
The fix: We created an ongoing slide deck where students and advisors could drop announcements for the student body. All other channels pointed to it: “Check the [school mascot] Diaries.”
Owner: Activities Coordinator (newly formalized)
Responsibilities:
Maintain master slide deck
Coordinate all channels to point to single source
Track which events have low attendance
Monthly check-in with student focus group
Result: Student attendance at optional events increased 23%, and email overload decreased considerably. The invisible system became reliable.
Your Move This Week
Step 1: Identify one “we always” pattern
Listen for recurring language. Write down one pattern.
Step 2: Map it (15 minutes)
Use the template. Document what actually happens.
Step 3: Decide its fate
Formalize it? → Create Ownership Charter
Fix it? → Identify what’s broken, assign someone to improve
Kill it? → Stop doing something that serves no one
What This Unlocks
When you start seeing invisible systems:
You gain clarity about what’s actually happening (not what you think happens)
You can improve existing patterns instead of always building new ones
You capture institutional knowledge before people leave
Ownership feels natural because you’re formalizing what people already do
This isn’t about adding more systems. It’s about seeing the systems you already have and making them work better.
The most powerful systems aren’t always the new ones you design. Sometimes they’re the invisible ones you finally name.
Your Experience
What “we always” patterns are hiding in your school? Hit reply and tell me. I’m always collecting invisible systems that became visible.
Systematically yours,
About the Author:
G (short for Gitane) is co-founder and Chief Creative Officer at EKG Collective, helping international schools turn communication complexity into systematic clarity. Learn more at ekgcollective.com.
I totally agree— the invisible systems take up people’s bandwidth to remember and disseminate to new folks… documenting it all can add clarity. Thanks for this!