All cases Case study – MedTech

When growth slows down innovation

Today, almost 50 teams deliver in a shared cadence.

Client
A global MedTech company
Industry
MedTech

Starting point

A global MedTech company realized that its organically grown structures were standing in the way of product development. We were engaged to develop the organization so that, despite its size, it becomes faster and more effective.

Six unconventional levers

  • The design team as the engine

    The transformation started in March 2024 with the mobilization of an internal design team. While the client team contributed the subject-matter expertise, we took on methodological leadership as enabler and facilitator. The design team consisted of 10 to 15 key people from different functions and hierarchy levels. All of them were released from 50% of their regular duties for the core phase of six to eight weeks. This was essential to drive the complex conceptual work with the necessary intensity.
  • Co-creation in practice

    The design phase was carried out consistently in co-creation. The future process organization was developed in joint workshops and sprints. We formed sub-teams to work out specific aspects such as role profiles, process flows or tool requirements in detail. This participatory approach helped us take into account the geographical distribution and the operational reality of the sites.
  • Providing a framework, enabling impact

    In this phase, we acted primarily as enabler and facilitator: Structure: We provided the methodological framework and ensured a common thread across all work steps. Facilitation: We led workshops and supported team development within the design team. Project management: We kept schedules on track and ensured the quality of the results.
  • The playbook as the foundation

    The design phase concluded with the playbook. As the central design concept, it defines roles, responsibilities, tools and processes. In the following phases, it served as the binding basis, was continuously updated and formed the foundation for the entire implementation planning.
  • Flexibility beats rigid roadmaps

    After design comes planning. But how do you plan a transformation for more than 1,000 employees across different sites and several business areas? By understanding communication as part of the implementation. Because transformation processes rarely run in a straight line, we deliberately avoided a tight communication corset. Instead of a fixed editorial plan, we worked our way forward step by step. This gave employees the clarity they needed in each phase while leaving us the freedom to respond quickly and realistically to unforeseen developments. The guardrails: Fast: regular updates, short response times, clear messages. Consistent: firmly embedded in the overall context of the transformation. Reliable: clear responsibilities and regular dates. Repeated: core messages were reinforced continuously across all channels. Targeted: information was tailored to each role so that it was relevant in day-to-day work.
  • Push instead of pull channels

    Our experience has shown that purely passive information offerings such as the intranet generate hardly any traffic in large projects. We therefore deliberately relied on push channels: Newsletter: The newsletter served as the main steering tool, with an open rate of around 80%. It was so successful that it was soon extended to adjacent areas. Engagement sessions: Virtual town halls with more than 200 participants delivered practical updates on implementation and training. Community channels: Google Chat spaces were set up for specific roles such as Product Owners and Technical Leads to foster professional exchange.
1’000+ employees in the transformation
~50 teams in the new structure

The transformation in numbers

80%
open rate of the newsletter as the main steering tool
200+
people at the first Program Increment Planning
~50
internal team coaches trained
4
iterative mandates instead of one large project
12
weeks planning cadence across all teams
10–15
key people in the design team, released 50% from their regular duties
3
weeks synchronized sprint rhythm

What is different today

More stable structures

Today, work increasingly comes to the teams. This helps to concentrate knowledge in stable units, even if the new processes still need to settle in detail.

Clearer accountability

New roles such as Product Owners help the teams gradually set priorities based more on real impact and less on who is loudest.

More transparency

Thanks to Jira™ and joint PI Planning, dependencies become visible much earlier.

The full story

Every phase, decision and learning in the complete case study. We will send it to you personally by email.

One-pager (PDF, 1 page) Instant, no form Download PDF