Build to Test

There's a stage we have in running an Innovation Engagement that's called Prototyping or Engineering. This is the culmination of our work to that point where we give our team the opportunity to take everything they've collected, learned, and observed to that point and put that into a workable model.

The simple road out is to just build a plan, cast a vision, give a powerpoint presentation, or something that covers the concept but doesn't necessarily lay out a good model and example of exactly what you're thinking. It's the difference in an architect showing someone blueprints and then creating a fly through of the building. Some people can construct the idea in their head from a blueprint, but most of us need more visualization.

This is where our principle comes into play. Why do we prototype? We prototype (or build) to test. The better we build a model the more critically and accurately we can assess it's viability and determine how it resonates with our teams and clients.

My encouragement for everyone here is that no matter what you're working on (program design, product development, etc.) there is always an opportunity to prototype well and allow your audiences to evaluate accurately on a good idea of your proposal. Yes, it's simple... but it makes a big difference. Just remember that the more you can show the better your opportunities for success in the long run will be.