Why continuous improvement, IT projects and business re-engineering never meet

Continuous improvement owns kaizen, Six Sigma projects and loss analysis. It moves fast, works locally and rarely gets engineering time for data access.

IT and digital owns systems, integrations and security. It moves at project cadence, is measured on delivery and risk, and is structurally cautious about tools business teams can change.

Business process re-engineering owns the operating model, often with a consultancy attached. It redesigns how work should happen, then hands over a target state that neither of the other two was resourced to build.

CI projects stall waiting for data. IT builds integrations without the process context that makes them useful. Re-engineering programmes design flows nobody can measure. The same downtime loss appears in three separate initiatives, each with its own definition, and none of them closes it.

The pattern that works: IT owns access, governance and security; business and CI teams own the Flows, calculations and apps built on top of that access. Nobody waits in a queue, and nobody bypasses controls.

In several deployments the business team built the integrations, the analytics and the alerts themselves, with IT providing access and governance. Delivery time changed from quarters to days without weakening control.

Pick one loss that all three groups already care about. Agree its definition in writing. Give the CI owner governed access to the data behind it. Let IT keep the guardrails. Publish the result where everyone sees the same number.

One shared number, owned jointly, does more for cross-functional alignment than a steering committee.