When Growth Outruns Operations: Lessons from the Middle of the Work

After twenty-five years of building, leading, and refining operational engines, I’ve come to see a pattern that many miss.

It’s not something I’ve learned from textbooks or management theory. It’s something I’ve learned from being in the room, having hard, thoughtful conversations with people who are right in the thick of it – leaders, partners, funders, vendors, and community builders who are sometimes, quite desperately, trying to keep up with their own growth. And I’ve seen this not just from a distance, but in the day-to-day of my own work – most recently as the Vice President of Operations at the Ottawa Community Foundation.

What I’ve come to realize, again and again, is that most organizations on a growth path don’t stall because the world shifted around them. They don’t stall because the ecosystem became hostile, or the business model collapsed, or because they lacked capability or ambition. It’s almost never a failure of vision. They most often stall because their operations can’t keep pace with the very growth they worked so hard to achieve. And the painful part is that you often don’t see it coming. It feels like things are working – until they aren’t.

I’ve sat across from seasoned executives still caught in the habit of making too many on-the-go decisions. I’ve worked alongside brilliant teams where processes still live in people’s heads, where every project starts from scratch, and where external partners, vendors, and service providers are never fully brought into the fold or advised on the standards and values they are aiming to hold. And what happens is predictable. The team starts spinning. Firefighting takes over. Long-term priorities quietly dissolve into reactive to-do lists. The day-to-day becomes a race to catch up, not to move forward. Mistakes stop being opportunities for learning and start becoming opportunities for blame. Punishment creeps in. People start protecting themselves instead of building together. And what started as a purpose-driven mission quietly begins to lose its edge.

I’ve seen this play out in multiple settings – not in theoretical case studies, but in real conversations with real people. In fact, the most painful part is that I’ve seen it in some of the most thoughtful, visionary, and well-intentioned teams. Hard work isn’t the missing piece. Hustle isn’t the issue. Vision isn’t the challenge. The issue, most often, is operational discipline. And it’s easy to say but harder to build. I don’t mean it as a one-time fix. I mean a rhythm, a way of building the foundation that can actually carry the weight of sustained growth.

This is where the lessons from over twenty-five years of operational and strategic leadership begin to crystallize. Operational excellence is not a singular project. It’s not a strategic plan. It’s not a bold, sweeping change. It’s a layered build – patient and deliberate. One layer at a time. And it’s often the work least understood, least noticed, and least celebrated.

You start by bringing order to the work. Standardization is not bureaucracy – it’s clarity. There’s something deeply liberating about having one clear, shared way of doing things. It frees the team from unnecessary decision-making, from guesswork, from stepping on each other’s toes. It creates breathing room.

Then you move into systematization. You stop building everything from scratch. You let your previous work become a foundation, not a memory. You begin to weave processes together. You build systems that can talk to each other. You create flows that make sense across the organization.

Then you start to automate. Not to cut people out, but to free people up. You eliminate the repetitive work that drains time and attention. You create space for your team to focus on work that requires judgement, nuance, and care.

And then you measure. You track the right things – not vanity metrics, not performance theatre, but the numbers that tell you how well your engine is running. You make them visible. You let them guide your choices, not your assumptions.

Then you commit to continuous improvement. This is where operational maturity comes alive. You stop waiting for annual reviews and grand redesigns. You start making small, meaningful fixes every week. You build the muscle for fast, responsive learning. You move from reacting to refining.

And then you share. You stop keeping your work within the walls of your team. You bring your partners, vendors, funders, advocates, and community into the process. You ask for feedback. You offer your learning. You create a shared language of improvement. In my experience at the Ottawa Community Foundation, this has been one of the most powerful moves. When you invite others in, you’re not just improving your own processes – you’re helping lift the whole ecosystem.

Only then, when these layers are in place, are you ready for real innovation. Not the kind that masquerades as chaos. Not shiny new distractions. But grounded, thoughtful, durable innovation – ideas that stick, scale, and actually move the organization forward.

This is not just a story about my work at a community foundation. I’ve seen this pattern repeat in start-ups, established businesses, significant non-profits, public organizations, and grassroots teams. Whether in my own operational leadership, in the strategy rooms I’ve sat in, or in the trusted conversations I’ve been privileged to have over the years, the message is often the same. The organizations that scale sustainably are the ones that build their operations like layers, not leaps. The ones that know that hustle won’t save you if the engine is loose. The ones that tighten the bolts before they step on the gas.

It’s easy to underestimate the discipline it takes to build this way. But when you get it right, the work feels lighter, the team moves faster, and the mission holds steady even as you grow. And when the inevitable fires come – because they always do – you’re not just reacting. You’re ready.

The temptation will always be to move quickly, to chase growth, to keep saying yes. But I’ve learned that the best leaders – the ones I’ve admired the most, the ones I’ve worked with and learned from – are the ones who take their time to build well. Growth is good. But growth that your operations can carry? That’s the kind that lasts.