Treat prototypes as learning, not proof of success
Rapid prototyping makes strategic ideas something a team can test and improve, rather than leave as possibilities discussed in a meeting. The practice starts with room to imagine freely and build on colleagues' ideas without immediately defaulting to feasibility concerns. Imagination then needs action: quickly testing assumptions, learning from what does not work and revising the idea towards what does. An unsuccessful attempt can therefore be useful when it informs the next iteration. The purpose is not failure for its own sake, or experimentation without judgment. It is to discover possibilities through action and learning. Treat a prototype as a way to develop an idea, not as proof that a whole business direction is viable.