PRINCIPLES
Best Practices for Sound Decsion Makin
1.1 Decision Framing and Disciplined Inquiry 1.1.1 Decisions — Information and Uncertainty 1.1.2 Disciplined Process — Analysis and Synthesis Stages 1.1.3 Problem Statement — Quantitative and Qualitative Information 1.1.4 Solution Opportunities — Existing Situation, Alternatives, Evaluation 1.1.5 Considerations — Guided Information Index 1.2 Stakeholder Collaboration and Decision Governance 1.2.1 Collaborative — Align Stakeholders Around Shared Objectives 1.2.2 Informed — Organize Service Provider Contributions 1.2.3 Planner as Orchestrator — Steward the Network 1.2.4 Facilitator Role — Conflict Resolution and Alignment 1.2.5 Caveat Emptor — Executive Override | 1.3 Trusted Information and Technology Governance 1.3.1 Integrated — Connect Information, People, and Activities 1.3.2 Evidence-Based — Establish a Trusted Information Foundation 1.3.3 AI Governance — Govern, Guide, Guard 1.4 Decision Readiness, Alternatives, and Risk 1.4.1 Decision-Driven — Organize Work Around Decisions 1.4.2 Alternatives-Driven — Evaluate Before Selecting 1.4.3 Anticipatory — Discover Before Committing 1.5 Lifecycle Stewardship, Adaptation, and Accountability 1.5.1 Adaptive — Respond to Changing Conditions 1.5.2 Lifecycle-Oriented — Align Short-Term with Long-Term 1.5.3 Business Case — Living Decision Instrument 1.5.4 Accountable — Govern and Preserve Decisions |
Introduction
This chapter describes the principles that govern how to conduct strategic predesign process successfully. Strategic predesign is an information-processing and decision-making discipline that is decision-driven, collaborative, informed by organized expert contributions, evidence-based, governed in its use of AI, integrated, anticipatory, alternatives-driven, lifecycle-oriented, adaptive, and accountable.
Owner decisions during strategic predesign have a wide range of consequences.
|
INVEST OR DO NOTHING? Is an investment required to achieve the strategy? |
BUILD OR RENOVATE? Which physical response best meets the need? |
LEASE OR OWN? Which real estate approach creates the best value? |
CONSOLIDATE OR RELOCATE? Should the portfolio be reorganized or moved? |
However, during strategic predesign, owners face recurring challenges: risks discovered too late, organizational misalignment, fragmented or unreliable data, static business cases, and executive decisions that are delayed or disconnected from the evidence and activities that produced them. By adopting the following principles, the owner can mitigate these challenges through a logical, disciplined approach – the strategic predesign process.
Principles are foundational rules for a logical, disciplined, and defensible strategic predesign process. The sets below address related considerations: decision framing and inquiry; stakeholder collaboration and decision governance; trusted information and technology governance; decision readiness, alternatives, and risk; and lifecycle stewardship, adaptation, and accountability. Together, they define the decisions to be made, align stakeholders and specialist contributors, establish a trusted information base, identify risks before commitment, evaluate alternatives and their lifecycle consequences, respond to changed conditions, and preserve responsibility for decisions and results. Applied consistently, they replace fragmented and reactive practices with a coordinated, transparent approach to real estate and capital investment. They also create a learning system in which decisions, outcomes, and changed conditions inform future action.
Strategic predesign is fundamentally a process for making decisions under uncertainty. Information and uncertainty are closely related: the greater the uncertainty surrounding a decision, the more information the strategic planner must discover, gather, evaluate, and interpret. Each well-supported choice narrows the range of viable alternatives and reduces uncertainty, although it may also reveal new questions or conditions that affect the outcome. Strategic predesign is therefore a disciplined process of inquiry. Strategic planners identify issues, frame questions, test assumptions, and resolve requests for information before incorporating recommendations into a business case.
Information processing for decision-making has two complementary stages: analysis and synthesis. Analysis separates a complex problem into understandable parts, defines the conditions that produced it, and identifies the choices the owner must make. Synthesis reconnects those parts by combining evidence, constraints, priorities, alternatives, and evaluation criteria into a coherent course of action. Analysis creates understanding; synthesis converts that understanding into a decision that can guide implementation.
Analysis requires both qualitative and quantitative information. Qualitative inquiry clarifies leadership vision, stakeholder goals and priorities, proposed strategies, and the reasoning behind them. Quantitative analysis establishes measurable facts and organizational conditions, forecasts demand, tests capacity, estimates costs, benefits, and risks, and defines performance requirements. Neither form of evidence is sufficient by itself. Together, they define a clear problem to solve and criteria against which the owner can evaluate potential solutions.
Synthesis begins by confirming the problem to solve and describing the existing situation. The planner then develops feasible alternatives, defines the criteria for evaluating them, and compares their consequences. The aim is not merely to identify a preferred option, but to show why that option is more responsive, feasible, and defensible than the others. The resulting business case summarizes the problem, the alternatives considered, their expected consequences, and the recommended course of action. The decision record documents the decision reached and any qualifications.
Considerations define the categories of information needed to understand a strategic predesign problem comprehensively and evaluate responses to it. The strategic planner will seek input from stakeholders, service providers and internal research. For the built environment, core considerations include function, form, economy, and time. Because capital and real estate decisions also affect the broader enterprise, the inquiry may extend to political, regulatory, organizational, technological, and cultural considerations. Using a consistent set of considerations provides an information index that the planner will use to prevent overlooking important consequences.
Engage owners, executives, end users, department leaders, internal service providers, and professional disciplines in defining problems, setting priorities, evaluating alternatives, and agreeing on success criteria. Collaboration is not simply consultation after a solution has been chosen; it is the structured inclusion of relevant knowledge while the problem and options are still being shaped. The planner should identify who is affected, who possesses essential information, who controls resources, who must implement the decision, and who has authority to approve it. Participants should understand their roles, the decisions open to influence, and the method for resolving disagreement. Collaboration does not mean that every participant has equal decision authority or that consensus is always required. It means that material concerns, operational realities, competing objectives, and consequences are made visible before commitment is made. A well-designed participatory process builds shared understanding, trust, commitment, and readiness for change, while a documented record of stakeholder input shows how that input influenced the outcome. As subject-matter experts, strategic planners orchestrate this process and maintain clear two-way communication among the stakeholders and the project sponsor.
The strategic planner engages internal and external service providers to collect and analyze information used throughout the process. Internal partners include human resources (HR), audiovisual and information technology (IT), security, facility operations, food service, and teams responsible for other employee amenities, such as fitness centers and lounges. External service providers contribute specialized expertise during each phase. Strategic planning may involve other planners, consultants, and workforce and workplace consultants. Real estate may involve brokers, analysts, demographic experts, planners, due diligence specialists, and market analysts. During project definition, specialists from the architecture, engineering, and construction (AEC) industry contribute expertise in project management, cost estimating, and scheduling. In-house project managers and procurement managers may join the strategic planner in preparing the project delivery strategy, with advice and counsel from developers, economic development representatives, and city planners. Programmers, IT consultants, site planners, building-type specialists, and workplace consultants are integrally involved in preparing the program of requirements and change-management plan. Organizing these contributors effectively depends on sound project organization and management techniques.
The strategic planner acts as an objective convener and systems integrator, stewarding a network of contributors toward shared outcomes rather than merely producing a plan. The planner clarifies roles and decision rights, establishes common methods, standards, interfaces, tools, and applications, and sustains the feedback loops that allow the network to learn and adapt. Value is created by linking scalable core capabilities with customized interfaces at the point of need. As planning becomes more modular, the planner shifts from directly performing isolated activities to building shared infrastructure, connecting diverse work processes, and coordinating contributors so the network operates as a coherent whole. The planner advances this principle through four complementary strategies:
In strategic predesign, the strategic planner acts as an impartial facilitator who transforms fragmented information, competing priorities, and implicit assumptions into a shared basis for decision-making. The planner establishes a single source of truth; makes assumptions, evaluation criteria, trade-offs, and business logic explicit and traceable; and clarifies governance, accountability, and decision rights. This foundation enables stakeholders to evaluate alternatives objectively, identify the specific causes of disagreement, and work toward an acceptable resolution. Sometimes when stakeholders are unable to agree, the planner may undertake a conflict resolution meeting. To do this, the planner begins by defining the issue, the purpose of the discussion, and the desired outcome. Stakeholders then generate possible solutions without judgment or criticism. After the options are understood, one stakeholder offers a proposal for consideration. If the proposal is not acceptable to all parties, those who disagree identify the changes required for acceptance and offer a counterproposal. The planner guides this iterative process until the group reaches an acceptable resolution or determines that agreement is not possible. The planner must test for genuine commitment and surface passive disagreement, including a potential “pocket veto,” before closing the discussion. If consensus cannot be achieved, the planner documents the alternatives, stakeholder positions, unresolved trade-offs, and rationale, then elevates the issue to the appropriate senior executive. Even when consensus is not possible, the process must produce a shared understanding of the issue, ensure that each position is heard, and make the final decision and its basis transparent. Applied at defined review and decision points, this process strengthens alignment, supports timely decisions, and reduces the risk that unresolved conflict will undermine subsequent planning or implementation.
Strategic predesign analysis is advisory: the planning team is responsible for producing a disciplined, evidence-based recommendation, while executives retain the authority to accept, modify, or override it. When executives choose a course that departs from the team’s recommendation, they assume ownership of the resulting risks, tradeoffs, and outcomes. The override should therefore be deliberate, transparent, and documented, including the decision rationale, the assumptions being accepted or rejected, the material risks identified by the planning team, and the measures by which the decision will be monitored and revisited. This principle applies whenever leadership overrides the planning team’s recommendation on headquarters or operations relocations, site or building acquisitions, lease agreements, major capital projects, technology or software integrations, strategic partnerships, or other consequential predesign decisions.
Preserve the analytical record: Document the planning team’s analysis, recommendation, assumptions, uncertainties, alternatives, and identified risks without altering them to conform to the executive decision. The record should distinguish professional advice from the course ultimately authorized.
State the basis for departure: Identify the strategic judgment, constraint, priority, or risk tolerance that justifies departing from the recommendation. Any new information or assumptions introduced by leadership should be explicit and, where practicable, tested before commitment.
Assign ownership and safeguards: Name the accountable executive, establish approval and escalation thresholds, define mitigation measures and decision checkpoints, and specify the indicators that will trigger reassessment. Authority to override does not transfer responsibility to the planning team; it requires leadership to govern the accepted exposure through the full decision cycle.
Connect organizational information, business functions, analytical methods, software, and AI within a common decision-support framework rather than allowing them to remain in isolated reports or applications. Integration has four dimensions. Information integration creates shared definitions, identifiers, assumptions, and sources. Process integration links strategic planning, real estate, finance, operations, technology, risk, procurement, and governance activities. Technical integration enables systems to exchange controlled and reliable information. Decision integration connects each recommendation and approval to the evidence, dependencies, and prior decisions that support it. The framework should establish an authoritative source for important information, ownership for maintaining it, rules for resolving inconsistencies, and appropriate access controls. Stakeholders should be able to exchange source material, analyses, assumptions, comments, and decisions without losing context or version history. Integration does not require one monolithic system; it requires interoperable components and a coherent information model. The framework should adapt to the needs of each predesign activity while preserving security, traceability, governance, and a reliable path from inquiry to recommendation and authorization.
The planner bases recommendations on information that is current, relevant, validated, and traceable to its source. An evidence-based process begins by defining the question to be answered and the standard of evidence appropriate to the decision. Planners should assess source authority, collection methods, completeness, consistency, age, and potential bias; reconcile conflicting data; and record important limitations. They should clearly distinguish verified facts from assumptions, estimates, interpretations, stakeholder preferences, and AI-generated outputs. Evidence should be proportionate to the importance and reversibility of the decision: a high-cost, high-risk, or long-lived commitment requires stronger validation, sensitivity testing, and more transparent reasoning than a limited and easily reversible action. Traceability is essential. A reviewer should be able to follow a recommendation from the evaluation criteria and analysis to the underlying source information. When definitive evidence is unavailable, the business case should state the uncertainty, explain the assumption used, and indicate how the assumption will be monitored or tested. A systematic review across all relevant considerations reduces reliance on fragmented, inconsistent, or untrustworthy data.
Establish a living AI governance model built around three functions:
Govern by setting an enterprise AI strategy, assigning accountable owners, classifying uses by risk, approving high-risk applications, monitoring performance, and overseeing compliance through an AI Governance Committee or equivalent authority. Governance should define who may authorize an AI use, who is accountable for its outputs, what records must be retained, and when a system must be suspended or retired.
Guide by issuing policies, standards, and operating procedures that define approved uses, prohibited uses, data protection, documentation requirements, procurement expectations, worker responsibilities, and the level of human review required. Guidance should be understandable to both technical and nontechnical users and should be reinforced through training.
Guard by applying technical and procedural controls that limit an AI agent’s authority, access, and autonomy. These controls may include restricted data access, testing before deployment, output verification, logging, monitoring for drift or bias, cybersecurity safeguards, escalation thresholds, and mandatory human intervention for consequential decisions. AI may assist with discovery, analysis, comparison, and drafting, but accountable people must retain authority for judgments and approvals. The model should be reviewed as technology, law, organizational risk, and experience evolve so that AI-assisted decisions remain lawful, secure, explainable, traceable, and subject to human accountability.
Organize the work around the decisions that must be made, not merely around the production of studies, meetings, or deliverables. Begin by identifying the sequence of decisions needed to move from an acknowledged problem to an authorized and implementable response. For each decision, define its purpose, scope, accountable authority, participants, required evidence, evaluation criteria, timing, dependencies, and possible outcomes. Activities and analyses should then be commissioned because they supply information required for a decision. A decision gate should confirm whether the initiative is ready to proceed, needs revision or further inquiry, should be deferred, or should stop. A decision-performance system should track readiness, unresolved issues, due dates, conditions of approval, and subsequent outcomes so that executives can act at the appropriate time. This approach prevents teams from producing information with no clear use, exposes decisions that are blocked, and reduces delay, ambiguity, duplication, and repeated work. It also ensures that analysis leads to action and that every major commitment has a clear owner and rationale.
Develop and objectively compare multiple feasible courses of action before selecting a preferred approach. The alternatives should include maintaining the status quo and, when appropriate, delaying action, changing policy or process, improving an existing asset, leasing or sharing resources, making a capital investment, or combining several strategies. Each option should be described at a comparable level of detail and evaluated against explicit criteria derived from the problem statement, stakeholder objectives, constraints, and success measures. The evaluation should examine organizational, functional, physical, financial, temporal, technological, environmental, operational, and risk implications over the relevant lifecycle. Scenario and sensitivity analysis should show how alternatives perform when demand, cost, timing, assumptions, or external conditions change. The process must avoid creating token alternatives solely to justify a predetermined preference. Instead, it should reveal genuine trade-offs, dependencies, future possibilities, and contingencies. Stakeholders should review both the criteria and the comparative results, and the planner should preserve the evidence, judgments, rejected options, and reasons for the final recommendation in the integrated decision-support system.
Identify risks, constraints, dependencies, and uncertainties before decisions become costly or difficult to reverse. Anticipation begins with a deliberate search for what is unknown, what could change, and what conditions must be true for an initiative to succeed. Strategic planners should test assumptions, examine external trends, identify regulatory and operational constraints, map dependencies, and consider second- and third-order effects rather than waiting for problems to surface. They should document each material risk, its likelihood and potential impact, the evidence supporting the assessment, the party responsible for monitoring it, and the proposed response. Early discovery creates time to avoid a risk, reduce its probability or impact, transfer it contractually or financially, prepare a contingency, or accept it knowingly. This principle also supports staged commitments: when uncertainty remains high, the owner can authorize additional investigation or a limited pilot instead of making an irreversible investment. Critical risks left unresolved during predesign are likely to reappear during design, procurement, construction, or operations, when corrective action is more disruptive and expensive.
Treat requirements, forecasts, assumptions, alternatives, schedules, and business cases as living information rather than fixed products. Reassess them at planned intervals, at formal decision gates, and when significant organizational, market, technological, regulatory, financial, or project conditions change. The planner should define the indicators to monitor, acceptable ranges of variation, responsibility for review, and thresholds that trigger renewed analysis or escalation. Adaptation should be controlled rather than improvised: material changes should lead to updated evidence, reassessment of alternatives, impact analysis, documented decisions, and revisions to related plans, budgets, schedules, risks, and performance measures. The record should distinguish routine refinement from a change significant enough to reconsider the project’s justification. Adaptability does not mean continually shifting objectives; it means retaining strategic intent while changing the means when evidence indicates that the original approach is no longer suitable. An ongoing business-case system prevents one-time approvals from becoming detached from current conditions.
Evaluate immediate organizational requirements alongside the long-term operational, financial, environmental, technological, and physical consequences of real estate and capital investments. Decisions made during predesign can create commitments that persist for decades, including staffing and maintenance obligations, energy and utility costs, technology dependencies, space constraints, financing exposure, resilience requirements, and future renewal or disposal costs. Lifecycle analysis should therefore consider acquisition or construction, activation, operation, maintenance, adaptation, renewal, and eventual disposition—not just initial cost. The planner should test whether a near-term solution preserves useful future options or creates avoidable lock-in. Develop a master schedule that links properties, initiatives, decision events, funding cycles, dependencies, useful lives, and anticipated consequences. Integrate the schedule into the decision-support system and review it regularly so that timing conflicts, upcoming reinvestment needs, and opportunities for coordination become visible. This principle keeps urgent demands from displacing long-term value and aligns near-term actions with enterprise strategy, affordability, resilience, and stewardship objectives.
Strategic predesign therefore combines an organized method of inquiry, a structured search for alternatives, and a disciplined decision-making process. Its principal output is a business case: a formal decision-support document used by executives to assess and authorize a proposed project, investment, or strategic initiative. A business case explains the need for action and evaluates the value, risks, costs, benefits, and implementation implications of available choices. It should enable executives and stakeholders to determine whether the enterprise can justify an initiative as feasible, timely, and aligned with enterprise objectives. At a minimum, it addresses these critical questions:
A business case helps prevent premature commitments based on incomplete or outdated information. It should function as a living decision instrument: the planner continues to test assumptions against new evidence, revises forecasts and estimates as conditions change, and revalidates the case at major decision gates before substantial capital or resources are committed. When circumstances materially change, the business case should make clear whether the initiative should proceed, be modified, be deferred, or stop.
Establish clear decision rights, approval requirements, and accountability for both the quality of recommendations and the consequences of authorized actions. Accountability begins with named roles: who prepares the analysis, who validates information, who recommends action, who approves it, who implements it, and who monitors results. These responsibilities should be separated or independently reviewed when conflicts of interest or the scale of risk make additional assurance necessary. Preserve the evidence, assumptions, alternatives, evaluation criteria, rationale, approvals, dissenting views, conditions, and commitments underlying each major decision. This record should be sufficient for a later reviewer to understand what was known at the time, why the decision was considered reasonable, and what results were expected. Continue scanning the organizational environment for events that could materially affect the enterprise, strategic plan, or implementation plan. After authorization, compare actual costs, benefits, risks, timing, and performance with the approved case; assign corrective actions when results depart from expectations; and record lessons for future decisions. Periodically review whether earlier decisions remain sound and why adaptations were made in response to unforeseen events or newly discovered information. Accountability is therefore both prospective and retrospective: it establishes responsibility before action and evaluates performance after action.
Prepared by Steven Parsahall, with the use of AI agents. © Copyright of the Strategic Predesign Association
Feedback on this section
Click on POST to share your thoughts, ideas, comments, and constructive critiques about this section. Tell us what is unclear, what could be improved, and what additional topics we should address.
Go to Explore the Practice |