Cockpit
    November 1, 2026 · 6 min

    When you need me – and when you don't

    Organization DesignOrganizational Debt

    You do NOT need me if …

    Your organization does NOT need a transformation if most of these points are lived reality for you:

    • It is crystal clear what winning looks like, and missing goals always has consequences.
    • One team or a group of teams covers the entire end-to-end responsibility, where one end is the customer and the other end is the deepest backend.
    • Whether your teams build software or data solutions: the teams are small, include business experts, and either the engineers talk directly to customers/users/citizens or another team member does so and actively works to find out what they want and need.
    • Every initiative is framed as hypotheses with kill criteria, checked regularly through short experiments, so direction can change quickly if assumptions don't hold.
    • Even if you woke someone in the middle of the night, anyone could recite the strategy in two sentences at most.
    • Processes and structures are lean and customer satisfaction rises steadily.
    • Workflows are efficient and at the same time flexible enough to react quickly.
    • Leaders work as a team and jointly own the results of several teams.
    • Clear, tightly scoped guidelines set the direction and are measured against KPIs in short iterations.
    • Every software or data solution is understood as temporary, with a fairly short half-life.
    • The number of initiatives spanning many teams is limited, so lead time stays short and measurable results are delivered regularly.
    • Individual learning is shared within the team, and team learning is shared across the organization.
    • Everyone understands how AI can be used in daily work for the benefit of customers/users/citizens.
    • Motivation is high, drawn from ambitious goals, the freedom to reach them as a team, and clear rules everyone follows.
    • Career paths, incentives and workflows are all aligned with the value chain.
    • All roles work on gaining more business and more technology understanding.
    • Lived rituals that fit the organization make the culture visible.

    When you need me

    Checklist — which symptoms tell you that your organization needs a transformation? The more of them you recognize, the more urgent the need to act:

    • Weeks or months pass between identifying a helpful improvement for the customer, user or citizen and that improvement being usable in production.
    • Several layers of leading, coordinating and managing roles across multiple hierarchy levels sit between an engineer and a customer, user or citizen.
    • You can easily fill a workshop with more than 30 people, most of whom want a say in what gets built and how — without being responsible for delivering it.
    • In your organization, careers are made by climbing the hierarchy — you leave a team and steer people.
    • Ask several team members about the current strategy and you get different answers.
    • A major strategic change of direction is barely possible because of historically grown structures and requires a long, costly, exhausting effort — by the time it's done, the strategy is outdated again.
    • The org chart and the actual workflow organization together form a kind of matrix.
    • Some activities many people want to do, so roles step on each other's toes — and other activities nobody wants to do.
    • A few people carry excessive responsibility, while most hold a small slice cut out of a larger context.
    • Coordinating and leading roles from different areas have partly different or conflicting goals or approaches.
    • Classic project management methods are applied by gut feeling and individually.
    • Classic project management methods degenerate into bureaucratic overhead.
    • Nobody can stand hearing "agile" anymore; Scrum was introduced, but agile values are not lived.
    • Your teams know only a handful of methods and apply even fewer.
    • Most delivery teams consist mainly of engineers or technical roles.
    • There are strong dependencies between teams.
    • Becoming a team lead is still an important career step in your organization.
    • There are conflicts in your organization that have become a real obstacle.
    • Team members cannot resolve conflicts on their own.
    • Sick days and turnover are high.
    • In your organization, strategy means slides and meetings, but nothing beyond that.
    • Leaders barely understand what engineers do.
    • Engineers barely understand what leaders do.
    • Words like "failure", "problem" or "mistake" are part of everyday language.
    • The dominant problem-solving strategy is calling a meeting with more than 10 invitees.
    • The same topics keep coming up and the same problems are discussed again and again.
    • Team members work on several things at once and are interrupted several times a day.
    • Almost everyone feels too much is happening at once and that calm and focus are missing.
    • Reviews are either so technical that business colleagues feel they get no value, or mostly slides, so engineers feel they get no value.
    • Using a restaurant as a metaphor, your planning feels roughly like this: the guests order a four-course menu and are irritated by construction noise, because a conservatory is being built while the restaurant is open. After the waiter has had to ask several times because of the noise, the cooks first have to go shopping, since a dish on the menu was never discussed and the ingredients are missing. Two cooks leave, the others get bored and have to help on the construction site. Once the ingredients arrive, total chaos breaks out and nobody knows where they are assigned. In the end there is too much meat and no sauce (nobody was responsible, and it wasn't explicitly on the menu). The vegetables are overcooked by now. The guests are appalled, the food was bad and the construction site unbearable. They leave quickly, never come back and order fast food instead. The construction site keeps growing, and conflicts arise in the kitchen and between kitchen and service.
    • You dream of planning working like a Michelin-starred restaurant: the menu is well thought out, the guests order, processes are clearly defined and the menu is ready in no time. The guests are delighted, come back regularly and recommend you.

    Keep reading: