The Real Purpose of Strategy Frameworks
- — Structured strategy tools are useful only when they are matched to the problem they were designed to solve.
- — OKRs separate what matters, what evidence will show progress and what work will create that change.
- — The Balanced Scorecard looks beyond financial results to the customer, process and capability drivers behind them.
- — Hoshin Kanri creates a two-way conversation between leadership direction and frontline constraints, while RACI clarifies who acts, owns, contributes and stays informed.
- — The starting question is not, "Which model should we use?" It is, "What problem are we trying to solve?"
At Intel, Andy Grove was dealing with a familiar problem of a fast-growing organisation: too many things were competing for attention. Priorities multiplied, effort became scattered, and working hard did not necessarily mean moving what mattered most.
Grove’s response was to create greater focus. He argued that an organisation needed a small number of well-chosen objectives like clear choices about what it would say yes to and, equally importantly, what it would say no to. He then paired those objectives with measurable results that showed whether progress was actually being made. This approach later became widely known as OKRs or Objectives and Key Results.
Robert Kaplan and David Norton had a different concern. American companies were relying heavily on financial measures such as revenue, cost and profit to judge performance. Those measures were essential, but they were not enough on their own. Financial results tell you what has already happened; they do not tell you what is happening now that may affect what comes next. Are your people building the right capabilities? Are your processes improving? Will your customers continue to choose you?
The Balanced Scorecard suggested that organisations should track measures across four areas viz. financial results, customers, internal processes, and organisational capability. Together, these give leaders a view of both current performance and the conditions that will determine future performance even before problems show up in the P&L.
At Toyota, the challenge was alignment. As the company grew rapidly, senior leaders set company-wide priorities, but different functions did not always understand them in the same way. A company-wide audit found that the intent behind company policy was not always clear, different departments interpreted priorities differently, and coordination across functions was weak.
The challenge was not just to send strategy down the organisation, but to bring operational reality back up. Teams needed a way to surface what was practical, where the constraints were, and what support or coordination would be required before the plan was finalised.
Hoshin Kanri created that two-way process. Leaders proposed direction; teams closer to the work tested it against operational reality; both sides adjusted before commitments were finalised. This back-and-forth became known as catchball.
The idea was simple: strategy should not only travel down the organisation, but reality from the organisation should also travel back up.
Three different management problems. Three different responses. And three ideas that still shape how organisations set priorities, measure performance and turn strategy into action.
But there is another challenge once strategy moves into execution: ownership. When work crosses teams or functions, responsibility can quickly become unclear. The underlying idea is simple: make the roles explicit. Clarify who does the work, who owns the result, whose input is needed and who only needs to stay informed. RACI gives that idea a simple structure.
Over time, ideas like these developed into frameworks i.e., structured ways of thinking that help organisations make sense of recurring management problems, ask the right questions and approach them more systematically. They also allow organisations to build on what others have learned, rather than starting from scratch each time.
But learning from someone else’s approach does not mean copying it blindly. Frameworks are thinking tools, not fixed prescriptions. They work best when you understand what they were designed to do. Understanding what a framework was created to solve helps you decide whether you need it at all, which part of it is useful, and how to apply it without turning the framework into the work itself.
Frameworks exist across almost every area of management, ranging from feedback and coaching to problem-solving and decision-making. This article focuses specifically on those that help organisations set direction, establish priorities, measure progress, align execution and clarify ownership.
What each framework was built to solve
1. OKRs: when the problem is focus and measurable progress
The power of OKRs lies in separating three things organisations often blur together: what matters, what evidence will show progress, and what work will be done to create it.
A team may say its objective is to launch a new product, run a campaign or redesign a process. But these are activities, not outcomes. They describe what the team plans to do, not what it wants to change as a result.
OKRs make that distinction explicit. The Objective defines what matters and forces a choice. The Key Results define the evidence; what would need to change for you to know the Objective is actually being achieved. And the Initiatives are the work undertaken to move those Key Results.
John Doerr learned the method at Intel and introduced it to Google in 1999. Google later made OKRs visible across the organisation, helping teams see how their priorities connected to broader company goals. Larry Page has credited OKRs with helping Google stay focused and on track through extraordinary growth.
Technology entrepreneur Bhavin Turakhia makes this line of sight explicit as a chain: Purpose → Company Objectives → Team Objectives → Key Results → Initiatives. The value is not the chain itself — it is that every person can trace their work back to the organisational outcome it is meant to influence. He runs this on a deliberate cadence: Company Objectives annually, Team Objectives quarterly, with regular check-ins and replanning in between. In his view, that discipline is what makes scaling possible.
Where OKRs often go wrong is in the way Key Results are written. Teams write things like “launch the campaign”, “complete the rollout” or “redesign the process”. These are activities or initiatives, as they describe what the team did. They say nothing about what changed as a result. A Key Result should answer a different question: not what did we do, but what moved because we did it?
The problem OKRs help solve: scattered priorities and the tendency to confuse completed work with meaningful progress.
2. The Balanced Scorecard: when the problem is what you are measuring
If leaders rely mainly on financial results to assess how the business is performing, they may see a problem only after it has already developed. By the time revenue starts to fall, some customers may already have left. By the time margins decline, process issues may have been building for months.
The issue was not that financial measures were unimportant. It was that they showed the outcome without always showing what was driving it. A fuller view requires looking beyond financial results to the customer, process and capability factors that shape them.
The Balanced Scorecard broadened the view across four perspectives viz. financial performance, customers, internal processes, and learning and growth. The four perspectives are not independent. Stronger capabilities tend to improve critical processes. Better processes tend to create greater customer value. Greater customer value tends to drive financial performance. A weakness developing in one part of that chain can become visible before it reaches the P&L.
Mobil’s North American Marketing and Refining division became one of the most documented early examples. Financial results were poor, but financial measures alone couldn’t explain why. Mobil’s market research revealed something that pure financial metrics had never surfaced: price-sensitive customers represented only about 20% of gasoline purchasers, while consumers making up roughly 60% of the market were willing to pay a premium, if they could buy at stations that were fast, friendly, and had good convenience stores. That insight came from looking at the customer perspective, not the financial one, and it shaped an entirely new strategy. The Balanced Scorecard then helped track whether the right things were being built to deliver it. The division moved from the bottom of its peer group in profitability to industry-leading performance.
But the same framework, applied carelessly, loses its value. When the template becomes the task, something quietly reverses. Teams add measures to look thorough, not to think clearly. Reviews grow longer, increasingly filled with numbers, and conversations grow thinner. And the question the scorecard was designed to ask i.e., are we managing today’s performance while building tomorrow’s, stops getting asked.
The problem the Balanced Scorecard helps solve: relying too heavily on financial outcomes and missing the customer, process and capability signals that may determine whether those outcomes can be sustained
3. Hoshin Kanri: when the problem is alignment across the organisation
A common failure in strategy deployment is not that the strategy is wrong. It is that it means different things to different people by the time it reaches the people doing the work.
A leadership team agrees on a few priorities. Those priorities move through presentations, planning meetings and targets. Each level interprets them through its own context, constraints and assumptions. By the time direction reaches the frontline, what people are working toward may no longer fully reflect what leadership originally intended.
The problem is not simply communication. Strategy has travelled down, but operational reality has not travelled back up.
Hoshin Kanri addressed this through catchball, a structured back-and-forth that moved through every level of the organisation. Leadership proposed the strategic direction. Each level below tested it against what was actually feasible in their area, surfacing constraints, dependencies and resource gaps that weren’t visible from the top. Plans were adjusted. Assumptions were challenged. By the time commitments were finalised, every level had contributed to shaping them rather than simply receiving them.
The result is alignment that has been built rather than assumed.
Ingersoll Rand provides a useful example of how this thinking travelled beyond Toyota. Its Business Operating System included a formal Goal Deployment Process designed to align and deploy breakthrough goals, annual goals, actions and measures across the organisation. It also brought product management, engineering and supply-chain teams together around common growth priorities, making alignment across functions part of how strategy was executed, rather than leaving each function to optimise independently.
The failure mode is straightforward. When Hoshin Kanri is implemented without genuine catchball — targets go down and acknowledgement comes back up — it becomes an elaborate cascade of mandates. The structure remains, but the dialogue disappears. Teams comply with the objectives they have been given rather than committing to objectives they have helped shape. Compliance and commitment produce very different results.
The problem Hoshin Kanri helps solve: the gap between what leadership intends and what different parts of the organisation ultimately understand, commit to and work toward.
4. RACI: when the problem is ownership and clarity
RACI is different from the other frameworks in this article. It does not help an organisation decide what to prioritise, what to measure or how to align strategy. It becomes useful only after those choices have been made, when execution involves several people or functions and ownership is unclear.
That is where a familiar problem appears. Everyone is involved, but ownership is unclear. Two teams assume the other is handling something. Several people believe they need to approve a decision. Others are pulled into meetings when they only need to be informed. Work slows down, decisions get revisited, and gaps appear between functions.
RACI gives that confusion a simple structure by assigning four roles to a task or decision:
The framework helps by making involvement explicit. It clarifies who acts, who owns, whose input is needed, and who needs to stay informed. That reduces duplication, unnecessary involvement and delays caused by unclear ownership.
The distinction between Responsible and Accountable matters. They are not the same role. Responsible is about doing. Accountable is about owning the outcome. You may assign responsibility for the work to someone else, but if you are Accountable, you still answer for the result.
RACI also has an important limitation. It can clarify ownership, but it cannot tell you whether the work itself is worth doing. If the outcome is still unclear, or the priority has not been agreed, a RACI matrix can create clarity around work that may not matter.
That is why it works best when the outcome is already clear, the work is defined, and several people or teams need to contribute to the result. In that situation, its value is not the matrix itself. It is the conversation the matrix forces: Who really owns this? Who needs to act? Who needs to contribute? And who does not need to be involved?
The problem RACI helps solve: ambiguity about ownership and roles when execution crosses team or functional boundaries — once the strategic outcome is already clear.
Different frameworks, different problems
These frameworks may all sit somewhere between strategy and execution, but they are not solving the same problem.
An organisation may face one of these problems or several of them. It may use one framework or combine elements from several.
That is why the starting question should not be: which framework should we use?
It should be: what problem are we trying to solve?
Once that is clear, the right framework becomes much easier to identify.
What changes when you understand the purpose
You may not always choose the framework your organisation uses. It may arrive with a template, a review cycle and a deadline attached.
But you can still ask a more useful question: what is this framework supposed to help us think about, and is it actually helping us do that?
The real purpose of these frameworks is not compliance, reporting or process. It is clearer thinking about problems that are genuinely difficult to solve. Each framework emerged from a real management challenge, such as focus, measurement, alignment or ownership, and offered a more structured way to think through it.
That is the difference between knowing a framework and understanding one.
Frequently Asked Questions
Q1. What is the real purpose of a strategy framework?
A framework gives leaders a structured way to think through recurring management problems. Its value is not the template itself, but whether it supports execution, creates measurable progress and helps teams connect strategic choices to operational reality.
Q2. How should leaders choose between strategy frameworks?
Choose the framework based on the management problems you are trying to solve. OKRs can sharpen focus, the Balanced Scorecard can connect drivers to financial performance, Hoshin Kanri can improve alignment between direction and frontline reality, and RACI can clarify ownership during execution.
Q3. How do OKRs support strategy deployment?
OKRs are a framework for translating priorities into objectives, Key Results and initiatives. Used well, the framework supports strategy deployment by defining measurable progress and helping teams distinguish the outcome they want to influence from the activity used to create it.
Q4. What does the Balanced Scorecard help organisations measure?
The Balanced Scorecard is a framework for looking beyond financial performance alone. It connects financial, customer, process and capability perspectives so leaders can see measurable progress earlier and make better decisions before weaknesses reach the P&L.
Q5. How does Hoshin Kanri improve alignment?
Hoshin Kanri is a framework for strategy deployment that combines leadership direction with operational reality. Through catchball, teams surface constraints and dependencies before commitments are finalised. The framework builds alignment through dialogue rather than assuming that a cascade automatically creates it.
Q6. What is catchball in Hoshin Kanri?
Catchball is the framework’s structured back-and-forth between leadership and teams. It brings operational reality into strategy deployment, tests assumptions and improves execution by allowing plans to be adjusted before objectives become fixed.
Q7. When should an organisation use RACI?
RACI is a framework for clarifying roles when several people or functions contribute to execution and financial performance. It is most useful after the outcome and priority are clear; otherwise, the framework may create ownership around work without resolving the underlying management problems.
Q8. Can organisations combine different strategy frameworks?
Yes. One framework may address focus while another addresses measurement, alignment or ownership. Combining frameworks can help when management problems overlap, provided leaders remain clear about the purpose of each tool and how it contributes to execution.
Q9. Why can strategy frameworks fail even when the model is sound?
A framework can become a compliance exercise when teams focus on filling templates instead of thinking. That weakens measurable progress, disconnects financial performance from its drivers and makes execution less responsive to operational reality.
Q10. What should managers ask when using an existing strategy framework?
Managers should ask what problem the framework is meant to solve and whether it is helping. That question keeps strategy deployment connected to measurable progress, protects alignment between levels and ensures financial performance is interpreted alongside the factors driving it. Used this way, the framework remains a thinking tool.
Priyanka Sahay is a Leadership Faculty at GlobalGyan Leadership Academy with experience across corporate leadership, entrepreneurship, and organisational development. She holds an MBA in International Business and is a qualified lawyer and psychologist. Her corporate experience, followed by building and managing her own venture, has given her a practical understanding of strategy, operations, people, and business decision-making. She works with middle and senior-level managers to develop strategic thinking, business acumen, and leadership effectiveness. Her multidisciplinary background brings together commercial, legal, and behavioural perspectives to help leaders make better decisions and navigate complex organisational challenges.
View LinkedIn Profile
GlobalGyan Leadership Academy 
Responses