Hoshin kanri: what it is, how it works, and how to implement it in manufacturing

What is hoshin kanri

Hoshin kanri is a systematic method for aligning an organisation’s long-term strategic direction with the daily work of every team and individual. It is often described as the bridge between the boardroom and the shop floor. Where traditional strategic planning ends when the annual plan is signed off, hoshin kanri only begins there. Its purpose is to make sure that the strategy actually gets executed, not that it merely gets written down. In practical terms it does this through a repeatable cycle of goal-setting, cascading those goals through catchball consultations, executing them at the operational level, reviewing results monthly with PDCA, and reflecting annually to feed the next cycle.

The literal meaning: hoshin plus kanri

The two Japanese words together capture the essence of the method. Hoshin means compass needle or direction, referring to the strategic bearing of the organisation. Kanri means management, administration or control. The combined term is commonly translated as compass management or direction management, and English-language practitioners also use policy deployment or strategy deployment as functional equivalents. All three translations describe the same underlying concept: how do we manage our direction so that we actually get where we said we were going. The literal image of a compass matters because it implies orientation for a journey, not a single destination marked on a slide.

Origins in post-war Japan and the Toyota system

Hoshin kanri was formalised by Professor Yoji Akao, a Japanese quality management scholar, who published the foundational work in the mid-1960s drawing on decades of Japanese practice in quality control and continuous improvement. The method took hold at Toyota during the growth of the Toyota Production System in the 1970s and 1980s, becoming one of the operating disciplines that let Toyota align a fast-growing multi-plant enterprise around a single strategic direction. That combination of theory (Akao) and industrial practice (Toyota) made hoshin kanri one of the pillars of what the West later called lean manufacturing. Its Japanese origin is more than historical trivia; the emphasis on consensus, bidirectional consultation and long time horizons reflects cultural assumptions that Western adopters had to consciously graft onto their own organisations.

Hoshin kanri today, beyond manufacturing

Manufacturing remains the natural home of hoshin kanri, but the method has spread far beyond its origins. Hewlett-Packard adopted it in the 1980s and remains a cited reference implementation. Danaher built its operating system partly around hoshin principles. John Deere, Cisco and Intel run variants adapted to their industries. Beyond commercial companies, hoshin kanri now appears in healthcare systems aligning multi-hospital networks, in financial services aligning retail branch networks, and in government agencies deploying multi-year policy programmes. The core method has proven portable because the problem it solves is universal: any organisation with more than a few dozen people faces the challenge of keeping strategy connected to execution, and hoshin kanri offers a repeatable answer.

The four foundational principles of hoshin kanri

Hoshin kanri rests on four principles that together turn strategic intent into operational reality. Bain’s 2023 Management Tools & Trends Survey of a thousand executives found Strategic Planning to be the most-used management tool at 48% adoption with a satisfaction rating of 4.03 out of 5, but the same survey highlighted a persistent gap: strategic plans exist, yet organisations struggle to make them actually drive daily action. The four principles below are what fills that gap.

Vertical alignment: strategy cascade from CEO to shop floor

Vertical alignment is the mechanism through which strategic goals flow from executive leadership down through management layers to the individuals who do the operational work. In hoshin kanri, this cascade is explicit rather than implicit. The CEO defines the top-level breakthrough objectives. Division heads translate them into divisional annual objectives. Department managers translate divisional objectives into departmental initiatives. Team leaders translate departmental initiatives into concrete daily actions. Every level knows how its work links to the level above and to the top-level direction. The point is not bureaucratic rigour; the point is that every person in the organisation can answer the question of how their work connects to the strategy, and that answer is visible in the same document their manager and their manager’s manager use.

Horizontal alignment: cross-functional coordination

Horizontal alignment is the mechanism that prevents silos from destroying strategic execution. A strategic objective almost never sits inside one department; a new product launch requires R&D, engineering, quality, procurement, production, marketing and sales working in sync. Hoshin kanri forces the departments involved in each strategic priority to agree on the plan together, to review progress together, and to escalate together when priorities conflict. This is not a matter of goodwill or good meetings; hoshin makes the cross-functional coordination structural by naming shared owners for shared objectives and reviewing progress at the cross-functional level rather than the departmental level.

PDCA as the operating cycle

The Plan-Do-Check-Act cycle is what turns hoshin kanri from an annual planning event into a continuous learning system. Plan defines what should happen. Do executes. Check reviews the results against the plan. Act adjusts the approach based on what was learned. In a mature hoshin kanri implementation, this cycle runs monthly at the operational level, quarterly at the divisional level, and annually at the enterprise level. Without PDCA discipline, the annual plan becomes an artefact on a wall, disconnected from what actually happens the other eleven months of the year. With PDCA, the plan becomes a hypothesis that gets tested against reality every month and updated based on evidence.

Catchball as bidirectional consultation

Catchball is the practice of throwing goals back and forth between organisational levels until they are refined into something both leadership and the team on the ground can commit to. A senior executive proposes a target for a division; the division leader challenges it based on what is actually feasible; the executive adjusts based on that challenge; the division leader consults with department managers; and so on down the cascade. The name comes from the image of tossing a ball back and forth, and it captures the essential quality of hoshin kanri that separates it from top-down mandates: the cascade is a conversation, not a monologue. Without catchball the cascade becomes an instruction handed down without buy-in, and adoption at the operational level dies quietly within one or two cycles.

The X matrix, the visual heart of hoshin kanri

The X matrix is the most recognisable visual element of hoshin kanri, a single-page diagram that captures long-term goals, annual objectives, improvement priorities, metrics, correlations and owners on one wall or one page. Its power is that it makes the whole strategy visible in one view, so anyone can walk up to it and understand not just what the goals are but also how they connect and who owns what. Spreadsheets and slide decks tend to hide these connections; the X matrix forces them into the open.

Four quadrants

The X matrix has four quadrants arranged around a central X shape. The bottom quadrant holds the long-term strategic goals, typically a three-to-five-year horizon that describes where the organisation intends to be. The left quadrant holds the annual objectives, the specific outcomes the current year has to deliver to move toward those long-term goals. The top quadrant holds the improvement priorities and tactical initiatives, the concrete work that will produce the annual outcomes. The right quadrant holds the metrics and KPIs that measure progress on each of the other three quadrants. The four quadrants are read as a chain: long-term goals drive annual objectives, annual objectives drive tactical priorities, tactical priorities are tracked through metrics that report back on all three.

Correlations: the dot matrix

The distinctive feature of the X matrix is the dot pattern in the corners where two quadrants meet. Each dot indicates that a specific item in one quadrant is correlated with a specific item in the adjacent quadrant. A filled dot means a strong correlation; a partially filled dot means a moderate correlation; an empty cell means no direct link. This visual grammar surfaces what is usually implicit: which tactical priorities actually drive which annual objectives, which annual objectives actually serve which long-term goals, which metrics actually track which priorities. When leadership walks up to the X matrix and sees that a favourite tactical initiative has no dots connecting it to any annual objective, the conversation about whether that initiative belongs in the plan becomes concrete rather than political.

Owners and teams around the perimeter

The perimeter of the X matrix carries the names of the people and teams responsible for each element. Each long-term goal has an executive sponsor. Each annual objective has an owner accountable for delivery. Each tactical priority has a project leader. Each metric has a data steward responsible for the numbers. Cross-functional teams working on shared priorities appear as team labels rather than single-name owners. The visual placement of owners around the matrix makes accountability explicit and public, which is a subtle but powerful mechanism in itself: it is harder to let a priority slide when your name is next to it on a wall the whole leadership team sees every month.

When to use the X matrix versus alternatives

The X matrix is not the only strategic visualisation available. The Balanced Scorecard uses four perspectives (financial, customer, internal process, learning and growth) arranged in a strategy map. OKR frameworks visualise objectives and key results in trees or nested lists. Each has its strengths. The X matrix wins when the leadership team needs a single one-page view that shows the entire strategy with explicit correlations and named owners. It works less well when the strategy is highly quarterly (where OKR’s quarterly cycle fits better) or when the organisation needs to communicate strategy to external stakeholders (where the Balanced Scorecard’s more polished aesthetic often lands better). For internal strategic alignment in a manufacturer running an annual planning cycle, the X matrix is unusually effective precisely because it refuses to hide anything.

How to implement hoshin kanri in seven steps

The canonical hoshin kanri implementation follows seven sequential steps that together cover a full annual cycle, from defining the strategic vision to reflecting on what was learned. Different practitioners describe the steps with slightly different names, but the underlying flow is remarkably consistent across sources. The seven steps below describe the flow in the form most commonly used in manufacturing settings.

Step 1: Define the strategic vision (True North)

The first step is to articulate the organisation’s True North, the long-term aspirational position that the strategic work will move toward. This is a five-to-ten-year horizon and it is deliberately broad rather than SMART. True North answers the question of what kind of organisation the company wants to be, not what specific numbers it wants to hit. Examples include zero-defect manufacturing, becoming the industry benchmark for on-time delivery, or achieving carbon-neutral production. True North is set by senior leadership and is refreshed only occasionally, when a fundamental shift in the business demands it.

Step 2: Set breakthrough objectives

Breakthrough objectives are the three-to-five transformational goals that would fundamentally change the organisation’s competitive position if achieved. They cover a three-to-five-year horizon and they are ambitious enough to require reshaping how the organisation works. Toyota’s discipline of keeping breakthrough objectives to three-to-five items is not an arbitrary limit; it reflects the reality that any leadership team can only sustain focus and executive attention on a small number of major transformations at once. Organisations that try to run ten or fifteen breakthrough objectives simultaneously typically end up running none of them well.

Step 3: Establish annual objectives

Annual objectives break the multi-year breakthrough objectives down into what the current year specifically has to deliver. Unlike breakthrough objectives, annual objectives are SMART: specific, measurable, achievable, relevant and time-bound. A breakthrough objective of achieving zero-defect manufacturing over five years might translate into an annual objective of reducing defect rate from 800 parts per million to 400 parts per million by the end of the current fiscal year. Each annual objective inherits from a breakthrough objective through visible correlation in the X matrix.

Step 4: Deploy goals via catchball

Deployment is where catchball actually happens. Annual objectives set at the executive level are proposed to division heads, who challenge them based on feasibility, resource constraints and dependencies. The executives adjust based on the challenges, then divisions propose sub-objectives to departments, departments challenge them, and so on down the cascade. This step takes weeks rather than days in a mature implementation, and it looks slow compared to a top-down mandate, but the buy-in it produces is what makes execution work in the following months. Skipping catchball to save time in the deployment phase reliably produces execution failures later that cost far more than the time saved.

Step 5: Execute at the operational level

Execution is where hoshin kanri meets daily work. Annual objectives now translate into concrete projects, kaizen events, capital investments and operational initiatives. In manufacturing this is where the hoshin plan materialises as project portfolios. A breakthrough objective might drive three annual objectives, each of which drives four or five projects, each of which has its own budget, schedule, resources and KPIs. The connection back to the strategic vision remains visible because every project traces up through the X matrix to a breakthrough objective and ultimately to True North.

Step 6: Review monthly with PDCA

Monthly reviews are the PDCA heartbeat of hoshin kanri. At each review, teams compare actual progress against planned progress for the month, identify variances, analyse root causes, and decide what adjustments are needed. This is not the annual review that happens at the end of the year; it is a monthly rhythm that keeps the plan connected to reality. Without monthly PDCA, variances accumulate silently and only become visible at the annual review, by which point they are too large to recover. With monthly PDCA, small variances get addressed while they are still small, and the annual review becomes a reflection on what was learned rather than a scramble to explain why the plan failed.

Step 7: Annual reflection (hansei)

The seventh step is the annual reflection, or hansei in Japanese, which precedes the start of the next planning cycle. Hansei is more than a retrospective on what got delivered against the plan; it is an honest examination of what the organisation learned about itself, its markets, its capabilities and its assumptions. What breakthrough objectives turned out to be more or less realistic than expected? What did the catchball process reveal about organisational readiness for change? What surprises appeared in the monthly PDCA cycles and what do they tell us about how the strategy needs to evolve? The hansei feeds directly into refreshing True North and setting the next year’s breakthrough objectives, closing the loop and starting the cycle again.

Hoshin kanri in manufacturing

Manufacturing is where hoshin kanri was born and where it still finds its most natural application. The characteristics that make manufacturing a good fit for hoshin kanri are the same ones that make manufacturing hard: long planning horizons, capital-intensive investments, complex cross-functional coordination, and the need for continuous improvement in parallel with major strategic initiatives. Hoshin kanri gives manufacturers a way to hold all of that together under a single strategic direction rather than letting each function optimise for its own goals in isolation.

Why manufacturing was the origin

Toyota developed hoshin kanri in a context that made the method both necessary and natural. Toyota was rebuilding Japan’s industrial base after the war, pursuing quality and productivity leadership in an industry dominated by American manufacturers, and doing so through a philosophy of continuous improvement that required every worker to be engaged in the strategic direction of the company. Hoshin kanri emerged as the practical mechanism that made these ambitions operational. The long time horizons of manufacturing (five to ten years from vision to production output) matched the multi-year cascade of hoshin. The need for cross-functional coordination between engineering, production and quality matched hoshin’s horizontal alignment principle. The culture of continuous improvement matched the monthly PDCA cycle. These fits explain why manufacturing remains the reference application for hoshin kanri decades later.

Hoshin kanri and continuous improvement programs

Kaizen and continuous improvement programmes are the operational engine that hoshin kanri drives. Without hoshin, kaizen tends to devolve into a scattered collection of local improvements that individually help but collectively do not add up to strategic change. With hoshin, each kaizen event is chosen because it serves a specific breakthrough objective, and the aggregated impact of hundreds of kaizen events over a year contributes measurably to the strategic direction. This is the difference between an organisation that runs improvement activities and an organisation that runs a strategic improvement programme: the presence of a hoshin cascade that gives every kaizen event a reason to exist within a bigger plan.

Hoshin kanri as a project portfolio driver

The most important operational consequence of hoshin kanri in manufacturing is that it turns strategic direction into a project portfolio. Breakthrough objectives break down into annual objectives, annual objectives break down into tactical priorities, and tactical priorities materialise as concrete projects with budgets, schedules and owners. A capital investment project to modernise a production line exists because it serves a breakthrough objective around capacity or quality. A new product development project exists because it serves a breakthrough objective around market position. A kaizen programme exists because it serves a breakthrough objective around operational excellence. The hoshin X matrix defines the direction; the project portfolio executes it. Manufacturers who run hoshin kanri without a coherent project portfolio system end up with X matrices on the wall and execution that continues on old momentum, disconnected from the new direction. This is where the systemic support of a project portfolio management system becomes decisive.

KPIs manufacturers actually track through hoshin

The KPIs that appear on the right side of a manufacturer’s X matrix cluster around a handful of families that consistently matter across the industry. Operational KPIs include capacity utilisation, overall equipment effectiveness (OEE), throughput, first-pass yield, defect rate and on-time delivery. Safety KPIs include lost-time injury frequency rate (LTIFR) and days away, restricted, or transferred (DART). Financial KPIs include gross margin, working capital as a percentage of revenue, and return on invested capital (ROIC). Strategic KPIs vary by breakthrough objective and might include market share in a target segment, revenue from products launched in the last three years, or carbon emissions per unit of output. What matters is that each KPI on the X matrix traces back through explicit correlations to a specific annual objective, and each annual objective traces back to a breakthrough objective. KPIs without that traceability are just numbers being reported; KPIs with traceability are the pulse of the strategy.

Hoshin kanri compared with other strategic frameworks

Hoshin kanri is one of several strategic frameworks available to organisations trying to close the gap between strategy and execution. The most common alternatives are OKR (objectives and key results), the Balanced Scorecard, and Management by Objectives (MBO). Each of these has its own history, mechanisms and best-fit conditions. Bain’s 2023 Management Tools & Trends Survey shows Strategic Planning at 48% adoption and Balanced Scorecard at 29%, with Dynamic Strategic Planning at only 27%, revealing that most organisations use some strategic framework but relatively few use one that adjusts continuously to new data. Understanding how these frameworks differ helps clarify when hoshin kanri is the right choice.

Hoshin kanri versus OKR

OKR (objectives and key results) emerged from Intel in the 1970s and became widely known through Google in the 2000s. It operates on a quarterly cycle with ambitious objectives scored against measurable key results, and it tends to work from the bottom up as much as top down. Hoshin kanri operates on an annual cycle with breakthrough objectives cascaded from True North through catchball, and it is stronger on the vertical and horizontal alignment mechanisms that OKR treats more lightly. The two frameworks are not mutually exclusive; several organisations use hoshin kanri for long-term strategic alignment and OKR for quarterly execution focus, treating them as complementary layers rather than substitutes.

Hoshin kanri versus Balanced Scorecard

The Balanced Scorecard was introduced by Kaplan and Norton in a 1992 Harvard Business Review article and became one of the most widely adopted strategic management frameworks of the following two decades. Its distinctive contribution is the four-perspective model (financial, customer, internal process, learning and growth) captured in a strategy map. The Balanced Scorecard is stronger than hoshin kanri as a communication artefact for external stakeholders and boards, and it forces attention to non-financial perspectives that often get neglected. Hoshin kanri is stronger as an operational execution system, with its emphasis on cascade, catchball and monthly PDCA. Many mature organisations use both: the Balanced Scorecard as the framework for defining and communicating strategy, hoshin kanri as the framework for executing it.

Hoshin kanri versus Management by Objectives (MBO)

Management by Objectives was introduced by Peter Drucker in his 1954 book The Practice of Management. It focused on individual objectives negotiated between a manager and an employee, with those individual objectives collectively adding up to organisational goals. MBO is in many ways the ancestor of both hoshin kanri and OKR, and it introduced the fundamental idea that objectives should be explicit and shared rather than implicit. Where MBO stopped was in the systemic mechanisms for cascading and coordinating objectives across the organisation. Hoshin kanri added the X matrix, catchball, and PDCA as those missing mechanisms. In organisations that still practise MBO, hoshin kanri is often adopted as an evolution rather than a replacement.

Common pitfalls when implementing hoshin kanri

Hoshin kanri implementations fail in predictable ways. Four pitfalls account for most of the failures, and each one is preventable once teams know what to look for. Recognising these pitfalls early makes the difference between an implementation that becomes part of how the organisation works and one that fades into another abandoned management initiative.

Too many breakthrough objectives

The most common mistake is setting too many breakthrough objectives at the top of the cascade. Leadership teams often have ten or fifteen priorities they consider strategically important, and the temptation to include all of them in the hoshin plan is strong. The problem is that a leadership team can only sustain focus and executive attention on a small number of major transformations simultaneously, and organisations that try to run ten or fifteen breakthroughs end up running none of them well. Toyota’s discipline of three-to-five breakthrough objectives reflects hard experience with this limit rather than an arbitrary number.

Cascade without catchball

The second common pitfall is implementing the cascade as a top-down monologue rather than a bidirectional consultation. This tends to happen when leadership feels time pressure and treats catchball as optional. The consequence is that annual objectives arrive at operational teams without buy-in, without adjustments based on operational reality, and without the sense of ownership that catchball produces. Adoption at the operational level then dies quietly within one or two cycles. Skipping catchball to save weeks in the deployment phase reliably produces execution failures later that cost months of recovery.

X matrix without review cadence

The third pitfall is treating the X matrix as an annual event rather than a living document. Teams create the X matrix in a two-day planning workshop, publish it on the wall, and then do not return to it until the following year. Without the monthly PDCA rhythm, variances accumulate silently, priorities drift, and the X matrix becomes an artefact disconnected from what actually happens the other eleven months of the year. The X matrix earns its value only through the discipline of monthly review, where each element gets examined against actual progress and adjustments get made.

Missing linkage to the project portfolio

The fourth pitfall is defining hoshin objectives without connecting them to the concrete projects that will actually deliver them. This shows up most often in organisations that treat hoshin as a strategy exercise rather than an execution system. Breakthrough objectives exist on the X matrix; annual objectives exist on the X matrix; tactical priorities exist on the X matrix; and none of them are traced through to specific projects with budgets, schedules, resources and owners. Six months in, leadership discovers that the strategic objectives are not moving because no one is doing the concrete work that would move them. This is the pitfall that most cleanly points to the need for systemic project portfolio support, which is what the next section addresses.

How systemic project portfolio support enables hoshin kanri at scale

Hoshin kanri produces strategic direction; a project portfolio management system produces execution. For a manufacturer running hoshin kanri at scale, the two need to work together rather than in parallel. FlexiProject sits in the execution layer, taking the breakthrough and annual objectives defined through the hoshin process and turning them into the operational reality of managed project portfolios. The three subsections below describe where the fit works, and the fourth describes where FlexiProject deliberately does not compete with the hoshin process itself.

From X matrix to project portfolio

The X matrix defines what the organisation intends to achieve; the project portfolio delivers it. FlexiProject holds the projects that materialise each breakthrough objective, each annual objective and each tactical priority, with visible traceability from the strategic goal to the concrete work being done. A breakthrough objective around capacity growth cascades into three annual objectives, each of which drives four or five projects in the capex portfolio. A breakthrough objective around product innovation cascades into annual objectives that drive projects in the NPD portfolio. The connection stays visible because every project inside FlexiProject can be tagged to the specific hoshin objective it serves.

KPI cascading across portfolios

The KPIs on the X matrix cascade down to KPIs at portfolio level and KPIs at project level. FlexiProject enables this cascade in a system rather than in spreadsheets and email threads. A hoshin KPI on defect rate at enterprise level rolls down into portfolio-level KPIs on kaizen event outcomes, and further down into project-level KPIs on individual improvement initiatives. When the enterprise KPI moves, leadership can trace exactly which portfolios and which projects drove the movement, and when it does not move, leadership can see where the execution is stuck. That traceability is what turns KPIs from monthly reporting numbers into actual pulse of the strategy.

What FlexiProject does not do

FlexiProject does not draw the X matrix, does not facilitate catchball conversations, and does not replace the strategic thinking that goes into defining True North and breakthrough objectives. Those activities belong in the hoshin process itself, facilitated by leadership and often supported by dedicated strategy facilitation tools or workshops. FlexiProject picks up after the strategic direction is defined, taking the outputs of the hoshin process and running the project portfolio that executes them. This honest boundary matters because it prevents the failure mode of buying a tool and expecting it to substitute for the strategic conversation. Hoshin kanri is a management practice; project portfolio management is the operational infrastructure that lets that practice actually produce results.

Frequently asked questions

Is hoshin kanri only for manufacturing?

No. Manufacturing is where hoshin kanri was developed and where it remains the strongest fit, but it works in any organisation that has multi-year strategic ambitions, multiple functions that need to coordinate, and enough size that the strategy cannot simply be communicated verbally. Hewlett-Packard, Danaher and John Deere run it in manufacturing contexts, but Cisco and Intel run variants in technology, and healthcare systems, financial services and government agencies have adopted the method in the last two decades. What matters is not the industry but the presence of the underlying problem hoshin kanri solves.

How long does hoshin kanri implementation take?

A first hoshin kanri cycle typically takes three to six months from executive commitment to the first monthly review. Setting True North and breakthrough objectives is fast (two to four weeks); cascading annual objectives through catchball takes longer (six to ten weeks); establishing the monthly PDCA rhythm takes another four to eight weeks of practice before it becomes routine. The method reaches maturity over two to three annual cycles rather than in the first year. Organisations that expect hoshin kanri to be operational in the first quarter tend to skip catchball and pay for that shortcut in adoption failures later.

Can hoshin kanri coexist with OKR?

Yes, and several organisations use both frameworks together. Hoshin kanri handles the annual strategic cascade with a five-year horizon and monthly PDCA; OKR handles quarterly execution focus with team-level accountability. The two frameworks map onto different time horizons and different organisational levels rather than competing for the same slot. The pattern that works is to derive OKR objectives each quarter from the hoshin annual objectives, treating OKR as the quarterly refinement of the annual plan rather than a parallel strategic framework.

What is the ideal number of breakthrough objectives?

Three to five is the standard recommendation, drawn from Toyota’s practice and confirmed by decades of implementations elsewhere. The number reflects the practical limit of executive attention rather than any theoretical principle. A leadership team can genuinely focus on three or four major transformations simultaneously; beyond five, focus dilutes and none of the breakthroughs get the sustained attention they need to succeed. Organisations that come to hoshin kanri with ten or fifteen strategic priorities need to do the difficult work of prioritising down to three-to-five before they can run hoshin kanri effectively.

Do we need special software for hoshin kanri?

Not for the hoshin process itself. The X matrix can be created in PowerPoint, on a whiteboard, or in a dedicated visualisation tool; catchball happens in meetings; monthly PDCA reviews happen in conference rooms. What does need software support is the execution layer beneath hoshin: the project portfolios that materialise the strategic objectives. A project portfolio management system is what turns hoshin kanri from a strategic exercise into operational reality, providing the traceability from breakthrough objectives to concrete projects, the KPI cascade from enterprise level to project level, and the review cadence that keeps the plan connected to execution.

Hoshin kanri is a Japanese strategic management method that connects long-term company direction to daily operational execution through four principles: vertical alignment cascading goals from CEO to shop floor, horizontal alignment coordinating across departments, PDCA turning strategy into a continuous learning cycle, and catchball ensuring the cascade is a bidirectional conversation. Its visual signature is the X matrix, a single-page diagram that captures long-term goals, annual objectives, improvement priorities, metrics, correlations and owners in one view. The canonical implementation follows seven steps, from defining True North through annual reflection (hansei), and in manufacturing it materialises as a project portfolio where breakthrough objectives break down into concrete capital investments, new product development projects, kaizen initiatives and engineering-to-order fulfilment. Compared with OKR, Balanced Scorecard and MBO, hoshin kanri stands out for its combination of annual cascade discipline and monthly PDCA rhythm, which is why manufacturers with multi-year strategic ambitions and multiple project portfolios keep returning to it as their operational strategy framework. FlexiProject provides the execution layer beneath hoshin kanri, running the project portfolios that materialise strategic objectives without trying to substitute for the strategic conversation itself. If a manufacturer’s hoshin implementation needs a portfolio management system to close the loop between strategic direction and daily execution, thirty days of full access with no credit card is a practical way to test the fit.