Cockpit
    November 11, 2025 · 1 min

    Cadence, not framework

    Cadence

    Two-week sprints for everything and everyone, whether they fit or not, only create frustration.

    A technical process is NOT a functional process, NOT a governance process and NOT a strategy.

    Some tasks take seconds, others a day, a few workdays, two weeks or three months. The key is Cadence!

    How do you harmonize these different processes and rhythms meaningfully? That is precisely the art.

    A company offering Software as a Service (SaaS) for B2C customers needs different ways of working, methods and roles in a team building web app features than a company manufacturing physical products for B2B customers, where a team is rolling out a new ERP system.

    A pharmaceutical company needs different approaches for teams supporting field sales reps than a public authority facing the task of migrating large monolithic legacy systems that must reliably serve citizens.

    Implementing an AI chatbot for general use is a different AI initiative than building predictive maintenance for machinery.

    Sure — you have to start somewhere. But the best starting point is not an off-the-shelf framework — it is mindset and culture.

    Keep reading: