There is a point in the growth of every operator-built business where the habits that created the company begin working against it. Saying yes to everything, holding all the context yourself, and hiring fast to keep pace. These instincts feel like strengths because they produce results. But they do not scale. The founder who built the business through personal effort and judgment eventually becomes the bottleneck preventing it from growing further. The question is whether you recognize that inflection point and build the structural replacement before the business stalls under its own weight.
I run Ontario Towing in Ottawa. Twenty-five years in business, over seven hundred five-star Google reviews, and a reputation built on showing up fast and treating people honestly in a sector where customers only call on one of their worst days. When someone is stranded or has been in an accident, the company that arrives represents the entire experience. Earning trust in that moment requires more than good intentions, and keeping that trust while doubling your team and your revenue requires intentionality. Five years ago, I realized I did not have a strategy problem. I had a structural problem. John Doerr’s Measure What Matters gave me the framework to diagnose it.
Three Failure Patterns That Look Like Growth
Before implementing OKRs, three structural problems were hiding behind what appeared to be a healthy business.
The first was undifferentiated demand acceptance. We treated every inbound call as equal. A low-margin roadside assist across town occupied the same truck and driver that could have served a higher-value long-distance tow or a commercial contract. We never stopped serving the people who needed us most. But without a system to allocate resources intentionally, we were spreading the operation thin. We were busy constantly, but busyness is not a strategy.
The second was founder dependency. I was the only person who knew which jobs to prioritize, which accounts mattered, and which drivers were available for what. Every decision was routed through me, not because the team lacked capability, but because we had never built systems to distribute judgment. The art of delegation is not about handing off tasks. It is about creating the conditions where your team can make decisions that reflect the same standards you would apply yourself. Without that structure, delegation feels like a risk rather than a strategy.
The third was reactive hiring. As volume increased, we brought on drivers to keep up, but without defined roles, training standards, or performance expectations. In an industry where one bad interaction can undo years of earned trust, inconsistent service quality is an existential risk.
How OKRs Addressed Each Problem
Doerr’s framework is often presented as a goal-setting methodology, but it’s more than that. For an operator-led business at a scaling inflection point, OKRs function as a decision architecture that distributes judgment across the organization.
Focus and commit addressed undifferentiated demand. Quarterly objectives forced us to articulate what mattered most and, critically, what did not. This meant deliberately delegating certain categories of work, not because we could not do them, but because they consumed resources that should have been directed toward growth. For the first time, saying no to a job was a strategic act rather than a failure of hustle.
Align and connect broke the founder bottleneck. When objectives are explicit and shared, team members make judgment calls without routing every decision through one person. A driver who understands the quarterly priority can triage a dispatch conflict without waiting for instructions. A dispatcher who understands that our reputation depends on transparency can handle a pricing conversation without a script.
Track for accountability replaced instinct with operational metrics. Before OKRs, my sense of how the business was performing was largely intuitive, shaped by whichever calls I had taken that day. Structured tracking enabled us to measure what actually mattered, including customer experience indicators that would have previously gone unnoticed until they became complaints.
Stretch for amazing reframed what the business could become. Within five years, we expanded from local operations into long-distance towing, reaching Montreal and the United States. That expansion came because the framework had built a team capable of recognizing and executing on opportunities without sacrificing service integrity.
Scaling Culture Without Diluting It
Doerr’s CFR model, Conversations, Feedback, Recognition, addressed the hardest part of growth: the transition from direct oversight to distributed management. In a small crew, the founder sees everything. Quality control is automatic because proximity is constant. In towing, this matters more than in most industries. Every interaction happens during a customer’s worst day. The margin for error is effectively zero.
CFRs replaced the instinct to micromanage. Regular structured conversations replaced ad hoc check-ins. Feedback became a system rather than a reaction to problems. Recognition reinforced the behaviours aligned with our objectives and our values. People understood what was expected, received consistent signals about their performance, and could self-correct without waiting for the founder to notice.
The Real Lesson
The central insight from implementing OKRs is not about goal-setting. It is about recognizing the moment when founder-driven execution becomes a liability rather than an asset. In our case, the stakes were compounded by operating in an industry where trust is scarce and hard-won. We could not afford to scale in a way that compromised the thing that made us worth scaling. OKRs gave us a system for protecting what mattered while pursuing what was next.
