A pilot is an extended trial period of your solution before committing to going to market. Unlike prototyping, you should feel confident in your solution and be testing how it works with the staff, support, materials, resources, and partners in place.
Start by creating learning objectives. At a high level, what are you looking to achieve through your pilot and what do you hope to learn?
To help clarify these goals, draw a map of all touchpoints your pilot will look to affect – people, places, and things. It might be helpful to reference your User-Centred Research findings to think about all your different users within the system and what their experience might be with the pilot.
Now, ask how can you isolate what you want to learn for each part of the processes you just sketched out, from creation, to point of sale, to continued use, and beyond.
Create a plan for how you intend to facilitate the pilot and get input for these learnings as your pilot launches.
Remember, you will probably have many iterations as you learn. If your desired outcome is not achieved, how can you iterate on the part of the system that can be improved, rather than rethink the entire solution?
A collaboration between architect Thomas Rau and Philips resulted in a successful bespoke light as a service model. Philips, who maintain control of the lighting, are now refining the business model for wider use.Read more >>