INSIGHT / FIELD NOTE

Why operating models should follow the work

For many organisations, the strongest model starts with how value actually moves through the business rather than the org chart.

READING NOTE

IN THIS ARTICLE

    Organisation charts show reporting relationships. Operating models need to show how work, decisions, information and accountability move from demand to outcome. Those are related views, but they are not the same thing.

    Start with value flow

    Choose a meaningful unit of work such as a customer request, product change, service case or investment decision and follow it end to end. Note where it enters the organisation, where it waits, which teams change it and which decisions determine whether it moves forward.

    This view reveals dependencies that a department-by-department review can miss. A process may appear efficient inside each function while the total journey is slow because every boundary creates a queue, a recheck or a new interpretation of priority.

    Design the interfaces between teams

    Operating problems often live at interfaces. One team completes its task but the next team lacks context. Measures reward local output while the overall outcome deteriorates. Ownership changes without a clear acceptance point.

    A stronger model defines what passes across each boundary and what good handoff quality looks like.

    • What information must travel with the work?
    • Who accepts the handoff and can reject incomplete input?
    • Which measure reflects the end-to-end outcome rather than local activity?
    • Where should an exception be resolved instead of escalated?

    Use structure only where it helps the flow

    Once the work is understood, roles, teams and governance can be designed around it. Sometimes that confirms the existing structure. In other cases it shows that a cross-functional team, shared service or different decision cadence would remove unnecessary coordination.

    The point is not constant reorganisation. It is to stop treating the current reporting structure as proof that the operating model is already coherent.

    Measure the work, not the diagram

    A redesigned model should improve observable behaviour: cycle time, quality, predictability, decision speed, customer outcome or the amount of rework between teams. If the only evidence of change is a new chart and new role titles, the operating model has not yet been tested.

    Follow the work again after implementation. The gaps between the intended model and actual behaviour are where the next useful adjustments become visible.

    DECISION CHECK

    The organisation chart tells you where people report. The operating model should tell you how the organisation produces an outcome.

    Your next move is already visible

    Now make it earn its place.