Choose a journey you can observe
Use a process with a clear start and finish, such as an enquiry becoming a reviewed response. Avoid a first pilot that depends on several departments agreeing on new policies. Pick an owner who can inspect the result and explain what a successful outcome looks like.
Record the current baseline
Count the steps, the typical handling time and the common corrections. These observations do not need to be sophisticated. They need to describe the actual process. Keep exceptional cases visible rather than removing them from the comparison.
Run with sample data first
Test the public input, internal record, AI assistance and review screen as one journey. Confirm who can see and change each field. Check that the process still makes sense when the AI step is unavailable. The business should retain a practical way to continue working.
Expand only after a useful result
Compare the pilot with the baseline and include the new maintenance work. If the result is helpful, add the next connected process. A broad platform can support gradual expansion; it does not require a large migration on day one.
Practical guidance for this comparison. The examples describe work to configure and validate, not a tested product deployment. Editorial method and product sources.