10 Implementation
Improving Practices and Enabling a Decision-Support System
Introduction 1.0 Implementing Strategic Predesign Improvements 1.1 Connect Strategy, Capability, and Decision Support 2.0 Improve the Organization 2.1 Align the Organizational Design Dimensions 2.2 Make Change Management Part of the Work 3.0 Competitive Advantage or Public Value 4.0 Build an Integrated Decision-Support System 4.1 Use AI: Interpretation and Draft Assistance 4.2 Software: Integration, Automation, and Validated Analysis 4.3 Data: Authoritative Records and Controlled Evidence 4.4 People: Judgment, Accountability, and Authorization 4.5 Apply Govern, Guide, Guard 5.0 Principles for Implementation 5.1 Start with the Decision 5.2 Integrate the Process, Systems, and Data 5.3 Establish Trusted, Traceable Evidence 5.4 Govern Internal and External Information Differently 5.5 Use Agentic Capabilities Selectively and Within Boundaries 5.6 Preserve Human Authority and Accountability 5.7 Compare Alternatives and Reveal Uncertainty 5.8 Preserve Information Continuity Across the Lifecycle 5.9 Capture Reasoning and Learn from Outcomes 5.10 Redesign the Work Process with Its Practitioners 5.11 Pilot Narrowly and Measure Decision Value 5.12 Requirements to Define and Validate through Implementation | 6.0 Apply Improvements through the Predesign Phases 6.1 Strategic Planning: Establish Direction and Compare Portfolio Responses 6.2 Real Estate: Test Fit and Control Commitments 6.3 Project Definition: Reconcile Requirements and Establish Readiness 7.0 Implementation Roadmap 7.1 Define the Decisions and Governance 7.2 Establish the Trusted Information Foundation 7.3 Design a Bounded Pilot 7.4 Configure, Test, and Train 7.5 Evaluate Decision Value 7.6 Expand and Connect Lifecycle Learning 7.7 Pilot Scorecard and Acceptance Rules 7.8 Roadmap RACI Matrix 8.0 Implementation Outcome |
Implementation turns strategic predesign into a repeatable organizational capability. It is a coordinated way to translate enterprise strategy into justified decisions and approved requirements before design begins or capital is committed. This chapter explains how to improve organizational arrangements, work processes, information, and technology together. The aim is better leadership decisions that achieve competitive advantage or public value.
Implementation defines the capability needed, redesign the work with its practitioners, configure the supporting information and tools, test the results, and retain approved improvements. Foundations provides the lifecycle and systems framework. Organization explains authority, participation, organizational design, and change management. Process defines the three predesign phases—Strategic Planning, Real Estate, and Project Definition—and the decisions and evidence developed within them. Procedures supply adaptable protocols and review questions. Techniques provide repeatable methods, tools, templates, and reviewable outputs., while Decision-Support System organizes evidence preparation, analysis, governance, and controlled records into four logical tiers. These chapters to define the work; use Implementation to assign ownership, configure the workflow, verify performance, and adopt tested improvements.
Implement a strategic predesign decision-support system as a redesigned operating model. Fragmented information, mismatched planning horizons, conflicting priorities, unclear ownership, and static business cases are problems of coordinated work as well as technology. Address their causes through a defined workflow, governed evidence, integrated software, proportionate AI assistance, and identifiable leadership judgment and accountability.
Missing evidence creates uncertainty. Requiring the collect and validate the information needed for the decision.
Different interpretations create equivocality. Necessitating facilitated work sessions, concrete options, and feedback to establish operational meaning.
Competing priorities require explicit criteria and an authorized decision; more data alone cannot decide which priority should prevail.
Assess whether information demand exceeds the organization’s capacity to review and coordinate it.
Reduce unnecessary transfers and duplicate work, provide approved capacity or schedule allowances where justified, and strengthen information systems and lateral coordination where needed. Record the diagnosis, chosen response, responsible parties, and remain uncertainty before configuring automation.
Evaluate the organizational capability the strategy requires. Examples include comparing portfolio options consistently, adapting capacity as demand changes, or translating business-unit needs into design-ready requirements. For each capability, identify the decisions it supports, the current performance gap, the changes needed, the accountable owner, and the evidence that will demonstrate improvement.
Apply the organization-design framework. Strategy establishes direction; required capabilities connect that direction to choices about structure, processes, people, and rewards. A new tool cannot resolve conflicting authority, inadequate staffing, or incentives that favor isolated departmental outcomes.
Start engagement during Strategic Planning and continue through Real Estate and Project Definition. Use vision sessions, user interviews, cross-functional workshops, and repeated option reviews to establish shared meaning and test apparent agreement.
Explain terms such as flexibility, collaboration, and efficiency in the context of actual work. Record dissent, operational constraints, and unresolved questions; silence is not evidence of support.
Prepare a communication plan that identifies each audience, the reason for change, the proposed future state, effects on roles, the responsible sender, timing, channels, and feedback routes. Distinguish proposals from authorized decisions.
Assign responsibility for answering concerns and reporting how feedback affected the outcome. Coordinate these activities with project milestones, funding, staffing, and technology readiness rather than adding them after the plan is approved.
Maintain a controlled playbook containing the workflow, role assignments, review questions, templates, evidence rules, escalation routes, and lessons from tested changes. Use it for onboarding and future projects.
Project-specific approved requirements belong in the Program of Requirements (POR) and supporting records; related commissioning expectations may be recorded in an Owner’s Project Requirements (OPR) document.
Competitive advantage is the strategic purpose, not an automatic consequence of installing software or producing analysis faster. The Process chapter connects facilities choices to the organization’s competitive context; Organization connects strategy to the capabilities needed to execute it.
Use those connections to explain why the proposed improvement matters, how it changes the organization’s work, and which outcomes would demonstrate value. For mission-driven and public-sector organizations, apply the same discipline to service effectiveness, continuity, transparency, and responsible use of resources.
Record a traceable value chain for each proposed improvement: strategic need → required capability → organizational and technology changes → better decision or approved requirement → intended outcome → review evidence. Assign an owner for monitoring the intended benefit. Separate expected benefits from demonstrated results and examine implementation cost, dependencies, and trade-offs in the business case.
Assess these responses as alternatives. An apparent saving may shift costs to fit-out, relocation, disruption, maintenance, or end-of-term obligations.
A faster recommendation may require more verification or omit a critical requirement. Compare the whole commitment and retain flexibility where uncertainty justifies staged action.
Configure the four logical tiers described in Decision-Support System.
Components describe what the system uses; tiers describe responsibilities and information handoffs. Neither is a set of additional predesign phases.
Integration and automation operate across the tiers, and human verification applies at every consequential handoff. Assign an owner and acceptance criteria for each interface rather than requiring four separate applications or one centralized database.
Use the four pillars in Foundations to select the simplest combination that supports the redesigned workflow. Prepare a system brief stating the decision and users served, approved sources, record owners, information exchanges, tools, permissions, validation methods, review points, support responsibilities, and limits.
Distinguish the technology that supports predesign analysis from the IT, AV, network, and building-system requirements of the proposed facility; coordinate both, but do not confuse their scopes or approvals.
Use AI where interpreting supplied material helps a defined task: finding relevant evidence, drafting themes from interviews, identifying candidate requirements or conflicts, and preparing option narratives. Define the permitted sources, expected contribution, reviewer, and acceptance checks before use.
Retrieval-augmented generation (RAG) retrieves reference material to support an AI response, but does not guarantee complete retrieval, accurate interpretation, or valid citations. Preserve retrieved source references, versions, and qualifications; check material claims against the underlying records and report missing or conflicting evidence.
A practitioner checks the interpretation and confirms requirements before they enter an approved baseline. Add multi-step agents only when the task requires them and simpler assistance is insufficient; begin with read-only access, draft outputs, explicit stop conditions, and human review.
Use software to connect compatible records and interfaces, execute approved routine actions, manage review status, and perform spatial, financial, or environmental analysis. Build each reusable decision model from separately identified observed data, reference benchmarks, adjustable assumptions, calculation rules, and evaluation criteria.
Version these layers and retain the inputs, method, and results for each material scenario. Run defined calculations in the analytical service rather than relying on a language model to generate numerical answers; AI may propose questions or explain checked outputs.
Validate definitions, mappings, calculation methods, units, assumptions, and exceptions, and document uncertainty for statistical forecasts or optimization methods. Use rule-based automation for predictable tasks such as missing information flags and review reminders.
Use spatial tools or dashboards only where the decision needs them. Repeatability, integration, or an attractive display does not establish correctness: reviewers must check both the inputs and the method.
Begin by assigning the governing record and source owner for each decision use, not by choosing a new storage platform. Identify which enterprise and lifecycle systems hold the authoritative records for strategy, workforce assumptions, leases, costs, utilization, property constraints, and prior outcomes.
Agree consistent identifiers and definitions from portfolio to asset level. Distinguish workforce headcount, attendance, occupancy, utilization, and required capacity; align their periods, locations, populations, and assumptions before comparison.
Keep source records separate from analytical outputs, and record owner, date, version, permissions, and validation status. An existing enterprise data lake may provide curated evidence but is optional and does not make its content authoritative.
A common data environment controls information status, review, sharing, and versions; it is not synonymous with a data lake or necessarily one application. Use only necessary authorized personnel information.
Check external evidence for authority, currency, jurisdiction, suitability, and reuse terms; public availability does not establish accuracy or permission to reuse.
Assign people to frame the problem, establish priorities, interpret uncertainty, validate evidence and calculations, reconcile stakeholder differences, recommend alternatives, and make authorized decisions. Preserve the recommendation separately from the decision record.
Where leadership departs from the recommendation, retain the original analysis and document the accountable authority, reasons, accepted risks, safeguards, monitoring indicators, and reassessment conditions.
Choose methods that fit the assignment’s scale, complexity, uncertainty, and proposed commitment rather than deploying the entire catalogue.
Use conventional methods as the baseline and add AI assistance where its contribution provides a substantive benefit.
Define the decisions before choosing tools. Identify the organizational goal, the alternatives, the limits, and the person authorized to decide. Agree which measures matter, such as space efficiency, adjacency, lifecycle cost, carbon impact, and occupant flow.
Strategic predesign encompasses Strategic Planning, Real Estate, and Project Definition, upstream of design and construction. Late recognition of space needs can allow market availability to drive decisions instead of business requirements. The system should help determine whether—and how—an initiative should proceed, rather than assume that a new building or a real estate transaction is the answer.
Implementation implication: For each decision, record its owner, evidence, criteria, alternatives, and output. Assess uncertainty early: use automated extraction for clear, documented requirements and workshops where needs or priorities are unclear.
Treat AI as one component of an operating model. A conversational interface alone does not establish a reliable decision-support system.
Growth projections, lease obligations, occupancy indicators from sensors and badge records, and financial metrics can remain in disconnected systems. Manual reconciliation can leave baseline assessments incomplete. An integrated model connects these sources to the decision workflow: data supplies evidence, software applies validated rules and calculations, automation executes defined tasks, AI supports retrieval and synthesis, and people interpret results and authorize decisions.
Implementation implication: Map the existing predesign workflow, information exchanges, and software interfaces first. Define which tasks require AI interpretation, rule-based automation, or validated calculation engines. Integrate data into existing transactional and operational activities, including broker correspondence, tour feedback, and proposal-term summaries, to build portfolio intelligence without unnecessary administrative work.
Ground analysis is approved, authoritative information, and make the basis of each consequential conclusion inspectable.
Use shared definitions and identifiers for buildings, spaces, leases, costs, and authorized personnel data. Organize historical project benchmarks, space ratios, costs, post-occupancy findings, site information, and applicable regulatory requirements. Record stakeholder needs, culture, and mission requirements in searchable categories. Connected, governed sources can serve this purpose; one central database is not required. Source links and consistent definitions help reviewers check evidence but do not guarantee accuracy.
Implementation implication: Record source, date, version, ownership, and verification status. Distinguish documented facts, assumptions, calculated results, and AI-generated interpretations. If evidence is missing or contradictory, the system should identify the gap rather than manufacture certainty.
Combine protected enterprise knowledge with selected public information, but do not treat either category as automatically reliable.
Unmanaged use of AI outside approved organizational controls, often called “shadow AI,” can expose private information and intellectual property and weaken the audit trail. Combine a governed enterprise information environment with selected external sources for market, demographic, regulatory, and benchmark evidence. Protected internal records and public information require different access and verification controls; neither is automatically reliable.
Implementation implication: Establish access permissions and rules for admitting external evidence. Confidential information should remain protected, while public information should be evaluated for authority, relevance, and currency.
Apply multi-step AI workflows where they improve a defined process—not simply because autonomy is available.
Use AI to find information, extract draft requirements from interviews and briefs, and compare evidence. People must check the extracted requirements before they become approved inputs. Use rule-based automation for routine tasks and validated software for spatial, financial, and environmental calculations. Where needed, use parametric test-fitting tools or portfolio models to compare massing, adjacency, and layout options. Choose capabilities for the decision at hand; do not deploy them all by default.
Implementation implication: Start with a bound task and clear review points. Specify what the system may access or change, when it must stop, and who reviews exceptions. Make calculation methods, inputs, and limits visible.
Keep responsibility for strategic choices with identifiable people.
“AI acts within authorized boundaries; people decide” applies to organizational priorities, stakeholder values, investment, risk, and long-term commitments. Executive approval alone does not ensure operational readiness: conflicting business-unit priorities, misaligned incentives, inadequate capability development, and unclear ownership can delay execution or reduce value. Human governance must connect strategic approval with practitioner validation, operational responsibilities, and stakeholder deliberation.
Implementation implication: Assign decision owners and approval gates. AI may assemble evidence and compare alternatives; people should establish priorities, resolve trade-offs, and authorize commitments.
Design the system to support deliberation rather than merely producing a persuasive recommendation.
Business cases become outdated as economic conditions, work policies, staffing, or operations change. Keep decision models reviewable and compare options using current evidence—for example, lease exit costs, consolidation savings, and commute impacts. A comparison view can show how changed assumptions affect results; an interactive dashboard is optional. Faster analysis must not bypass approval or public deliberation.
Implementation implication: Apply the same criteria to each option, disclose assumptions, and test whether changed conditions alter the conclusion. Include no-project or defer options where appropriate. Compare short-term budgets and staffing changes with actual lease, fit-out, and facility commitments rather than relying on generic planning horizons.
Create reusable, structured predesign information rather than an isolated final report.
Information is often rebuilt at phase transitions, making institutional knowledge difficult to retain. Carry predesign evidence and reasoning into design, construction, operations, and future portfolio planning. Continuously updated portfolio models can connect space-planning rules, lease benchmarks, and headcount assumptions across the asset lifecycle while retaining dated records of the evidence used for each approved decision.
Implementation implication: Carry forward approved requirements, assumptions, constraints, decision criteria, and decision history using consistent identifiers and version control. Continuity need not mean one monolithic database; it means that information remains connected and interpretable.
Retain why a decision was made—not just its final answer.
A searchable record of prior reasoning helps teams reuse knowledge rather than rediscover it. Capture work processes, assumptions, criteria, alternatives, stakeholder reasoning, lessons learned, and outcomes. For portfolio planning, connect supply and financial commitments with observed occupancy and utilization and qualitative employee experience. This combined evidence can improve demand assessments beyond predetermined space-entitlement ratios alone.
Implementation implication: Maintain a decision record linking evidence, alternatives, rationale, approval, and subsequent results. Use later outcomes to improve future predesign analysis.
Implementation is an organizational change effort, not merely software deployment.
Consistent data protocols, practitioner involvement, small pilots, gradual expansion, and cost-benefit monitoring support process change. Address conflicting priorities and operational readiness as well as software adoption. For public asset delivery, incorporate early community engagement, applicable legislative and zoning requirements, and transparent scenario evaluation to support public trust and continuity through multi-year leadership transitions.
Implementation implication: Assign a process owner and involve practitioners, executives, and affected stakeholders. Use review workshops to test options against operational and cultural needs, resolve conflicts, and record agreed changes. Train users to check evidence and assumptions, not simply accept fluent outputs.
Start with a manageable decision-support use case and scale only after demonstrating value.
Test whether the system improves evidence retrieval and option preparation without increasing errors or review effort. Measure quality, total effort, cost as well as speed. A short pilot can show immediate value, but later project and operating results are needed to assess long-term benefits.
Implementation implication: Measure more than usage and time saved. Evaluate evidence completeness, traceability, errors, rework, usefulness of alternatives, and downstream changes caused by missed requirements. Establish a baseline before the pilot.
The six-stage implementation roadmap below assigns work, responsibilities, and improvement gates for defining, testing, and maintaining these requirements. These implementation stages are distinct from the three predesign phases and their investment and project authorizations.
The implementation stages below improve how strategic predesign is performed; they do not replace its three phases or create permission to commit funds, transact property, award contracts, or begin design. Apply the common Procedures groups throughout: problem framing; participation and coordination; evidence and information governance; risk; alternatives and business case; and authorization, change control, and learning.
Adapt the inquiry to uncertainty and the proposed commitment.
The strategic planner leads Executive Vision, Portfolio Analysis, and preparation of the Business Case. Use the improved workflow to connect mission, competitive or service context, business-unit demand, asset capacity, and financial commitments.
Compare work-process change, technology, use of existing resources, and expansion, optimization, or contraction. Record criteria, scenarios, assumptions, resources, intended benefits, and conditions for sponsor direction.
Maintain the business case as a living decision instrument rather than a one-time persuasive report.
The portfolio and asset manager leads location strategy and site-selection criteria, market survey and technical due diligence, and transaction readiness and lease negotiation. Use common definitions and evaluation criteria to compare functional fit, availability, infrastructure, lifecycle cost, timing, and risks.
Qualified advisers validate material technical, environmental, legal, and commercial findings. Negotiation authority is not commitment authority.
Transfer authorized direction, evidence, requirements, commercial terms, risks, and outstanding actions to the receiving project team.
The project manager coordinates the project management team, translating business priorities into a Program of Requirements (POR), and alignment of delivery and procurement with project objectives. Apply the five programming steps—establish goals, collect and analyze facts, test and evaluate concepts, determine needs, and state the problem—across function, form, economy, and time.
Validate stakeholder and technical requirements, reconcile scope, budget, schedule, and risk, and document the delivery strategy. Assemble the charter, POR, updated business case, and readiness findings for the designated owner’s authorization decision.
Findings may require a return to earlier assumptions or approvals. Where no real estate decision is needed, proceed from Strategic Planning to Project Definition within the authorized mandate.
Where critical uncertainty affects a property commitment, authorize the needed definition work before making that commitment. A readiness review establishes evidence; the authorized owner decision specifies whether and under what conditions work may proceed.
Transaction, procurement, design, and later construction permissions remain separate.
Establish a human-governed strategic predesign capability for Strategic Planning, Real Estate, and Project Definition. The operating model combines AI + Software + Data + People, with integration and automation supporting the workflow.
The roadmap addresses organizational alignment, information fragmentation, planning-horizon mismatches, static business cases, and governance risks. Begin with one decision workflow; expand only when organizational readiness and tested results justify it.
Use the principles as operating rules, the six implementation stages as the improvement delivery plan, and the RACI matrix to assign task responsibility. Within the predesign decisions served by the pilot, apply the Organization chapter’s RAPID framework and established phase leadership.
Planning assumption: approximately 24 weeks to establish and evaluate a bounded pilot, followed by controlled expansion. Timing depends on data readiness, security review, integration complexity, and available staff. Advance through approval gates, not simply because a scheduled date has arrived.
This proposed role-based matrix assigns tasks and implementation Gates 1–6. Confirm role holders and delegated authority at Gate 1.
R — Responsible: performs the work. A — Accountable: owns completion or the specified implementation decision; each row has exactly one A. C — Consulted: provides input before completion. I — Informed: receives status or results. A/R: owns and performs the activity. —: no routine assignment.
Required specialist signoffs remain mandatory even where the role is marked C; accountability does not permit bypassing them.
Role key: ES = Executive sponsor; PO = Predesign process owner; DO = Authorized decision owner for the relevant Strategic Planning, Real Estate, or Project Definition decision; DS = Data steward; TL = Technical lead; SR = Security reviewer; PT = Practitioner pilot team, including the relevant phase leader, professional reviewers, stakeholder facilitation, and assigned HR, Communications, Finance, Legal, Procurement, and operations contributors; LT = Receiving lifecycle team, represented by a designated receiving owner.
Assign an individual role holder for each A, including where a team is represented. Identify change-management and benefit-monitoring owners within these assignments rather than leaving them implicit. AI/agents support responsible people; they hold no accountability or approval authority.
RACI Matrix
|
Stage / activity or approval |
ES |
PO |
DO |
DS |
TL |
SR |
PT |
LT |
|
1. Charter, goals, measures, uncertainty, roles, decision map, baseline plan |
A |
R |
C |
C |
C |
C |
R |
C |
|
Gate 1. Approve scope, resources, and decision boundaries |
A |
R |
C |
I |
C |
C |
I |
I |
|
2. Source register, benchmarks, site and regulatory evidence, stakeholder needs, data model |
I |
A |
C |
R |
R |
C |
C |
C |
|
2. Access rules and authorization controls |
I |
A |
C |
R |
R |
C |
C |
C |
|
Gate 2. Confirm evidence readiness and authorized access |
I |
A |
C |
R |
C |
R |
C |
I |
|
3. Pilot cases, reviewed requirements, comparison tools, test design, baseline |
I |
A |
C |
C |
R |
C |
R |
C |
|
3. Agent permissions, stop conditions, escalation rules |
I |
A |
C |
C |
R |
C |
R |
I |
|
Gate 3. Approve test scope, review rules, acceptance thresholds |
I |
R |
A |
C |
C |
C |
R |
I |
|
4. Configure retrieval, extraction, selected tools, integrations, controls, logs |
I |
A |
I |
R |
R |
C |
C |
I |
|
4. Validate evidence, calculations, permissions; resolve defects |
I |
A |
C |
R |
R |
R |
R |
I |
|
4. Review workshops, conflict resolution, rule changes, training and support |
I |
A |
C |
C |
R |
C |
R |
I |
|
Gate 4. Authorize supervised live use after required sign-offs |
I |
A/R |
C |
C |
R |
R |
C |
I |
|
5. Supervised pilot, scorecard, cost-benefit report, recommendation |
A |
R |
C |
R |
R |
C |
R |
C |
|
5. Approve each strategic choice and record final rationale |
I |
C |
A/R |
C |
C |
C |
R |
I |
|
Gate 5. Decide expand, revise, pause, or stop |
A |
R |
C |
C |
C |
C |
C |
C |
|
6. Expansion backlog, approved integrations, deployment package, funding proposal |
A |
R |
C |
R |
R |
C |
C |
C |
|
6. Prepare lifecycle handover and continuing ownership records |
I |
A |
C |
R |
R |
C |
C |
R |
|
Gate 6. Accept usable handover and receiving ownership |
I |
R |
C |
R |
R |
C |
C |
A |
|
6 / ongoing. Authorize funded releases after quality revalidation |
A |
R |
C |
R |
R |
C |
C |
C |
|
Ongoing. Source refresh, support, incidents, weekly issue reviews |
I |
A |
C |
R |
R |
R |
R |
C |
|
Ongoing. Compare predicted and actual outcomes, curate lessons, maintain repository |
I |
A |
C |
R |
C |
C |
R |
R |
|
Ongoing. Quarterly review of value, evidence, rules, tools, and controls |
C |
A/R |
C |
R |
R |
C |
C |
C |
The intended result is improved organizational capability: accountable people using repeatable procedures, connected evidence, and appropriate tools to make better decisions. Competitive advantage or public value depends on how well the organization puts these decisions into practice and learns from outcomes.
Prepared by Steven Parshall, 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 |