Strong Systems Are Not More Work

Ask most school or parish leaders why nobody's written down who's responsible for what, and you'll get some version of "we don't have time." This is often said by the same person who, twenty minutes earlier, explained the exact same thing to the third staff member this month. The irony writes itself. Nobody's laughing at the time, because everyone's too busy putting out a fire they've already put out twice before.

Structure has earned a bad reputation in places that are already stretched thin, and honestly, it's earned it fair. Somewhere along the way, "let's build a process" started meaning binders nobody reads and meetings that exist mostly to schedule other meetings. People hear "system" and picture more sign-off, more committee, more standing between them and the work they actually showed up to do. Given what passes for process improvement in a lot of workplaces, that fear isn't paranoid. It's earned.

Here's the part that gets missed, though. Without structure, the work doesn't go away. It just goes invisible. Every time someone has to stop and ask who's supposed to handle this, every time a new hire spends her first two months learning a lesson three other people already learned the hard way, every time a decision sits on a leader's desk for a week because nobody else had the authority to make it, that's work. It's just unscheduled, repeating, and never gets any easier with practice, because it was never written down anywhere in the first place. A good system trades that hidden, recurring cost for a much smaller, one-time cost: somebody sits down and writes the thing down. That trade is not close.

We've watched this play out enough times to stop being surprised by it. At one Catholic school we worked with, every facilities request, a flickering light, a leaking sink, a request to move tables before a Friday event, ran through a single administrative assistant's inbox, mostly because that's just where it had always gone. She'd been at it more than a decade and carried, almost entirely from memory, who handled what, what could wait until Monday, and what needed the maintenance director's sign-off versus the principal's. It worked, right up until she took a week of vacation and three things broke at once while everyone stood around asking each other who was supposed to know. We helped the school build a one-page chart: what gets handled by whom, what needs approval, what doesn't. Requests to her inbox dropped off fast, not because anyone worked harder, but because the building's people no longer needed her memory to function. She got her inbox back. The building kept running anyway.

A parish staff we worked with had a Monday morning meeting that had quietly grown to ninety minutes with no agenda, mostly because everyone had learned that whatever didn't get said there might not get addressed until next Monday. So everything got said there, at length, including things that had nothing to do with anyone but the two people discussing them while six others waited. We swapped it for a thirty-minute meeting and a shared agenda template anyone could add to ahead of time. The meeting got shorter. The communication got better, not worse, because people stopped relying on a crowded hour to catch everything and started writing things down where they actually belonged.

Neither fix required more staff, more software, or more meetings about meetings. Both required someone sitting down once, writing down what was already informally true, and making it visible to everyone instead of just the one person quietly carrying it. That's the whole trick, and it's almost insulting how simple it is once you see it done. Good structure is genuinely boring to look at. A one-page chart. An agenda template. Nobody's framing it for the office wall. But it's the difference between an institution where things get stuck on one desk and one where the work keeps moving even when somebody's out sick, on maternity leave, or, eventually, retired to Florida.

A few ways to tell whether structure is helping or just adding weight.

• A documented process costs time once. An undocumented one costs time every single time someone has to ask, guess, or redo it.
• A good system takes decisions off people's plates that they shouldn't have had to make in the first place. It doesn't hand them new ones.
• If a new process creates more meetings instead of fewer interruptions, it isn't really a system. It's busywork wearing a system's clothes.
• The simplest version that actually gets used beats the most thorough version sitting in a drawer, every time.

This is, underneath the practical case, also an argument from stewardship. Burning out your best people on invisible, repeating work isn't a careful use of the gifts they brought to the job. A clear system is one of the more concrete ways an institution can actually take care of the people who run it. Less circling back. Less guessing. More energy left over, by Tuesday afternoon, for the parts of the work that brought people there to begin with.

Jill Wollmer

Founder, Pax Ordo Advisors · June 2026