A growing Danish manufacturer of electric linear actuators adopts lean product development and creates a highly-disciplined new product development process that hits milestones with 30-40% faster lead times.

One of the seemingly inescapable fates of a growing business is that the larger it gets the more bureaucratic it becomes. Over time, a fast and agile company gradually becomes slower and less responsive to customer needs and market changes.

The company embarked on its first major change initiative. “Our customers loved what we made because it fit their needs, but our quality wasn’t always superb,” recalls John Frost, V.P. & General Manager.

One of the biggest challenges of that initial quality improvement project was top management. Managers had a tough time getting used to the different pace, new metrics and more deliberate quality control processes.


Challenge: Product development cycles became inconsistent and slow after recent decades of dramatic growth. Company leaders wanted to redesign the product development process to accelerate lead times and hit launch targets.

The company began implementing lean manufacturing practices in its production areas. That initiative eliminated excess handling, movement and inventory, significantly increasing throughput and productivity. 

Not long after LINAK implemented lean manufacturing practices in its production areas, it launched lean initiatives in its R&D departments. The process changes didn’t take root. Frost says the company wasn’t far enough along to apply lean to R&D.

TBM began working with LINAK to design and implement a new product development process. Management liked the kaizen workshop approach which forced cross-functional agreement and cooperation.

“A more structured way of doing R&D will give us speed and efficiency.”

Following an initial assessment of past projects, the first kaizen event team mapped out each phase of the current development process on a long sheet of brown paper. It was enlightening. Everyone had a rough idea of the process which had become messier over the years, but no one really had a detailed view of everything that happened from idea generation to product launch.

During subsequent kaizen workshops, improvement teams designed the new development process from the initial idea and project team formation through product launch and business review.

Solution: We analyzed the current development process and designed a three-tier process based on product complexity. This included periodic portfolio reviews, restructured project planning, performance management, and weekly escalation meetings to quickly resolve issues.

To achieve the objective, Linak Kaizen teams:

  • Analyzed the development workload by function
  • Established detailed flow and time estimates
  • Created a three-tier development process based on product complexity
  • Implemented a periodic review of new product ideas to actively manage the product portfolio and align resources
  • Created a restructured planning and performance management process to monitor tasks and due dates
  • Developed and tracked KPIs (planned vs. actual hours and completed dates)
  • Established weekly escalation meetings to address failures and road blocks software

The new approach also includes a periodic review of new product ideas to align resources and more actively manage the company’s product portfolio.

A restructured project planning and performance management process monitors tasks and due dates. They are also tracking key performance indicators (planned to actual hours, and completion dates, for each task) to drive future improvement.

Results: After more than a year of planning and initial implementation, the company was well on its way to achieving 30-40% faster product development lead times.

Going forward, product development managers will address any failures or roadblocks in weekly escalation meetings. “In R&D you’re typically trying to do something that has never been done before,” Frost concludes. “A lot of strange things can happen, and it’s rare where you have a project that runs as you believed or anticipated.”

Topics in this Case Study