From Strategy to Execution: A Conversation with Steven Macdonald, Founder of OKRs Tool

As organisations grow, the difficulty rarely lies in defining ambition.

Most leadership teams are clear on where they want to go. The challenge is sustaining alignment once execution pressure increases and complexity multiplies.

Steven Macdonald, founder of OKRs Tool, has worked closely with growing teams to implement Objectives and Key Results (OKRs) as an operational discipline rather than a planning ritual.

We spoke with him about where execution begins to drift, how OKRs fit into operational systems, and what leaders can do to maintain clarity at scale.

OpsMatters: Many organisations adopt OKRs with enthusiasm but struggle to sustain them. Where does execution typically begin to break down?

Steven: It usually breaks down after the kickoff. The planning session is energising. Objectives are defined, key results are agreed, and there’s a sense of shared direction. But once daily pressures resume, goals gradually lose influence over decision-making.

In growing organisations, dependencies increase quickly. Without a mechanism to revisit OKRs consistently, teams default to reactive work. The framework itself isn’t the issue. It’s the absence of operational rhythm that causes drift.

OpsMatters: How should OKRs function within an operational system rather than as a quarterly planning exercise?

Steven: When OKRs are treated as planning artefacts, they sit alongside operations. When they’re treated as an operating mechanism, they shape how work is prioritised and reviewed.

That means embedding them into weekly workflows. Clear ownership, visible progress, and predictable review cadence turn OKRs into feedback loops. In that context, they help leaders steer execution rather than simply measure it.

OpsMatters: Shared responsibility is common in modern organisations. How does that affect execution?

Steven: Shared responsibility often slows momentum. With a good OKR system, each objective will have a single accountable owner. That person coordinates progress and resolves friction points.

When objectives belong to departments instead of individuals, updates remain general. Clear ownership improves decision speed because accountability is explicit. It reduces ambiguity and accelerates follow-through.

OpsMatters: How important is review cadence in operational environments?

Steven: Cadence determines whether goals remain active or become archival. Regular review creates shorter feedback loops. Teams can adjust early instead of discovering issues at the end of a cycle.

In operational contexts, predictability improves when review is consistent. Small corrections prevent larger disruptions. Without cadence, drift becomes visible only after performance has already been affected.

OpsMatters: What role does visibility play in cross-functional alignment?

Steven: Visibility reduces coordination friction. In dependency-heavy environments, teams need shared context. If OKRs are only discussed in leadership forums, alignment weakens at execution level.

When objectives and progress are visible across teams, collaboration improves. It becomes easier to identify bottlenecks and make informed trade-offs. Transparency supports both accountability and efficiency.

OpsMatters: At what stage should organisations formalise OKRs within their operating model?

Steven: Earlier than many expect. Structure doesn’t mean bureaucracy; it means clarity. As soon as work regularly spans functions, formalising ownership and review becomes valuable.

Introducing OKRs early allows alignment habits to form before complexity escalates. Retrofitting structure later is usually more disruptive.

OpsMatters: How do OKRs intersect with risk management in operations?

Steven: Poor alignment is an operational risk. When teams pursue slightly different interpretations of priority, execution gaps widen quietly. OKRs, when reviewed consistently, surface misalignment early.

They also expose stalled initiatives before dependencies become critical. In that sense, they act as a risk-detection layer, highlighting drift before it impacts performance.

OpsMatters: Many leaders worry that formal goal systems reduce agility. How do you respond to that?

Steven: Agility depends on clarity. Without clarity, teams move quickly but not necessarily cohesively. Lightweight OKR systems provide structure without constraining adaptability.

When ownership and cadence are clear, teams can adjust direction confidently because they have visibility into impact. That strengthens agility rather than limiting it.

OpsMatters: What practical first step would you recommend for operations leaders who feel execution is drifting?

Steven: Introduce a predictable weekly review tied to outcomes, not activity. Keep it structured and concise. Pair that with explicit ownership for key initiatives.

Those two changes alone often improve alignment significantly. Once cadence and accountability are in place, visibility and prioritisation become easier to manage.

Closing Thoughts

Operational discipline rarely requires dramatic transformation. More often, it involves reinforcing clarity through ownership, cadence, and transparency.

For leaders navigating growth and complexity, OKRs can serve as alignment infrastructure when implemented as part of the operating rhythm rather than as a standalone planning exercise.

As Steven Macdonald’s experience with OKRs Tool highlights, execution strength lies less in ambitious objectives and more in the systems that sustain focus under pressure.