Reference:Glossary of terms/Design Principles
From STS Roundtable
| Important note: This page is part of the reference library of the STS Roundtable wiki. Items in the reference library are published, copyrighted works that are reproduced here by permission of the author. Edits to these pages will be removed unless those edits are explicitly to correct an error that may have occurred during the transcription of the original article to this wiki. |
This glossary of Socio-technical systems terms was published by, and is copyright of, Eli Berniker, May 1983
| Introduction | Systems and Organization | The Means | The Human System | Getting Something Done | The Analysis | Design | Design Concepts | Design Structure and Process | Design Principles |
|
Minimum Critical Specification
In organization design, minimum design is the best design. Only that which must be specified should be designed. Work must be doable so a technical system must be designed; however, jobs need not be defined. They are better left to the teams. In general, as much freedom as possible should be left to those who must make the organization work and adapt to change. Do not foreclose their options through over-design.
Incompleteness
Design is never complete until implemented and, given constant change, adaptation is a constant process of self-redesign. Thus, the actual design of the organization is always evolving. If the design team has done its work well, the organization will have gained the capability for useful and effective self-redesign. In an uncertain future, that is a very valuable organizational asset.
Reserved Decisions
All design decisions are reserved for the design team. Technical experts may only propose alternatives.
Valid Alternatives
Technical experts are required to propose at least two valid alternative designs so that differences between them may be utilized to surface assumptions and evaluate decision opportunities in terms of the philosophy statement.
