Define the outcome and baseline.
Identify a repeated workflow and the people responsible for it. Record current task volume, handling time, error patterns and what happens after the handoff. Define the outcome the pilot should improve.
A useful initial scope is narrow enough to test and meaningful enough to matter. Avoid evaluating an undefined “AI transformation” without a process owner or acceptance criteria.
- Which task and audience are in scope?
- What baseline can be measured?
- Which decisions must remain with people?
- What evidence would justify expansion?
Inspect the actual information and integrations.
Ask which approved sources the assistant uses and how they are maintained. Review account permissions, model/provider dependencies and where the information travels.
Request a live explanation of record matching, persistence acknowledgement, duplicate events and integration failures. A provider logo list is not an integration acceptance test.
- Document the source of truth for each record.
- Verify authentication and credential scopes.
- Test missing and conflicting information.
- Assign a content owner and an operator for failures.
Make pilot acceptance explicit.
Build a representative test set containing normal, ambiguous, unauthorized and failure scenarios. Review wrong answers and missed escalations alongside successful tasks.
Agree who signs off and which conditions stop the rollout. A successful narrow pilot should lead to a deliberate scope decision, not automatic permission for unrelated actions.
Review total cost and operational ownership.
Separate discovery and implementation from recurring operation and provider usage. Confirm included channels, volumes, maintenance, support and change handling.
Record deployment, monitoring, incident contact and recovery responsibilities. Require the relevant privacy, security and commercial documents for the actual proposed configuration.
- Named delivery and business owners.
- Written inclusions, exclusions and dependencies.
- Measured acceptance criteria and a release plan.
- An agreed review cycle after launch.
General workflow guidance. Product availability, provider requirements and implementation scope are confirmed for each project.
