Define the pilot
Map the workflow with users. Agree requirements, acceptance criteria, boundaries, the owner and the baseline before introducing a new way of working.
AI ADOPTION SPRINT
An AI adoption sprint for one useful workflow.
For teams with a use case ready to test. Define what good looks like, run a supported pilot and decide whether to refine, expand or stop.
Discuss your pilotWork directly with Austin · Scope and fee agreed first
REQUIREMENTS. TESTING. ADOPTION.One agreed workflowA defined pilot groupDuration and fee agreed after scoping
WHAT WORKING TOGETHER LOOKS LIKE
From a defined need to a tested workflow.
Test with people
Coordinate user testing, task-based coaching and structured feedback. Work with your tool owner or technical team to resolve issues and refine the workflow.
Make the next decision
Review the adoption scorecard and feedback. Leave with a prioritised backlog and a recommendation to refine, expand or stop, plus support and handover responsibilities.
Before we start
Do we need to complete the diagnostic first?
No. If the use case, access and ownership are already clear, we can start with a sprint. If those are uncertain, a diagnostic may be a better first step.
What is included in the scope?
One agreed workflow and pilot group, requirements and testing support, coaching, a feedback log and a close-out review. The proposal defines sessions, deliverables, duration and responsibilities.
Does this include building an AI product?
Simple configuration or prototyping can be agreed where appropriate. Custom software engineering, integrations, licences, security approval and production support are not included by default. Technical responsibilities are agreed before kickoff.
YOUR NEXT STEP
Discuss your pilot
Share the challenge, the team involved and what you want to change. I’ll help clarify the right scope and next step.
Send an enquiry →Compare the ways to work together →