📋 A Checklist Is Not a Change Plan

🚨 Nobody is arguing about whether this matters. 🚨

Background checks, emergency evacuation plans, check-in and check-out systems, abuse prevention training. Every operator I know wants these things handled properly. We work with children. The stakes are not abstract to us.

So when instructors push back on a risk management rollout, corporate teams sometimes read it as resistance to the substance. What they're hearing is frustration with the execution, and in this case the execution has a specific, diagnosable problem that has very little to do with safety and everything to do with how organizations approach hard change.

📄 What Landed in the Inbox

Condensed, here's what franchisees received:

A checklist to complete in a CRM system. Background checks for every employee over 18, using a vendor of your choosing, at your cost, renewed every two and a half years. A student check-in and check-out system meeting baseline requirements, vendor of your choosing, at your cost. An emergency evacuation plan you develop and maintain. A safety inspection. A communication escalation plan. A water sensor, if you're in the US. And mandatory annual training.

That last one is worth sitting with. For the franchisee: abuse prevention at 111 minutes, active assailant preparedness at 49, health emergencies at 31, seizures at 29, life-threatening allergies at 17, fire extinguisher basics at 13, and breathing emergencies at 12. That's four hours and twenty-two minutes. Annually. Plus every employee over 18 completes the 111-minute abuse prevention module, also annually, which the instructor administers by logging into their own single account and replaying the content for staff.

Then there's the part that changes the temperature of the whole document. Failure to complete may constitute a breach of the Franchise Agreement. Marking something complete that isn't may result in losing insurance eligibility. And insurance renewal is not automatic, so if you miss the opt-in, coverage lapses.

Four months to absorb all of it, in year one.

🧠 The Diagnosis

Ronald Heifetz, who developed the adaptive leadership framework at Harvard, draws a distinction that explains this entire situation.

A technical problem has a known solution. Someone with the right expertise can identify what needs to happen, issue instructions, and the problem gets solved. Protocol works. Procedure works. Authority works.

An adaptive challenge is different. There's no ready-made answer, and solving it requires the people involved to actually change how they work, what they prioritize, and sometimes what they believe. You cannot instruct your way through it.

Heifetz's central warning is that the most common cause of leadership failure is treating an adaptive challenge as though it were a technical problem.

That's what happened here.

Standardizing risk management across hundreds of independently owned centers is adaptive work. It requires operators to rebuild daily routines, change how families move through their space, restructure hiring, absorb new costs, and shift how they think about liability in a business most of them entered because they love teaching kids math.

The organization responded with a checklist, a deadline, and a compliance consequence. Those are technical tools. They're the right tools for a technical problem and they are almost perfectly wrong for an adaptive one.

🔍 Three Things I Keep Hearing

Each one maps to something Heifetz would have predicted.

"Tell us what to do, then help us do it." Instructors received a list of requirements and a list of vendors. What they didn't receive was guidance on how to evaluate a check-in system, what a compliant evacuation plan looks like for a 1,200 square foot strip mall unit, or how to run background checks in a province where the process differs from the US. Heifetz calls the missing piece a holding environment: enough structure and support that people can do hard work without being overwhelmed by it. A vendor list is not a holding environment.

"Four months isn't enough." Adaptive work takes longer than technical work. Always. That's the nature of the thing rather than operator reluctance. When you're asking people to change how they operate, the timeline has to account for learning time, not only execution time.

"We need to talk to corporate, not just our field consultant." This is the one I'd flag hardest if I were coaching this team. Field consultants are being asked to carry a message they didn't design and can't fully explain. That's an unfair position for them and an unsatisfying one for instructors. When change is this significant, the people who made the decision need to be in the room at least once.

🤐 The Missing Sentence

One paragraph would have changed how this landed, and it never got written. The paragraph that answers why now.

The document says the risk landscape is evolving and standards are maturing. That's true and it's also the kind of sentence that could have been written in any year, about any industry, by anyone.

Sweeping risk management overhauls with compliance teeth attached do not typically emerge from a general sense that standards should improve. Something usually prompts them. An incident, a claim, an insurer conversation, a legal exposure that became suddenly concrete.

I don't know what prompted this one. Neither does anyone else in the network. And that's the actual problem, because when an organization doesn't explain what changed, people fill the silence themselves. Instructors are trading theories right now. Some of those theories are probably wrong. All of them are less useful than whatever the real answer is.

I wrote a whole post about this pattern a while back. Organizations stay technically honest while avoiding the thing everyone senses. Here, the avoidance has a cost that's easy to measure: an operator who understands the urgency will move faster than one who thinks they're being handed paperwork.

There's almost always a version of the truth that legal can live with. "Recent experience across the network made clear that our standards needed to be more consistent" concedes nothing and explains everything.

⚖️ The Liability Language Problem

Some version of the franchisee is solely responsible appears six times in this document. Alongside it: KNA does not supervise or direct, does not constitute inspection or approval or control, does not undertake or assume any duty to ensure safety, does not employ or supervise or control center personnel, assumes no responsibility for vendors, does not assume liability for operations.

Every one of those sentences is doing legitimate legal work. Franchisors have to maintain the independent contractor relationship or they inherit liability they can't manage. I'm not naive about that.

But read it as an operator reads it, in one sitting, in the same document that's telling you to complete eight work streams in four months or risk breaching your agreement.

The message that comes through is: do all of this, at your cost, and understand that if something goes wrong we were never involved.

That's a rough thing to receive from a partner. And it's fixable without changing a word of the legal content. Put the requirements and the support in one document. Put the legal framing in an appendix, or a separate memo, or the agreement itself where it belongs. Same protection, completely different experience.

💫 Today's Spark: You Can Mandate Compliance. You Can't Mandate Capacity.

An organization can require an operator to do something. What it cannot do by requirement alone is make them able to do it well, on time, and with the understanding that makes it stick.

Compliance gets you a completed checklist. Capacity gets you a network where safety practices survive past the deadline, get maintained without prompting, and protect students on a random Tuesday in March when nobody is watching.

The second one is what the organization is trying to buy. The tools it reached for only produce the first.

🔥 Ignite Action: How I'd Rebuild This Rollout

If I were coaching the team that owns this launch, here's the sequence I'd run.

✨ Final Word

Designing a risk management program across hundreds of independently owned businesses in two countries, under insurer pressure, with liability constraints shaping every sentence, is hard work. The requirements themselves are reasonable. Most of them are overdue. The gap is in the execution, and execution is the fixable part.

Instructors, a word: the substance here is not the enemy. Background checks and evacuation plans and abuse prevention training protect our students and, frankly, protect us. Push hard on timeline and support, because those asks are legitimate and worth making. Don't let frustration with the rollout turn into an argument against the requirements themselves.

And to anyone at head office still reading, the thing your operators are telling you is that they don't have what they need to do this well in the time they've been given. That's a capacity problem. Compliance pressure is the wrong response to it, because an operator who can't meet a deadline and fears the consequence will quietly mark the box and move on. You'll get a clean dashboard and an unchanged network.

The deadline is still months out. Adding a live session, a tiering plan, and a real support library between now and then costs a fraction of what a second-year re-do would.

📣 Ask your network what they need to finish this on time. Then build that, before the deadline does the asking for you.

—Tina 💫

I work with franchise organizations and leadership teams on the communication layer between corporate decisions and operator implementation. If this resonated, let's connect: tina@tandemspark.coach