Bring the work as it really happens
A polished procedure document is less useful than one recent example. Bring the spreadsheet, email chain, form, checklist or screenshot the team actually uses.
Include the awkward cases
The normal path explains what can be streamlined; exceptions explain where judgement and safeguards are needed. Two or three examples of work going wrong are often the most useful material in the conversation.
- Who starts and finishes the process
- Systems, files and inboxes involved
- Typical weekly or monthly volume
- Waiting, rework and common mistakes
- What a genuinely better result would look like
Leave product choices until later
You do not need to decide whether the answer is AI, integration or a new application. A good assessment starts with cost, risk and outcome, then chooses the smallest technical change that can improve them.