Make the work and its owner visible
Map how a task starts, which information it needs and what counts as completion. Approvals, scheduling or service delivery can then use explicit states and assigned responsibilities. Staff should be able to distinguish work waiting for input from work ready for action and work already completed.
Build around the operating rules
Agree who may change records, which checks prevent invalid transitions and what happens when information is missing. Persistent records must support the team’s next action. Existing-system connections are scoped separately, and a recovery path is needed when a dependency is unavailable or a task is interrupted.
Bring one process worth fixing
Share sample records, current spreadsheets and an example task from start to finish. Include unusual cases and the person who resolves them. We agree a first release for one team and test it against the process before considering additional departments, workflows or integrations.