The Montags-Check

Where your work waits and why. In 2 to 6 weeks.

For organisations where everyone is busy and the work still takes too long. We measure where it waits, find the cause in the organisation, the workflow or IT, and put a target design in front of you.

Implementation is not part of it. You commission it separately afterwards, if you want.

Request the Montags-Check

Rather talk first? The intro call is free and takes 30 to 60 minutes, in person in Hamburg or Munich if you prefer.

Lead time from 20 days to 5, measured across the entire value stream (Energy). Read the full case

How the check works

Four steps, as in every one of our projects

1
Measure
We measure where the work waits: how long it lies, how often it is handed over and what each station spends its time on. Afterwards it is clear where the bottleneck sits.
2
Find the cause
We lay the org chart, the process map and the system landscape on top of each other. Where ownership and system boundaries do not match, we look for the cause.
3
Exploit
We check what can be got out of the bottleneck without rebuilding anything, and try it out. We record what it brought.
4
Decide
You get a decision paper: leave the bottleneck where it is and use it fully, or elevate it. With options and costs.

After that come steps 3 and 4 of how we work, changing things together and staying until it runs, as a separate assignment. How we work →

Result

What you have in hand afterwards

Baseline report: the measurement at the start. You measure every later change against it.
Conway map: org chart, process map and system landscape on top of each other, with the places where ownership and system do not match.
Bottleneck diagnosis: where the bottleneck sits, what keeps it there and in which layer the cause lies.
Exploit log: what we tried at the bottleneck without rebuilding anything, and what it brought.
Decision paper: the options with their costs.
Exit criterion: The check is done when the decision paper is ready and you can decide without us how to go on.

In a picture

What the Conway map makes visible

Both teams are busy. The work waits at the boundary between them, and that boundary was drawn by the org chart.

The principle with twelve teams and systems

Prerequisites

What we need from you

To reach a diagnosis in 2 to 6 weeks, we need from you:

Access to case or ticket data (Jira, ServiceNow, ERP workflow or similar)
the current org chart
an overview of the system landscape
one contact each from the business, the workflow and IT
a sponsor from the management board or division management

Frame

Duration, team, price

Duration

2 to 6 weeks, depending on size.

Team

Always with IT depth. The same people look through all three layers, in the same week.

Price

Fixed price by size, from €12,000 plus VAT. The size is set by the number of teams and systems in the value stream under review.

References

An example

From 20 days to 5

Energy

The bottleneck: the approvals. Every configuration waited for several departments that had to sign off one after another.

The cause: an agile operating model in which the approvals had stayed in the old line organisation. (organisation)

Our solution: We reviewed the operating model, removed the approvals that slowed things down, streamlined the end-to-end process with BPMN and Lean, and cleaned up the portfolio.

Key result

Lead time from 20 days to 5. It has stayed there ever since.

Organisation Process

Read the full case