I was a good executor before I was a leader.
I knew how to manage my caseload, hit my deadlines, and keep my commitments. I had systems that worked for me. I knew what was on my plate, what was coming, and what needed my attention today versus next week.
Then I became responsible for a team. And I realized, fairly quickly, that my system for managing my own work had absolutely nothing to offer me for managing theirs.
I’m Stephanie Everett. I’ve spent over two decades working with law firm leaders, first as a practicing attorney who built and ran my own firm, then as a consultant working with thousands of firms across the country. The operations gap is one of the most consistent things I see—and it almost never gets named correctly. Leaders don’t struggle with operations because they’re disorganized. They struggle because managing a team’s work is a completely different skill than managing your own, and most of them were never taught how.
Why Managing Your Own Work Doesn’t Prepare You to Manage a Team’s
When you manage your own work, the feedback loop is tight. You know what you committed to. You know when something is slipping. You feel the deadline pressure directly. Your system only has to hold one person accountable: you.
When you’re responsible for a team, every one of those things changes. You can’t feel someone else’s deadline pressure. You don’t automatically know when a commitment is quietly drifting until it’s already late. You have no idea what’s sitting on someone’s desk stalled versus moving forward unless you’ve built a way to see it.
Most leaders respond to this by asking for more updates, checking in more frequently, or staying closely involved in the work. That feels like managing. It’s actually a workaround for not having a system. And it doesn’t scale. The more people on your team, the more that approach becomes a second full-time job layered on top of the actual job.
What Managing a Team’s Work Actually Requires
Leading Operations—one of the Four Cornerstones of our Next Level Leader framework—is built around this specific challenge. It’s not about the leader executing better. It’s about building the infrastructure that lets the team execute reliably, with visibility for the leader that doesn’t require constant personal involvement.
There are five elements, and together they answer one question: how does work get done around here, and does it happen because the system makes it happen, or because you personally make it happen?
Priorities have to be explicit and shared. You know what matters most. Your team is guessing. Unless you’ve told them, specifically, and returned to it regularly enough that the answer is still current. When priorities live only in the leader’s head, every decision that requires a tradeoff must be routed through the leader. That’s not strategy; that’s a bottleneck dressed up as management.
Commitments need a visible home. When a commitment lives in someone’s notebook, or in the memory of the person who made it, it exists conditionally. When commitments are captured in a shared, visible system—who owns it, what specifically will be done, by when—accountability becomes structural rather than personal. The leader doesn’t have to remember everything. The system does.
Delegation has to be specific enough to create accountability. “Handle this” is not delegation. It’s transfer of anxiety. Real delegation answers four questions: what is the outcome, what is the timeline, what decisions can you make independently, and how and when will we check in. When those four things are clear, there’s something specific to be accountable to. When they’re not, results are unpredictable and the follow-up conversation is always awkward.
Problems need to surface early. In every firm I’ve worked with, the leaders who have the hardest time operationally are the ones who consistently find out about problems after they’ve already become crises. The solution isn’t to ask for more updates. It’s to create an environment where people feel safe bringing problems early—where raising a flag results in help, not frustration. That’s cultural as much as structural, and it starts with how the leader responds the first few times someone brings them a problem that isn’t fully blown up yet.
Meetings need to produce decisions and clear owners. Most law firm meetings are discussions. Someone talks about what’s happening, everyone nods, and everyone leaves with a slightly different understanding of what happens next. A well-run meeting ends with explicit decisions captured and specific commitments made: who, what, and by when. That’s not bureaucracy. That’s how work moves forward without the leader chasing it down individually afterward.
Why This Gap Is So Common—and So Unacknowledged
Law firms don’t teach this. There’s no moment in legal training, and no standard milestone in a legal career, where someone sits you down and says: here’s how to create visibility into your team’s work without micromanaging, here’s how to build accountability that doesn’t require your constant presence, here’s how to run a meeting that produces something.
You get promoted because you were good at your own work. Then you’re handed a team and the implicit assumption is that the skills transfer.
They don’t. And the leaders who figure this out on their own do it slowly, expensively, through years of recurring problems and the nagging feeling that their team should be performing better than it is.
The Question Worth Asking
Think about the last problem your team had that genuinely surprised you. Not a client issue that came out of nowhere, but a team execution problem. A missed deadline, a dropped commitment, a project that stalled without anyone flagging it.
Ask yourself: was there a system that should have surfaced this earlier, and didn’t? Or was there no system at all?
If the honest answer is the second one, that’s not a team problem. That’s a design problem. And it’s yours to solve.