AI for Humans: Building Your First Pilot Project
A step-by-step guide to planning, delivering and evaluating a successful AI pilot that builds confidence and momentum.
If you have been following this series and already assessed your readiness, improved your data foundations and identified a few low-risk entry points, you are now in a good place to launch your first AI pilot.
This controlled experiment will allow you to demonstrate value, build organisational capability, and learn valuable lessons before wider implementation.
In this fourth instalment of our series, we provide a step-by-step guide to planning, delivering and evaluating a successful AI pilot that builds confidence and momentum.
Scoping Your AI Pilot
The most effective AI pilots are carefully scoped to balance meaningful impact with manageable delivery. Your pilot should be:
1. Focused on a Specific Business Challenge
Ideally one that improves both business outcomes and people’s experience of the work.
- Target a single, well-defined issue rather than multiple problems
- Choose a challenge with clear metrics that can show measurable improvement
- Select an area where even modest gains would be valuable
Examples of suitable first pilots:
While operational use cases are often the easiest place to begin, not all AI pilots need to focus on automation or prediction. You might also pilot AI to support content creation, trend analysis or completely new ideas. The same principles apply, even if the outcomes are more exploratory or insight-driven.
2. Achievable Within 2 to 3 Months
- Long enough to show meaningful outcomes
- Short enough to maintain momentum and stakeholder interest
- Structured to deliver incremental value during delivery
3. Contained Within Clear Boundaries
So your team can experiment safely and confidently.
- Limited to a specific team, process or customer group
- Minimal dependencies on wider systems or teams
- Clear entry and exit points for evaluation
4. Aligned with Future Opportunities
- Similar to applications, you might scale later
- Uses data and processes relevant to broader goals
- Tests capabilities that could be expanded
It would be challenging to tick every box perfectly, but aiming for this balance will help your pilot succeed without stretching your team too thin.
Sustainability check: Choose a Problem That Matters. When selecting your AI pilot, prioritise challenges that have a real-world sustainability angle. That might mean reducing paper-based workflows, cutting waste from overproduction, or freeing up employee time for higher-value tasks. A well-chosen pilot can deliver digital gains while contributing to environmental or social goals from the start.
The Minimum Viable Team
You do not need a large team to get started, but you do need shared ownership and the opportunity for your people to develop new skills. At a minimum, we recommend four core roles.
1. Business Champion
This person defines the business challenge, secures resources and stakeholder support, and makes key decisions throughout the pilot. Often a process owner or department head, they connect the pilot to real-world business outcomes.
2. Technical Implementer
Responsible for managing the technical delivery, coordinating with internal IT or external vendors, and ensuring everything integrates smoothly. Likely candidates include an IT team member, a business analyst or a vendor consultant.
3. Data Specialist
Focused on data quality, availability and interpretation, this role supports analysis and helps identify any issues with the inputs or outputs. This is often covered by an analyst, database administrator, or data-savvy team member.
4. End User Representative
Brings day-to-day process knowledge, tests the solution in real scenarios, and provides feedback on usability. Often best filled by frontline staff who work directly with the process being improved.
Not every organisation will have all four roles available in-house. If you are working with limited resources, consider assigning part-time responsibilities, involving a vendor or external partner temporarily to reduce technical overhead. The key is to maintain clear ownership and keep the feedback loop active throughout the pilot.
Sustainability check: Don’t Forget the Human Impact. Digital sustainability includes people. Involving the right people in the pilot process early not only improves your results, it helps reduce resistance, builds internal capability and supports long-term adoption. A thoughtful pilot can improve digital confidence and wellbeing, especially when it reduces friction or repetitive work for teams.
Timeline and Milestones
A clear, structured timeline helps maintain progress and build trust. Below is a typical 10-week pilot framework.
Weeks 1 to 2: Planning and Preparation
- Finalise pilot objectives and success measures
- Establish baseline performance metrics
- Prepare data and technical environments
- Onboard the team and transfer knowledge
Deliverable: Signed pilot charter with success criteria
Weeks 3 to 4: Initial Implementation
- Configure initial setup and integrations
- Train users on new tools or processes
- Begin testing with limited data or users
- Set up feedback mechanisms
Deliverable: Functional prototype with core capability
This stage provides an opportunity to build confidence and curiosity in your team. Make space to share early wins, ask questions, and involve people in shaping how the tool fits their real-world workflow.
Weeks 5 to 8: Operational Testing
- Roll out the full pilot scope
- Monitor results and collect user input
- Refine based on early learnings
- Record key challenges and adjustments
Deliverable: Pilot live and generating performance data
Weeks 9 to 10: Evaluation and Recommendations
- Compare outcomes against baseline and objectives
- Capture lessons learned and areas to improve
- Develop next-step recommendations
- Share findings with stakeholders
Deliverable: Full evaluation report
Tip: Allow a 10 to 15% buffer for the unexpected. It always comes up.
A successful pilot needs a clear path to what comes next. If you do not plan for how to transition into full implementation, the pilot may stall or lose momentum. Link your findings to broader strategic goals, prepare a simple cost-benefit case, and map out the resource needs to scale. Even a one-page plan will help make your next move actionable.
Sustainability check: Build Once, Scale Thoughtfully
Pilots are a chance to test what works without waste. Use this phase to validate ideas, avoid overengineering, and document approaches that can be reused. Reusable components, smarter data processes, and cross-team learning all reduce duplication and help you scale with efficiency and care, hallmarks of sustainable digital delivery.
Measuring Success
Primary metrics matter, but they rarely tell the whole story, especially in a pilot. To understand whether your project is working and worth scaling, it helps to look at a broader set of outcomes across these four areas:
1. Business Impact
- Efficiency, accuracy, or cost improvements
- Financial benefit (savings, revenue, resource reallocation)
- Time or capacity gains
Example metrics:
2. Process Improvement
- More consistent workflows
- Fewer exceptions or escalations
- Stronger compliance or quality
3. Organisational Learning
- Increased confidence in future AI use
- More internal capability
- New ideas discovered
4. User Experience
- High adoption and satisfaction
- Positive feedback from users or customers
- Unanticipated improvements
Is a Pilot the Right Approach?
In some cases, what looks like a pilot is really an early version of a new product, service or system. Ask whether you are genuinely testing assumptions or simply rolling something out in stages. If it is the latter, be clear about this upfront. Calling something a pilot can reduce scrutiny, but it may also limit investment, commitment or user support. Be honest about your intent and structure the work accordingly.
Pitfalls to Avoid
Even small, well-planned AI pilots can hit common roadblocks. These challenges often stem from good intentions, like trying to show too much value too soon, but can slow progress or undermine confidence. Knowing what to watch for helps you stay focused, adapt early and keep your pilot on track.
Trying to Solve Everything
What: Expanding the scope to cover multiple problems or features Why: Pressure to deliver broad impact from the start Avoid: Focus on one core challenge and defer the rest for future phases
Waiting for Perfect Data
What: Holding off on the pilot until data is fully clean and complete Why: Belief that AI won’t work without perfect inputs Avoid: Start with what you have and improve data quality as you go
Setting and Forgetting
What: Launching the pilot without a plan for follow-up Why: Treating AI implementation like a one-off software rollout Avoid: Build in regular checks and reviews to monitor performance
Keeping Quiet
What: Not sharing updates, progress or setbacks during the pilot Why: Concern about things going wrong or uncertainty in outcomes Avoid: Communicate openly and regularly, including what’s still in progress
Managing Common Risks
Even with a focused scope and solid plan, small issues can surface during delivery. By identifying common risks early and setting up simple fallback options, you can keep the pilot moving forward and avoid unnecessary delays. A simple risk plan goes a long way. Address these issues before they become blockers:
A well-structured pilot is one of the most practical ways to build confidence with AI. Keep the scope tight, involve the right people and focus on learning as much as delivering.
If you would like support planning and delivering your first AI pilot. Our Digital Product and AI service.