
Before You Add Something New, Remove the Friction
Imagine it’s Thursday at 3:40. A teacher is entering the same information for the third time. She doesn’t complain. She’s skilled and quick. She’s also stopped asking why it has to be done three times, because she already knows: that’s just how things are done.
Most leaders walk past that moment. I think it deserves a second look, because sometimes the most supportive thing a leader can do is make the work easier to do well.
Schools are remarkably good at adding. A new initiative. A new form. A new meeting, program, expectation, data point, committee, platform, or "quick" task. Most of these are added for good reasons. We see a need and want to respond. That instinct comes from commitment.
But there is a question leaders need to ask more often: Before we add something else, what can we remove?
Because sometimes the solution to an overwhelmed system is not another support. Sometimes it is less friction.
Good intentions can still create overload.
Overload rarely happens because someone decided to make everyone's work harder. It happens gradually: one reasonable request at a time, one procedure layered over an old one, one meeting that never leaves the calendar, one initiative that never officially ended. Each addition seems manageable. Together, they create weight.
And eventually we hear it. "There just isn't enough time." "Which priority is actually the priority?" "I'm entering the same information in three places." "I'm not sure who owns that."
Those statements are not necessarily resistance. Sometimes they are data.
Friction is information.
Last week, I wrote that a workaround is information. The same is true of friction. Repeated confusion, delays, questions, duplication, and exhaustion around the same process are all telling us something.
A strong leader doesn't immediately assume, "People need to try harder." A strong leader gets curious: "Why is this so difficult to do well?"
That question moves us from evaluating only the person to examining the conditions around the person. Sometimes a performance issue really is a performance issue, and people need feedback, coaching, and accountability. But sometimes what looks like a people problem is a system problem. Before deciding someone is disorganized because they missed a deadline, ask whether the deadline was clear, whether they had what they needed, and whether three other urgent requests landed at the same time. Accountability still matters. It matters more when the system has made success reasonably possible.
There is leadership in subtraction.
Improvement doesn't always mean another strategy, training, or tool. It can look like removing a redundant form, shortening a meeting, eliminating an unnecessary approval, combining two processes, protecting uninterrupted work time, or reducing the number of priorities. It can sound like: "We are not doing that anymore."
Leaders often tell teams what to add. We rarely say out loud what they may stop doing, so people keep carrying both the old expectation and the new one. (We'll talk about clarity next week. For now, notice how often permission to stop is the missing piece.)
Sometimes the most strategic decision isn't "What should we start?" It is "What are we finally willing to stop?"
Grace can look like removing something.
We've been talking about grace. We often think of it as something one person extends to another, and it is. But grace can be structural too: simplifying a process, allowing an alternative path, removing an unnecessary requirement, or acknowledging, "This system is asking too much right now."
Grace is not the absence of accountability. It is the recognition that people sometimes need room to recover, repair, and begin again. Sometimes that means asking people to do more. Sometimes it means helping them do what matters most. And sometimes it means removing what no longer needs to be carried.
Try a friction audit.
Instead of starting your next leadership conversation with "What else should we be doing?" ask your team: Where does the work feel harder than it should?
Then listen. You might hear, "We enter this twice." "No one knows who approves that." "This meeting could be an email." "We are still doing this because we used to be required to."
Do not defend the process. Get curious. Ask what is creating the friction, what would make this easier to do well, what we can simplify, clarify, or stop, and what should remain because it genuinely adds value.
Then try Stop. Start. Continue. Stop: what are we doing that no longer adds enough value to justify the time, energy, or complexity it requires? Start: what would improve clarity, support, effectiveness, or connection? Continue: what is working well and deserves to be protected? That last one matters. Strong organizations protect what works while changing what doesn't, and that creates ownership rather than constant reinvention.
Do not automate the friction.
Technology can make inefficient systems move faster, but faster is not necessarily better. Before automating a process, ask whether it should exist in its current form at all. Otherwise, we risk becoming incredibly efficient at doing unnecessary things.
The goal is not more technology. The goal is more capacity for meaningful work, including the work we should never try to make frictionless: the conversation with a struggling teacher, the child who needs another minute, the family that needs to feel heard, the leadership decision that requires reflection rather than reaction. That is where we want human energy going. Not toward figuring out which version of the spreadsheet is the right one.
Less friction. More capacity.
Strong systems do not make meaningful work effortless. They make it possible. They reduce unnecessary confusion, protect capacity, support accountability, and leave room for grace. People are not an unlimited organizational resource, and we'll come back to capacity as a leadership responsibility in two weeks. When we protect people's attention, energy, and trust, students benefit too.
So before adding the next initiative, meeting, form, program, expectation, or tool, ask: What can we remove first?
Not because we expect less. Because we want people to have enough capacity to do the most important work well. That is not lowering the standard. That is designing for success.
That is the work of a Heartbeat Educator.
🌱 Protect the heartbeat.
Continue the conversation. What is one unnecessary friction point you would remove tomorrow if you could? Join us inside The Steady Schools Community and add your perspective: https://www.skool.com/bo-knowz-learning-7950/about
Sometimes the first step toward a steadier system is simply naming what no longer needs to be so hard.
