Piloting is a way to test a nearly-final version of your solution in a real-world setting with real users.
It’s not a simulation—it’s a small-scale launch designed to learn how your design performs outside the lab or workshop. Pilots help you see how people actually use, experience, and adapt to a service, product, or process. You learn what works well, what breaks down, and what still needs adjustment—before investing in a full rollout.
Best Practices
Narrow the scope. Keep the scope small but realistic—aim to reflect real use conditions.
Define success. This will help you know if your pilot is successful or not towards the end.
Set up feedback loops. This allows users to share what’s working and what’s not.
Involve frontline staff. They’re key to understanding adoption and impact.
Plan for iteration. Piloting is a learning phase, not a final test.
Basic Steps
1. Define the goal. What do you want to learn or validate through the pilot?
2. Set parameters. Decide who, where, how long, and what part of the solution will be tested.
3. Prepare support. Ensure users have what they need to participate successfully.
4. Run the pilot. Launch the experience with close observation and open feedback channels.
5. Collect data. Gather qualitative and quantitative insights.
6. Reflect and refine. Adjust the solution based on what you learn before scaling up.
Benefits
- Tests feasibility, usability, and adoption in real-world conditions
- Builds confidence among stakeholders before full implementation
- Surfaces unexpected challenges and opportunities
- Helps smooth the path for wider rollout
Our Recommended Resources
Piloting bridges the gap between design and delivery. It gives you a chance to learn what it’s really like for people to use your solution in their everyday lives. With thoughtful observation and iteration, a pilot helps you build something that works in theory—and in practice.