To learn about organizational prototyping we have to peal it apart into smaller pieces. Starting at the definition of a ‘normal’ prototype. And after that the prototype in the context of organizational change.
A prototype is an early sample, model, or release of a product built to test a concept or process or to act as a thing to be replicated or learned from. It is a term used in a variety of contexts, including semantics, design, electronics, and software programming. A prototype is generally used to evaluate a new design to enhance precision by system analysts and users. Prototyping serves to provide specifications for a real, working system rather than a theoretical one. In some design workflow models, creating a prototype (a process sometimes called materialization) is the step between the formalization and the evaluation of an idea.
Normally a prototype is an early sample of a product. In the context of organizational change it is an early sample of an improvement within the organization. An idea, a hunch, or just an improvement. Without fully document and plan this change, first prototype it.
To help you out a little bit more. We defined a couple of ingredients, good prototypes consists of.
When you are in a process of optimizing (or completely reinventing) the way you work.…