From Burnout to Boundaries: How I Stopped Explaining it Harder and Started Leading Differently

I want to tell you about a period in my career when I was doing everything right and it wasn't working.

I was a solo emergency management director. Under-resourced, often misunderstood, and genuinely committed to building something good. Every year I made the case for what I needed. Every year I explained it clearly, backed it up with data, and made my best argument. And every year the answer was some version of no, or not yet, or we'll see.

I kept explaining it harder. It kept not working.

What I didn't understand then was that I was solving a technical problem, make a better case, get better results, when the actual problem was adaptive. It wasn't about the quality of my argument. It was about how the work was understood, how it was valued, and how I was showing up in relationship to the people who held the resources.

I didn't have that language yet. What I had was frustration.

The Workflow Study

One of my leaders finally said: do a workflow study. Show us what you're actually doing. Justify your requests.

I was frustrated. I did it anyway.

A workflow study, at its simplest, is an honest accounting of where your time goes. Not the job description version, the real version. What are you actually doing every week? What's taking more time than it should? What's falling through the cracks because there isn't enough of you to go around? What are you doing that someone else could own?

Mine wasn't elaborate. But it was honest, and it showed something important: I wasn't trying to offload my work. I was trying to build a great program with the capacity I had, and the gap between what was expected and what was possible was real and documented.

It worked. Kind of. It opened a door that explaining it harder never had.

The Meeting Matrix

Once I started looking honestly at my workflow, I turned the same lens on my calendar. I went through every recurring meeting and asked a simple question: why am I here?

Not defensively. Genuinely. What is my role in this meeting? Am I contributing or just present? Is this the best use of my time, or is this a habit nobody has questioned?

Some meetings I left. Some I restructured. Some I realized I needed to show up to differently, not as a passive attendee but as someone with a specific purpose and something to contribute.

The meeting matrix sounds like a small thing. It wasn't. It gave me back time and it gave me clarity about where my energy was actually going.

The Sustainability Plan

The workflow study and the meeting matrix fed into something bigger: a sustainability plan. If this program was going to work long term, what did that actually require? What was essential and what was noise? What partnerships needed to be stronger? What boundaries needed to be set?

I gave a presentation at a professional conference called From Burnout to Boundaries and walked through all of it. I talked about what hadn't worked first, explaining it harder, asking for the same resources every year and getting nowhere. Practitioners in the room recognized it immediately. They wanted the process. Not the theory. The actual tools.

What Changed

Here's what I want you to hear: these tools look technical. A workflow study, a meeting matrix, a sustainability plan. They sound like productivity hacks.

They aren't. Or they aren't only that.

What they did was make the work visible. They created a shared language between me and my leadership about what was actually happening and what was actually needed. They shifted the conversation from "she wants more resources" to "here is what this program requires and here is what is realistic."

But the bigger shift was in how I framed the conversation itself. Instead of coming in with my program goals and asking for engagement, I started asking: how do you want our program to look? What do you need it to do? That question created shared ownership where there had been resistance. Leaders invest in what they own.

My confidence went up. My stress went down. Things started moving forward in ways they hadn't before. Not because I had more resources, though some things did improve, but because I understood the work differently and I was showing up differently.

I was leading from a clearer sense of who I was and what I was doing. That changed everything.

The Framework Behind the Tools

It was sometime after all of this that I discovered adaptive leadership, the framework developed by Ronald Heifetz and Marty Linsky at Harvard. When I read about the distinction between technical and adaptive challenges, everything clicked into place. I realized that what I had been doing by instinct and necessity had a name. And I realized how much it could offer to other practitioners in the same situation.

That's what eventually became The Balcony Guild and the card decks. But that's a story for another post.

For now, I want to leave you with this: if you're explaining it harder and it's not working, the problem probably isn't your argument. Step back. Look at where your time is actually going. Look at what the work requires and what you're actually delivering. Make it visible, to yourself first, and then to the people who need to understand it.

That's the first move. Everything else follows from there.