By 
Follow the work
Choose a recurring workflow with a clear owner, such as receiving and approving a service request. Map who starts it, what information moves, where it waits and how completion is recognised. Ask the team to describe unusual cases. A process map that ignores exceptions will provide an incomplete basis for a new system.
Remove unnecessary complexity
Question duplicate entry, unclear approvals and reports nobody uses. Agree which controls are essential and who owns them. Automating a poorly understood process can preserve its problems at greater speed. Make a small improvement to the process itself before committing to a larger technical solution.
Choose a baseline and an outcome
Measure something the process owner can explain: elapsed time, rework, incomplete requests or time spent looking for information. Define how it will be measured and over what period. Avoid promising a percentage improvement without evidence. The purpose of the baseline is to make later discussion more concrete.
Pilot with the people who use it
Test the revised workflow with a bounded group and permitted sample information. Include users with different responsibilities and access needs. Provide instructions, a route for questions and a way to continue critical work when the new process is unavailable. Capture feedback about the work itself, not only the appearance of the interface.
Expand when the operating model is ready
Review the results with the process owner. Confirm who manages accounts, maintains reference data, supports users and funds ongoing operation. Record what worked, what remains unresolved and what the next phase would require. Transformation becomes sustainable when responsibility for the new way of working is as clear as the technology.
An INJIVA planning perspective. Examples are illustrative, not client case studies.
