From Lean Projects to Lean Enterprise: Using Hoshin Kanri to Make Lean Construction Stick

Why This Paper Matters

Lean Construction has demonstrated that project teams can improve planning reliability, coordination, workflow, and collaboration. However, these improvements often weaken when the project ends.

Project teams disperse, leaders rotate, client and contractual conditions change, and improvement routines are not always transferred to the next project. In many organizations, Lean therefore depends on a few committed champions rather than on a durable company-wide management system.

The result is a recurring pattern:

• One project achieves strong Lean results.
• The next project starts again from the beginning.
• Lessons learned remain within the previous team.
• Different projects adopt Lean at different levels.
• Leadership attention shifts to other priorities.
• Lean gradually becomes an optional initiative rather than the normal way of managing work.

The paper argues that this is not mainly a problem with Lean tools. Last Planner, pull planning, visual management, A3 problem-solving, and other practices can work effectively. The deeper issue is whether the organization has a governance system that keeps priorities clear, connects strategy with project execution, and carries learning from one project to another.

This paper matters because it reframes Lean sustainability as an enterprise management problem, not simply a project implementation problem.

What the Paper is Saying

The central argument is that Lean Construction and Hoshin Kanri address different but connected needs.

Lean Construction primarily provides principles and routines for improving project production. It helps project teams plan collaboratively, manage flow, remove constraints, solve problems, and improve reliability.

Hoshin Kanri provides a system for deciding which improvements matter most, translating them across organizational levels, reviewing progress, and ensuring that learning influences future work.

In simple terms: Lean Construction improves how projects operate, while Hoshin Kanri helps the company sustain, align, and learn from those improvements.

The paper identifies three recurring enterprise-level problems:

The paper proposes Hoshin Kanri as a possible response because it provides mechanisms for focus, alignment, review, and learning across the enterprise.

The Approach or Idea Introduced

Hoshin Kanri, often translated as policy deployment or strategy deployment, is a management system that connects long-term organizational direction with annual priorities and day-to-day execution.

The paper emphasizes that Hoshin Kanri should not be reduced to an X-matrix or an annual planning workshop. Its value comes from the management routines that keep priorities, execution, and learning connected.

Three mechanisms are especially important:

Focus on the “Vital Few”

Hoshin Kanri requires leadership to select a limited number of strategic priorities rather than launch too many disconnected initiatives.

For Lean Construction, this means the organization may decide that certain capabilities—such as reliable planning, constraint management, production flow, or collaborative problem-solving—are enterprise priorities that must be developed consistently across projects.

This focus helps prevent Lean from becoming one more initiative competing for attention.

Catchball: Turning Strategy into Feasible Commitments

Catchball is an iterative dialogue in which objectives, methods, resources, constraints, and targets are discussed across leadership, functions, and project teams.

Instead of senior leaders simply cascading Lean targets downward, project teams help determine:

• What is realistic in their project context?
• What resources and capabilities are required?
• What constraints will affect implementation?
• What measures should be used?
• What support must come from the enterprise?

This dialogue improves ownership and reduces the gap between corporate ambition and project reality.

Structured Review and PDCA

Hoshin Kanri uses recurring reviews to examine both performance and the health of the management system.

Monthly or periodic reviews identify gaps, obstacles, and required countermeasures while work is still in progress. Annual reviews examine whether the right priorities were selected and whether the organization’s deployment process worked effectively.

This is different from traditional lessons learned, which often occur after the project has finished. Hoshin Kanri is intended to make learning continuous and connected to execution.

The paper therefore presents Hoshin Kanri as the managerial infrastructure that may connect project-level Lean practices with enterprise strategy, accountability, and organizational learning.

Potential Benefits

The proposed integration may help construction companies achieve several benefits:

• More Consistent Lean Adoption: By defining Lean as an enterprise priority and reviewing it regularly, companies can reduce variation between projects and avoid depending entirely on local champions.
• Better Alignment Between Corporate and Project Priorities: Catchball allows enterprise strategy to be translated into practical project commitments while ensuring that site realities, contractual conditions, and resource limitations inform corporate decisions.
• Reduced Initiative Overload: The “vital few” principle helps leadership concentrate attention and resources on a small number of improvements that directly support business strategy.
• Faster Cross-Project Learning: Recurring reviews can identify lessons while projects are still active and convert them into updated standards, training, routines, or support for other projects.
• Greater Leadership Accountability: Hoshin Kanri makes Lean sustainability a leadership responsibility rather than something delegated only to Lean specialists or project teams. Leaders must review progress, remove organizational constraints, allocate resources, and evaluate whether the management system itself is functioning.
• Stronger Organizational Capability: Over time, Lean knowledge may become embedded in normal management routines, standards, leadership expectations, and organizational identity. The company gradually moves from “using Lean on selected projects” toward operating as a Lean enterprise.

These benefits are supported conceptually by the literature and cases reviewed in the paper, but they have not yet been validated as causal outcomes through a longitudinal enterprise-level study.

Challenges and Implementation

Hoshin Kanri will not automatically make Lean sustainable. Poor implementation may turn it into another planning or reporting exercise.

Key challenges include:

• Leadership selecting too many priorities
• Targets being cascaded without meaningful catchball
• Reviews becoming status-report meetings rather than problem-solving discussions
• Excessive focus on the X-matrix instead of management behavior
• Corporate priorities being disconnected from project conditions
• Project teams perceiving Lean as additional work
• Learning being documented but not converted into standards or routines
• Lean remaining dependent on specialists rather than line management

APDI Perspective and Way Forward

From APDI’s perspective, the paper addresses one of the most important reasons Lean transformations fail: organizations focus heavily on tools and project pilots but pay insufficient attention to enterprise governance.

Many companies have already conducted Lean training, implemented pull planning, established visual boards, or piloted Last Planner. Yet implementation weakens when the original project ends or when the people who led the initiative move elsewhere.

This suggests that the real challenge is not simply how to implement Lean, but:

How does the organization keep Lean aligned, reviewed, learned, and reinforced across projects for many years?

Hoshin Kanri offers a useful response because it connects four levels that are often separated in construction companies:

• Enterprise strategy
• Functional and business-unit priorities
• Project-level commitments
• Daily operational management

For Indonesian construction and EPC companies, the approach must be adapted to local conditions. Important considerations include hierarchical decision-making, reluctance to challenge unrealistic targets, strong functional silos, inconsistent project leadership, and the tendency for improvement programs to depend on senior sponsorship without becoming embedded in normal management.

Catchball may be especially valuable in this context. However, it must become a genuine two-way dialogue rather than a formal meeting in which project teams are expected to agree with targets already decided by leadership.

APDI also sees an important connection between Hoshin Kanri and other Lean management practices:

• Hoshin Kanri selects and deploys strategic priorities.
• A3 thinking supports structured problem-solving.
• Last Planner improves project production planning and commitment reliability.
• Daily management provides operational visibility and escalation.
• Standardization and knowledge management carry learning across projects.

The next step should be a longitudinal pilot within a contractor or EPC company that manages multiple projects. The pilot should examine whether Hoshin Kanri improves:

• Consistency of Lean adoption across projects
• Alignment between enterprise strategy and project practices
• Leadership participation and accountability
• Transfer of lessons and standards between projects
• Continuity of Lean routines after project and leadership transitions
• Business and project performance over several review cycles

The paper’s most important contribution is its shift in perspective: Lean Construction becomes sustainable not when more tools are deployed, but when the organization creates a management system that keeps priorities focused, commitments aligned, reviews active, and learning moving from one project to the next.