Stop Cascading Goals. Start Aligning Decisions.

I watched a mid-sized software company spend three months implementing OKRs. The leadership team hired a consultant, ran workshops, cascaded objectives from company level to department level to individual level. Every goal had three key results. Every key result had an owner. The whole structure looked beautiful in the spreadsheet.

A few months later, someone asked: "Why do we have OKRs if people only look at them before their reviews?"

That question matters. Not whether your goals cascade properly. Not whether everyone has objectives. But whether anyone actually uses them when it counts.

I've written before about the three walls organisations hit with strategy: getting the right level of detail, making strategy usable for daily decisions, and measuring progress amid changing priorities. Goal cascades don't solve these problems. They just create the illusion that you have.

The Real Problem with Goal Cascades

Goal cascades work brilliantly in enterprises. When you have thousands of people and complex coordination challenges, a structured goal hierarchy makes sense.

But in a company with 10 to 100 people? Goal cascades solve the wrong problem.

The challenge isn't measuring whether people hit their targets. It's making sure everyone makes similar decisions when facing similar situations. Your product manager deciding between two features. Your customer success lead choosing how to allocate their time. Your operations person determining which process improvement to tackle first.

These aren't big, visible decisions. They're the dozens of small, high-volume decisions that happen every day. In small organisations, these decisions either compound into strategic progress or they don't. You can't afford the inefficiency of misalignment that larger companies absorb with their established customer base and market position.

The Alignment Illusion

The hardest part about alignment isn't creating it. It's recognising when you don't have it.

Every leadership team I've worked with believed they were more aligned than they actually were. Everyone nods in the strategy meeting. Everyone agrees the goals make sense. And then everyone makes different assumptions about what those goals mean in practice.

I call this assumption creep. Your CEO says "customer-centric" and thinks it means prioritising retention. Your product lead hears the same phrase and thinks it means faster feature delivery. Your sales director interprets it as more flexibility in deal terms. They're all acting on "the strategy" but pointing in different directions.

The problem intensifies because goal cascades measure outcomes, not the reasoning that produces those outcomes. You can hit your OKR while making decisions that completely contradict strategic intent.

What Alignment Actually Means

Real alignment isn't about metric trees. It's about shared understanding of what matters strategically.

When your team is aligned, they look at the same situation and reach similar conclusions. Not because they checked a goal cascade. Because they understand what's at stake and can evaluate the implications of their choices.

This matters most for decisions that don't feel strategic enough to warrant executive attention. The engineer choosing how to handle technical debt. The account manager deciding which customer requests to escalate. The operations coordinator determining which task to do first.

Between 10 and 100 people, you hit a painful middle ground. Too big for everyone to be in every conversation. Too small to have dedicated strategy teams managing cascading goals.

And here's the critical part: alignment isn't just for leadership. Everyone who makes decisions needs to be aligned. Your junior team members are making dozens of judgment calls every day that either advance the strategy or work against it.

Building Decision Contexts Instead

You build decision contexts that travel with people as they work. Not elaborate documents. Practical understanding that helps people evaluate choices in real-time.

A good decision context explains: "When facing this type of decision, here's what matters strategically and why." It's about understanding implications, not following rules.

For example, instead of an OKR like "Increase customer satisfaction score by 10 points," you might create a decision context: "Customer requests are opportunities to demonstrate capability in our strategic focus areas and deepen relationships with accounts we're expanding. They become problems when they pull us into commodity work or dilute our expertise positioning." That context helps your customer success team understand what's at stake in dozens of interactions every week.

The test of a good decision context is simple: can two people independently facing similar decisions arrive at similar conclusions because they understand what matters?

Where This Changes Behavior

I've seen the difference this makes in practical terms.

A professional services firm I worked with had an OKR around "client satisfaction." Sounds reasonable. But when their consultants faced decisions about scope creep, everyone made different calls. Some said yes to everything, burning out their teams. Others said no to everything to ensure the original goals were delivered, damaging client relationships.

Instead replace the OKR with a decision context: "Scope decisions affect our strategic positioning and team capability. Accepting scope expansion that demonstrates our expertise in strategic areas or deepens key client relationships advances the strategy. Accepting scope that pulls us into commodity work or spreads expertise too thin works against it."

Suddenly, consultants were making consistent decisions. Not because they were following rules. Because they understood what was at stake strategically. Client satisfaction improved. So did team utilisation. So did strategic positioning.

The context changed behavior. The OKR just measured outcomes without explaining what mattered.

How AI Actually Helps Here

AI excels at identifying patterns in decisions across your organisation. When three different people face similar choices and make different calls, AI can surface that misalignment immediately. You can then create or refine the decision context to address it.

AI can also help teams apply contexts in real-time. Instead of remembering multiple strategic principles while evaluating options, people can describe their situation and get guidance that explains what matters strategically and why.

This isn't about replacing judgment. It's about scaling understanding. Your leadership team's strategic thinking becomes available to everyone making decisions, not just during quarterly reviews.

Start Simple

You don't need to replace your entire goal system immediately. Start with one area where you're seeing inconsistent decisions despite having clear goals.

Identify three types of decisions that happen repeatedly in that area. Write down the context that would help people understand what matters strategically in those decisions. Share it with the people who face those decisions and see if it helps them reach consistent, strategic choices.

If it works, that's alignment. If it doesn't, refine the context until it does.

Goal cascades measure whether you're succeeding. Decision contexts explain what success means. In organisations with 10 to 100 people, you need the second more than the first.

Stop optimising for measurement. Start optimising for aligned decisions. That's where mid-market companies actually win.