The Technical Design Diagnostic
The best way to understand what a good design solution requires is NOT to start designing.
The Technical Design Diagnostic came to my attention about 1990. Unfortunately I have lost track of its origins - perhaps Fred Stitt?
The concept of the Technical Design Diagnostic is that it is a first step in getting a handle on the project. If your goal is to find the best design that meets your client's program, including budget and schedule, which it should be, then the Technical Design Diagnostic is the most direct way to do that.
The Technical Design Diagnostic also takes less time than a design study that ignores the parameters that will inevitably bring you back to just a subset of what you once thought was possible. I have found that by using the Technical Design Diagnostic, the project design concept becomes very clear in just a day or so for most projects.
The Technical Design Diagnostic is intended to be followed one step after the other in roughly the order shown here. When you have thought all these issues through, then you are ready to start designing.
The purpose of the Technical Design Diagnostic process is to make solid decisions and set limits in the earliest pre-design stages. We haven’t found a better or faster way to reduce revisions and speed up the entire design process.
Comments are closed.
Your use of Architekwiki is implicit agreement with the
© 2012-2022 Architekwiki