GOOD STORIES

Fixing Bottlenecks in Product Release

Delays in the approval and release processes can create significant bottlenecks in the supply chain, jeopardizing a company's ability to meet demand. We recently helped a client overcome such challenges by implementing a Flow Management System. Here, we tackled inefficiencies in their batch release process, ultimately reducing lead time variability by 37% and enabling weekly releases to triple. This scalable solution, now being digitized for broader application, empowered our client to exceed weekly targets and restore operational predictability.

THE CHALLENGE

Release Process Becomes Supply Chain Bottleneck

The client reached out because the approval of deviations and batch release for external manufacturers had become a bottleneck in their supply chain. They were unable to meet their weekly targets and, without intervention, could not see how they would catch up to their yearly target.

Unable to meet demand and unaware of the root cause, management felt that their unpredictable performance was affecting their trustworthiness and leverage, both internally and with their manufacturers.

For the project to be successful, the objectives were to:

  • Improve the predictability of batch releases
  • Increase weekly releases to enable them to meet their yearly target
  • Ensure the solution was scalable to handle the additional scope of products and manufacturers
Group of people sitting around a table with laptops in an office or meeting room with large windows and curtains.

OUR APPROACH

Implementing a Flow Management System

We approached the problem using our Observe-Think-Improve methodology to ensure any solution targeted the right problem.

Visual showcasing company approach

OBSERVE

Understanding the Current State

Verification of Core Process Activity

Prior to our arrival, a process mapping workshop had been held. To reduce re-work, we decided to verify the mapping with users to add enriching details like timeframes, document flows, and IT systems. This also helped us identify necessary and wasteful process variations. The review uncovered several systemic issues:

  • Frequent changes in deviation ownership led to unclear responsibilities and deadlines.
  • Task allocation, critical to the process, was performed reactively due to perceived unpredictability.
  • Variations among manufacturers prevented process and IT system standardization as this did not fit into the internal IT landscape and process standard.

Analysis of Current Process Performance

The process verification provided insight into the IT landscape, enabling the creation of a dataset to analyze past process performance. Key findings included:

  • A lead time of over 10 days from deviation occurrence to client notification.
  • 25% of deviation reports were late, adding an average of 17 days to release lead times.

Assessment of Supporting Processes

The analysis showed that control mechanisms, such as securing deviation reports were handled and ensuring early notifications, could greatly stabilize release times. However, coordination meetings revealed that processes were more reactive than proactive. Every week, the batches were hand-carried for release, which often delayed other tasks. Key observations were:

  • Late issue discovery increased resolution times, delaying releases.
  • Overtime was frequently required as unexpected issues arose late in the week.
Icons on a dark background: binoculars (exploration), magnifying glass with arrow pointing to target (analysis), folder with connected elements (information), document with key symbol (security), interconnected nodes/gears (network), and arrows around a question mark (direction).

THINK

Developing and Testing the Hypothesis

Problem definition

Due to a lack of overview of activities and effort required before the expected week of release, the organization spends its effort clarifying the status of activities, assigning tasks, and escalating issues for a batch during the same week. This limits their performance as they can focus their efforts only on one to two prioritized batches.

Hypothesis

Implementing a takt system with the activities and relative effort required prior to release would enable the organization to

  1. Complete activities earlier, positively impacting lead time
  2. Enable earlier escalation, increasing the chance of the organization being able to “bounce back” form delays.
  3. Remove delays in the week of release, reducing the need for overtime.
Icons on a dark background: brain with radiating lines (thinking), documents with calendar and graph (planning), and clock with motion lines (time management).

IMPROVE

Continuous Improvement and Anchoring Change

To test this hypothesis, the team developed a minimally viable solution to quickly implement and adapt the tool. They used a standard takt time to align with current performance, focusing on three key elements during implementation:

  1. Process Transparency: The process map was showcased to clarify responsibilities and identify whether issues stemmed from the process or non-compliance. It facilitated ongoing improvement discussions, shifting from solving individual issues to reducing process risks.
  2. Flow Management: The team aggregated tasks into a takt flow to plan releases and manage deviations. The takt time highlighted tasks that needed completion to meet weekly and future release targets, helping allocate resources more efficiently.
  3. Structure Support: The team integrated the takt tool into daily meetings for quick issue escalation. It provided clear paths for escalation to management, ensuring timely resolution of resource allocation and other operational issues.

After implementation, weekly releases increased. Continuous improvements were made based on user feedback, with the tool being maintained and enhanced by the users themselves. The organization embraced the tool, often exceeding weekly targets by up to 70%, a performance previously unseen.

As the solution proved effective, we moved to digitalization. Wireframes, user stories, and requirements were created, and we advised the business on software options. Once a supplier was selected, we supported the development and implementation of the digital tool.

Icons on a dark background: document with magnifying glasses (analysis), hand with bar graph (growth), arrows in motion (strategy), and light bulb with puzzle pieces (innovation).

The Results

Increased Efficiency and Predictability

Within six months, we achieved the following results:

  • Reduced variance to enable better predictions of releases: The variance in batch release lead time was by reduced by 37% percent, overall enabling better predictions of releases.
  • Increase in weekly releases to meet yearly target: The team achieved 3x more releases weekly on average, positioning them on the right path to meet their yearly target.
  • Scalable solution: We supported the initiation of a fully digitalized solution, capable of scaling up the benefits with an additional scope of products and manufacturers. We anchored the solution with the users to ensure the results will continue after our departure.

KEEN TO LEARN MORE?

Ready to Unblock Your Release Process?

If this story felt familiar, you’re not alone. We helped this client cut lead time variability by 37% and triple their weekly releases—without overloading the team. 

If you’re facing similar bottlenecks, contact Jakob G. Thorup, Partner at Emendo Improvement, to explore how we can help restore predictability to your release flow. 

Jakob Thorup Hansen

Jakob Gradert Thorup

Partner

Explore Our Good Stories

HAVE A QUESTION

Get in touch.

FAQ

  1. A flow management system organizes and monitors the sequence and timing of tasks required to move products through processes such as batch release, production, or distribution. It helps streamline workflows, improve predictability, and reduce bottlenecks by visualizing task dependencies and prioritizing work in progress. 

  2. Bottlenecks in product release can lead to delayed shipments, unmet customer demand, increased operational costs, and reduced overall supply chain efficiency. Addressing these bottlenecks is essential for maintaining reliable production schedules and meeting yearly output targets. 

  3. Typical causes include: 

    • Unclear process responsibilities 
    • Reactive rather than proactive task allocation 
    • Lack of process transparency 
    • Inefficient deviation management 
    • Manual handovers or approval processes without digital support 
  4. A takt-based flow management system breaks down workflows into standardized time units (takt time), enabling teams to align tasks, anticipate issues, and proactively manage workloads. This approach reduces late escalations, clarifies priorities, and minimizes lead time variability. 

  5. Digitalization provides real-time visibility, automates task tracking, integrates data from multiple systems, and improves scalability. It helps maintain consistency across departments and locations while reducing reliance on manual processes or paper-based methods.