I’m currently mid-digital detox! As I mentioned in my last piece, when our brains are at capacity, we tend to grab for quick fixes, those “band-aid” solutions that treat a symptom but leave the system messy.

If I’m being honest, my “always-on” lifestyle was a symptom I’d been treating with a bit too much caffeine and a stubborn refusal to put my phone down. To honor the Shokunin spirit of doing things properly, I’ve decided to go cold turkey on the pings and pokes for a few days to look at my own “architecture.” After all, if this newsletter didn’t show up while I was busy staring at trees, I wouldn't be delivering on my promise that a good system should work even when its human isn't there. 😎

While I’m out, I’m resurfacing a piece I wrote for The Fix about the most important architecture in your school: your internal communication. This piece is a guide to “lifting the lid” on how your team actually talks to each other, and why auditing that flow is the ultimate act of discipline for any school leader.

I’m off to find some quiet and, hopefully, some better questions to bring back to you next week. Enjoy the read!

— G

The Invisible Glue: Why Your School Needs an Internal Comms Audit

Originally published in The Fix, February 2026. Lightly edited for practice by design.

We spend weeks perfecting the prospectus. We obsess over open day speeches. We A/B test the admissions landing page.

But how much time do we spend analyzing how we speak to each other?

In most schools, internal communications run on autopilot. A legacy mix of Friday emails, briefing notes, WhatsApp groups, corridor conversations, and the occasional all-staff meeting. It works. Sort of.

Until it doesn’t.

If you’re noticing signs of “information fatigue” among staff, or if key messages keep getting lost in the noise, it’s time for an Internal Communications Audit.

Here’s why lifting the lid on your internal comms could be the most valuable thing you do this term.

1. You can’t fix what you can’t see

Most school leaders believe they communicate effectively because they consistently send information out.

That’s a deceptive metric.

Communication isn’t measured by what’s sent. It’s measured by what’s received.

An audit shifts you from assumptions (”It’s in the Friday bulletin, everybody’s seen it.”) to concrete data. It maps the reality of information flow, not the idealized version. You might uncover that your support staff feel completely disconnected from the school’s vision, or that your Heads of Department are drowning in emails that could have been resolved in a five-minute meeting.

2. The problem with marking your own homework

Auditing your own communications is technically possible. Practically, it’s nearly impossible to see the water you’re swimming in.

Internal teams suffer from the Curse of Knowledge. You know what you meant to say, so you assume everyone else understood it. And staff are rarely 100% honest with leadership about communication failures because nobody wants to seem critical or difficult.

A true audit requires psychological safety. Think of it this way: you need a neutral outsider to hold up a mirror so your team can be completely frank. They need to feel totally safe saying, “Honestly, that Monday meeting is the worst,” without worrying about ticking off the person who runs it. You rarely get that level of unfiltered truth without bringing in an external partner to help break the ice.

3. Taming the channel complexity

Schools are notorious for “channel creep.”

Email for formal announcements. WhatsApp for the sports department. The calendar lives on the portal. Urgent notices go on the staff room whiteboard. Oh, and someone started a Slack workspace that half the team joined.

When there are too many channels, staff don’t know where to look. So they stop looking altogether.

An audit lets you inventory every platform currently in use and identify where the friction lives. It gives you the evidence you need to say, “We’re retiring these three platforms and focusing on these two.” It’s a call driven by data, not by feeling bad about getting rid of something.

4. Boosting staff morale and retention

There’s a direct line between communication and culture.

Poor communication is a root cause of staff feeling disrespected, burned out, and undervalued. Staff feel disrespected when they hear about big decisions from parents instead of directly from management. Burnout happens when we expect staff to read and act on emails sent at 9 PM by 8 AM the next morning. And when staff are kept “out of the loop,” they naturally start to feel less valued.

An audit (specifically the listening part, with surveys, focus groups, and one-on-one interviews) is therapeutic. It shows staff that you care about their working experience, not just their productivity. By identifying pain points, you can make operational tweaks that have genuine impact on wellbeing.

5. Aligning the internal with the external

Your staff are your biggest brand ambassadors.

When your internal communications are rigid and isolated, contradicting your external promise of a “collaborative, forward-thinking environment,” you face a major issue. That gap isn’t strategic brand positioning. It’s deceptive brand fiction.

An audit ensures that the voice you use internally matches the brand you sell externally. If your staff don’t buy into the school’s vision, they certainly can’t sell it to parents.

Try this: the channel inventory exercise

Before committing to a full audit, run this 30-minute diagnostic with your leadership team.

Step 1: List every communication channel currently in use. Email, Learning Management System, Student Information System, WhatsApp, bulletin boards, portals, newsletters, shared drives, printed memos, verbal announcements. All of it.

Step 2: For each channel, answer four questions.

• Who owns it?

• What type of information goes here?

• How urgent is the content?

• Who’s expected to check it, and how often?

Step 3: Identify the gaps.

• Are there channels with unclear ownership?

• Are urgent messages competing with routine updates?

• Do staff know where to look for what they need?

If you discover more than five active channels, or if anyone says “I’m not sure who manages that,” you’ve found your starting point.

This week’s move

If a full audit isn’t in the cards right now, start with the 30-minute diagnostic above. One conversation with your leadership team, a whiteboard, and a list. Version 1.0 is better than a perfect plan you never execute.

Next up: Back to regularly scheduled programming next week. Internal comms will be weaving through the next few issues, so consider this the warm-up.

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.

This piece was originally published in The Fix. Follow them for sharp, practical HR and operations thinking built for international schools. It's one of the few newsletters in this space that actually respects your time.

Where We Are

I want to start by acknowledging the weight you’re carrying right now. End of April, in a school building, is a high-altitude climb. Between budget finalizations, recruitment cycles, and the sheer emotional velocity of the “end-of-year” rush, the air feels a little thin.

That’s exactly why we tend to grab for quick fixes. When our cognitive load is maxed out, the long-term discipline of building a design practice can feel like an impossible luxury. We aren’t always looking for a transformation. Often, we are just looking for relief.

Over time, I have seen this play out in a few different ways, but perhaps the most costly one is the one I’ll share with you today.

A school I was working with signed a contract for a platform meant to solve a single nagging symptom: login friction. They wanted students to have single sign-on access to every app on their iPads. The vendor was credible. The price was reasonable. The logic was “common sense.”

But halfway through pre-launch, the team paused. The platform did exactly what it promised, but it didn’t answer the questions nobody had bothered to ask.

The tool worked. The implementation was flawless. The system remained broken because the questions were skipped.

The Pattern We Don't See

With the very best intentions, we jump from a perceived problem to a shiny solution without ever pausing on the architecture that connects them.

Someone names a frustration. Someone else names a tool. We agree. We sign. We launch.

Then, six months later, we are genuinely surprised when the solution creates its own category of complexity.

The problem isn’t the tool. It’s that we never defined what success actually looked like.

Product designer wrote a piece a while back that names this exactly.

He argues that a designer is only as good as the quality of their questions.

Tools change. Methodologies drift. What separates a junior designer from a senior one isn’t software fluency. It’s the quality of what they ask before they ever touch the drawing board.

Schools are no different.

Three Questions (Before You Sign)

You don’t need a 50-page audit. You need three questions, asked with disciplined silence, before any decision about a system, a platform, or a piece of communication:

1. Whose problem is this, exactly?

Not “the school’s.” Not “the community’s.” Name a specific person in a specific moment. If you can’t visualize the human who is suffering, you don’t have a problem yet, you have a feeling.

2. Are we fixing the system or the symptom?

“Students forget passwords” is a symptom. “Our digital environment is a fragmented maze of disconnected identities” is a system. Tools fix symptoms. Design fixes systems.

3. How will we know it worked?

Pick your signal in advance. If you can't say what would tell you the spend was worth it six months from now, you also can't say what would tell you it wasn't.

This Week’s Move

Trace a Decision

Pick one decision your school made in the last twelve months: a new software, a new duty roster, or a new newsletter format.

Apply the three questions retroactively:

1. Whose problem was it, specifically?

2. What were we actually trying to fix? (System vs. Symptom)

3. How do we know it worked?

If the answers feel hazy, don’t panic. You don’t have to redo the decision. You just have to notice the gap.

The work is about catching the moment a question gets skipped and learning to pause for ten minutes when it matters most.

Your Experience

What’s a decision your school made that you wish someone had asked a question about first? Hit reply and tell me. I read every one, and your stories help us design better frameworks for everyone.

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.

Where We Are

I just spent the last Sunday afternoon back in the EdTech trenches, running an experience mapping workshop for a group of school technologists.

As we were mapping out the "Monday Morning Reality," that messy, high-friction moment where a teacher is trying to take attendance while the WiFi drops and a student is having a meltdown, I was reminded of an insightful podcast episode I listened to a while back featuring the Spain-born, Japan-based illustrator .

Mendo tells a story about a man in a Japanese bookshop who took several minutes to wrap a gift with excruciating, meditative slowness. When Mendo tried to hurry him, the man looked up and asked,

Do you want it gift-wrapped or not?

In Japan, this is the shokunin spirit: the artisan’s commitment to doing a thing properly, all the way, with no shortcuts.

As school leaders, we are excellent at handling the gift itself: the multi-million dollar curricula, the strategic plans, the recruitment of top talent. But the conversation with colleagues yesterday confirmed a strategic blind spot: We are often delivering a beautiful gift in a torn, messy wrapper.

The Wrapper is the Experience

In school operations, the “wrapping” is your information architecture.

It’s the way-finding in our portals.

It’s the plain language in our policies.

It’s the “front door” you build for every process.

If a teacher has to click 8 times to request a stapler, or a parent can’t figure out who to email about a bullying concern, the “wrapper” is broken. And when the wrapping is difficult to open, people eventually stop wanting the gift.

Luis Mendo noted that “frictionless life is too cold.” And it’s true that, in design, friction can lead to serendipity.

But in schools, unintended friction is a tax on the soul. It is the opposite of the shokunin spirit. Without that intentionality, we tell our community their time doesn't quite matter.

Strategizing Retention through the Micro

We often think of retention as a “Macro” problem solved by salary increases or expensive campus upgrades. But true retention, for both families and staff, is won or lost in these microscopic moments of intentional “wrapping.”

1. For Families: The Wrapper is Trust

Trust is a series of microscopic interactions. When a parent raises a concern and enters a “Black Box” of silence for four days, they don’t think you’re “busy.” They think you don’t care.

• The Shokunin Move: Closing that visibility gap with a "Friday Pulse" update is the act of gift-wrapping a difficult moment. It tells the parent: I am holding this situation with care, even if it isn't resolved yet. This is the black box problem I wrote about earlier, pulled open just enough to let a little light in.

2. For Staff: The Wrapper is Cognitive Peace

Burnout rarely comes from the big projects. It comes from the triage tax, the low-grade cognitive load of navigating broken pathways, which I've written about before.

• The Shokunin Move: When you apply an artisan's mindset to a procurement form, making it intuitive and "low-floor," you aren't just being efficient. You are gift-wrapping their day. You are giving that teacher back the cognitive capacity they need for their students. This is pathmaps thinking applied to something as mundane as buying a stapler.

Share

Simplicity is a Leadership Service

True craftsmanship in leadership means interrogating design instead of blaming people. When we ignore the micro, we force our people to exercise “The Silent Veto.” They smile in the meeting and then quietly return to whatever worked for them previously, because change fatigue is real and our systems are too exhausting to navigate.

The man in the bookshop knew that the experience of the gift began with the first fold of the paper.

Our job is to see the “spaghetti paths” we’ve created and be brave enough to straighten them. We must ask: Who is gift-wrapping the moments at our school?

This Week’s Move

The Shokunin Micro-Audit

Pick one tiny, routine interaction in your school this week. Maybe it’s how a teacher reports a broken lightbulb or how a new family finds the bus schedule.

1. Walk the Path: Actually do the task yourself.

2. Check the Wrapper: How many clicks? How much jargon? Where does the “Status Bar” disappear?

3. Refold the Paper: Can you remove one unnecessary step? Can you clarify one sentence? Can you make the “front door” more obvious?

Small details aren’t “extra” work. They are the work that makes the gift of education possible to receive.

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.

Where We Are

Every August, a new teacher lands at your school. Maybe they flew in from Amman. Maybe they drove across town. Either way, they’re standing in a hallway they don’t recognize, holding a laptop they haven’t set up, about to walk into a role that someone else shaped for years.

Everything they need to know—the culture, the quirks, the unwritten rules, the reason the schedule changes in February—lived inside the person who just left, taking, perhaps, more institutional memory than any digital archive or physical handbook could ever hope to capture.

The new teacher will spend the next three to six months rebuilding what already existed. That’s not a learning curve, but an institutional reset. And it happens at every international school, every single year.

That’s a systems problem.

Over the past three weeks, the Leaving Well series has explored the Experience Asymmetry (Post 19), the Knowledge Harvest (Post 20), and Designing Better School Departures (Post 21). But there’s one more piece—arguably the most important one—that ties everything together.

The departure isn’t the end of the story. It’s the beginning of someone else’s.

This week, I’m writing with , co-founder of SkoolSpot. Ash and I kept arriving at the same conclusion from opposite directions: I see departure design through the lens of communication systems and human experience; Ash sees it through the lens of HR operations and institutional data. The insight we kept circling is identical: offboarding and onboarding aren’t two separate processes. They’re one loop.

And for many schools, the bridge between them hasn’t quite been built yet.

Here's our attempt to build that bridge. Grab a beverage and settle in. ☕️

Two Lenses, One Loop

Picture a relay race where the first runner drops the baton, walks off the track, and the second runner has to go find it in the grass somewhere. That’s the current state of staff transitions at most schools.

Whether these tasks sit within a dedicated HR office or on the desk of a Senior Admin wearing multiple hats, the exit workflow and the onboarding workflow almost never talk to each other.

The exit interview asks: “What is the one thing we could have done better to support you during your time here?” The onboarding survey asks: “How was your first month?” But nobody connects the answers. Nobody asks: “What did the last person say was broken, and did we fix it before the new person arrived?”

That gap — between what one person reports on the way out and what the next person experiences on the way in — isn’t occasional. It’s systemic.

Across schools, we consistently see the same pattern: feedback is collected on departure and experience is measured on arrival. But without a system to close the loop, one doesn’t inform the other. We’re listening, but we’re not hearing.

An example we often see sits across two functions that rarely operate as one system: HR and Academic Leadership.

A departing teacher shares in their exit interview that:

It wasn’t clear when things were due, I was hearing different expectations from different people, and I ended up spending a lot of time just trying to piece it together.

HR captures that feedback as part of the exit process.

At the same time, Academic Leadership focuses on hiring the replacement and preparing orientation materials.

Each function does its job. But they are operating in isolation, not in connection.

Three months later, the incoming teacher reports:

I keep getting mixed messages about deadlines and expectations, and I have to ask a lot of questions to figure out what direction to follow.

From each department’s perspective, nothing failed.
From a systems perspective, nothing improved.

The issue was already known. It just wasn’t made visible to the people shaping the next experience.

It is worth noting the additional layer that can make this harder to resolve in international schools.

People as Systems: When Expertise Walks Out the Door

As we mapped out the connection between our two perspectives, we kept coming back to one central realization: When knowledge isn’t codified, the person is the system. When they leave, the system breaks.

In part 2 of the Leaving Well series, we looked at the Knowledge Harvest—the three layers of institutional knowledge (process, relationship, context) and how to capture them.

But our shared framing cuts even deeper.

The secondary principal who carries the logic of the entire master schedule in their head. The admissions director who knows every family by name. The IT manager who is the only person who understands the legacy systems.

In systems thinking, you’d call this a single point of failure. In schools, we call it Tuesday.

The fix isn’t to make people less important. It’s to make their knowledge less fragile. We need processes that systematically convert individual expertise into institutional assets before the person walks out the door—and onboarding processes that deliver those assets to the next person in a way they can actually use.

The Heroics Trap: Why Schools Run on Informal Labor

In most schools, transitions work because someone steps in.

A middle leader notices a new hire is struggling and steps in to help. Before long, they become the informal point of contact for the entire team.

A longer-term staff member once showed a few new hires around the neighborhood. Now they are the unofficial guide for every incoming cohort.

A principal suggests, “Talk to Ayesha, she knows how HR processes work.” Within weeks, Ayesha has a calendar full of one-on-one meetings because there is no shared place where that knowledge lives - and no formal role that owns it.

None of these roles were designed.

But each of them fills a gap. And crucially, each of them fills a gap that exists because accountability was never clearly assigned in the first place. Ayesha didn’t become the informal HR guide because she was appointed. She became it because no one was. The responsibility didn’t move to her deliberately. It drifted there quietly, because the system never defined where it belonged.

This is what we call the Heroics Trap.

The system appears to function, but only because individuals are compensating for a system that was never fully designed.

In many schools, this is framed as a preference for being “less bureaucratic”, “more organic”, and sometimes suggesting that their staff “prefer flexibility over structure”. But in practice, it often means the structure was never defined, and accountability shifts quietly onto individuals to figure things out.

What looks like flexibility is often just a lack of clarity. And that lack of clarity doesn’t disappear. It gets absorbed by people.

People don’t resist clarity. They resist confusion.

Without that clarity, individuals are left to interpret expectations on their own. Responsibilities accumulate informally. Job descriptions drift from reality. What someone actually owns becomes a matter of habit and assumption rather than explicit agreement. And that is where inconsistency, frustration, and unnecessary tension begin.

People don’t disengage because expectations are high. They disengage when expectations are unclear.

The problem is that heroics don’t scale.

They create inconsistency, because the experience depends on who happens to be around. They create burnout, because the same reliable people carry the load again and again. And they create fragility, because when those people leave, the system they were holding together leaves with them.

When a school hires someone, it makes a promise of clarity and support. When the lived experience is confusion and informal workarounds, that promise breaks, and dissonance becomes disengagement. Not because people don’t care. Because the system doesn’t match the promise.

The alternative isn’t to remove the human element. It’s to support it.

When systems are in place, people still care. They still step in. But they are no longer compensating for gaps. They are building on a foundation.

Less heroics. Better outcomes.

From Compliance to Contribution: Closing the Loop

In the first part of this series, G introduced the shift from a Compliance Mindset (”did they return the keys?”) to a Contribution Mindset that honors a person’s legacy. When we look at staff transitions through this lens, we see a loop that moves through four phases. It begins with the logistical baseline of Compliance, but then deepens into the Capture of knowledge and the active Contribution to the role’s future.

The final, and most vital, stage is Connection.

This is where the loop actually closes: when the outputs of the departure (the video time capsules, relationship maps, and role histories) become the primary inputs for the new hire’s arrival.

When this connection is working, the departing staff member isn’t just leaving; they are actively setting their successor up for success.

But the feedback loop sits on top of something more fundamental. And if that foundation is missing, the loop has nothing solid to close around.

Role clarity is itself a system.

Not a bureaucratic exercise, and not a one-time HR task. A living structure that makes visible what each person owns, what they are accountable for, and where their responsibilities end and someone else’s begin. Without it, everything built on top — the processes, the handoffs, the data flows — rests on assumption rather than agreement.

Which returns us, quickly, to heroics.

A platform like SkoolSpot can make the feedback loop possible. Exit data can be structured and made accessible. Onboarding can be designed with that input in mind. The conditions for the loop to close can exist.

But if the underlying roles are unclear, the data reflects that ambiguity. Departure feedback describes an experience shaped by blurry expectations. Onboarding materials prepare someone for a role that doesn’t match what they will actually be asked to do. The loop closes — but it loops around the same confusion.

The system has to be designed at every layer.

Brand Stewardship: Your Alumni Are Your Recruiters

Your departing staff are your most credible marketing channel. In the tight-knit world of international education, the question travels fast: “How was it there?” The answer isn’t shaped by the branded tote bag they got at orientation. It’s shaped by the last month. A teacher whose knowledge was honored becomes an ambassador. A teacher who felt like a line item on a checklist tells a different story.

Breaking the Silos

Someone needs to own the continuity.

Not all the tasks—just the connection. This requires a person or a team who sees the full arc of the staff journey. Someone who can ask:

What did the last three people in this role say was the biggest challenge, and have we addressed it in the onboarding for the next person?

The Departure Loop: A Timeline

• November-March (The Announcement): Launch the Departure Experience Audit. This is the moment to move beyond simple logistics and begin mapping the institutional legacy that needs to be preserved.

• April (The Harvest): Activate the Knowledge Harvest. This is when the “hidden” logic of the role is codified through video time capsules and stakeholder maps while the expert is still on the ground.

• May-June (The Sunset): Design the Sunset. Execute closing rituals and student bridge communications, ensuring the departing staff member leaves with a sense of dignity and accomplishment.

• June/Orientation Planning (The Connection): Close the Loop. Leadership and receiving teams review departure intelligence to customize the onboarding plan, ensuring the next arrival is informed by specific context rather than generic templates.

• August (The Arrival): Complete the Loop. The new hire receives a curated set of transition assets built specifically for them, providing a clear path forward rather than a “cold start” or a link to a cluttered shared drive.

  Share

This Week’s Move

Pull together your school’s exit checklist and your onboarding checklist. Put them side by side. Draw a line between every item on the exit list that should inform something on the onboarding list.

How many lines did you draw? If the answer is zero, you’ve found the break in your loop.

Pick one connection. Maybe it’s routing the Knowledge Harvest assets to the incoming person’s welcome package. The loop doesn’t close overnight, but it starts closing the moment you decide departure and arrival are two chapters of the same story.

Systematically yours,

G and Ash

About the Authors:

(a.k.a. “G”) is co-founder and Chief Creative Officer at EKG Collective, helping international schools turn communication complexity into systematic clarity.

is co-founder and CEO of SkoolSpot, a platform designed to help international schools manage people operations with "Less Heroics."

Where We Are

Maddie was eighteen when she finally named the ghost in the room. In an interview with researcher Tanya Crossman, she said:

I lived with a mentality that “everyone leaves.” I just recently moved off to college and I had a really close friend get mad at me for pushing her away... Honestly, I still expect us to eventually lose touch anyway because people move on. That’s all I’ve ever known.

Crossman heard some variation of “everyone leaves” in scores of the 270 interviews for her book Misunderstood: The Impact of Growing Up Overseas in the 21st Century (2016).

Think about that as a design constraint. This goes beyond “sadness.” It is a worldview. It is a logic model for human connection baked in before adulthood: Attachment is just the first half of loss.

When we don’t design the departure experience, we aren’t just losing institutional knowledge. We are unintentionally mass-producing a generation of “Internal Leavers,” people who start exiting a relationship the moment they start it.

This isn’t a criticism of schools; it is a call for more deliberate design.

The Leavers: Grief Wearing a Hoodie

When a family leaves, they lose the “background noise” of their lives: the specific slant of 4 PM light in their kitchen, the shortcut through the park, and the barista who knows their order.

Adults often prioritize the logistics: the shipping container, the last phone bill, the “exciting move.” Children, however, live in ambiguous grief. Nothing is “wrong,” really. The family chose this, often after thoughtful discussions about the future. Yet a ten-year-old is still left with the feeling that their world has ended.

Usually, they put that feeling in a box labeled “Resilience.”

In the international school world, “They’re so resilient” is often a polite way of saying “I’m glad they aren’t making a scene.” But as Reddit’s TCK communities often point out, that “resilience” is often just emotional calcification.

Researchers call it “Expat Child Syndrome.” It looks like withdrawal or teenage moodiness. but in reality, it’s just grief wearing a hoodie.

The Stayers: The Perpetual Tour Guide

Here is the part that our schools unintentionally leave out: It is often harder to be the one left behind.

While we throw farewell parties for the families moving to London or Singapore, the children staying behind are treated as a non-issue. The common assumption is that they’ll simply make new friends and move on.

But in a school with 20% turnover, a “stayer” doesn’t just lose one friend. They lose their social infrastructure. Every June is a demolition; every August is a construction site.

On TCK forums, stayers often describe feeling like “perpetual tour guides.” They get tired of explaining the “inside jokes” to new arrivals. They get tired of being the only one who remembers the bench by the science building was “ours.”

This builds the “Everyone Leaves” armor. These kids learn to connect superficially because “going all-in” on a friendship feels like volunteering for heartbreak.

The Opportunity for Intentional Design

This emotional landscape isn’t anyone’s “fault,” but it is a gap that schools are uniquely positioned to fill.

When a family departs or a friend stays behind, parents often feel a lingering sense of isolation. They watch their children navigate these transitions and hope the institution that brought them together can help navigate the fallout.

Schools don’t need to take the blame for the nature of global mobility, but they can take the lead in being more deliberate. By treating transitions as a design challenge rather than a logistical one, we move from “handling” departures to honoring them.

Designing the Goodbye

If we treated departures with the same intentionality we bring to curriculum design, our approach would shift:

1. Naming the Loss: While well-intentioned, “happy talks” about exciting new chapters can feel like emotional gaslighting to a child who is hurting. Intentional design means using language that acknowledges that goodbyes are hard and significant.

2. Closure Rituals for Kids: Adults design goodbye events for adult comfort—speeches, gifts, and photos. Children need agency; in this case, the ability to influence how their own story ends at a school. Moves are almost always “done to” children, leaving them feeling like passive cargo. Shifting this power allows them to choose the scale and style of their goodbye, moving them from being spectators of a transition to the architects of it. This might look like “friendship time capsules” or collaborative projects that remain at the school after the student leaves, ensuring their presence is still felt.

3. The August/September “Stayer” Check-in: We can design specific touchpoints for the students who stay. A check-in during the first few weeks of school should focus on the “Swiss cheese” holes in their social circle, acknowledging that the start of school is a social transition even if they didn’t move.

4. The “Stay-in-Touch” Bridge: Left to chance, these friendships often evaporate. Schools can facilitate the handoff by normalizing the exchange of contact info and supporting alumni networks that have a more intentional focus on connection. And when that bridge-building is done well, it starts to look less like a school initiative and more like a philosophy. One organization has already mapped what that philosophy looks like.

The Alumni Manifesto

[YELLOW CAR]’s Alumni Manifesto offers a framework that treats alumni engagement as a direct continuation of the student experience.

Imagine handing a graduating student a “backpack” containing eight elements they can “play” in different combinations throughout their lives.

When we design for the long term, we offer our students:

• Belonging & Connection: A sense of home and a “red thread” that keeps them connected to their story.

• Guidance & Mentorship: Lifelong traveling companions who offer advice when they hit a fork in the road.

• Nostalgia & Celebration: Punctuation marks for their lives, remembering the milestones and the “good old days.”

• Generosity & Legacy: An open-handed way of living where they leave a mark for those who come after.

This framework transforms the school from a place they used to attend into a lifelong “home base.”

This Week’s Move

This is a great opportunity for some internal research. Start by identifying a “Long-Term Stayer”—a student who has watched multiple cohorts of friends depart. As keepers of your school’s memory, they offer unique insight into the emotional weight of social turnover. Then:

1. The One-Question Interview: Ask: “When your friends leave, what do you wish the school did?”

2. Active Listening: Avoid the urge to “fix” or explain. Document the raw feedback.

3. Agenda Item: Place this feedback at the top of the next Senior Leadership Team meeting to serve as the catalyst for a “Transitions-Care” protocol.

The children who stay can tell us exactly what is broken. We just need to be deliberate enough to ask.

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.

Where We Are

You arrive at your new school in August. You’re jet-lagged, overstimulated, and trying to remember which building has the staff room and which one has the copier that actually works.

You’ve stepped in to coordinate a department at a moment of significant change. Someone points you toward the “Handover Folder” your predecessor left behind. You open it.

One Word document. Three broken links. A couple of login credentials.

It’s a very true story 🙋🏻‍♀️.

This, in UX design, is what we call a “dead end” — a repository where information goes to die because it was never designed for the person actually using it. The folder wasn’t built for you. It was built to satisfy the requirement that something was left behind.

In last week’s post, we explored the Experience Asymmetry — how schools invest enormous energy into arrivals and treat departures as administrative afterthoughts. Today, we’re looking at the remedy: The Knowledge Harvest.

The cost of getting this wrong is not abstract. ISC Research’s Global Market Overview 2025 confirms what most international school leaders already feel in their bones: in a sector now employing over 730,500 staff across 15,000 schools, teacher movement is only accelerating. With nearly half of surveyed teachers planning to move on within one to six years, that's not a trickle of turnover. That's a river.

Here is the number that should be front-and-center in our transition planning: research consistently shows that approximately 42% of institutional knowledge lives exclusively inside individual employees’ heads. When those people leave, that knowledge doesn’t get filed. It vanishes.

The same research, from Panopto, found that knowledge workers waste an average of 5.3 hours per week either waiting for information from colleagues or recreating knowledge that already existed somewhere. Schools aren't knowledge-economy companies, but the pattern is identical: your new Digital Learning coordinator spending weeks rediscovering what your departing coordinator already knew — that’s not an onboarding hiccup. That’s a design failure.

The "Jobs to Be Done" Lens

There’s a powerful framework from design thinking called Jobs to Be Done, popularized by Clayton Christensen at Harvard Business School. The core insight is elegantly simple: people don’t buy products. They hire them to accomplish a specific job.

Apply that lens to the transition:

When a departing staff member creates a handover, they aren’t just “documenting their work.” They are building a tool that their successor is hiring to survive their first 90 days.

Instead of asking, “What did I do?” (which produces a data dump), the departing person should ask, “What does my successor need to accomplish?” (which produces a map). The difference is as stark as handing someone a phone book versus handing them directions to the restaurant.

The Three-Layer Handover Protocol

In my experience, handovers usually only capture the procedural “what.” But institutional knowledge has three distinct layers. The deeper you go, the more fragile—and valuable—the knowledge becomes.

Layer 1: The Process Layer (The “What”)

This is the standard content: curriculum maps, schedules, login credentials, and budget spreadsheets.

Process knowledge is the skeleton of the role. To make it more effective:

• Make it visual: A flowchart of the field trip approval process is ten times more useful than a five-page memo. Decision trees and workflow diagrams speak a universal language.

• Record it, don’t just write it: A 3-minute screen recording of how to navigate the budget request system is worth more than a page of text. Your successor can pause, rewind, and follow along.

Tool Tip

With Google Workspace for Education, which many of our schools use, this is built directly into your workflow. You can use the native Record feature in Google Slides to capture your screen and voiceover simultaneously, or use Google Vids to create a quick, polished instructional clip.

📽️ Here’s a Google Vids tutorial to get you started, by fellow creator .

Layer 2: The Relationship Layer (The “Who”)

Schools run on social capital. Every veteran staff member carries an invisible map of relationships: who to call when the copier breaks on the morning of the school play; which parent needs a five-minute check-in before a committee meeting; which department head is irritable on Friday afternoons.

This layer is almost never documented, yet it takes new hires the longest to rebuild.

• Create a Stakeholder Map: Who are the five people your successor needs to have coffee with in their first week? Who is the unsung hero in the admin office?

• Record a “Relationship Briefing”: This works beautifully as a 5-minute voice memo. It’s conversational and captures nuances that written notes flatten. Your successor can listen to it on their commute during their first week.

Doug Ota’s research in Safe Passage reminds us that transitions are relational disruptions. A stakeholder map doesn’t replace those lost connections, but it prevents a “cold start.”

Layer 3: The Contextual Layer (The “Why”)

This is the most fragile knowledge—and the most expensive to lose. It’s the “why” behind the “what.” Why did we stop using that math resource? Why do we hold the assembly in the gym instead of the theater?

Tacit knowledge—the unwritten, experience-born understanding that shapes daily decisions—represents roughly 80% of an organization’s total knowledge base. This is where institutions develop amnesia.

• Build Video Time Capsules: A 2-minute video of a departing coordinator answering one specific question is worth more than a hundred pages of documentation. Keep the prompts specific. To ease the process, I’ve built a set of cards you can use:

  

🔗 Download and save the full-sized cards here.

When to Start the Harvest (Hint: Not the Last Week!)

The Knowledge Harvest should begin the moment someone announces they’re leaving—not during their final week when they are mentally packing boxes.

The Ideal Timeline:

1. Post-Announcement: Schedule the Process Layer capture. It’s straightforward and low emotional load.

2. Start of Second Semester: Facilitate the Relationship Layer. This often sparks meaningful reflections on the connections they’ve built.

3. Final 2 Weeks: Record the Contextual Layer. The “why” stories flow more naturally when someone is already in a reflective, looking-back mindset.

Ownership matters: A “Transition Lead” or supervisor should facilitate this. Left to their own devices, most people default to a data dump. They need someone to ask the right questions.

Not sure who should lead this? Sometimes an outside perspective can ask the questions that feel too “obvious” for colleagues to raise. This is what we do at EKG Collective. If you’d like help designing your transition process, let’s talk!

Reframe the Handover as a Legacy

We often treat handovers as a chore—the last administrative box to tick before heading to the airport. But when we design them through the lens of legacy, the energy shifts.

The departing person isn’t being “strip-mined” for info; they are planting seeds. They are ensuring the programs they spent years building don’t develop amnesia the moment they walk out the door.

What’s Coming Next in the Leaving Well series

Next week: The Family Experience. How to design for the families staying behind and those leaving alongside you.

This Week’s Move

Think about the most critical function in your school that currently lives exclusively inside someone’s head. Ask that person one question:

“If you had to leave tomorrow, what are the three ‘pro-tips’ your successor would need to survive their first month?”

Record the answer. A voice memo, a quick video, or a sticky note. You’ve just started your harvest.

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.

Where We Are

It’s a scene we all know: July/August orientation. The campus is buzzing. There are branded tote bags, administrators waiting at the airport, and curated cocktail hours where everyone’s name tag includes their home country and a fun fact.

We treat the beginning like a welcome home: meticulously planned, and centered on belonging.

Now look at the end of that journey.

When the same staff member leaves three, five, or ten years later, the experience often feels like a quiet eviction. The “Departure Protocol” is usually a dry HR checklist: return your keys, sign this form, empty your cubby, and clean up your drive.

In international schools, where 15 to 25 percent of our community turns over every single year, this isn’t a “niceness” problem. It’s a design failure.

Welcome to the first installment of Leaving Well, a series on redesigning the final 10% of the school experience to protect institutional knowledge and honor the people who built it.

Share practice by design

The Experience Asymmetry

In UX design, professionals talk about the “onboarding” and “offboarding” of users. Schools have borrowed the language, but perhaps not the intention.

Great companies know that the way a user leaves a service determines whether they’ll ever come back, or what they’ll tell their friends.

In my experience, schools have a massive experience asymmetry.

We invest heavily in the “Hello” and almost nothing in the “Goodbye.”

Think about it. Your onboarding probably has 15 to 20 intentionally designed touchpoints. The orientation spreadsheet alone runs multiple tabs. There’s a welcome committee. A mentorship program. A “First 30 Days” plan.

The offboarding, on the other hand? Maybe 3 to 5 touchpoints, and most of them, administrative.

That gap is not neutral. It has costs, and they’re bigger than most school leaders realize.

Three Hidden Costs of a Bad Goodbye

1. The Friction Cost

Here’s an experience I’ve personally witnessed: A curriculum coordinator left an international school after eight years. She’d built a Google Site that served as the central hub for her program: resources for parents, unit overviews, event calendars, contact information. The Admissions team linked it in its official resources for new families. Families bookmarked it. Teachers used it, too, but perhaps not as often. It was, for all practical purposes, the public face of that department.

When she departed, nobody flagged the site as institutional property. For different logistical reasons, it lived under her personal school account. And when the agreed-upon date for account deletion arrived, IT followed the protocol. The account was deleted, and so was that site. Gone.

What came next was a slew of 404 errors and emails to the front office asking what happened. The front office didn’t know. Neither did the new curriculum coordinator, who now took it upon himself to rebuild the whole thing with bits and bobs shared by older staff. And that was his first quarter of school experience…

That’s the Friction Cost. Every hour a new hire spends reconstructing what already existed is an hour they’re not spending on students. An employee who departs without structured knowledge transfer can create 40 to 80 hours of ramp-up work for their replacement.

2. The Cultural Cost

Doug Ota, author of Safe Passage and one of the leading voices on transitions in international schools, names three groups in every school community: Arrivers, Leavers, and Stayers.

Most schools focus their energy on Arrivers (welcome!) and Leavers (goodbye!). But the Stayers carry the heaviest load. They’re absorbing the emotional weight of colleagues departing. They’re rebuilding team dynamics every August. And they are watching.

If you treat departing staff like they’ve already vanished, you teach your remaining staff that loyalty has an expiration date. Stayers don’t say it out loud, but they think it: Is this how they’ll handle it when I leave?

That thought doesn’t show up in exit interviews. It shows up in engagement surveys, in the slow burn from people who watched a decade of service get acknowledged with a card and a hallway handshake.

3. The Brand Cost

International education is a small world, and your departing staff are about to enter the rest of it.

In the tight-knit circuit of international schooling, your reputation isn’t just built by your brochure. It’s built by the teacher at a dinner party in Bangkok talking about how they felt during their last month at your school in Bogotá. It’s the counselor at a regional conference answering the question everyone asks about their former school: “How was it there?”

The answer to that question is shaped far more by how they left than by how they arrived.

A teacher who felt valued on the way out becomes an ambassador. A teacher who felt like a line item on a checklist? That story travels too.

And It's Not Just Staff

Students and families experience this asymmetry too, often more sharply.

When a student who’s been at your school for six years transfers out, what happens to their digital life? In most schools, IT deactivates the account. Google Drive files, Seesaw portfolios, messages from teachers, blogs and digital artifacts of their entire school identity, gone. Often without warning.

When we delete digital identities without support or ceremony, we’re telling departing families: your data mattered to us while you were enrolled. Now it doesn’t.

That’s not malicious. Nobody intends that message.

But intent and experience are two different things, and in design, experience is the one that counts.

Talking about experience…

Ready to simplify how your school communicates?

Every email, update, and announcement is a designed experience, whether you intended it that way or not. The Clarity Sprint is a self-facilitated 60-minute team workshop that helps you find the friction and fix it: language, format, handoffs, and context.

Three tracks: Admin, Comms, or Teachers.
One goal: reaching the reader where they are.

Get the Clarity Sprint →

The Design Shift: From Compliance to Contribution

To fix this, we need to move away from a Compliance Mindset (”Did they follow the departure rules?”) to a Contribution Mindset (”How are they leaving a legacy?”).

The first step is seeing the friction.

In design, we use a Friction Audit to identify where a process is slowing people down or causing frustration. If a teacher spends their last two weeks in a state of panic trying to “clean up” their files while also saying goodbye to students, writing report cards, and packing up an apartment to ship overseas, that is high-friction design. It’s bad for the teacher, and it’s bad for the school.

The Tool: The Departure Experience Audit

This week, I want to challenge you to look at your school’s exit process through the lens of a journey map. Instead of evaluating the checklist, map the actual experience a departing person encounters.

The Four Phases of Leaving Well:

1. The Announcement. How is the news shared? Does the person feel like a “traitor” or a celebrated alumnus? Is the timing controlled and dignified, or does word leak out through the rumor mill before the person has even told their closest colleagues?

2. The Harvest. Is the handover a chore (filling out forms in the final week) or a consultation (structured knowledge-sharing sessions across the final month)? Is the departing person treated as someone being mined, or as someone contributing their wisdom?

3. The Sunset. When does digital access end? Is it a cliff (locked out at midnight on the last day) or a ramp (a guided two-week transition window where files are migrated, access is transferred, and nothing important falls through the cracks)?

4. The Ritual. Is the farewell generic (”Thanks for your years of service!”) or specific (”Here’s the impact you had on our science department, and here’s how we’re making sure it lives on”)?

What’s Coming Next in the Leaving Well series

Next week: The Knowledge Harvest. How to move beyond the “handover folder” and capture the informal wisdom that actually keeps a school running. The official documentation most schools request captures about 20% of what matters. I’ll show you how to get the other 80%.

This Week’s Move

Pick one role, a staff member who left recently, or a student family who transferred out. Map the four phases, as described above:

1️⃣ Announcement
2️⃣ Harvest
3️⃣ Sunset
4️⃣ Ritual

Then do this ⤵️

The practice by design Prompt

Take your current exit checklist and put it on your desk. Cross out every item that exists for the school’s legal or administrative protection: keys, laptops, forms, signatures.

What’s left?

If the answer is an empty page, that's not the end of the process. That's the beginning of a better one. Next week, we go beyond the checklist.

Your Experience

What’s the best goodbye you’ve ever witnessed at a school? And what’s one departure experience that still makes you cringe? Hit reply. I’m building this series from your stories, and every response shapes what comes next.

By the way, I’m still collecting answers for this poll I started last week. Here’s what my LinkedIn network thinks:

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

Before anything else: I want to hold space for our colleagues and friends navigating difficult, uncertain times right now as a result of the distressing recent events in the Middle East. Many of you are making tough decisions, or watching from a distance, worried about the people you care about. I'm thinking of you. This newsletter is a small thing, but I hope it continues to be a useful one.

On that note, you may have noticed practice by design went quiet for a couple of weeks. It wasn’t because I ran out of things to say, but because I was (finally!) finishing something I’ve been building behind the scenes. (More on that in a minute.)

Stepping away from the weekly rhythm gave me space to reflect on something that’s been nagging at me since we wrapped the Beyond the Org Chart series: the tension between knowing a system needs attention and finding the time to actually fix it.

The Math Behind Spending Time to Save Time

You feel this, right?

You know your onboarding docs are outdated. You know your weekly newsletter template could use a rethink. You know the way parents submit concerns has devolved into a spaghetti path of forwarded emails and “just checking in” follow-ups.

You know all of this. And you’ll get to it... eventually. After the accreditation visit. After graduation. After summer. After.

Here is the guiding principle I return to in every conversation with school leaders:

Fifteen minutes mapping how information actually moves through your building. Twenty minutes auditing a single communication pathway. An afternoon asking, “Why do we do it this way?” about a process everyone assumes is fine just because no one is complaining loudly enough.

That’s not extra work. That’s the work that makes everything else lighter.

A principal recently told me she spent a single morning mapping her school’s parent inquiry flow. She discovered that a routine question about dismissals was bouncing between three people, generating separate email chains, and taking two days to resolve a thirty-second issue.

With her team, she fixed it in an afternoon. They built a simple FAQ page, added a QR code to their pick-up/drop-off area, and redirected the inquiry form. The whole project took maybe three hours.

That was eight months ago. Her front office estimates they’ve saved over 200 hours of staff time since.

Three hours invested. Two hundred hours recovered. That is the math of spending time to save time.

And honestly, that’s what everything I write in practice by design comes down to. Journey maps, service blueprints, invisible system audits... they’re all variations on the same principle: stop long enough to see what’s actually happening, and you’ll find the fix faster than you think!

Introducing The Clarity Sprint

Speaking of spending time to save time, I have news. The Clarity Sprint is officially ready.

For those who’ve been following along, this is the complete, self-paced workshop I’ve been building from the Design for Clarity series. It takes everything we covered and turns it into a facilitated 60-minute team experience.

Choose Your Track

I built this workshop with three distinct audiences in mind: Senior Admin, Comms Leaders, and Middle Leaders/Teachers. When your team dives in, they’ll choose the track that best fits their role.

📦 What's Inside the Workshop:

• An interactive, video-embedded slide deck: Four distinct sprints (The Invisible Network, Visual Hierarchy, The Mobile Audit, and Plain Language), all guided by video instruction built right into the deck. You don’t need to be an expert to run this—just press play, keep time, and give your team space to do the work.

• A facilitator quick-start guide: Exact scripts and pacing tips so you can walk into the room feeling prepared, even if you’ve never run a workshop before.

• Emergency artifacts: Three hyper-realistic, jargon-filled “dummy” communications so your team can practice editing (just in case someone forgets to bring their own examples).

Could AI do this for you?

Of course. But, ultimately, this protected hour is all about learning to communicate better and adapting to the times—an exercise everyone can learn more from.

A Note on Pricing

I’ve made this pay-what-you-want, from $0 to whatever you feel it’s worth.

If you have a PD budget and want to support the mission, your contribution is genuinely appreciated; it’s what allows me to keep building resources like this.

But if you don’t have the budget right now, take it for $0 and go make your school’s communication better. That is the whole point!

Get the Sprint!

Not sure if it’s for you?

I’ve made the introductory video for Sprint 1 (The Invisible Network) available for free. Watch it, share it with your team, and see if the lightbulbs go on.

Duration: ˜3 minutes

Share This with a Colleague

Coming Next Week: The Offboarding Series

Now, for what’s ahead.

I’ve been thinking about offboarding for a long time, especially having recently been on both sides of the transition: creating the departure checklists, and then actually having to use them myself. And when I talk about offboarding, I don’t mean the exit interview or the farewell parties. I mean the actual systems—or lack thereof—that determine what happens when someone leaves your school.

Think about it: schools invest weeks onboarding new staff. Orientations, welcome binders, campus tours, buddy systems. But when someone leaves?

Usually, it’s a rushed handover. A shared drive folder that may or may not contain anything useful. A hearty “good luck!” from someone already mentally checked out. And ultimately, a new hire who spends their first three months trying to decode which processes lived entirely inside their predecessor’s head.

Offboarding is the communication design problem almost nobody talks about. And in international schools, where staff turnover is a structural reality, the cost of getting it wrong compounds year after year.

Starting next Wednesday, I’m launching a new series on designing offboarding systems that protect institutional knowledge, support the people leaving, and set up the people arriving.

But I want to build this one with you. Before I write a single word, I want to know what matters most to your experience.

Quick Poll: The Offboarding Gap

Have a specific story?

Hit reply and tell me:

What do you wish your previous school had done better when you left?

Or what did you walk into at your current school that made you think, “How did no one write this down?”

I will literally read every reply and build the frameworks around your real experiences. This series is yours as much as it is mine. Let’s design it together.

It’s good to be back. I missed this.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

A father raises a concern about bullying. He emails the advisor, just as the school directory instructed. The advisor responds promptly and says she will look into it.

A week later, the father runs into the division head at drop-off and mentions the situation. The division head has no idea what he’s talking about.

Not because the advisor dropped the ball. She is mid-investigation, gathering observations, consulting with the counselor. She hadn’t looped in the division head because there was nothing to escalate yet.

She was being efficient. But to the father, she looked like she was acting in a vacuum.

In that 30-second conversation at the curb, the father goes from trusting that the process was underway to wondering: “How seriously are they taking this?” Before leaving the parking lot, he emails the head of school.

Now the head of school contacts the division head, who contacts the advisor, who feels blindsided and undermined. A chain reaction happens because the father interpreted a routine information gap as institutional neglect.

The advisor did her job. The division head was appropriately out of the loop. And the father’s conclusion was entirely reasonable given what he could see.

That is not a people problem. That’s a systems problem.

The Pattern Behind Every Problem in This Series

That one conversation at the curb contains every problem we’ve explored in this series.

In part 1, parents emailed three people about one concern because they couldn’t tell whose job it was. In part 2, a teacher spent $73 of her own money because nobody owned the procurement path. In part 3, we built pathmaps because process documentation existed, but navigation didn’t. In part 4, a parent spiraled in silence because the advisor’s work was invisible to the person it served.

Four different symptoms. One diagnosis: role legibility, or the ability for every person in your school community to understand who does what, why, and how those roles connect in real time.

This is different from the visibility we discussed last week. Visibility is whether you can see that work is happening. Legibility is whether you can read who does what and how those roles connect.

The Expectations Gap

In most schools, if you ask staff members to write down the responsibilities of the person in the next role over, the answers will not align. (Try it at your next staff meeting. Make a game of it. The results might surprise you!)

The teacher assumes the counselor is making the call. The counselor assumes the advisor is already on it. The advisor assumes the teacher is managing the classroom fallout. The division head assumes everyone is in the loop because of an email thread from last Tuesday.

I call this the Expectations Gap: the invisible mismatch between what each person believes other roles are doing and what those roles actually do.

It turns professional collaboration into a game of administrative hot potato. 🥔

And it’s not just staff. Every person in your school carries an internal map of how the system works. Parents have one. Teachers have one. Counselors have one. These maps aren’t wrong, exactly. But nobody has ever laid them side by side to see where they diverge.

Go back to the father at pickup. His map said: “I contacted the advisor. If something important were happening, leadership would know.” The advisor’s map said: “I’m coordinating a team response. The division head gets involved only if this escalates to a formal investigation.”

Both maps were reasonable. Neither was shared. And what collapses in that gap is trust.

The Expectations Gap explains why well-meaning people in well-designed schools still produce misaligned outcomes. Everyone is operating from their own map, and nobody has checked whether the maps match.

From Org Chart to Role Ecosystem

An org chart is a photograph. It captures reporting lines at a single moment in time, frozen and flat.

What you need is a film. You need to see how roles move, connect, and respond when something actually happens.

I’m calling this the Role Ecosystem: a scenario-based map of how roles activate, interact, and hand off when triggered by a specific event.

If the father from our opening story had received a message at the start saying, “Your advisor is leading this process. The division head becomes involved only if the concern moves to a formal investigation,” that pickup conversation would have gone very differently. He wouldn’t have interpreted the division head’s unawareness as negligence. He would have understood it as the system working exactly as designed.

Share practice by design

💡 Go Deeper: Teaming

Amy Edmondson, a Harvard Business School professor who studies how organizations coordinate under uncertainty, draws a distinction that matters for schools. She separates teams (static groups with stable membership who practice together) from teaming (the ability to coordinate fluidly with people you may not have worked with before).

Schools are teaming environments. Your counselor, advisor, and classroom teacher don’t sit in a room together every day as a fixed team. They form temporary constellations around specific students, then dissolve when the situation resolves. Edmondson’s research shows that when you can’t rely on shared history to drive coordination, you need explicit role structures that tell people their cue, their handoff, and what others can see.

That is exactly what the Role Ecosystem provides. If teaming is the mindset, the Role Ecosystem is the scaffolding.

🎥 Highly recommended watch: How to turn a group of strangers into a team ⬇️

Building Your Role Ecosystem: The Three-Layer Approach

You don’t need to map every scenario in your school. Start with one high-friction situation and apply three layers.

Layer 1: The Trigger Map

Pick a scenario. Let’s use the one from this series: “Parent raises a concern about their child’s social experience.”

List every role that gets activated: Advisor. Counselor. Grade-level team. Classroom teacher. Division head. Front office (who might receive the initial call). Even the parent themselves. They have a role in this system too.

Layer 2: The Choreography

For each role, define three things:

What do they do first? The advisor logs the concern and acknowledges receipt within 4 hours.

Who do they notify, and when? The advisor alerts the counselor same-day. The counselor briefs the teacher before any classroom observation.

What does the family see? The advisor sends a confirmation email. The counselor sends the Friday Pulse. The division head is invisible unless escalation occurs.

This is where you’ll discover the gaps.

Layer 3: The Visibility Assignment

This is what makes a Role Ecosystem different from a workflow chart. For every action in the choreography, ask: Who can see this happening?

Some actions should be visible to the family (the acknowledgment email, the Friday Pulse). Some should be visible only to staff (the internal consultation, the observation notes). Some need to be visible to leadership (escalation triggers, resolution timelines).

When you map visibility alongside choreography, you eliminate two problems at once: the internal confusion about who does what and the external silence that makes families lose trust.

The Skeptic’s Reality Check

“We already have protocols for this.”

Maybe. But can your new advisor, the one who started in August, describe the coordination sequence without asking a veteran colleague? Can a parent tell you what happens after they send the email?

If the protocol lives in a Google Drive folder nobody remembers about, it’s not a protocol. It’s a wish.

The difference between a protocol and a Role Ecosystem is the difference between a recipe locked in a drawer and a recipe taped to the kitchen wall. The content might be identical, but it’s the accessibility that makes it top of mind.

Schools that document role coordination for common scenarios (parent concern, student support referral, new family onboarding) spend significantly less time doing damage control.

It’s all about eliminating the guesswork that creates duplicated effort.

The Series in One Frame

Before we wrap, here’s the full "Beyond the Org Chart” system, viewed from five angles:

◈ The Directory tells people where to go.

◈ The Journey Map shows where the friction is.

◈ The Pathmap tells them how the process works.

◈ The Pulse proves that the process is working.

◈ The Role Ecosystem tells your team who does what, when, and in coordination with whom.

Each post in this series gave you one piece. Together, they form a complete communication architecture for your school.

This Week’s Move: Build One Choreography

Here’s the fastest way to find the biggest gap in your school’s coordination: look for the handoff where two people both assume the other is acting.

Step 1: Identify the scenario that generates the most “who’s handling this?” friction. (If you’re not sure, look at where leaders get cc’d most often. That’s usually the gap.)

Step 2: List every role that activates when this scenario occurs.

Step 3: For each role, write one sentence answering: “What do they do first, and who do they notify?”

Step 4: Draw the visibility line. For each action, note whether the family can see it happening or not.

You’ll likely find at least one handoff where nobody owns the update and at least one moment where the family goes dark.

Those are your design opportunities. That's your practice by design.

Just the commitment to notice where systems fail people and to do something about it, one choreography at a time.

A Short Intermission

This post concludes the Beyond the Org Chart series, and the timing feels right for a brief pause. I want to wish a restful February break to the many schools on holiday this week, and a happy Year of the Horse 🐴 to those celebrating the Lunar New Year.

I’m taking a short break to focus on The Clarity Sprint I promised earlier this year. To be transparent, the volume of work has been more significant than I anticipated, which is a positive problem to have!

I’ll be back in your inbox in early March with fresh insights and the final release of this one-hour, self-paced course.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

A colleague stopped me during last week’s AAIE gathering in Toronto with a story about a week of silence that nearly broke her trust in her daughter’s school.

The daughter, a well-adjusted, 15-year-old student at a boarding school, had been feeling progressively excluded from her classroom/social circles. For this family, the situation felt especially vulnerable and confusing.

So the parent did what parents normally do: She emailed the advisor on Monday. The advisor replied almost instantly: “I’ll look into this and get back to you soon.”

Then... silence.

Tuesday. Wednesday. Thursday. By Friday, the parent was concerned. Did they forget? Am I being a helicopter parent? Is my daughter being overly sensitive?

What my colleague did not know then: The advisor had already put the word out to the grade-level team, observed two lunch periods, consulted the counselor, and interviewed a couple of her classmates.

They were working incredibly hard. But to the parent, that week was a “Black Box” of perceived abandonment.

This is the Silent Gap: the psychological void that opens when a parent knows they’ve asked for help, but has no idea if anyone is actually listening.

The Line of Visibility

In part 1 of this 5-part series, we talked about Service Blueprinting, which is the line between what parents see (Frontstage) and what you do (Backstage).

We solved Routing (part 1) and Entry Points (part 3). But we haven’t fully addressed the Visibility Gap.

Most schools treat a parent concern like a library book: you check it in, and you don’t hear anything until it’s due back.

But a child is a high-stakes emotional investment, and when a parent enters the “Black Box,” they don’t just wait. They invent narratives. And often, the narrative is: “The school does not care as much as I do.”

The Solution: Making the Backstage Visible

If you want to stop the “just checking in” emails that clog senior leadership’s inboxes, you don’t need a better policy. You need to eliminate the silence.

Enter the “Pizza Tracker for Pedagogy”

Companies like Domino’s and Amazon revolutionized the experience of waiting. Domino’s famously realized that customer frustration isn’t caused by the 30-minute wait, but by the 30-minute void. When you can see the dough being prepared and the pizza entering the oven, your brain moves from “Where is my dinner?” to “My dinner is in progress.”

But a school isn’t delivering pizzas. When a parent asks about a social conflict or a learning gap, they’re asking about something at the core of your educational mission. What happens next—the observations, the consultations, the adjusted seating arrangements—isn’t administrative overhead. It’s pedagogy. And if it’s invisible, its value is invisible too.

By making your “backstage” milestones visible, you prevent worried parents from becoming angry parents.

When families feel informed, they are significantly less likely to escalate a classroom issue to the Board or the Principal’s office. You aren’t just “being nice”; you are strategically protecting your team’s time.

The Strategy

For high-anxiety processes like investigations or learning support referrals, give the family a clear picture of what's going to happen before the work begins. Then keep them updated as it unfolds.

Two tools make this work efficiently:

1. The Tracker

Imagine an internal tracker where a staff member simply checks a box for “Observation Complete.” That check triggers an automated, branded email to the parent: “Update: We have moved to Stage 3. This means our team is now reviewing observations to draft a plan. Expect a human check-in by [Date].”

It's a small ask for IT that creates a high-trust experience for the family.

• Stage 1: Logged & Assigned

• Stage 2: Observing & Gathering Information (classroom observations, reviewing relevant records)

• Stage 3: Team Consultation

• Stage 4: Action Plan Drafted

• Stage 5: Family Resolution Meeting

2. The Friday Pulse (The “Anti-Anxiety” Protocol)

This is the simplest, highest-impact system you can implement right now. If a case is open, the parent gets a “Pulse” update every Friday before 4:00 PM, even if there is no new news.

• “Hi [Parent], we are still in the observation phase of the social concern you raised. We’ve completed two observations and have one more scheduled for Monday. I’ll have a full update for you by Wednesday. Have a restful weekend.”

To give you an example you can replicate at your school, I’ve designed the Transparent Concern Path, which is a blueprint that maps your internal “backstage” efforts to the “frontstage” parent experience.

Share practice by design

The Skeptic’s Reality Check

You might ask: “Isn’t this just more work for an exhausted staff?”

The hard truth is that you are already doing this work. You are just doing it in the form of “damage control” later. When we leave parents in the dark, we aren’t saving our staff’s time, but merely deferring the expenditure of it until it’s paid back with the interest of a parent’s anxiety.

Silence creates a reactive cycle where your team spends more time answering “what’s the status?” than they would have spent simply providing it.

Writing a 30-second “Pulse” email on Friday is a choice; dealing with an angry parent on Monday morning who thinks you’ve ignored them all week is a crisis. One requires a brief moment of focus; the other requires a meeting, a debrief, and a significant emotional toll.

This Week’s Move: Audit the Silence

Pick your school’s most opaque process (likely your IEP path or Discipline/Bullying investigations).

1. Define the Milestones: What are the 4–5 “Backstage” steps that parents currently never see?

2. Assign the Pulse: Who is responsible for the Friday update? (Hint: It’s often an administrative assistant or case manager, not the busy teacher).

3. Request the Automation: Sit down with IT and ask: “How can we trigger a milestone email based on a status change in our internal tracker?”

Want Help Fixing Your Visibility Gaps?

It’s hard to spot (and fix) problems when you’re stuck in the day-to-day grind. I help teams find those blind spots where stakeholders are spiraling in silence and build the automated solutions needed to win back their trust.

If you want to eliminate the “Silent Gap” but don’t have the internal bandwidth to lead the audit yourself, let’s talk. 👋

What’s Coming Next in the Beyond the Org Chart series

(This) Series Finale

We've fixed routing, mapped teacher journeys, built pathmaps, and closed the visibility gap with families. But every one of those problems traces back to a single root cause: people don't understand who does what, why, or how those roles connect to each other.

In the final installment, I'm introducing the Role Ecosystem: a framework that replaces your static org chart with a living map of how roles actually activate when something happens.

Because fixing processes only works if everyone can see their part in the system.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

Last week, we met the teacher who paid $73 for science supplies because the “official” path was too exhausting to find.

If you did a journey map after that post, you likely saw the same thing: your staff isn’t “failing to follow the process.”

They are simply choosing the path of least resistance.

The problem isn’t a lack of guidance…usually, there’s too much of it (hello, onboarding packet!).

The problem is a lack of navigation.

Toronto Fixed Its Underground Maze. Your School Can Too.

I’m writing this from Canada, and the timing for this particular post couldn’t be more fitting.

This week, I'm in Toronto for the AAIE Global Leadership Conversation, working and learning with these two (and a few other brilliant minds).

The conference brought over 500 participants into a single hotel with more than 1,000 rooms. Think about that for a second. Five hundred people navigating dozens of session halls, breakout spaces, registration desks, meeting rooms… all under one roof.

And yet, somehow, nobody gets lost. Not really. Not for long.

Because the hotel’s way-finding system, combined with the conference’s own signage, does the heavy lifting. The environment speaks. You don’t have to ask. You just… move.

The PATH

The real lesson, however, comes from walking into Toronto’s PATH system, the world’s largest underground pedestrian network. This thirty-kilometer tunnel system connects over 75 buildings, serving more than 200,000 commuters every single business day.

For decades, the PATH was notoriously confusing. The tunnels were built piecemeal over fifty years by different developers, each with their own signage. A sprawling underground city where even daily commuters could get turned around.

Then, in 2024, the city completed a comprehensive way-finding overhaul. They scrapped the old compass-based color system, which, it turns out, nobody actually understood, and replaced it with something far simpler.

The system doesn’t ask you to memorize a code. It shows you where things actually are.

On my one free day exploring the city (in crisp -17ºC weather!), I paused there, underground, watching dozens of commuters navigate without hesitation, and I thought: This is exactly what we need in our schools.

Not new systems or bigger manuals. A better map.

The Turnaround: From Scavenger Hunt to Support

I once worked at an international school where the staff was “system-fatigued.” Every administrative task felt like a test they hadn’t studied for.

We didn’t buy a new platform or hire a new assistant to solve this. Instead, my team and I sat down with our audit and rebuilt the process around five human-centered questions (truth be told, leading this effort ourselves taught us that the best solutions are often the simplest):

1. Where is the Front Door? We placed one permanent, unmoving “Quick Links” page in the staff portal. One click. Always there.

2. Is the Form “Low-Floor”? We stripped purchase and professional learning request forms down to the absolute essentials. No jargon, just: What do you need? When do you need it?

3. Does the Data Know Where to Go? We automated the handoff. The form routed itself based on the manager selected—no manual forwarding, no “Who do I send this to?”

4. Is the System Pulsing? We eliminated “the void” with an automated confirmation: “We have your request. Expect a status update by [DATE].”

5. What is the Promise? We published clear guidelines that explicitly outlined the next steps.

Six months later, out-of-pocket spending and reimbursement requests—which are always a nightmare to process—had nearly vanished. Even better, the nature of the communication shifted. Emails regarding professional development changed entirely; instead of “How do I do this?” they became meaningful requests for conversations with divisional leaders about professional growth. Because the new system automatically kept teachers informed, the Purchasing Manager saw a 60% drop in “status check” emails.

The friction hadn’t just moved; it had dissolved.

The Anatomy of a Pathmap

When you rebuild a process with intention, you are telling your staff: Your time is too valuable to spend it hunting for a PDF.

Every process in your school needs a pathmap. Not a policy manual, but a simple, one-page guide that answers the four questions every “lost” teacher has:

• When do I use this? (e.g., “Any classroom purchase under $500.”)

• How do I start? (The direct link to the “Front Door.”)

• What happens next? (The “Promise” or timeline.)

• Who is my human contact if the system breaks?

Here’s an example I built for you:

Your Tools for the Rebuild

I’ve built the Teacher Wayfinding Toolkit to help you do the “thinking work” of this redesign. Inside, you’ll find the Process Builder, which prompts you through these questions to help you design a path that actually fits your school’s culture.

Download the Toolkit

How to use it:

1. Click the button above to download the HTML file to your computer

2. Locate the downloaded file in your Downloads folder (it’s called teacher-wayfinding-toolkit.html)

3. Double-click the file to open it in your web browser

4. The interactive toolkit will guide you through 5 questions to build your pathmap

What you’ll create:

By the end of the process builder, you’ll have a complete, downloadable pathmap that you can:

• Customize with your branding (My recommendation! Choose the text file to do so)

• Share with your staff (as is - HTML file)

• Post in your staff portal

• Print and display in workrooms

Note: This is a standalone HTML file that works completely offline. No login required, no data sent anywhere—it runs entirely in your browser.

What’s Coming Next in the Beyond the Org Chart series

Next week: How Parents Navigate Your Systems. We've focused on teachers for the past two weeks. Now we're flipping the lens to families. Parents face the same navigation challenges, but with higher stakes and less institutional knowledge. I'll show you how to build family-facing pathmaps that reduce "black box" frustration and create confidence in your school's responsiveness.

This Week’s Move

Build One Bridge

Pick the one process you audited last week, the one where you feel like your teachers are currently “paying the tax.”

Use the Process Builder in the Teacher Wayfinding Toolkit to define its new “Front Door” and its “Promise.” Write your one-page Pathmap using the four-question structure:

1. When do I use this?

2. How do I start?

3. What happens next?

4. Who is my human contact?

Publish it where people can actually see it: staff portal homepage, pinned in your communications channel, printed and posted in the workroom.

Don’t overthink it. Version 1.0 is better than a perfect plan you never execute.

The city of Toronto didn’t fix its underground city by writing a better manual. It fixed it by making the next step obvious at every single junction.

Your school can do the same thing, and it starts with one process and one pathmap.

Because when a teacher doesn’t have to spend their Sunday night wondering how to request a sub or book a room, they spend it resting. And a rested teacher is a teacher who stays.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

A second-year teacher needs to order graduated cylinders for a science unit starting in fourteen days.

She starts with her department chair, who points to a requisition form that isn’t in the shared drive. She asks the admin. assistant, who suggests checking with the purchasing manager. She asks a veteran colleague, who shrugs and says, “I usually just email the principal and hope for the best.”

After three days, five conversations, and zero clarity, she reaches a breaking point. It’s not a loud break; it’s a quiet one. She opens her laptop, goes to Amazon, and spends $73 of her own money.

That isn’t a “busy teacher” problem. It’s a systems problem.

The Invisible Tax

Last week, we looked at why parents see your school as a “black box,” defaulting to emailing whoever is most accessible because they don’t know who actually does what.

But your teachers are navigating that same fog every day.

When a teacher can't find the "front door" to a basic process, they pay an invisible tax, one that drains the cognitive energy that should be reserved for students.

The solution isn't complex. You don't need new software or a complete culture overhaul.

You need to make the invisible visible.

Why It Matters

When systems are opaque, three things happen (and each one carries a cost your school can’t afford):

The Cognitive Load Tax

Teachers spend an average of 4.7 hours per month hunting for procedural information such as forms, approval workflows, who handles what. Cognitive Load Theory confirms what teachers already know: when working memory is cluttered with procedural confusion, there’s less room for creative problem-solving. Every minute spent thinking “How do I even do this?” is a minute not spent thinking “How can I better support my students?”

The Innovation Ceiling

The science teacher with the $73 cylinders had three other ideas that month. She didn’t pursue any of them. When the “tax” to innovate is too high, teachers stop trying. They don’t quit their jobs; they quit their ideas.

The “In-Crowd” Gatekeeping

If “how things work” only lives in the heads of the veterans, you’ve accidentally created a hierarchy. New hires and international staff are left outside the circle, forced to beg for information. That isn’t just inefficient; it’s inequitable.

When onboarding depends on tribal knowledge rather than documented processes, you’re telling new teachers: “Figure it out, or prove you’re worthy of help.” That’s not the culture most schools claim to want.

A Favorite Diagnostic: The Journey Map

If you’ve followed my work for any length of time, you know I’m a dedicated proponent of this tool—not just as an operations enthusiast, but because I believe that better systems are the highest form of empathy we can offer our staff. Journey mapping is, quite simply, my #1 recommendation for school leaders who want to move from "putting out fires" to building sustainable systems that center the human experience.

You can’t fix a system you haven’t seen, and this kind of audit allows you to do just that.

Journey Mapping is a diagnostic tool that traces the actual steps, thoughts, and frustrations a teacher experiences while trying to get something done. It’s not about how the process should work; it’s about how it feels right now.

To show you what this looks like in practice, I’ve mapped out that opening story to visualize the “Current Reality,” turning a confusing maze into a visible path:

When you see the map, the fix becomes obvious. It’s rarely about the teacher’s capability: it’s about the lack of an entry point and the absence of a status bar.

Small Wins: The Power of the Front Door

Improving a system doesn’t have to mean writing a 50-page handbook or overhauling your entire culture.

Sometimes, it’s as simple as building a clear front door.

Think about the smallest friction point in your school: a broken stapler in the workroom, a lightbulb out in the hall, or a room that needs booking. If the teacher has to think for more than three seconds about who to tell, the system is broken.

A “Small Win” is putting a QR code on the wall that says “Report an Issue Here.”

It moves the cognitive load from the teacher to the system.

This Week’s Move: Trace One Path

Pick the one process that causes the most “How do I...” emails in your inbox. Maybe it’s room bookings, IT tickets, or facilities requests.

Instead of guessing where the friction lies, take 20 minutes to perform a simple audit on that one process.

Here’s the simplest way to map the current reality:

1. Identify the Entry Point: Where exactly does a teacher start? (An old email? A specific person? A bookmark they made during orientation week and can never find?)

2. Document the Micro-Steps: List every single action they take. Don’t skip the “small” things, like “waited two days for a reply” or “searched the shared drive for five minutes.”

3. Layer in the Emotion: At each step, note the feeling. Are they feeling supported, or are they feeling like they’re being an “annoyance” just by asking?

4. Find the Resignation Point: Identify the exact moment where the teacher decides it’s easier to just do it themselves or give up entirely.

Don’t try to solve the problem this week. Just document the reality as it exists today. Once you see the emotional arc of your systems, the path to rebuilding them becomes clear.

What’s Coming Next in the Beyond the Org Chart series

Next week: Pathmaps Over Policy: Making School Systems Intuitive

Once you’ve mapped where teachers get lost, I’ll show you how to rebuild the process with clear pathways, transparent timelines, and documentation that actually lives where people can find it.

By the end of next week, you’ll have documented and published pathways for the processes that currently live only in people’s heads.

Systems as Care: See you at AAIE!

Next week, I’ll be heading to the AAIE (Association for the Advancement of International Education) conference to lend a hand to the wonderful AAIE core team with comms and logistics. (Have I mentioned I’ve been an assistant producer and executive assistant in the “before international teaching” times? I still love a good high-stakes logistics puzzle 😉.)

I will also have an opportunity to speak with school leaders from around the world.

I’ll be presenting “The Handoff Problem: Designing Better Family Experiences Across Your Technology Systems.” Whether it’s a teacher trying to order supplies or a family trying to navigate enrollment, if the baton is dropped between departments, the whole system slows down. We’ll be exploring how to bridge those silos to serve our communities better.

Because, beyond efficiency, clear systems are a form of care.

If you’re attending AAIE in Toronto, come say hi 👋 on Wednesday, February 4th at 9:30 AM. Let’s talk about how to make the invisible visible.

Your Experience

I’m genuinely curious: what’s the one process in your school that makes teachers feel like they’re bothering someone just by asking?

Hit reply and tell me, or leave a comment below. I learn a great deal from your replies and comments.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

A parent has a concern about their child’s behavior in class.

They email the homeroom teacher, the division head, and the school counselor. All three.

It seems harmless. They’re just covering their bases…

But think about what you just created: three professionals now need to coordinate who’s handling this, avoid duplicating responses, and figure out if this is a discipline issue (division head), a developmental concern (counselor), a classroom management situation (teacher), or something requiring all three.

That coordination work is the invisible cognitive load you’ve just distributed across three people’s already-full plates.

The Triage Tax

If you’ve been following along with this series, you know we’ve been exploring how invisible organizational structure creates friction everywhere.

Here’s something that is quietly draining your teachers’ energy every single day:

Parents don’t know who handles what type of issue.

So they email everyone. Or worse, they email the person who’s most accessible—usually the classroom teacher—regardless of whether that teacher has the expertise (and sometimes the authority) to address the concern.

Now your teachers stop what they’re doing to triage emails that have nothing to do with their actual job. They forward them to the right people, context gets lost in translation, and response times balloon because nobody realized this needed urgent attention until it had already passed through three inboxes.

The Concept: Service Blueprinting

This week, we’re fixing that using a tool from service design called Service Blueprinting.

While Journey Mapping (which we covered a few weeks ago) tracks what the parent feels, a Service Blueprint tracks how your school operates to deliver that experience. The Nielsen Norman Group has a solid 3-minute breakdown of the full methodology if you want to go deeper.

But here’s what matters for your school right now:

A Service Blueprint is divided by a critical boundary called the Line of Visibility.

Frontstage (Above the Line): What the parent sees—the email they send, the reply they get.

Backstage (Below the Line): What your staff does—the forwarding, the debating “whose job is this?”, the coordination chaos.

Here is the reality of the Triage Tax: The parent sees a simple “Frontstage” action—they sent one email. But “Backstage,” your staff is engaged in a messy, tangled web of coordination to figure out who should answer.

Because the parent cannot see the Backstage effort, they don’t value it.

They only feel the delay, which is inevitably part of this experience.

The Fix

We’re going to redesign your service blueprint so the frontstage action routes correctly from the start—eliminating the backstage chaos entirely.

How? We (re)create your “Who to Contact” directory and make it actually visible.

This directory changes the service blueprint. Instead of the email landing in a teacher’s inbox (requiring backstage triage), the directory routes the parent to the correct expert before they hit send.

A Three-Step Plan to Reclaim That Capacity

Step 1: Map the Spaghetti (Do This Now)

Before you can direct parents, you need to see what’s actually happening.

Map the mess: Take one recent complex email—something like “My child is struggling in math and seems anxious.”

Write down every person who touched it:

Teacher → Department Chair → Counselor → Learning Support Coordinator → back to Teacher for final response.

Count the handoffs. That’s your spaghetti diagram.

Define the straight lines: Rapid-fire list your top 5-7 issue categories and assign one clear owner for each:

• Academic/Curriculum: Teacher/Department Chair

• Learning Support: Learning Support Coordinator

• Social-Emotional: Counselor

• Operations: Operations Manager (Bus, Lunch, Facilities)

• Health: Nurse

• Billing/Enrollment: Business Office

Step 2: The Quick Win

Translate those “straight lines” into a clear, one-page directory for parents, such as this:

• Publish it where parents will actually see it

  Do not bury this in a handbook nobody reads. Put it here:

  • Parent portal homepage — First thing they see when they log in

  • Website navigation bar — “Quick Answers” or “Who to Contact”

  • New family welcome packet — Literally page 2

  • Back-to-school orientation slides — Normalize using it from day one

  And here’s the key move:

  Train your teachers to redirect using the directory.

  When a teacher gets an email about billing, their response becomes:

  “Thanks for reaching out! For billing questions, our Business Office can help you faster than I can. You can reach them directly at billing@school.edu, or find all contacts in our [Issue Directory].”

  That’s not dismissive; that’s protecting their cognitive capacity while serving the parent better.

  What if parents push back?

  Some will. They’ll say “I just wanted to ask you quickly.”

  Your response:

  “I totally understand! And [Name] in [Department] can answer this way faster and more accurately than I can. I want to make sure you get the right info.”

  You’re not dismissing them. You’re serving them better.

Step 3: The System Fix (Your Long Game)

The ultimate move? Partner with IT to add a “Who should I contact?” widget to your portal. Before a parent can send a message, they answer: What is this about? The system then routes the message to the correct person automatically.

Reality check: This might take 4 weeks. It might take 4 months depending on your IT capacity and competing priorities. That’s fine. The directory (Step 2) solves 80% of the problem immediately. This just makes it foolproof.

Don’t have a portal? Use a shared Google Form. Parent fills it out → form auto-routes to correct person based on their selection. Same outcome, different tool.

Note: You likely won’t need custom code for this. Most school portals and form builders have “conditional logic” already built in.

Why This Works

Time Recovery: Every email that goes directly to the right person instead of bouncing through three inboxes saves 15-30 minutes of staff coordination time.

Faster Resolution: Parent concerns resolve 48-72 hours faster when they reach the right person first, avoiding the translation lag and context loss.

Reduced Burnout: Teachers don’t burn out from teaching. They burn out from being the universal “Service Desk” for every category of concern. This gives them permission to protect their attention.

Straight lines beat spaghetti paths.

Need a Structured Way to Work Through This?

Last week I introduced The Clarity Sprint—a self-paced workshop based on the Design for Clarity series. If you missed it, here’s the 90-second overview:

Pick your team type (Senior Admin, Comms, or Middle Leaders & Teachers), gather your group, and walk through a systematic process to audit and redesign one critical piece of your school’s communication—like the directory we just discussed.

Coming soon. I’m finalizing details now.
Format: Self-paced, video-guided workshop
Investment: $67—your support helps me keep practice by design free while creating resources like this.

Get notified when it launches ⤵️

What’s Coming Next in the Beyond the Org Chart series

Next week: The Teacher Who Stopped Asking for Help. Because if parents can’t navigate your systems, imagine what your own staff experience when they need to request supplies, book a room, or get IT support. The invisible structure problem doesn’t stop at the school gates; it’s happening internally too.

This Week’s Move

Pick ONE issue category that currently travels through a “Spaghetti” path at your school. Blueprint the mess. Then, write one clear “Who to Contact” entry and publish it in your next newsletter.

See the difference straight lines make.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

Welcome to 2026.

If the air feels a little thin right now, you aren’t imagining it. Between the political uncertainty keeping colleagues up at night and the sheer complexity of running a school, the load is heavy. (I’m writing this from my hometown in southern Brazil, where I’ve been caring for family—so I’m feeling the weight of complexity in my own way.)

That’s exactly why I’m not writing to you about politics today. I want to talk about the one thing you can actually get your hands around: clarity.

Specifically, whether your community actually understands what you do all day.

The Conversation I Can't Stop Thinking About

A few weeks ago, I sat down with friends who also happen to be parents at an international school. Smart people. Corporate backgrounds. Actively engaged in their school community.

They told me, bluntly, that they think assistant principals and curriculum coordinators are “wasteful middle management.”

Let that sink in.

They genuinely believe the principal should handle discipline, operations, and curriculum decisions, on top of strategic leadership. They can’t figure out who does what or why these roles exist.

They aren’t being malicious. They’re confused.

That conversation stayed with me, so I took it to LinkedIn. I asked:

“If schools made their organizational structure clearer, who would benefit MOST?”

86% said: “Everyone—it’s a systems problem.”

This isn’t a people problem. It’s, in fact, a systems design problem.

And unlike the geopolitical landscape, this is something we can actually fix.

The Invisible Architecture

You know why your structure looks the way it does. Your org chart is the result of years of careful thinking about cognitive load, safety, and pedagogical quality.

But you keep that logic inside your head.

You publish the boxes and lines, but not the why. Parents see titles, not functions. Teachers see their classroom, not the system connecting them to the office next door.

So people fill in the gaps with assumptions:

• Corporate parents assume schools run like Fortune 500s. (They don’t.)

• Teachers assume everyone knows what a coordinator does. (They don’t.)

• Admin assumes the rationale is obvious. (It never is.)

The result? Your carefully designed system gets judged as bloated or inefficient. Not because it is, but because nobody designed the explanation.

Your Quick Win: The AI Role Clarity Audit

Before you try to fix the communication, you need to see where the cracks are.

You don’t need a committee for this. You need 10 minutes and this AI prompt. It acts as a mirror, showing you exactly what your job descriptions look like to an outsider.

Copy/paste this:

"I need help ensuring our school community understands why specific roles exist and what they do.

For each role listed below, generate:

• What this role does (2 sentences maximum, jargon-free)
• Why it matters to [choose: students/parents/teachers]
• One concrete example of what would break if this role didn't exist

Make the language accessible to someone with no education background. Avoid phrases like 'pedagogical leadership' or 'instructional coaching.' Use plain language that explains the actual impact.

Roles to clarify:
[List 5-8 key roles that your community finds confusing]

Context about our school:
[2-3 sentences: school type, size, location, any unique features]"

What you’ll find:

• Some roles are genuinely hard to explain (that’s a structural issue).

• Some explanations are drowning in jargon.

• Some roles create massive value that’s totally invisible to parents.

But don’t publish the results yet. Just treat it as diagnostic data for the moment.

Over the next five weeks, I'll show you exactly how to turn these insights into action.

New Series: Beyond the Org Chart

You said organizational clarity benefits everyone. You’re right.

Starting next week: a 5-part series exploring what happens when school structure stays invisible, from vendors who can’t find decision-makers to board members making policy in a vacuum.

Each includes frameworks you can implement immediately.

First post: Next Wednesday.

Coming Soon: The Clarity Sprint

The year just started, but I know you don’t have time for a course. Honestly? You shouldn’t need one.

But you do need this fixed.

That's why I'm launching The Clarity Sprint—a 60-minute team workshop based on the last five editions of practice by design. No fluff. Pick your team type (Senior Admin, Comms, or Middle Leaders & Teachers), gather your group, and walk through a systematic process to audit and redesign one critical piece of your school's communication.

The promise:

• One redesigned artifact (an email template, a clearer org chart, a policy doc—your call)

• A reusable framework you can use forever

• 60 minutes of work. That’s it.

Watch the 90-second intro:

Coming soon. I’m finalizing details now.
Format: Self-paced, video-guided workshop
Investment: $67—your support helps me keep practice by design free while creating resources like this.

Get notified when it's ready ⤵️

Why This Matters Right Now

Semester start energy is high right now. But the honeymoon phase won't last long.

This is the moment where invisible complexity starts causing friction. The new family gets frustrated because they don’t know who to email. The teacher gets annoyed because they don’t know who makes curriculum decisions. Parents start whispering about “bloat.”

You can spend the next four months defending your structure. Or you can spend 60 minutes redesigning how you communicate it.

The world outside your gates is uncertain enough. Let’s make sure the world inside them makes sense.

Run the audit. See what you find. And come back next Wednesday, because we’re going deeper.

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

If I asked to see your school’s communication system, you would invariably show me an Org Chart.

You’d show me tidy boxes and straight lines. The Principal connects to the Assistant Principal. The AP connects to the Department Heads. The Heads connect to the Teachers.

It looks logical. It looks organized.

It is also a lie.

That chart shows who reports to whom. It does not show who talks to whom.

Real schools don’t operate on reporting lines. They operate on conversations.

The Grade 3 teacher doesn’t ask the network manager for IT help; they ask the tech-savvy teacher next door.

Parents don’t check your website for updates; they check the WhatsApp group run by that one influential dad.

New staff don’t read the handbook; they ask the person sitting at the desk across from them.

Over the last four weeks, we’ve learned to design clear messages (emails, newsletters, policies). But even the perfect artifact fails if it travels down a broken road.

Today, in the final piece of this clarity puzzle, we zoom out, because crafting the message is only one part of a bigger system.

The Shift: From Broadcast to Network

We tend to think of school communication as a broadcast:

I speak ➔ You listen.

But effective communication is actually a network:

I signal ➔ You receive ➔ You interpret ➔ You act.

When we treat communication as a broadcast, we obsess over our output. Did I hit send? Was the grammar correct?

When we treat it as a network, we obsess over the connection. Did it reach the right node? Did it trigger the right response? And if it failed—where did the breakdown happen?

To answer these questions, we need a holistic view of the entire system. That’s where Network Mapping comes in, a human-centered systems thinking tool that reveals not just where information goes, but where it gets stuck, distorted, or lost entirely.

Seeing the Invisible: Two Examples of a Broken Map

A network map is a diagnostic tool. It shows the difference between how you think your system works and how it actually works. You plot the official channels alongside the real ones. You trace where information should flow versus where it actually travels. And most importantly, you identify the gaps—the missing handoffs, the competing messages, the nodes that exist in your head but not in practice.

Let me show you what this looks like in action, with two communication breakdowns I’ve personally seen in schools.

Example 1: The Admissions Handoff Failure

This map visualizes the “Day One Ambush.”

The Admissions Director is busy managing applications and making promises to prospective parents. The Learning Support/EAL Coordinator is fielding unexpected needs from teaching faculty who suddenly have a student requiring resources they weren’t told about. Meanwhile, rumors about “easy entry” are circulating in parent WhatsApp groups.

The problem? These two people are working hard, but they’re working in silos. The crucial Capacity Check—the moment where they talk before an offer is made—is missing entirely. There’s no handoff protocol between the person making enrollment promises and the person who has to deliver on them.

What happens? A student arrives on Day One with learning support needs that blindsided the school. Parents feel misled. Staff feel under-resourced and frustrated. And the unofficial channels—those WhatsApp groups—are now shaping the school’s reputation more than any official communication ever could.

Example 2: The Drop-Off Mess

This map shows what happens when official policy meets reality.

The school sends a clear email announcement to the Parent Body and Staff Body about the updated drop-off procedures. They update the School Website with a dedicated policy page for new families. It’s all very official, very organized.

But on the ground? Completely different story. Front Office staff are giving verbal instructions to parents who arrive late. Security Guards are directing drivers with on-site guidance that may or may not match the email. Students are sharing shortcuts in their own chat groups. And the Parent WhatsApp Group is buzzing with rumors and tips that contradict the signage at the gate.

The official channels—email, website, formal announcements—are competing with the unofficial ones. And they’re losing. Because when people need information right now, they don’t check the policy page. They ask the person standing in front of them or check the group chat.

So What Do We Do About It?

These maps reveal a hard truth: you can’t fix a broken network by writing a better email.

The Drop-Off Mess isn’t solved by clearer language in the announcement. The Admissions Handoff Failure isn’t solved by better formatting in the handbook.

They’re solved by designing the connections themselves—by mapping where information actually travels, identifying the missing handoffs, and building the pathways that close the gaps.

This is what the last five weeks have been building toward. Not just better messages. Better systems.

The Grand Unification: Your Design System

Think of your school communication like a Subway System—but instead of trains and tracks, you’re designing information networks.

To get a passenger (your reader) from Point A (confusion) to Point B (action), you need five distinct elements working in harmony:

1. The Foundation: Design Principles (Week 1)

This is the Station Architecture. Proximity, Alignment, and White Space ensure the environment is navigable, not chaotic. If the station is a mess, people turn around before they even enter.

2. The Signage: Visual Hierarchy (Week 2)

This is the Wayfinding. Bold headlines and clear zones tell the passenger exactly where to look. Without it, they stand on the platform, lost in the noise.

3. The Experience: Context Awareness (Week 3)

This is the Train Design. Is it built for the rush hour commute (mobile/distracted)? If you force a desktop experience on a mobile passenger, they can’t board the train.

4. The Announcement: Plain Language (Week 4)

This is the Speaker System. Is the voice muffled and bureaucratic (”Please be advised regarding concomitant delays”), or is it crisp and clear (”Train delayed 5 minutes”)?

5. The Map: Network Thinking (Week 5)

This is the Track Layout. It ensures the stations actually connect. If there is no track between Admissions and Learning Support, the train derails.

If you miss any one of these, the passenger gets lost—not because they’re not paying attention, but because the system failed them.

That’s what those network maps revealed. The breakdowns weren’t about lazy staff or uninformed parents. They were about system design failures. Missing nodes. Competing channels. Broken handoffs.

But systems can be redesigned.

The New Standard: You Are an Architect

We started this series because you were tired of repeating yourself. You were tired of sending emails that felt like shouting into a void.

The solution isn’t to shout louder. It’s to design better.

You’re not just writing emails anymore. You’re building the pathways that make communication work.

• You use Principles to build structure.

• You use Hierarchy to signal importance.

• You use Context to respect reality.

• You use Plain Language to include everyone.

• You use Network Thinking to connect the people.

When you do this, you aren’t just communicating information. You are building trust. And trust is the only platform that can support the weight of what we do in schools.

So there you have it: you’ve learned to see the invisible. Now it’s time to build something better.

Your Final Design for Clarity Toolkit (Coming in January)

I want you to leave this series with a complete toolkit.

That’s why I’m compiling every checklist, principle, and template from the past five weeks—plus video walkthroughs—into a comprehensive Design for Clarity Course.

It will be available mid-January, right after I emerge from a short hibernation.

After five weeks of dissecting internal communications and mapping invisible networks, I’m taking my own advice and creating some serious white space on my calendar. I’m taking a break to recharge, redesign, and possibly relearn how to speak without using the word “hierarchy.” 🙃

Details January 14.

Want Help Mapping Your Network?

Network mapping is something I do as a consultant—I come into your school, interview people across departments, and map the connections that should exist but don’t.

Sometimes the clearest view comes from outside the system.

Until Then

I want to leave you with a quote recently attributed to Charles Eames (of the famous Eames lounge chairs and thousands of other life-changing designs). When asked about who we design for, he said:

“You design for someone you love, and it can be you.”

When you design a clear email, you are showing appreciation to your community by respecting their time.

When you design a clear system, you are showing appreciation to your future self by reducing the chaos.

Thank you for reading, for caring, and for doing the hard work of making complexity clear. Here’s wishing you and yours joyful and connection-filled holidays ahead. 🕯️✨

Systematically (and seasonally) 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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

By now, you’ve built messages that look clear and fit real contexts.

In Part 4, we’ll focus on the words themselves, because clarity isn’t just visual; it’s linguistic.

You probably didn’t become an educator to spend your evenings decoding your own emails.

Yet it happens all the time.

A parent writes back: “So… what exactly do we need to do?”

A student submits half the assignment: “I wasn’t sure what part counted.”

A colleague admits they missed a detail: “Sorry, I didn’t understand that section.”

You reread your original message and think, It’s right there!

But to your reader, it wasn’t obvious.

A reason for this is that we write the way school taught us to write: dense, polite, “professional.”

We aim to sound competent and end up sounding complicated.

It’s not a lack of effort.

It’s that no one told us simplicity is a service.

The Plain Language Promise

Plain language isn’t the opposite of intelligence; it’s the expression of empathy.

It says: I’ll do the mental work so you don’t have to.

When you write plainly, you make knowledge portable.

Everyone—from your ELL families to your board members—can act on the same information without extra translation.

And the research backs this up: A 2020 study by Labrador and BVA Group found that readers are 38% more likely to understand text written in plain language compared to traditional “professional” writing. That’s not a minor improvement; that’s the difference between comprehension and confusion.

The benefits ripple:

• Fewer clarification emails

• Fewer missteps

• More trust in leadership

This is how communication stops feeling like complexity control and starts feeling like capacity building.

How to Get There

1 — Adopt the Plain Language Promise

Post this above your desk or share it with your team:

✅ Students can follow directions the first time.

✅ Parents understand what their child needs to do.

✅ Staff don’t need a decoder ring.

✅ Criteria are clear enough for students to self-assess.

If a message fails one of those, it’s time to rewrite.

2 — Follow Five Micro Rules

Use active voice.
“Submit the form by Friday” beats “Forms should be submitted by Friday.”

Active voice helps the message stay clear and easy to read, according to the federal Plain Language Guidelines.

Shorten sentences.
Aim for 8–16 words. Long sentences hide meaning in the middle.

Prefer specific verbs.
Bring, sign, upload > engage with, facilitate, explore.

Sequence clearly.
Use numbers: 1 → 2 → 3. Readers can see progress.

Explain jargon once in six words or fewer.
(”Formative assessment = practice feedback, not grades.”)

3 — Combine Plain Language with Visual Hierarchy

Remember the visual hierarchy principles from Part 2? Plain language makes them work even better.

Here’s the powerful connection: Visual hierarchy shows what matters. Plain language makes it understandable.

You can create perfect visual emphasis on a deadline—bold, isolated, impossible to miss—but if the words say “kindly ensure timely submission of requisite documentation,” nobody knows what to do.

Conversely, you can write crystal-clear instructions in active voice, but if they’re buried in paragraph eight with no visual emphasis, nobody will find them.

The magic happens when you combine both:

Visual hierarchy = Shows where to look
Plain language = Makes it instantly understandable when they get there

Digital.gov’s plain language design guidelines emphasize this integration: “Legible and well-organized writing is easier to understand than traditional styles.” They recommend combining clear word choice with strategic design elements.

For instance, when you use tables to show complex relationships, you’re using visual design to support plain language. Instead of writing:

“Students in grades 3-5 should complete 30-50 minutes of homework on week nights, while students in grades 6-8 should complete 60-90 minutes, and high school students should expect 90-120 minutes depending on their course load.”

You create a table with clear labels and simple data:

The table provides visual hierarchy (you can scan to find your grade level). The plain language makes each cell immediately understandable. Together, they create instant clarity.

4 — Apply It Where It Hurts Most

Classroom instructions

Before:

“Students are expected to engage with the provided resources and demonstrate understanding through completion of the attached task.”

After:

Assignment Steps:

1. Watch the short video

2. Answer three questions below

3. Submit your answers by Friday

Parent updates

Before:

“We kindly request that all parents ensure timely submission of the medical form required for participation in upcoming activities.”

After:

Action needed: Send your child’s medical form by Wednesday so they can join the field trip.

[Link to form]

Questions? Reply to this email.

Leadership communication

Before:

“Our intent is to implement a phased approach contingent upon resource availability.”

After:

“We’ll roll this out in two phases once resources are ready.”

Why It Works

The human brain wants closure: What is this? What do I do? When is it due?

Plain language answers those three questions before the reader has to ask.

It also changes tone.

Simple words read as friendly, not flat.

Your audience feels that you’re talking with them, not at them.

And here’s the beautiful part: plain language requires no special design skills. You already know how to talk to people clearly in conversation. Plain language just means writing the way you’d explain something face-to-face.

A Quick Self-Check

After drafting, read your message aloud.

If you need to inhale halfway through a sentence, it’s too long.

If any word makes you sound like policy instead of person, replace it.

If you wouldn’t say it out loud to a colleague or parent, rephrase until you would.

What’s Coming Next

Design as Conversation — Mapping the Network

You’ve learned to design individual messages (visual hierarchy, context awareness, plain language). Next week, we’ll zoom out to see how all your messages work together as a coherent conversation across your entire school.

The complete Design for Clarity mini-course—with video walkthroughs, interactive templates, before/after libraries, and implementation tools—will be available at the end of this series for those who want the full system.

Share practice by design

Your Experience

Which phrase or habit do you catch yourself overusing—something that sounds professional but confuses people?

To me, it’s the word “concomitant.” It’s a common word in my native Portuguese, but I always find that people give me a quizzical look when I say it in English! (Turns out “at the same time” works just fine.)

I’m always curious and could use more examples. Hit reply and share!

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

Last week, we talked about visual hierarchy and how it controls how people experience the messages we write and send.

This week, let’s dig deeper into something that undermines even the best-designed message: context.

Your head of school sends an urgent update at 4:47 PM.

You’re in the grocery store parking lot. Kids are arguing in the backseat. You open the email on your phone.

A spreadsheet. Seventeen columns. Font size: microscopic.

You pinch. You zoom. You scroll sideways trying to follow a single row across your screen. You accidentally tap a link. You’re now on a different website. You navigate back. The email reloads at the top.

The kids are now physically fighting. You give up.

Three days later, you’re in a meeting where everyone’s discussing the urgent changes. Everyone except you, because you never actually read past column three.

Sound familiar?

You’ve probably sent the exact same type of email.

The Great Context Disconnect

We have a fundamental mismatch in schools. We create communications in one context (seated, focused, large screen, quiet office) but they’re consumed in completely different contexts (standing, distracted, small screen, complete chaos).

It’s like preparing a gourmet meal and serving it on a roller coaster.

The Interaction Design Foundation calls this “context-aware design”—creating communications that work not in ideal conditions, but in the actual conditions where they’ll be encountered.

And those actual conditions? They’re messier than we want to admit.

The Mobile Majority Reality Check

Let me share some numbers that should fundamentally change how you create every piece of school communication:

Between 50-60% of email opens come from mobile devices in 2024. Not eventually. First. Almost 60% of people check their emails first thing in the morning on their phones.

Researchers found that average attention spans on screens dropped from two-and-a-half minutes in 2004 to just 47 seconds by 2020. That’s total. For everything they do on that screen.

Our lived experience in schools allows us to affirm that parents overwhelmingly check school communications on mobile devices first, not desktop computers.

We’re designing for the exception, not the rule.

The Three Contexts That Control Comprehension

Over my 15+ years in international schools, I’ve observed my fair share of community members interacting with school communications. That’s students, parents, staff and administrators.

I’ve identified three context factors that determine whether your message gets through:

Context Factor 1: The Device Dictatorship

Phone readers see 30-50 characters per line in portrait mode. They scroll vertically. They tap, not click.

Tablet readers see 50-80 characters per line depending on orientation. They might be in portrait or landscape. They’re often multitasking with other apps.

Desktop readers see 60-75 characters per line in well-designed emails. They have multiple tabs open. They’re probably at work.

Same message, three completely different experiences.

Context Factor 2: The Attention Competition

The average American checks their phone 205 times a day according to this recent article by reviews.org. Mobile readers aren’t just reading on a smaller screen; they’re reading on a device literally designed to interrupt them.

While reading your email, the average phone user receives:

• 2-3 notifications from other apps

• 1-2 text messages

• Multiple badge updates

• Possibly an actual phone call

Your carefully crafted message is competing with their entire digital life.

Context Factor 3: The Environmental Reality

Desktop reading happens in relatively controlled environments. Mobile reading happens while walking, while watching TV, and in transit.

You’re not competing for attention: you’re competing for attention fragments.

The reality is that people only scroll down emails and webpages if they have a reason to.

The Nielsen Norman Group (NN/g) has insightful research on this scrolling behavior:

The Hidden Cost of Context Blindness

When we ignore reading context, here’s what actually happens in schools:

The Permission Slip Panic
Field trip tomorrow. Permission slip attached as PDF. Parents can’t open PDFs easily on phones. Frantic morning scramble for paper copies.

The Schedule Change Confusion
Complex schedule changes presented in a table. Looks perfect on desktop. Completely unreadable on phones. Parents show up at wrong times.

The Policy Update That Nobody Read
New homework policy explained in detail—in paragraph eight of a dense email. Mobile readers never scroll that far. Teachers field questions all semester.

The Board Meeting Mystery
Important board documents attached as multi-tab spreadsheets. Board members trying to review on iPads during commute. They arrive unprepared, meeting runs long, decisions delayed.

The Mobile-First Method That Works

Here’s a systematic approach that ensures your communications work everywhere:

The Progressive Disclosure Pattern

Think of your message like an accordion, not a novel:

Line 1: The absolute essential (what/when/action needed)
Lines 2-5: Critical context (why it matters, who’s affected)
Lines 6-15: Supporting details (how it works, what to expect)
Link to more: Complete information (full policy, detailed instructions)

Each level works independently. Readers can stop anywhere and still have something useful.

The Thumb-Friendly Format

Design for one-handed phone use:

• Links and buttons: Minimum 44x44 pixel tap targets

• Line length: 50-60 characters maximum

• Paragraph length: 2-3 lines on mobile (about 50 words)

• Spacing: 1.5x line height minimum

• Font size: 16px minimum for body text

The Scan-and-Go Structure

Mobile readers scan in an F-pattern. Put critical information:

• In the first two words of headlines

• At the beginning of paragraphs

• In short, bulleted lists (not long sentences)

• Before any “Read more” links

Context-Aware Templates You Can Use

The Emergency Alert Formula

WHAT: Snow day - School closed
WHEN: Tomorrow, Tuesday Dec 5
ACTION: No action needed

Details at: [school website]
Questions: [phone number]

The Event Announcement Structure

Science Fair - Thursday, March 10, 6 PM

WHERE: Main Gym
WHO: Grades 3-5
BRING: Your curiosity!

[REGISTER HERE - big button]

Full details: [link]

The Policy Update Framework

NEW: Homework Policy Starting Jan 8

KEY CHANGE: 
Max 10 minutes per grade level

MEANS FOR YOU:
- Grade 3: 30 min max
- Grade 4: 40 min max  
- Grade 5: 50 min max

Full policy: [link]
Questions? Reply to this email

Your Move This Week

Take your most important regular communication—the one that absolutely cannot be misunderstood.

Monday: Write it as you normally would.

Tuesday: Apply the progressive disclosure pattern. Rewrite with mobile line lengths.

Wednesday: Test on three devices in realistic conditions (standing, one-handed, distracted).

Thursday: Revise based on what failed during testing.

Friday: Send it and track questions. I guarantee you’ll get fewer confused responses.

What’s Coming Next

The Words That Work

You’ve built visual hierarchy. You understand context. But what about the words themselves?

Next week, we tackle plain language—how to write so clearly that comprehension becomes automatic, regardless of reading level or native language.

The complete Design for Clarity mini-course—with video walkthroughs, interactive templates, before/after libraries, and implementation tools—will be available at the end of this series for those who want the full system.

Share practice by design

Your Experience

I’d love to know if this resonates with you. Reply with your context test results. What surprised you? What are you changing immediately?

I read every message—sometimes on my phone while walking my dog! 🙃

Systematically yours,
G

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.

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Where We Are

Last week, we talked about the five design principles and how journey mapping reveals where communication breaks down.

This week, let’s dig deeper into the principle that controls how people experience every message you send.

You’re sitting in that department meeting. The chair projects slide three of twenty-seven.

It’s a wall of text. Twelve bullet points, all the same size, all the same weight.

Your eyes scan for something—anything—to anchor to. Nothing stands out. Everything competes for attention. So you check your phone under the table.

By slide seven, you’ve retained exactly zero information.

Later that day, the uncomfortable realization hits: this is exactly how parents feel reading your newsletters. How teachers experience your policy updates. How students navigate your assignment instructions.

The problem isn’t that people don’t want to pay attention. It’s that when everything screams for attention, nothing gets heard.

The Science Behind the Scanning

Here’s what actually happens in your brain when you encounter a wall of undifferentiated text: your cognitive processing slows to a crawl.

Our brains process visual information far more efficiently than text, but only when that visual information has clear structure.

Without visual hierarchy, your brain treats every element as equally important, forcing it to evaluate each piece individually.

It’s exhausting. And exhaustion leads to one predictable outcome: disengagement.

The reality is that visual hierarchy controls the delivery of the experience. If you don’t know where to look, it’s almost impossible to extract meaning quickly…and in our attention-starved world, “quickly” is all you get.

But here’s the insight that changes everything: you already know how to create hierarchy. You do it every time you teach or deliver a presentation.

The Hidden Hierarchy You Already Use

Think about it: every successful lesson you’ve ever taught used visual hierarchy, just not on paper.

Watch yourself next time you’re explaining something complex to students. You naturally create hierarchy through the following:

Volume shifts: raising your voice for key points, dropping to a whisper for emphasis.

Temporal spacing: those strategic pauses that make students lean in.

Physical positioning: moving to different parts of the room to signal topic changes.

Gestural emphasis: those hand movements that underscore critical concepts.

Visual hierarchy is simply the written equivalent of what your body and voice do naturally. The question isn’t whether you can do it: it’s whether you’re translating that instinct to the page.

The Hierarchy Equation That Makes a Difference

After analyzing—and personally producing—thousands of school communications, I’ve identified a simple equation that works:

Impact = Size × Contrast × Isolation

Let me break it down with real examples:

Size alone isn’t enough. A large headline in a sea of other large text? Still invisible.

Contrast without purpose confuses. Five different colors competing? That’s visual noise, not hierarchy.

Isolation amplifies everything. One bold deadline surrounded by white space? Impossible to miss.

The most effective school communications use all three multipliers. And you don’t need to be a designer to do this.

But here’s another reality: even when we know the equation, we still fall into the same predictable traps. I see them everywhere, and I’ve been guilty of them myself.

The Democracy Trap
Treating all information equally because you don’t want anything to feel “less important.”

Result: nothing feels important at all.

The Highlight Hysteria
Using bold, italics, underlines, colors, and CAPS all in the same document.

When you emphasize everything, you emphasize nothing.

The Bury-the-Lead Syndrome
Putting critical information after context, explanation, or pleasantries.

Mobile readers never make it that far.

The Wall-of-Text Intimidation
Dense paragraphs that look like work to read.

People’s brains literally rebel against these visual blocks.

The Footnote Fallacy
Putting essential information in small print because “it’s just details.”

If it’s essential, it shouldn’t be microscopic.

So how do we avoid these traps? Stop thinking about individual elements and start thinking in zones.

The Three-Zone System for Instant Clarity

Instead of thinking about hierarchy as a complex design principle, think of your communication as having three zones:

Zone 1: The Glance Zone
This is what people see without trying. It should contain only what matters if they read nothing else. In a 5-second drive-by reading, what must they know?

For schools, this is usually: deadlines, cancelled events, safety information, or required actions.

Zone 2: The Scan Zone
This is what people see when they’re interested enough to look closer. It provides context for Zone 1 and helps them decide whether to fully engage.

Think: brief explanations, key benefits, or simple next steps.

Zone 3: The Study Zone
This is for people who need complete information. They’ve committed to reading, so you can include details, background, and comprehensive instructions.

But here’s the crucial part: Zones 2 and 3 should never be required to understand Zone 1.

A Practical Toolkit You Can Use

The Headline Audit
Pull up your last five emails. Can someone understand the main point by reading only the subject lines and first lines? If not, you’re burying your lead.

The Squint Test
Display your document and squint until it’s blurry. The elements that remain visible are your true hierarchy. If everything blurs together, you have no hierarchy.

The 5-Second Challenge
Show your communication to someone for exactly 5 seconds. Take it away. What do they remember? That’s your actual hierarchy, regardless of what you intended.

The Highlighter Method
Print your communication. Use three highlighters:

• Pink for “must know even if reading nothing else”

• Yellow for “helpful context”

• Green for “reference details”

If you have more than 15% pink, you’re trying to make too much “critical.” If you have no pink, you’re not prioritizing at all.

Your Move This Week

Choose your most problematic recurring communication. Apply this three-step hierarchy makeover:

Step 1: Identify Your One Thing
If people remember only one element, what should it be? Make that element at least 3x larger than anything else.

Step 2: Create Breathing Room
Add white space around your critical element. Think of it as a spotlight—the empty space makes the important content shine.

Step 3: Reduce Everything Else
Demote non-essential elements. Smaller size, lighter color, or move to Zone 3. Be ruthless. Your clarity depends on it.

What’s Coming Next

When Perfect Design Meets Phone Reality

You’ve mastered hierarchy. But what happens when your beautifully designed email gets opened on a phone in a noisy Starbucks?

Next, we dive into context: why 78% of your carefully formatted messages are failing on mobile, and how to fix it.

The complete Design for Clarity mini-course—with video walkthroughs, interactive templates, before/after libraries, and implementation tools—will be available at the end of this series for those who want the full system.

Share practice by design

Your Experience

What’s the worst hierarchy disaster you’ve encountered in school communications? That document where you literally couldn’t figure out what mattered?

Reply and tell me about your hierarchy transformation this week. Send me your before/after. I love seeing these transformations in action!

Systematically yours,
G

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.

You know that deadline is in there somewhere. Was it paragraph two? Or five?

Eventually, you give up and send a message: “Quick question about that deadline...”

Then you realize: if you can’t find it, what about everyone else?

The moment you’re on the receiving end of unclear communication, everything shifts. Suddenly you start seeing design differently.

I’m writing this from Hanoi 🇻🇳, where I’m drinking Vietnamese coffee strong enough to power a motorbike (and trust me, there are about 5 million of those weaving around me right now). The pace here makes Bucharest look like a meditation retreat!

I’m here leading marketing for Learning2 Worldwide, working alongside this incredible team to bring together educators from across Asia.

And here’s what spending time in this beautiful, complex city has reminded me: when dozens of educators descend on a conference, the communication principles that keep everyone on track are exactly the same ones that would fix your overwhelming inbox.

This week kicks off a five-part mini-course I’ve called Design for Clarity—and by the end, you’ll have a complete system for designing communication that actually works for everyone.

Each week, I’ll share one core strategy you can implement immediately.

At the end of the series, the complete course (with video walkthroughs, interactive templates, and implementation tools) will be available for those who want the full deep-dive.

🎧 Prefer Audio?

Here’s a human-recorded audio version with Chief Voice Officer Kirk McDavitt. Hit play, or keep reading below.

Practical Design for Everyday Communication

And What I Mean By “Design”

By “design,” I mean the principles that make information findable, understandable, and actionable—even when your reader is distracted, tired, or reading on a cracked phone screen while dodging motorbikes. (Too specific? Maybe.)

You already use these instinctively when you teach or host workshops.

You pause on important points.

You underline key terms.

You organize the board so your learners can follow.

Design principles just translate that teaching instinct into written communication, so your emails, assignments, and reports work as clearly as your lessons.

Here’s What Happens When Design Breaks

Teachers reread your weekly update twice and still miss the deadline.

Students submit incomplete work because they couldn’t find the requirements.

Parents email asking questions you just answered, because the information was buried in paragraph four.

You end up answering the same question over and over, wondering why no one reads carefully anymore.

But they are reading. They’re just scanning for signals.

And when every line looks equally important, their brain treats it all equally: as background noise.

Five Principles That Fix This

The best part? They work for everything, whether you’re writing to students, parents, staff, or your board.

Principle 1: Proximity
Related information lives together

Think about what happens when you scatter related details across a page. Your reader has to hold multiple pieces in memory while hunting for connections. Their brain is working overtime just to piece together what belongs with what.

That creates cognitive load, and that mental effort is the enemy of clarity.

Principle 2: Hierarchy
Most important information is most prominent

Here’s the reality: your reader’s eye is always looking for patterns, always asking “what matters most here?”

Hierarchy answers that question visually.

When you make critical information impossible to miss—through size, weight, color, or position—you’re guiding their eye exactly where it needs to go.

Principle 3: Repetition
Consistent patterns create familiarity

When you use the same structure every time—same email format, same assignment template, same board report layout—something interesting happens.

Your readers stop spending mental energy figuring out your format. That energy goes straight to understanding your actual content instead.

Principle 4: Contrast
Important things stand out from routine things

You’ve probably noticed this yourself: when everything is bold, nothing is bold.

Contrast is what helps your reader distinguish urgent from routine, required from optional, action from context. But it only works when you save strong contrast for what genuinely deserves that level of attention.

Principle 5: White Space
Intentional emptiness improves comprehension

White space isn’t wasted space—it’s breathing room.

It groups related information together, separates different ideas, and keeps your page from feeling overwhelming. Think of it as the visual pause that helps your reader process what they’re seeing.

Before and After: Watch These Principles Transform an Assignment

Here’s what we often see:

BEFORE:

Welcome to Unit 3! For this project you’ll research one historical figure from the time period we’ve been studying and create a presentation. The presentation should be 5 slides and you’ll present it to the class for 3-5 minutes. Make sure to include a works cited page with at least 3 sources. The due date is Monday, March 10 by 11:59 PM. If you want extra credit you can interview a family member about how this historical figure influenced their life or create a timeline of major events. The rubric is attached at the bottom of this page. If you need help, come to the homework help room on Tuesdays from 3-4 PM.

What’s wrong here? Proximity, hierarchy, white space, contrast—not good.

Requirements are tangled with suggestions. The due date is buried mid-paragraph. The rubric reference gets lost at the end.

And what happens for the learner? They scroll, they get confused, they give up, they plan to ask tomorrow, then they forget, and finally, they submit incomplete work.

And you’re once again frustrated, wondering why they can’t just follow directions.

Now let’s redesign it:

AFTER:

UNIT 3 PROJECT — RESEARCH PRESENTATION DUE: Monday, March 10 by 11:59 PM

WHAT YOU MUST DO:

— Research one historical figure from our unit

— Create 5-slide presentation

— Present to class (3-5 minutes)

— Submit works cited page with 3+ sources

— Full rubric: [link]

OPTIONAL EXTENSIONS:

— Interview family member about this figure’s influence

— Create timeline of major events

NEED HELP?

Homework Help Room: Tuesdays 3-4 PM

So, what changed?

Proximity: Related requirements are grouped together: all the must-dos live in one section, all the optional stuff in another.

Hierarchy: The due date is impossible to miss. It’s at the top, it’s bold, and your eye lands there immediately.

Contrast: Required vs. optional is crystal clear. No more students doing the extensions and skipping the actual requirements.

Repetition: Make this the template for every assignment. Learners know exactly where to look for what they need.

White space: Everything has room to breathe. Your eye can process one section before moving to the next.

The result? Learners understand in 15 seconds instead of 3 confused minutes.

But First: You Need to See Where Clarity Breaks Down

Before you can apply these principles, you need to diagnose where your current communication is failing. And I have a powerful mapping technique to recommend: Journey Mapping.

Journey mapping shows you your reader’s step-by-step experience, including every emotion and obstacle along the way.

But first, let me show you what journey mapping actually looks like in practice.

The Nielsen Norman Group (NN/g) has a great explainer on journey mapping fundamentals:

(If you’re not familiar with NN/g, they’re the gold standard for user experience research—because your community members are users of your communication systems.)

Now here’s how to adapt this for school communication:

1. Pick one specific communication (weekly email, assignment template, board report)

2. List every step your reader takes to find information or complete a task

3. Note how they feel at each step (confident? confused? frustrated?)

4. Identify where negative emotions appear

5. Put AI to Work: Once you’ve identified pain points, use AI to help you brainstorm solutions.

Those negative emotions reveal design problems you can fix with the five principles we just discussed.

For example, if your journey map shows teachers getting frustrated at Step 3 (”Scroll through email to find link to form”), that’s a proximity problem—the link should live right next to the instruction, not three paragraphs later.

If it shows parents feeling uncertain at Step 2 (”Figure out which date applies to my child”), that’s a hierarchy problem—the most relevant information isn’t prominent enough.

Your Move This Week

Journey map one communication you send regularly.

1. Pick something—a weekly email, assignment template, board report

2. Recruit three actual readers.

3. Watch them try to find three pieces of information. Time them. Note where they struggle.

4. Then ask yourself: which of the five principles would fix each friction point?

To help you get started, I’ve created a Journey Mapping Quick Start Guide that’s easy to share with colleagues so you can work together on this.

Download the Toolkit

What’s Coming Next

This is just one piece of the puzzle. Over the next four weeks, we’ll build on these five principles—exploring how to make them work in real school contexts, how to implement them across your communication systems, and how to get your team on board without adding to anyone’s workload.

Next week: Part 2 — Visual Hierarchy: Making Priority Obvious at a Glance

The complete Design for Clarity mini-course—with video walkthroughs, interactive templates, before/after libraries, and implementation tools—will be available at the end of this series for those who want the full system.

For now, go map one journey! You’ll be amazed what 15 minutes of observation reveals.

Your Experience

Have you ever journey-mapped a communication process? Or caught yourself on the receiving end of a confusing email and thought “there has to be a better way”?

Hit reply and tell me what you discover when you watch real people interact with your communication. I read every message.

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.

Watch the 6.5-minute version, or keep reading

(This is a good one to share—forward it to someone who’s been wrestling with robotic AI outputs.)

Where We Are

A head of school uses ChatGPT to compose the weekly memo for parents.

The result is grammatically perfect but entirely forgettable.

She sighs, concluding that AI can’t capture her school’s unique voice.

But it can.

The problem isn’t the AI; it’s how we prompt it. We often use AI like dull scissors, hoping for precision but settling for mangled output.

Why Most AI Prompts Produce Robotic Results

Most of us use AI like a vending machine: “Write an email about spirit week.” “Create a parent survey.” “Draft a staff memo.”

Press button, get output.

And that’s exactly what we get: functional, forgettable, and robotic results.

But if you treat AI less like a task-taker and more like a communications partner, it starts producing work that actually sounds like you. No complex prompts required. Just a shift in how you frame what you need.

The shift? Think like a designer instead of a task manager.

What Designer Prompting Actually Delivers

Designer prompting applies the same human-centered thinking you’d use when briefing a new hire, focusing on people, feelings, and context rather than just deliverables.

Here’s what changes:

Fewer revisions: Better prompts mean less back-and-forth editing.

Consistent voice: AI that understands your tone produces communications that sound authentically yours.

Faster creation: When AI grasps your context, content happens with less effort.

The Five Principles of Designer Prompting

So what does designer prompting actually look like?

Instead of listing requirements, you describe the experience you want to create.

Instead of specifying outputs, you paint the scene:

• Who’s reading this?

• What are they feeling?

• What do they need?

Here are five principles that make this shift concrete, turning vague AI into a communications partner that gets your school.

Principle 1: Start with Feeling, Not Features

Before you mention format or length, define the emotional energy.

Instead of: “Write a message about the new homework policy.”

Try: “Write a message about our new homework policy. It should feel like a calm, confident conversation—not defensive, not apologetic. Warm but authoritative.”

AI tools are surprisingly good at capturing tone when you give them an emotional target.

Principle 2: Design the Scene, Not Just the Output

Describe what happens when someone encounters your communication.

Instead of: “Create a staff memo about the crisis protocol.”

Try: “When teachers read this, they should immediately know: what changed, why it matters for their classroom, and what to do in the next 24 hours. After reading, they should feel more prepared, not more anxious.”

You’re designing a reading experience, not just delivering information.

Principle 3: Prompt for Behavior

Design for completion behavior and emotional response.

For a parent survey: “The survey should feel quick: parents should think ‘this will take 2 minutes’ when they see it. The tone should communicate ‘we genuinely want to improve’ not ‘we’re checking a box.’”

Principle 4: Acknowledge the Emotional Moment

Map the emotional landscape first.

For standardized testing week: “Parents receiving this are probably feeling stress about their child’s performance, confusion about what scores mean, and worry about test anxiety. The email should acknowledge these feelings without dwelling on them.”

When you name the emotion, AI can write to it rather than around it.

Principle 5: Build Context Once, Use It Forever

AI has conversational memory. Use it.

Start your conversation with: “I’m the communications director at an international K-12 school with 650 students. Our communication style is warm but clear; we avoid jargon and write in short, scannable sections.”

Now every subsequent prompt benefits from this foundation.

Share practice by design

What This Looks Like in Practice

Let me show you the difference.

Task-Manager Prompt: “Write an announcement about spirit week.”

Result? Generic. Forgettable. Doesn’t inspire participation.

Designer Prompt: “Write a spirit week announcement for middle school families. It should feel like an invitation to fun, not a formal notification. Open with the most exciting theme to hook attention. Use short, energetic sentences. Close with something that makes participation feel easy and inclusive.”

Result? Completely different energy. Achieves the goal: high participation.

Same AI. Different prompt. Different result.

Your Move This Week

Pick one communication you send regularly.

Rewrite your prompt using these principles:

1. Start with feeling: “This should feel like...”

2. Design the scene: “When someone reads this, they should...”

3. Prompt for behavior: “After reading, they’ll...”

4. Acknowledge emotion: “The reader is probably feeling...”

5. Build context: “We’re a [type] school with...”

Compare the outputs. Forward both to one colleague and ask: “Which one sounds more like us?”

The difference between “make this better” and prompting like a designer is the difference between spending 2 hours rewriting and spending 10 minutes refining.

That time compounds weekly.

Your Experience

Have you tried prompting AI for school communications? What’s worked? What’s made you want to throw your laptop out the window?

Hit reply. I’d love to learn more with you.

And if you haven’t filled out that 10-second survey I sent last week, it’s still open—your input shapes what I build next. 🙏🏻

Start Survey

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.