The Site Coordinator Overlay

Downloads for The Manager Hat.

Two after-school programs with equally talented staff — yet one flows and one scrambles. The difference isn’t the people; it’s the systems underneath them. This overview introduces the first of the four hats: the Manager takes care of the “stuff” — schedules, supplies, spaces, data, logistics — because a Manager doesn’t manage people, a Manager manages the environment in which people succeed. It maps the journey ahead (the foundational reframe, the four clusters of Manager work, and an honest caution) and names the hat’s quiet power: it’s the foundation the other three hats stand on, and what makes the Super 7 and the Elite 8 possible.

The boss who hovered over you made you less capable; the boss who set you up and got out of your way earned your best work. That’s the whole hat: you don’t manage people, you manage the environment they work in. This lesson widens the Trilogy’s “manage the space, not the children” to a whole program — making the right thing the easy thing, and building systems that pass the real test: they work even when you’re not there. Managing is upstream work — don’t bail water, fix the leak — and its payoff is freeing your people to spend all their energy on kids.

Transitions don’t break because of bad kids or bad staff — they break because of missing structure. This lesson covers the first and most visible cluster of Manager work: operations and logistics (schedules, spaces, supplies, transitions, calendar — the Super 7’s Scheduling and Rotations lives right here), keeping information moving so confusion never grows into chaos, and coordinating the events and enrichment that make a program special. The through-line is to prepare the environment in advance — prep in the calm so the day runs smooth — clearing the runway so every Team Leader can fly.

Running a program without tracking is like steering a ship with the windows painted over. This lesson builds the instruments: attendance and enrollment (including the ASES/ELO-P compliance that is often the very thing keeping the doors open and funded), broader data and reporting that let you decide wisely instead of guessing, and family communication systems that turn parents into partners. It closes with a caution — people learn to “look right to mask not being right,” so track the numbers, then read the people underneath them.

Every seasoned leader remembers the near-miss the system caught. Safety and compliance aren’t one priority among many — they’re the floor everything else stands on, and the Manager guards it. This lesson covers safety and risk management (emergency procedures, drills, and release protocols — physical, emotional, and social), compliance and documentation (the unglamorous backbone that keeps a program legal and funded), and staffing logistics and coverage — with a clear boundary: the Manager schedules and assigns staff, but developing them belongs to the Supervisor and Coach hats. The standard in this cluster is every time, no exceptions.

There’s a real difference between asking “did we get through it?” and asking “are we getting better?” This lesson builds the systems that let you ask the second question: resource stewardship (budget, purchasing, and inventory, so every dollar serves kids and you never run out by surprise) and the continuous-improvement loop that collects honest feedback and real data. It’s also the bridge to the fourth hat — the Manager builds the feedback systems; the Change Agent uses what they reveal to lead real change — because no program is ever finished.

An honest confession nearly every new leader will recognize: Manager work is concrete, satisfying, and full of clear right answers — which makes it the easiest hat to hide in. This closing lesson names the trap (you can look busy and productive buried in paperwork while never leading the people who need you), gives two honest signs you’re hiding, and reframes the whole point: great management is meant to free you from constant managing so you can supervise, coach, and lead change. Master this hat not to live in it, but so you can take it off the moment your people need another.

Downloads for The Supervisor Hat.

The bad supervisor is either absent (lets problems fester until they explode) or harsh (all criticism, no recognition); the rare good one holds the line and sees the good. This overview introduces the second hat: the Supervisor makes sure that what should be happening actually is — watching what really happens rather than what the plan said, looking for compliance (are staff doing what they’re supposed to?) and competence (can they do the basic job?), and sitting across, because across is the seat where you hold a standard. It frames supervising adults as the Trilogy pointed at grown-ups, with one real difference — transparency, because adults “look right to mask not being right” — and names the hat’s signature balance: accountability with recognition.

You cannot supervise from behind a desk. This lesson establishes the foundation of the hat: being physically and mentally present in the program spaces — Manage By Walking Around, widened to a whole site — so you can identify the gaps between what was planned and what is actually happening. Because adults “look right to mask not being right,” it teaches watching past the surface (calm is not the same as good), solving problems while they’re still small, and being present as someone who sees everything — attention, not surveillance — so staff experience support rather than a hawk waiting to swoop.

“That discipline was rough” is an opinion — and you can’t build a growth conversation on an opinion. This lesson teaches the hardest, most important observation skill: separating what you actually saw and heard (“eight of twelve students had their heads down, directions given once”) from your verdict about it (“management was poor”). Your opinion is your compass, not your talking point — it guides where the conversation goes but stays on your side of the table — and the concrete observation is what travels to the coaching conversation, anchors the “I noticed… I wonder…” stem, and keeps you correctable if you misread.

You can’t hold anyone to a line they were never clearly given. This lesson covers setting clear expectations the C4K way — communicating what quality looks like with both examples and non-examples, aligned to program values, funders, and the California Quality Standards — then holding the line: ensuring procedures are followed, verifying documentation, and addressing non-compliance immediately and directly (firm limits, for adults). It names the Supervisor’s signature role as the bridge — making sure the Manager’s systems are actually implemented with fidelity in the real room — and reframes holding the line as the caring act, because firm and warm aren’t opposites.

A room that looks perfect from the doorway may be quiet from boredom or fear, with almost no real learning happening. This lesson is where the Supervisor hat meets the curriculum: what you’re watching staff deliver is the Nifty 9 and the Trilogy, which makes you quality control on the curriculum. It walks the four things you watch for — competency, positive-discipline oversight, transitions and program flow, and lesson delivery and engagement — and turns on the discernment the whole hat requires: seeing past “looks right” to whether real quality is present. The kids were quiet — but were they learning?

Every other expectation has room for a developing staff member to grow into over time; safety does not. This lesson covers overseeing physical, emotional, and social safety — genuine supervision of every child, proper student-release procedures every single time — and the response safety uniquely demands: immediate, and without exception. It reframes that firmness as love (you’re protecting a child, and the staff member too), and names the counterintuitive gift: when the safety line is genuinely non-negotiable, everyone relaxes and rises above it. Safety culture is caught from the Site Coordinator.

A boss who only notices what you did wrong trains you to hide; a leader who catches you doing right and also tells you the honest truth earns your best work. This lesson covers the half most supervisors skip — immediate, specific recognition, catching staff being good — and the other half, the accountability conversation, framed as positive discipline grown up: clear choices, a known next step, real and escalating consequences, up to the job not being a fit, all named without cruelty. The hard part is responding rather than reacting when a staff member pushes back — modeling the very adulthood you’re asking them to grow into.

The most important distinction in the whole overlay: knowing, and showing, which hat you’re wearing. Blur them and the staff member can’t tell whether they’re being held to a standard or supported through a struggle — and that uncertainty destabilizes them. This lesson draws the line clean: the Supervisor sits across (compliance and competence, “get it done,” where positive discipline lives); the Coach sits beside (competence and capacity, “let’s work through it,” where a person can be vulnerable). The two produce different responses by design — and the simplest way to make it visible is to let your body match your intent: across to hold a standard, beside to grow a person.

Downloads for The Coach Hat.

The person who truly helped you grow didn’t hand you answers — they asked the questions that helped you find your own, and you walked away more capable, not more dependent. This overview introduces the third hat: where the Supervisor holds a standard, the Coach grows a person. Its center is one truth — coaching is asking, not telling — and a particular seat: the Coach sits beside, on the person’s side of the table, growing both competence (the job they have now) and capacity (the deeper skills they carry to any job). It maps the journey ahead (what coaching is, the process, the six-level continuum, and the conversation) and holds one boundary throughout: you coach to strengthen a person’s practice — never the non-negotiables, which are the Supervisor’s firm line.

One helper jumps in with “here’s what you do”; the other asks “what have you tried? what might you do differently?” The first solves today and creates dependence; the second builds a thinker. This lesson establishes the soul of the hat — real coaching draws a person’s best work out rather than pouring yours in — and separates it from the sideline “coach” who simply tells. It holds the humility that keeps coaching honest (“in my experience”: what worked for you may not work for them) and the boundary that keeps it clear (coach to strengthen, never the non-negotiables), with the goal always in view: a person who can think without you.

A doctor who prescribes before examining sends you running for the door — and coaching is the same: before you open your mouth, you observe, analyze, and prioritize. This lesson teaches observing like a recording (what you actually saw and heard, not your verdict), analyzing the root cause beneath the surface (the same rough transition can spring from a planning gap, a skill gap, or a confidence gap), and prioritizing with four lenses — Impact, Frequency, Leverage, and Readiness, because growth follows readiness. It also names the handoff: the clean recording travels from the Supervisor to the Coach; the verdict never does.

Coaching everyone the same way abandons the terrified beginner and insults the ready veteran — so you match your coaching to where the person actually is. This lesson starts at the bottom two rungs: Directive (for the brand-new — you tell and direct, and what you ask for must be easy and doable today: “walk around, smile, phone in your pocket”), and Directive-Coaching (still directing, but now beginning to ask “what have you already tried?”). It’s also where two supports enter — assigning training and modules (a coach can get help), and job-shadowing done right, by first prepping the shadowed staff member to narrate their own thinking.

As a person grows into real skill, coaching becomes a two-way craft. This lesson covers the middle levels: Coaching-Directive, where you add role-play (“you be the kids”) and role-modeling (you work the room live, narrating your thinking), and Coaching — the level the hat is named for — home of “I noticed… I wonder…,” modified and formal sessions, and side-by-side coaching (they act, you guide in real time — set up in advance, and not for everyone). Across these two levels the balance tips from “watch me and let’s talk” to “you go, and I’ll wonder with you.”

You know you’ve coached well when the person stops waiting for you and starts coming to you. This lesson covers the top of the continuum: Integrating (the relationship flips — “I intend to do this; I just want to check I didn’t miss anything”) and Innovating (the person identifies their own needs and adapts the practices to their own style, sometimes improving them). Here your touch is lightest — a sounding board for someone driving their own growth — because the goal was always a person who coaches themselves. The staff you grow to self-management are your future leaders.

You can know the whole continuum and still fumble the real moment, so this lesson slows down to the conversation itself, which has a simple, portable shape. “I noticed” opens with the concrete recording (factual, nothing to defend against — which is exactly why observing like a recording matters). “I wonder what might happen if…” offers an open door rather than a command, then genuinely asks “what do you think?” and listens. Strategies are offered lightly as options, not orders, and the conversation closes by handing the reflection back — the 3-2-1: three things that resonated, two new wonders, one action this week.

In the rush of a program day you won’t be thinking about frameworks — you’ll just have a staff member in front of you and one choice: do I tell, or do I ask? This closing lesson brings the hat together: start with “what am I striving for right now?” (grow the person → Coach, beside; hold a standard → Supervisor, across), read the person’s level (abandoning a beginner or insulting an expert are both real mistakes), and hold the two humilities — “in my experience,” and observe like a recording (and if you misread, pivot). The truth that ties it together: the goal of great coaching is a person who needs less coaching — you succeed most when they need you least.

Downloads for The Change Agent Hat.

Most change we lived through as kids landed from the top, all at once, with no “why” attached. This overview introduces the fourth and final hat: where the Manager runs the environment, the Supervisor holds the standard, and the Coach grows the person, the Change Agent grows the whole system over time. Its center is the difference between transactional work (“getting through the day”) and transformational work (“getting better every day”), and the stance that makes it possible: one foot in the future and one foot in reality — the difference between an espousal (something you say you want) and an aspiration (a clear destination plus real steps you’ll pivot along). Many roads to Sacramento, but the destination doesn’t change. Done well, the payoff is Sustainable Excellence — a program that keeps improving even after you’ve moved on.

Some jobs you just keep up with — you clock in, work the list, clock out, and a year later nothing has changed. This lesson names the two kinds of work you do every day: transactional (maintaining operations — essential, but only keeping the day running) and transformational (closing the gap between what is and what could be). It names the trap — the urgent, endless transactional work quietly crowds out the important — and the leader’s first job in this hat: protecting the room to improve on purpose. A vision with no foot in reality is only an espousal; an aspiration is a clear end-in-mind plus steps you’ll pivot. Anchored to purpose, flexible on the path.

Being handed the what with none of the why is a hollow way to be led. This lesson plants the first foot in the future by getting three words straight — Vision (where we’re going), Mission (why we exist), and Purpose (why it matters) — and keeping all three alive in everyday conversation, not laminated on a wall. It teaches connecting each person’s role to the larger purpose (the same table wiped “to get it done” versus “so every child feels cared about”), setting vision with people rather than in a box (people support what they help create), and re-generating the vision, because enthusiasm fades on its own and a vision you never revisit slides back into an espousal.

We prescribe before we examine all the time — jumping to solutions before honestly looking at what’s happening. This lesson plants the second foot: current reality is evidence, not a feeling, gathered from more than one source (surveys, conversations, observations, outcomes, data) and named clearly without blame — because the moment naming reality curdles into finding someone to blame, people stop telling you the truth. It gives two frameworks for organizing what you gather: SWOT (Strengths, Weaknesses, Opportunities, Threats) as the approachable first tool, and the Double-Loop (what happened → why → what to change) for fixing the cause instead of the symptom. The third and most powerful framework, the Iceberg, gets its own lesson next.

What you notice is only the tip; most of the iceberg sits hidden beneath the water. This lesson teaches the most important first question — is this a pattern or an anomaly? An anomaly gets noted and watched, but you never rebuild systems around noise; only a genuine pattern earns the trip below the surface. When it is a pattern, you look in two layers — the systems (which are designed to produce specific results, so a bad result means a suspect system) and the mental models and beliefs of the people who built and protect them — then verify with artifacts, and pivot if you misread. Understand the behavior, don’t excuse it, and when discipline is called for, make the choices clear.

You don’t pour a foundation on sand — no matter how beautiful the house on top. This lesson is the bridge between the foot in reality and the foot in the future: before you build toward the vision, weigh the Three C’s — Compliance (what’s required by law, ed code, and funder — the non-negotiable floor), Competence (whether your people can do the work as it exists today), and Capacity (the room and energy to take on what’s next). The order matters: get compliance and present-competence solid first, then build upward with your eyes on the future. Getting the foundation right isn’t the opposite of being visionary — it’s what makes the vision possible.

Change too much, too fast — a whole new routine overnight — and it falls apart; change that lasts is paced. With both feet planted, this lesson crosses the gap between destination and starting point: designing the pathway as a clear, prioritized sequence matched to real resources, and running the Continuous Quality Improvement cycle — Current Reality → Goal → Objectives → Strategies → Tactics — with success named in observable indicators. It teaches pacing (assess readiness first; challenging but not overwhelming), reframes a pivot as learning rather than failure (so teams surface problems instead of hiding them), and offers the pearl: change needs a grain of sand, a bit of scheduled, scaffolded discomfort — with the honest exception of pulling the band-aid off cleanly when there’s no other way.

Change done to us we quietly wait out; change we own, we carry — so this closing lesson brings it home through people. The same change lands differently on the eager, the anxious, and those quietly grieving the old way, so you read your people before you push. It introduces CBT — Current Best Thinking — the best understanding you have right now, which changes as you learn, and the leader’s two jobs: knowing when to pull the trigger, and helping people see the CBT for themselves so they drive the change. It gathers the people-side moves (onboard into the why, co-create, communicate, distribute leadership, monitor impact) and then puts all four hats on at once, choosing among them with one question: “What am I really striving for?” Master all four, and you don’t just run a program — you grow one.

Five cross-hat scenarios worked right on the page — the first is a model.