In order to minimize any challenge to your assumptions for this event, I'd like to offer a few of my expectations for your consideration, discussion, and ultimately our mutual agreement. First of all, I derived from the sponsor session a real likelihood for certain exercises which we should be prepared to implement. There are many ways to look at the work that goes on in a DesignShop process. The nomenclature associated with the following list of leads has been developed in the MG Taylor network over many years. It tends to divide the work into functional tasks, such as documenting reports and conversations via keyboard on a computer, handling graphics, or producing the final product.
Some nomenclature seems necessary to help people understand the process and their place in it.
I'm not advocating the elimination of nomenclature. But language defines and builds structure. Structure frees and constrains. While it seems logical and natural to organize our KreWs around different tasks to be done, there may be other ways of approaching the problem. As the technology in Management Centers becomes ever more sophisticated, we risk fragmenting into hierarchies of specialties.