Understand Needs – Organizational documentation is reviewed and stakeholders are engaged to develop a consensual understanding of user needs, system requirements, daily workflow and supportive features. Extensive programming efforts may be necessary to prepare for organizational “culture change” efforts being undertaken in conjunction with architectural development.
 

Define Objectives – The entire scope of the project–including the envisioned building spaces and features–are defined and described. Discrete design strategies are identified based upon their associated likelihood of either advancing desirable outcomes or mitigating undesirable outcomes; this process is commonly referred to as “evidence-based design.”
 

Prioritize Goals – User needs and organizational objectives serve as the primary means for prioritizing associated design strategies. Costs associated with the successful advancement of goals and avoidance of undesirable outcomes may also be estimated to further prioritize the selection and implementation of specific products or features.
 

Secure Resources – Credible, objective and reliable information and/or outlets for products are secured along with evaluation metrics and/or measures. Information, costs and requirements associated with the installation, training or ongoing operation informs the selection and procurement of design-specific strategies or features.