Menu
Log in



Log in

5 Oganization

Participants, Roles and Responsibilities


1.1 Enterprise

1.1.1 Organizing Model

1.1.2 A Framework for Organization Design

1.1.3 Real Estate Function

1.2 Decision Makers

1.2.1 Private-Sector Owners

1.2.2 Developer / Investment Owners

1.2.3 Public-Sector Owners

1.2.4 Executive Management and Project Sponsors

1.2.5 Owner’s Project Manager

1.3 Stakeholders

1.3.1 Owners, Executives, and Sponsors

1.3.2 End Users and Cross-Functional Enterprise Departments

1.3.3 Service Providers and Advisors

1.3.4 Strategic Planners

1.3.5 Real Estate Advisers

1.3.6 Architectural Programmers and Workplace Consultants

1.3.7 Project Managers, Including Appointed OPMs

1.3.8 IT Project Managers

1.3.9 External and Public Stakeholders


1.4 Roles and Responsibilities

1.4.1 Leadership Responsibilities and Partners

1.4.2 RAPID Matrix

1.4.3 Phase Gates

1.5 Change Management

1.5.1 Application to the Strategic Predesign Process

1.5.2 Change Management Communication Plan

1.5.3 Putting the Plan into Practice

1.6 Process Improvement

1.6.1 Application to the Real Estate Function

1.6.2 Application to Strategic Predesign

1.6.3 Developing the Internal Delivery Team

1.6.4 Cross-Functional Delivery Team


Introduction

Strategic predesign connects enterprise strategy to the requirements for physical assets and capital projects before design begins. This chapter explains how organizational design, governance, phase leadership, and stakeholder participation support that work. It begins with enterprise organization and owner authority, then defines stakeholder and service-provider roles, decision responsibilities, and phase gates. The three predesign phases—Strategic Planning, Real Estate, and Project Definition—establish the direction and approved requirements that guide subsequent design, construction, and operations. The chapter then addresses change management and process improvement: engaging stakeholders, communicating decisions, refining workflows, and developing internal delivery teams while projects progress. Cross-functional coordination, mentoring, and documented playbooks help retain practical knowledge for future work. Together, these practices connect clear authority and requirements with the people and processes needed to carry them into successful delivery and operations.

1.1 Enterprise

An enterprise is a business, organization, institution, or government agency considered as a coordinated whole. In this chapter, the term refers primarily to organizations whose capital planning involves multiple operating units, functions, or locations. These enterprises commonly exhibit the following traits, although size and hierarchy alone do not define an enterprise:

  • ·       Cross-Functional Scope: It integrates multiple specialized departments—such as Real Estate, Human Resources, Information Technology, Legal, Procurement, and Finance—toward a unified strategic mission.
  • ·       Portfolio Scale: It manages extensive physical, technological, or human assets across multiple locations, regional hubs, or global markets.
  • ·       Formal Governance: It uses governing bodies, such as steering committees and executive leadership teams, together with task-responsibility frameworks such as RACI and decision-role frameworks such as RAPID to allocate resources and coordinate complex projects.

1.1.1 Organizing Model

Strategic predesign works best when strategy, structure, processes, rewards, and people reinforce one another. These five organizational design dimensions follow Jay Galbraith’s Star Model. Aligning them can reduce friction, conflicting priorities, delays, and value leakage while supporting strategy execution.

1. Strategy

Strategy defines the organization’s direction: its vision, mission, goals, objectives, and sources of competitive advantage or public value. In strategic predesign, it establishes the criteria for evaluating alternatives and making trade-offs across the remaining organizational design dimensions.

2. Structure

Structure is the formal placement of power and authority within the organization. It involves the following features:

  • ·       Specialization: The types and numbers of job specialties.
  • ·       Shape: The span of control (flat vs. tall hierarchies).
  • ·       Distribution of Power: Centralization versus decentralization of decision-making.
  • ·       Departmentalization: How units are grouped (e.g., functional, product, geographic, or matrix).

3. Processes

Processes govern work, information flow, and decision-making across the organization. They operate in two directions:

  • ·       Vertical processes: Allocation of scarce resources and funding, supported by planning and budgeting cycles and information exchanged between organizational levels.
  • ·       Horizontal (lateral) processes: Cross-functional workflows, networks, integrative roles, and teams that cut across silos to speed up execution.

Structure defines reporting lines, hierarchies, functional departments, and formal divisions of labor. Processes connect these arrangements through workflows, decision channels, information exchanges, and cross-functional interaction. As work becomes more uncertain or complex, reporting lines alone may not provide enough coordination. Leaders must also align lateral relationships, goal setting, and information systems so the organization can adapt and execute effectively.

4. Rewards

Rewards include performance measures, compensation, recognition, and incentives. They align individual goals and motivations with the organization’s strategic direction. Misaligned rewards can undermine operating-model changes by encouraging behavior that conflicts with the intended outcomes.

5. People

Human resource policies address recruitment, selection, rotation, training, and career development. Together, they develop the mindsets, skills, and organizational capabilities needed to execute the strategy.

1.1.2 A Framework for Organization Design

Enterprises vary in form and purpose, and their organizational arrangements change as they respond to competitive pressures and other external forces. During Strategic Planning, the strategic planner identifies the capabilities the enterprise needs to achieve its mission. The framework below makes that connection explicit: strategy defines the required capabilities, while structure, processes, people, and rewards enable them. Capabilities link strategic intent to organizational choices; they are not a replacement for strategy in Galbraith’s five-category Star Model. Aligning and realigning these choices supports competitive advantage or, for mission-driven organizations, effective mission delivery.

1.1.3 Real Estate Function

The same framework applies to the real estate function across Strategy and Planning, Design and Construction, and Facility Operations. A real estate director uses the Star Model’s five categories to align this function with enterprise strategy. The following descriptions explain how required capabilities connect that strategy to structure, processes, people, and rewards.

Capabilities are the organizational abilities needed to execute the strategy. They identify what the enterprise must do well to differentiate itself in its competitive environment or fulfill its mission, and they help define the critical success factors against which organizational choices are evaluated.

Structure determines where formal power and authority reside. Organizational units are typically grouped by function, geography, customer, or product. These arrangements establish reporting relationships, decision authority, and formal communication channels.

Processes are connected activities that move work and information vertically and horizontally through the organization. Work processes and management processes define the roles and responsibilities needed to perform activities, identify when work can be completed within one unit, and establish when collaboration is required.

People policies guide employee selection, staffing, training, and development, including communication between employees and managers. These policies develop the skills and capabilities managers and employees need to work effectively. They are shaped by the organization’s shared culture: the values, mindsets, and norms of behavior that develop over time.

Rewards align individual behavior and performance with the organization’s mission. They include compensation, recognition, and incentives, supported by metrics used to evaluate individual and collective performance. Measures indicate progress; rewards reinforce the behavior needed to achieve it.

1.2 Decision Makers

1.2.1 Private-Sector Owners

Private-sector owners hold ownership interests in an enterprise. Their economic and governance powers depend on its legal structure and governing documents; an ownership interest does not necessarily confer day-to-day management authority. Common forms of ownership include.

Shareholders / Stockholders: In publicly or privately held corporations, shareholders hold equity shares. Their economic and voting rights depend on the number and class of shares held and the corporation’s governing documents.

Partners: In partnerships, such as law firms, architectural practices, or consulting firms, partners hold ownership interests. Their rights to profits, responsibility for losses, management authority, and personal liability depend on the partnership structure, governing agreement, and applicable law; general and limited partners do not necessarily share the same responsibilities.

Sole Proprietors: In smaller enterprises, a single individual owns and operates the business entirely, holding 100% of financial and legal responsibility.

Members: In Limited Liability Companies (LLCs), the owners are referred to as members.

Founders & Private Equity / Venture Capital Firms: In growing commercial enterprises or startups, early founders and institutional investors who hold equity are key owners guiding strategic direction.

Key Responsibilities and Rights of Enterprise Owners:

  1. Ultimate Governance & Control: Owners typically elect a Board of Directors (in corporations) to oversee executive management and ensure the business aligns with owner interests.
  2. Financial Residual Claim: Owners are entitled to the residual profits of the enterprise (distributed via dividends, profit-sharing, or equity growth) after expenses and applicable liabilities are accounted for, subject to lawful distribution requirements.
  3. Strategic Alignment: In the context of capital planning and strategic predesign, owners set the high-level vision, risk appetite, and capital expenditure (CapEx) thresholds that dictate how physical assets, portfolios, and enterprise projects are funded and prioritized.

1.2.2 Developer / Investment Owners

Developer and investment owners are private-sector entities, commercial developers, institutional investors, or corporate entities that commission, finance, construct, and operate real estate assets and infrastructure to generate financial returns, maximize capital appreciation, or satisfy specific corporate portfolio strategies.

 Unlike public-sector entities driven by public service mandates, developer and investment owners prioritize bottom-line financial performance, return on investment (ROI), internal rate of return (IRR), net operating income (NOI), and property asset valuation.

Projects are evaluated through a lens of market risk, leasing velocity, construction cost volatility, debt financing costs, and exit strategies (e.g., disposition, recapitalization, or long-term hold).

Projects are funded through complex private capital structures involving equity partners, institutional lenders, construction loans, mezzanine debt, and occasionally public-private incentives or tax credits.

Time is directly tied to capital cost; minimizing the predesign, entitlement, and construction timeline is paramount to reducing carrying costs and capturing market demand windows.

How Developer / Investment Owners Operate in Strategic Predesign

  1. Market-Driven Opportunity & Feasibility: Decision-making begins by identifying market gaps, demographic shifts, highest-and-best-use analyses, and tenant demand signals to validate project viability before committing heavy capital.
  2. Pro Forma & Program Alignment: Programming and spatial layout decisions are tightly coupled with financial feasibility models—balancing gross-to-net rentable area ratios, efficiency standards, and target construction budgets.
  3. Speed and Schedule Optimization: Predesign processes are compressed and structured to secure entitlements, zoning variances, and schematic design approvals rapidly to lock in financing terms and construction pricing.
  4. Exit and Asset Lifecycle Strategy: Initial programming decisions evaluate long-term flexibility, tenant adaptability, and operational efficiency to maximize asset liquidity and eventual resale or refinancing value.

1.2.3 Public-Sector Owners

Public-sector owners are government entities, public agencies, or publicly constituted institutions that commission, finance, or operate public assets and infrastructure, such as schools, civic buildings, transit systems, military installations, and utilities. They pursue public-service mandates within statutory governance, funding, and accountability requirements. Private-sector objectives vary and may include financial returns, operational effectiveness, or institutional missions.

Public-sector owners are accountable to the public through their governing institutions and applicable oversight processes. Decisions may be subject to public scrutiny, records-disclosure requirements, and hearings, with applicable exceptions; citizens and taxpayers are not corporate shareholders.

Instead of maximizing profit margins, public-sector owners prioritize public health, safety, community equity, long-term civic utility, and regulatory compliance.

Projects are typically financed via public funds, municipal bonds, tax revenues, or federal/state grants. Budgets are tied to rigid fiscal year cycles and statutory approval processes, requiring high levels of financial transparency.

They must navigate extensive bureaucratic, environmental, zoning, and statutory procurement mandates that dictate how projects are budgeted, bid on, and executed.

How Public Sector Owners Operate in Strategic Predesign

  1. Democratic Governance & Stakeholder Alignment: Decision-making authority is often distributed across elected boards, commissioners, civic committees, and specialized public agencies. Achieving alignment requires balancing diverse public interests, political considerations, and community feedback.
  • 2.      Transparent Procurement Rules: Public-sector owners follow the procurement rules applicable to their jurisdiction, funding source, and service type. These may require competitive solicitations, qualifications-based selection, documented evaluation, or authorized exceptions. Requests for qualifications (RFQs) and requests for proposals (RFPs) are possible instruments, not universal requirements. Applicable participation requirements and fiscal controls must be established for each procurement.
  1. Long-Horizon Asset Stewardship: Because public assets are intended to serve communities for decades (often generations), public-sector owners place heavy emphasis on lifecycle performance, durability, energy efficiency, and operational ease rather than short-term cost savings.

1.2.4 Executive Management and Project Sponsors

Executive management and project sponsorship often overlap in major initiatives, but they carry distinct authorities, accountabilities, and perspectives. The same person may hold both roles; the project charter must distinguish enterprise authority from initiative-specific responsibilities.

Role Dimension

Owners

Executive Management

Project Sponsors

Core Definition

Private-sector owners, or the designated public-sector commissioning authority, whose rights and responsibilities are established by the applicable governance framework.

The senior leadership team, such as the C-suite or managing partners, appointed under the enterprise’s governance arrangements to direct strategy implementation and operations.

The specific business leaders or champions who secure funding, authorize resources, and champion a specific initiative.

Primary Focus

Long-term asset value, enterprise-wide risk, capital allocation, and strategic direction.

Operational effectiveness, cross-functional coordination, financial stewardship, mission delivery, and portfolio performance.

Business outcome delivery, cross-functional alignment, and removing political or operational roadblocks for a project.

Decision Authority

Exercises reserved approvals for capital budgets, governing documents, and major portfolio transactions through the designated owner or board authority.

Translates owner vision into operational policies, approves enterprise-wide guidelines, and manages executive talent.

Champions the business case, secures business-unit alignment, and transitions within delegated limits; escalates reserved decisions to the designated owner or executive authority.

The Owner's Role Sets the Boundaries: Owners establish the risk appetite and overall financial thresholds. In a real estate or capital project, they define how much capital can be deployed across the enterprise portfolio and what long-term strategic goals must be met.

  1. Executive Management Translates Strategy into Action: Executive leadership takes the owner's mandate and designs the governance framework (such as portfolio dashboards, cross-functional partnerships across Real Estate, HR, IT, and Finance, and performance KPIs).
  2. Project Sponsors Drive the Specific Initiative: The project sponsor champions the initiative from Strategic Planning through Real Estate and Project Definition, rather than first appearing during Project Definition. The sponsor is accountable for the intended business outcomes, secures authorized resources, and ensures that real estate strategy and Problem Seeking programming reflect enterprise needs. Phase-gate decisions remain subject to the sponsor’s delegated authority and any reserved owner approvals.

1.2.5 Owner’s Project Manager

An Owner’s Project Manager (OPM) is a professional or firm engaged by the owner to provide project-management advice and representation within an agreed scope. The term Owner’s Representative is often used for a similar owner-side role, but the titles are not necessarily interchangeable. Services may span planning, design, construction, and closeout; authority, agency status, and any fiduciary obligations depend on the appointment, contract, and applicable law.

An OPM supplements the owner’s internal capacity and specialized expertise during capital planning and delivery. Within the agreed mandate, the OPM coordinates the baseline established during Project Definition, monitors costs and schedules, reviews proposed changes, and reports deviations for resolution. Procurement support may include preparing RFQs or RFPs where applicable, evaluating submissions, and supporting contract negotiations with Procurement and Legal. The OPM coordinates early review of site constraints, permitting, and constructability risks and facilitates communication among Real Estate, Finance, Legal, IT, HR, and external delivery partners. These services do not confer signature authority, replace specialist professional duties, or guarantee project outcomes.

Why Enterprises and Public Owners Use OPMs:

  1. Bridging the Knowledge Gap: Architecture, engineering, and construction (AEC) delivery is highly technical. An OPM translates complex construction metrics, building codes, and engineering data into clear, actionable insights for executive management and project sponsors.
  • 2.      Maintaining Accountability: The OPM monitors delivery against the approved Program of Requirements, coordinates reviews, and reports deviations for resolution. This oversight does not replace the designer’s professional responsibilities or the contractor’s quality-control obligations.
  • 3.      Preserving Internal Resources: By coordinating day-to-day owner-side activities, submittal tracking, and contractor meetings within the agreed scope, the OPM allows the owner’s internal team to focus on core operations. Construction administration, technical submittal review, and site-management duties remain with the parties assigned those responsibilities by contract.

1.3 Stakeholders

Stakeholders are individuals, groups, or organizational units that can affect, be affected by, or perceive themselves to be affected by project decisions and outcomes. Strategic predesign connects enterprise business strategy with physical-space delivery, so participation extends beyond the project team to internal leadership, cross-functional departments, external partners, and communities. The following sections distinguish these groups and their contributions.

1.3.1 Owners, Executives, and Sponsors

Owners and Governing Boards: Exercise ownership and governance rights under the applicable legal structure; establish or approve capital limits, strategic direction, and risk tolerance through designated authorities. Board duties and owner rights are distinct and depend on governing documents and applicable law.

Executive Management (C-Suite & Managing Partners): Translate the owner's vision into operational directives, establish cross-functional governance frameworks (such as steering committees), and oversee portfolio performance.

Project Sponsors: Act as the business-unit champions or internal owners of a specific initiative (e.g., HQ relocation or hybrid workplace transition), securing project funding and driving internal alignment.

1.3.2 End Users and Cross-Functional Enterprise Departments

Business or Administrative Units: These are the primary operations of the enterprise that have the responsibility for the delivery of goods and services to customers and constituents.

Real Estate, Design and Construction, and Facilities and Workplace Operations: These functions manage portfolio assets, lease negotiations, and site selection; oversee design and construction projects; and operate facilities and associated services. Depending on the enterprise, services may include office support, safety and security, travel, janitorial work, mailroom operations, shipping and receiving, reception and visitor processing, food and beverage, venue management, and maintenance.

Human Resources (HR): Champions organizational culture, employee experience, headcount forecasting, and change management.

Information Technology (IT): Defines digital infrastructure, AV systems, smart-building technology, and data security requirements.

Finance / Accounting / Treasury: Manages business case modeling, ROI analysis, cash flow projections, and budget controls.

Legal & Procurement: Navigates regulatory compliance, contract negotiations, vendor agreements, and risk mitigation.

Communications: Responsible for internal (employee) and external (public) messaging and communications.

Stakeholder engagement begins in Strategic Planning and continues through Real Estate and Project Definition. RAPID (Recommend, Agree, Perform, Input, Decide) clarifies roles for significant decisions; it complements, rather than replaces, task assignments and an engagement plan. Early cross-functional participation helps expose conflicting requirements and reduce misaligned expectations, scope creep, and downstream changes.

1.3.3 Service Providers and Advisors

Service providers and advisers contribute specialized expertise across strategic predesign and the built-environment lifecycle. Their work often overlaps, but coordination does not make their contractual duties interchangeable. This overview identifies the disciplines; the following subsections explain the planning, real estate, programming, project-management, and technology roles in more detail.

Owner’s Project Managers (OPMs) / Owner’s Representatives: Owner-side advisers who manage master schedules and budgets and coordinate the delivery team within a defined appointment. Independence, decision authority, and any fiduciary duties depend on the contract and applicable law.

Design & Architecture Teams: Translate the Program of Requirements into spatial, functional, and aesthetic designs (planners, architects, interior designers, and specialized consultants).

Engineering & Technical Consultants: Provide structural, MEP (mechanical, electrical, plumbing), civil, and acoustic expertise to ensure technical feasibility.

Real Estate Brokers & Transactional Advisers: Conduct market surveys, source pre-qualified properties, and lead lease negotiations.

Contractors and Construction Managers: Contractors execute construction and manage site activities within their contracts. A construction manager may provide owner-side advisory services or undertake construction delivery responsibilities, depending on the delivery model and appointment; not every construction manager performs the physical buildout.

Facilities and Workplace Operations: Outsourced management and maintenance of facilities, facility operations and employee services.

1.3.4  Strategic Planners

Strategic planners align the enterprise’s long-term business goals, vision, and growth trajectory with portfolio-wide physical and organizational strategies. They establish the planning basis for location decisions and project requirements.

Primary Responsibilities:

  • ·       Translating executive business plans and headcount forecasts into overarching spatial and operational requirements.
  • ·       Assessing macro-environment trends, hybrid work models, and competitive positioning (such as using Porter’s Five Forces to understand industry competition where relevant to enterprise strategy).
  • ·       Defining enterprise-wide design guidelines, performance criteria, and the initial business case for capital initiatives.
  • ·       Monitoring portfolio health on an ongoing basis through Integrated Workplace Management Systems (IWMS) and dashboards.

1.3.5 Real Estate Advisers

Real estate advisers source and evaluate physical assets that match the enterprise’s operational and financial parameters. They support transactions and negotiations within their authorized scope, working with the portfolio team, Legal, and Finance.

Primary Responsibilities:

  • ·       Conducting market surveys, demographic/labor supply analyses, and zip code/drive-time assessments.
  • ·       Touring and evaluating pre-qualified properties and negotiating lease transactions or purchase agreements.
  • ·       Structuring lease agreements to maximize operational flexibility (e.g., securing expansion, contraction, or termination options).
  • ·       Performing preliminary financial modeling regarding rent obligations, operating expenditure (OpEx), and tenant improvement (TI) allowances.

1.3.6 Architectural Programmers and Workplace Consultants

Architectural programmers and workplace consultants translate qualitative information about organizational culture and quantitative business-unit needs into a data-informed Program of Requirements (POR). The POR defines what the project must achieve and provides the basis for subsequent design.

Primary Responsibilities:

  • ·       Conducting stakeholder interviews, focus groups, and co-design sessions with business-unit leads and HR.
  • ·       Defining spatial typologies, functional adjacencies, desk-sharing ratios, and square-footage allocations per seat/employee.
  • ·       Applying structured programming methodologies, such as Problem Seeking: establish Goals; collect and analyze Facts; uncover and test Concepts; determine Needs; and state the Problem.
  • ·       Establishing the functional adequacy and spatial standards that the design and architectural teams will execute against.

1.3.7 Project Managers, Including Appointed OPMs

Project managers coordinate Project Definition and execute the approved delivery plan by managing scope, schedule, budget, and cross-functional coordination. An appointed OPM performs the owner-side services assigned by contract; the appointment determines the role’s scope and authority.

Primary Responsibilities:

  • ·       Developing project governance arrangements, master schedules, and decision-role matrices, such as RAPID, for approval by the designated authority.
  • ·       Developing and tracking preliminary capital expenditure (CapEx) budgets and managing cost controls throughout the lifecycle.
  • ·       Coordinating the procurement of design, engineering, and construction services with Procurement and Legal using the authorized selection method, which may include RFQs, RFPs, or other applicable procedures.
  • ·       Representing the owner within the assigned mandate, coordinating risk mitigation and cross-functional issue resolution, and managing the handoff from strategic predesign to design and construction. Contractual authority and any fiduciary duties must be expressly established.

1.3.8 IT Project Managers

The IT Project Manager coordinates the project’s technology scope, budget, schedule, and operational readiness with the overall Project Manager. The role connects facility requirements with secure, maintainable technology systems for new facilities, renovations, and relocations, including hybrid work, data protection, and operational workflows.

Primary Responsibilities:

  • ·       Technology Requirements and Readiness: Translate business and user needs into coordinated technology requirements, validation criteria, and readiness plans for facilities and relocations.
  • ·       Digital Infrastructure and Smart-Building Planning: Coordinate requirements for network architecture, fiber capacity, wireless coverage and capacity, Internet of Things (IoT) sensors, and smart-building systems. Select technology standards against approved performance, security, compatibility, and lifecycle requirements rather than prescribing a particular generation for every project.
  • ·       AV and Collaboration Technology Integration: Coordinate specialist design and budgeting for audio-visual (AV) systems, hybrid meeting rooms, town-hall broadcasting, and collaboration tools selected against approved user, security, and interoperability requirements.
  • ·       Cross-Functional Coordination with IT and Security: Collaborate with internal IT departments, physical security teams, and data protection officers to coordinate cybersecurity requirements, badge-access control systems, and data access and reporting requirements.
  • ·       Vendor and Sourcing Management: Coordinate technology sourcing with Procurement, review applicable RFQs and RFPs, and manage low-voltage, cabling, and hardware installation interfaces within delegated authority and contracted scopes.
  • ·       Budget and Schedule Alignment: Manage the approved technology CapEx budget and coordinate procurement, installation, testing, and operational readiness with the master project schedule.

1.3.9 External and Public Stakeholders

Regulatory Bodies: Municipalities, planning commissions, and government agencies that enforce zoning laws, building codes, environmental regulations, and public safety standards.

The Community & Public Users: Citizens, local neighborhoods, or client bases who interact with the asset, particularly in public-sector or civic projects where transparency and public trust are paramount.

1.4 Roles and Responsibilities

1.4.1 Leadership Responsibilities and Partners

The following table consolidates the roles described above and shows their principal responsibilities and partners across strategic predesign and subsequent delivery. Strategic planners lead strategic evaluation; portfolio and asset managers lead real estate work; and project managers coordinate Project Definition and delivery. These are phase-leadership assignments, not automatic approval rights. Contractual duties and decision authority remain governed by approved appointments and delegations.

Role

 Responsibilities

Partners

CRE Executive / Head of Real Estate

Align the portfolio with enterprise strategy; establish executive governance; coordinate capital expenditure (CapEx) allocation within delegated limits; oversee portfolio performance and enterprise real estate risk.

Owners/Board; Executive Management; Project Sponsors; Finance and financial planning and analysis (FP&A); Legal; functional leads.

Strategic Planner, Portfolio and Asset Manager

Strategic planners develop portfolio strategy and evaluate demand, alternatives, and footprint optimization. Portfolio and asset managers analyze markets, establish search criteria, evaluate sites and property fit, coordinate due diligence, manage transactions and negotiations within authorization, and maintain landlord relations.

CRE Executive; Sponsor; Finance; Legal; Procurement; commercial brokers and real estate advisers; business-unit leaders; programmers; technical specialists; facility operations.

Workplace Strategist, Programmer, HR, Communications and Change Managers

Integrate hybrid-work policy and cultural objectives; track utilization and employee experience; conduct focus groups and facility programming; prepare the Program of Requirements; coordinate employee communication plans, move guides, and change management. Programming specialists develop requirements with users; HR and Communications lead their respective policies and engagement work.

Business-unit leaders and end users; Sponsor; HR; internal Communications; workplace consultants and programmers; Project Manager; IT; Finance; design teams; facility operations.

Project Managers

Coordinate Project Definition and capital project delivery; manage approved scope, budget, schedule, and risk; coordinate design reviews, contractor procurement, and delivery oversight within the appointment; maintain controlled handoffs. Project management integrates specialist work rather than replacing design, engineering, or contractor responsibilities.

Sponsor; Steering Committee; appointed Owner’s Project Manager; programmers; architects and engineers; Procurement; Finance; Legal; general contractors and construction managers; IT Project Manager; IT/AV integrators; facilities and workplace operations.

Design, Engineering and Construction Delivery Professionals

Translate the approved Program of Requirements into spatial and architectural design and engineered systems; deliver authorized capital buildouts. Designers and engineers perform their appointed professional services. Contractors perform contracted construction and site-management duties; construction managers provide advisory or construction delivery services according to their appointment. The Project Manager coordinates owner-side oversight without replacing these responsibilities.

Project Manager/Owner’s Representative; programmers; architects; engineering and technical consultants; general contractors and construction managers; IT/AV integrators; Procurement; facility operations.

Technology, IT, and Audio-Visual (AV) Managers

Define and deliver digital infrastructure, network security, smart-building integration, and AV systems; align technology procurement and deployment with project delivery; support operational readiness and IT helpdesk services.

IT department and IT Project Manager; Project Manager; IT/AV integrators; architects and engineers; Security; Procurement; Finance; business-unit users; facility operations.

Finance, Legal and Procurement Managers

Finance manages capital and budget controls and applicable accounting requirements; Legal addresses contractual and regulatory matters; Procurement manages vendor sourcing and the procurement process. Together, they support contract management and domain-specific risk mitigation without displacing designated approval authorities.

Owners/Executive Management; Sponsor; CRE Executive; FP&A; Project Manager; portfolio team; IT; specialist consultants; contractors and vendors; facility operations.

Facilities and Workplace Operations Managers

Provide operational input to planning and delivery; manage day-to-day facilities, vendors, physical security, reception and visitor experience, event and food services, and maintenance after occupancy or relocation.

Security; property managers; facilities and service vendors; Project Manager; portfolio team; IT/helpdesk; HR and Communications; business-unit users.

1.4.2 RAPID Matrix

This proposed matrix applies Bain & Company’s RAPID decision-role framework to Strategic Planning, Real Estate, and Project Definition. It links working outputs to decisions about their acceptance or authorization. RAPID assigns decision roles; it is not a task-responsibility matrix or a sequence of steps.
R — Recommend: One lead gathers input, develops options, prepares recommendation.
A — Agree: Confirm that the recommendation meets specified mandatory requirements before it reaches the decision maker. Assign this role sparingly; it is not general approval authority.
P — Perform: Implement the decision once authorized. Preparation and analysis before the decision belong to R and its contributors, not to P solely because they perform tasks.
I — Input: Contribute evidence and advice without concurrence or decision authority.
D — Decide: One designated authority makes the decision for the row. The assignments below are proposals to be confirmed against the approved governance framework.

Role abbreviations and authority. SP = Strategic Planner; PAM = Portfolio and Asset Manager; PM = Project Manager, including an appointed OPM only within its mandate; Sponsor = Project Sponsor; EM = Executive Management, including the corporate real estate (CRE) executive as applicable; Owner = designated owner, board, or public-sector authority; SC = Steering Committee. A phase leader’s D covers acceptance of working outputs within approved scope, not capital commitments, contracts, or reserved owner decisions. D* marks an authority that has not yet been designated: assign the Sponsor where delegation permits, otherwise the authorized EM or Owner decision maker. Where a collective body decides, record its governing decision rule. Before using any row, confirm the named R and D, each mandatory A requirement, approval thresholds, signature limits, and escalation route. If separate decisions require different authorities, record them separately rather than assigning multiple Ds to one decision.

Stakeholder abbreviations. BU/users = business or administrative unit leaders and end users; BU leaders = those unit leaders. FIN = Finance, Accounting, and Treasury, including FP&A. HR/COM = HR, Communications, and workplace/change-management leads as relevant. IT = IT department; IT PM = IT Project Manager. OPS = facilities and workplace operations, safety/security, and relevant outsourced providers. RE advisers = brokers and transaction advisers. Technical specialists include architecture, engineering, environmental, survey, and valuation advisers as required. Programming = architectural programmers and workplace consultants. Data owners and the Information Manager have task-specific information responsibilities. Regulators and community/public users provide input where applicable; statutory determinations remain separate from internal RAPID authority. Contractors and construction managers provide predesign feasibility, estimating, scheduling, and delivery input only when engaged. This matrix does not authorize construction execution.

Phase 1.1 — Strategic Planning

Step / Task

Recommend

Agree

Perform

Input

Decide

1.1.1 Establish executive vision and strategic direction

Facilitate vision session

SP

—

SP; advisers communicate and apply accepted direction

Owner; Sponsor; BU/users; HR/COM; FIN; CRE Executive

EM — working strategic direction within Owner mandate

1.1.2 Analyze portfolio, forecast demand, and evaluate scenarios

Establish information operating model

SP

IT — security/access; data owners — stewardship

SP; data owners

PAM; FIN; HR; OPS; Legal

SP

Prepare demand forecast

SP

—

SP; FIN; HR; BU leaders maintain and apply accepted forecast

EM; Sponsor; PAM; workplace leads; IT; OPS

SP

Audit portfolio supply and obligations

PAM

—

Planning/portfolio team maintains accepted inventory and obligations record

Legal; FIN; OPS; RE advisers; data owners

SP

Assess occupant experience

Workplace strategy lead

—

Planning/workplace team applies accepted findings to planning

BU/users; HR/COM; OPS; IT; public users where relevant

SP

Define strategic challenge

SP

—

SP applies accepted challenge statement to scenario evaluation

Sponsor; EM; PAM; FIN; HR; BU leaders; OPS

SP

Compare strategic scenarios

SP

—

SP; advisers; FIN use accepted evaluation in the business case

Sponsor; EM; PAM; Procurement; Legal; IT; HR/COM; BU/users; OPS

SP — accepts evaluation output for recommendation; does not approve strategic direction

Build strategic financial model

FIN

FIN — financial assumptions and controls

FIN; planning; Procurement maintain and apply accepted model

SP; PAM; Sponsor; Legal; OPS; BU leaders

SP — planning model acceptance

1.1.3 Prepare business case and obtain planning approval

Issue planning business case; approve planning direction and next-phase work

SP

FIN — affordability; Legal/ Procurement — applicable conditions

SP records the decision; PAM initiates authorized next-phase work

EM; Owner; BU leaders; HR/COM; IT; OPS; advisers

Sponsor — subject to reserved Owner/EM thresholds

Phase 1.2 — Real Estate

Step / task

Recommend

Agree

Perform

Input

Decide

1.2.1 Develop location strategy and approve selection criteria

Prepare and approve property search criteria — before candidate review

PAM

FIN — affordability limits; Legal — mandatory constraints

PAM; RE advisers apply approved search criteria

SP; BU/users; HR; IT; OPS; Programming; technical specialists; CRE Executive

Sponsor — proposed criteria approval authority

1.2.2 Survey market, complete due diligence, and evaluate properties

Conduct market survey and site visits

PAM

—

RE adviser; portfolio team; specialists pursue accepted shortlist within scope

BU leaders; HR; OPS; Programming; IT; FIN

PAM — shortlist/ evaluation scope

Complete specialist due diligence

PAM — consolidated findings

Legal — legal constraints; IT — security constraints

Legal; environmental; survey; architecture; engineering; IT; valuation specialists maintain accepted findings and track conditions

OPS; FIN; Procurement; RE advisers; regulators where required

PAM — evidence acceptance, not waiver of requirements

Test property fit and lifecycle cost

PAM

FIN — cost assumptions

Portfolio team; Programming; technical specialists; FIN apply accepted fit and cost findings

BU/users; HR; IT; OPS; PM/OPM if appointed; construction advisers if engaged

PAM — comparative evaluation

1.2.3 Confirm transaction readiness and negotiate authorized commitments

Negotiate and obtain commitment approval

PAM

Legal — binding terms; Procurement — process; FIN — funding/obligations

Authorized signatory executes after approval; PAM, RE adviser, Legal, and Procurement implement approved terms within mandate

Sponsor; EM/CRE Executive; Owner; IT; OPS; BU leaders; technical specialists

D* — designated commitment authority

Authorize real estate direction and transfer real estate baseline to Project Definition

PAM

PM — handoff completeness; Legal/FIN — outstanding commitment conditions

PAM transfers records; PM receives controlled baseline

SP; Sponsor; SC; IT; OPS; Programming; Procurement

Sponsor — phase transition; property commitments remain separately approved

Phase 1.3 — Project Definition

Step / Task

Recommend

Agree

Perform

Input

Decide

1.3.1 Mobilize project team and establish governance

Mobilize team and approve charter

PM

FIN — resources; Legal/Procurement — applicable appointment and sourcing requirements

Sponsor; PM; IT PM; authorized specialists

EM; Owner; SC; PAM; BU leaders; HR/COM; OPS; OPM if separately appointed

Sponsor — charter within delegated authority

Establish common data environment

PM

IT — security/access; Legal — applicable records requirements

PM; Information Manager

Data owners; IT PM; Programming; technical specialists; Procurement

PM

Approved Plan — charter, responsibility framework, milestone schedule, specialist scopes, controlled information environment

PM

FIN; Legal/Procurement; IT — respective controlled baselines

PM maintains; workstream leaders implement authorized plan

SC; EM; BU leaders; PAM; OPS

Sponsor — confirms complete plan package

1.3.2 Develop and validate Program of Requirements

Conduct programming inquiry

Programming lead

—

Programming/workplace consultants; users; specialists apply accepted findings to requirements development

BU/users; HR/COM; IT PM; OPS; FIN; PAM; community/public users where relevant

PM — inquiry scope and working output

Quantify and reconcile needs

Programming lead

FIN — budget; IT — technology/security constraints

Programmer; PM; IT PM; estimator; scheduler; technical specialists incorporate accepted needs into the draft POR

BU leaders; HR; OPS; PAM; construction advisers if engaged; Sponsor

PM — reconciled recommendation within baseline

Finalize POR and problem statements; approve POR and supporting baselines

PM

FIN — budget; IT — technology constraints; Legal — applicable compliance

Programming team; PM control and issue the approved POR for subsequent work

Sponsor; SC; BU/users; HR/COM; OPS; technical specialists; PAM

Owner — designated POR approval authority

1.3.3 Align delivery and procurement; complete readiness review

Prepare delivery and sourcing strategy

PM

Procurement — sourcing rules; Legal — contractual approach; FIN — funding constraints

PM; Procurement Manager; Legal implement approved sourcing strategy; awards require separate authorization

IT PM; Programming; design/engineering advisers; construction advisers if engaged; OPS; SC

Sponsor — strategy approval, not contract award

Prepare and update business case

PM

FIN — financial baseline; Legal/Procurement — relevant obligations

PM; Sponsor; FIN submit the accepted business case to the gate authority

EM; Owner; SC; PAM; IT PM; BU leaders; HR; OPS; estimator/scheduler

Sponsor — accepts recommendation for gate submission

Conduct Project Readiness Review

PM — readiness recommendation

FIN; Legal/Procurement; IT — mandatory domain clearances

PM; SC record the readiness determination and track required follow-up

Owner; EM; Sponsor; Programming; BU leaders; OPS; technical specialists

D* — Sponsor or single authorized executive specified in charter

Approval to Proceed — authorize, condition, defer, or decline entry to design

Sponsor

FIN; Legal/Procurement; IT — unresolved mandatory conditions

PM records Owner decision, conditions and authorized next-phase actions

SC; EM; PAM; IT PM; Programming; BU leaders; OPS

Owner — designated authorization authority; may coincide with readiness D only under explicit delegation

1.4.3 Phase Gates

Phase 1.1 gate record: approved planning direction and next-phase work, including conditions, unresolved issues, financial assumptions, and any higher-level authorization required.

Phase 1.2 gate record: approved real estate direction, criteria and evaluation evidence, due-diligence findings, separately authorized property commitments, unresolved conditions, and the baseline transferred to the Project Manager.

Phase 1.3 gate records comprise: (1) the Approved Plan; (2) the owner-approved POR, including traceable requirements, success criteria, and reconciled scope, quality, budget, schedule, technology, and risk baselines; (3) Project Readiness Review findings and the updated business case; and (4) the recorded owner decision to proceed, proceed with conditions, defer, or decline. The readiness review establishes the evidence for a decision; it does not itself authorize the next phase. Record each condition, responsible party, and applicable delegation with the owner’s decision.

1.5 Change Management

Change management is a structured approach to helping individuals, teams, and organizations move from a current state to a desired future state. It complements project management: project management coordinates scope, schedule, budget, and deliverables, while the change management process addresses the people side of the transition. This includes understanding concerns, addressing barriers, and supporting the adoption and sustained use of new processes, spaces, and organizational arrangements.

1.5.1 Application to the Strategic Predesign Process

In strategic predesign, change management begins during Strategic Planning and continues through Real Estate and Project Definition. It is not an activity added after the plan is complete. Early engagement helps stakeholders discover needs, test assumptions, resolve differences, and establish requirements that people understand and can put into practice.

Applying change management to strategic predesign involves several key dimensions:

1. Moving from Ambiguity to Shared Understanding: In predesign, stakeholders may interpret the same goals differently or hold conflicting views of what a facility or organization needs to achieve. This ambiguity of meaning, sometimes called equivocality, must be addressed before requirements can be agreed.

Structured stakeholder engagement, visioning workshops, and scenario testing make assumptions and concerns visible. Repeated cycles of testing alternatives and reviewing evidence help participants develop a shared understanding before capital is committed.

2. Testing Apparent Agreement: The Abilene paradox describes a group choosing a course of action its members privately oppose because each mistakenly believes the others support it. In predesign, apparent agreement about space reductions, open-plan layouts, or operating models may conceal concerns that have not been expressed.

Change management supports candid participation through structured discussions, anonymous feedback where appropriate, and repeated opportunities to review proposals. These practices help users raise operational constraints and exceptions early. They reduce the risk that silence will be mistaken for agreement or that unresolved objections will delay design and construction; they do not guarantee consensus.

3. Matching Coordination to Information Needs: As uncertainty and task complexity increases, reporting lines alone may not provide enough capacity to exchange information and resolve issues.

Change management supports the governance framework by clarifying how decisions are communicated, how cross-functional teams work together, and how participants contribute within their roles. Clear objectives, information channels, and escalation routes help teams respond to new findings. Communication arrangements do not, by themselves, delegate decision authority or permit departure from approved requirements.

4. Learning from Experience and Recording Agreements: Without accessible records of past decisions and outcomes, an organization may repeat spatial or organizational problems.

Reviewing how previous facilities and operating arrangements performed helps stakeholders interpret experience and establish evidence-based criteria. This retrospective sensemaking informs, rather than substitutes for, current requirements analysis. Record the resulting agreements and their rationale in the Program of Requirements (POR) and supporting records. Once approved, these documents provide a controlled baseline for subsequent phases.

1.5.2 Change Management Communication Plan

A change management communication plan defines what information will be shared, who needs it, who will communicate it, when it will be delivered, and which channels will be used. It also establishes how stakeholders can ask questions and provide feedback throughout the transition.

The plan complements project updates rather than replacing them. The project manager coordinates delivery information; change-management practitioners, workplace consultants, HR, and Communications develop engagement messages within their assigned roles. Sponsors and managers communicate the reasons for change and its implications for affected teams. Together, these communications explain what is changing, address concerns, and support informed participation and adoption. The elements of the Communication Plan include:

  • ·       Audience Segmentation: Identify stakeholder groups—such as executives, managers, end users, and support staff—and tailor information to their roles, needs, and the effects of the change.
  • ·       Key Messages: Explain consistently why the change is needed, what the intended future state is, and what it means for individual roles. Distinguish proposals under review from approved decisions.
  • ·       Timing and Phasing: Align messages with planning, review, approval, and implementation milestones. Identify the sender responsible and communication channel so stakeholders receive relevant information in time to participate or prepare.
  • ·       Feedback Loops (Two-Way Communication): Provide ways to ask questions, raise concerns, and contribute operational evidence. Explain how feedback will be reviewed, answered, and reflected in decisions.

1.5.3 Putting the Plan into Practice

In strategic predesign, these elements put the four change-management dimensions into practice: they organize information exchange, test apparent agreement, establish shared meaning, and communicate the approved baseline.

1. Organizing Information Exchange: Complex tasks generate questions and exceptions that require more than top-down announcements.

Use cross-functional workshops and user-group meetings to gather information from those closest to the work. Define regular opportunities for users to explain workflows, constraints, and exceptions. Route recommendations to the designated decision maker under the chapter’s governance and RAPID arrangements; participation does not confer approval authority.

2. Checking Support Before Decisions: During visioning and option reviews, apparent agreement about space reductions, layouts, or workflows may leave operational concerns unresolved. Check understanding and support rather than treating a lack of objections as consensus.

Use anonymous surveys where appropriate, structured breakout discussions, and repeated scenario reviews to test assumptions before announcing final decisions. Record operational constraints, differences of opinion, and how they were addressed. The aim is informed participation and transparent resolution, not an assumption that every stakeholder must prefer the selected option.

3. Establishing Shared Meaning: Terms such as “flexibility,” “collaboration,” and “efficiency” may mean different things to different departments. Service providers may also interpret them differently if the organization’s culture and operating practices are not explained.

Share relevant case studies and review how past facilities performed under operating demands. Architectural programmers and workplace consultants then translate strategic goals and operating and architectural concepts into concrete functional requirements. This combination of experience review and requirements analysis establishes a shared vocabulary before design begins.

4. Communicating and Maintaining the Approved Baseline: Once requirements are reconciled and approved, publish and reinforce the Program of Requirements (POR) and supporting criteria. Use POR consistently for the program in this chapter. An Owner’s Project Requirements (OPR) document, used in commissioning to record owner expectations and performance requirements, is related but is not the same document by default.

Communicate the approved requirements and their rationale to the organization and the design and construction teams. The POR defines the problem before design develops the solution; it records requirements and decisions for agreement, approval, and subsequent use. Communication builds understanding, while formal change control governs revisions. The project manager records proposed changes to scope, site, budget, and schedule, coordinates impact assessments, and routes requests to the designated approval authority. The project manager approves changes only within expressly delegated limits and updates the controlled baseline after authorization.

1.6 Process Improvement

Process improvement is the systematic evaluation and refinement of operational workflows to reduce waste and cycle time, improve quality, and align work with organizational goals. Rather than focusing only on an individual asset or project outcome, it examines the system of work: how decisions are made, how responsibilities pass between departments, and how information moves through the organization.

Applied to corporate real estate and strategic predesign, process improvement strengthens how organizations assess portfolio needs, gather and validate requirements, and translate enterprise strategy into physical-space delivery. It complements change management: change management supports adoption, while process improvement refines the workflows through which the work is carried out.

1.6.1 Application to the Real Estate Function

In corporate real estate, process improvement helps reconcile financial controls, portfolio flexibility, and operational demand by making decision criteria, information needs, and handoffs explicit.

Streamlining Portfolio Governance and Decision-Making: Fragmented decisions—for example, business units leasing space independently without enterprise oversight—can weaken portfolio alignment. Consistent phase gates for expansion, consolidation, and acquisition help connect proposed leases and capital commitments to enterprise goals. Each commitment remains subject to the designated approval and signature authorities.

Improving Space Utilization and Reducing Waste: Occupancy and utilization of data help identify underused space and opportunities to adjust the portfolio. Evaluate these opportunities against peak demand, functional requirements, and employee experience rather than assuming that unused space is unnecessary or that reductions will preserve productivity.

Integrating Service Providers and Delivery: Map the handoffs among architects, contractors, facility managers, and owner-side teams. Clear inputs, deliverables, review responsibilities, and acceptance criteria can reduce avoidable delays and changes while supporting approved cost and schedule targets. Coordination does not replace each party’s contractual or professional responsibilities.

1.6.2 Application to Strategic Predesign

In strategic predesign, process improvement makes planning, real estate evaluation, and programming and requirements gathering repeatable without treating every project as identical. Use a consistent method, adapted to the project’s purpose, complexity, and constraints.

1. Standardizing the Transition from Strategy to Space: When projects use inconsistent methods to gather and validate requirements, user needs may be misunderstood and scope may expand without adequate review. A common process supports consistency while retaining project-specific inquiry.

Use structured visioning templates, stakeholder interview frameworks, and clear decision gates to translate organizational strategy into functional and spatial criteria. Standardize the method and required evidence, not the answers: requirements still need to reflect each project’s users and operating conditions.

2. Improving Information Flow and Reducing Escalation Bottlenecks: As uncertainty grows, issues that routine procedures do not cover can exceed the capacity of reporting lines alone.

Cross-functional user groups and integrated project teams bring relevant information together so operational constraints can be investigated and resolved promptly. Teams act within delegated limits and route decisions beyond those limits through the approved escalation process. Lateral coordination supplements governance; it does not bypass it.

3. Building Structured Feedback Loops: As discussed under Change Management, silence or apparent agreement may conceal unresolved concerns. The Abilene paradox is one form of mistaken agreement, not a universal explanation for stakeholder disagreement.

Build repeated cycles of proposal, feedback, and revision into requirements reviews. Test spatial assumptions with stakeholders, document concerns, and provide anonymous input channels where appropriate. These practices support candid participation and help identify operational needs before design; they do not guarantee psychological safety, agreement, or complete requirements.

4. Learning from Experience and Retaining Improvements: Make review and learn part of the process, rather than leaving them to informal recollection.

Review how previous facilities and workflows performed under operating demands, identify the causes of observed problems, and test proposed improvements before wider adoption. Use the findings to refine enterprise standards and future project requirements. Record project-specific requirements in the Program of Requirements (POR); maintain related commissioning requirements in the OPR where applicable. Approved baselines change only through authorized change control.

1.6.3 Developing the Internal Delivery Team

When an enterprise delivers a major project while establishing and onboarding its delivery team, it must manage two concurrent demands: project delivery and the development of working relationships, procedures, and organizational knowledge. The following framework coordinates these demands. It spans planning through operational transition and complements, rather than replaces, the three predesign phases and their approval gates. Onboarding and capability development continues across stages as project work progresses, culminating in documenting a repeatable  process using playbooks.

Prepared by Steven Parsahall, with the use of AI agents. © Copyright of the Strategic Predesign Association

Stage 1: Strategy, Portfolio, and Team Chartering: Define enterprise intent and delivery responsibilities while planning for team onboarding and the establishment of working procedures. Plan for the time and coordination needed to establish roles, information channels, and shared procedures. Phase-gate reviews should consider both project readiness and the availability of resources to carry out the authorized work.

Provide appropriate capacity allowances, such as planned onboarding time, schedule contingency, or specialized external advisers. Managers should base these allowances on identified delivery risks and obtain the required budget and schedule approvals.

Explain to stakeholders how onboarding and process development will be coordinated with delivery. Set realistic expectations for reviewing cycles, communication, and decision turnaround times.

Stage 2: Predesign, Requirements, and Integrated Onboarding: Use requirements development to clarify the asset’s needs while introducing incoming participants to enterprise goals, operating practices, and project procedures.

Include incoming managers and employees in relevant visioning workshops and spatial simulations. Explain the operating context and decision rationale as requirements are developed, so participation also supports onboarding.

Make expectations for questions and constructive disagreement explicit. Use structured review cycles and anonymous feedback where appropriate to help surface concerns and operational risks without if apparent agreement represents informed support.

Maintain agreed requirements and approved standards in the controlled POR and supporting records. Identify current versions, approval status, and decision rationale so incoming participants can distinguish the authorized baseline from proposals still under review.

Stage 3: Co-Development — Project Delivery and Capability Building: Deliver authorized milestones while developing cross-functional coordination and providing mentoring within the workflow.

Use clear procedures and performance targets for budget, milestones, and functional and spatial quality. Allow discretion within expressly delegated limits, while retaining mandatory controls, contractual duties, and approved requirements. Process simplification must not become a reason to bypass required reviews.

Pair incoming internal managers with experienced consultants or designated senior leads in cross-functional project teams. Use shared work and documented decision reviews to transfer practical knowledge and clarify interfaces between disciplines.

When design or construction issues exceed delegated limits or require specialist determinations, escalate them through the approved route. Designated leaders and specialists can support resolution and explain the reasoning while preserving required approvals and professional responsibilities.

Stage 4: Operational Transition and Learning: Hand over the asset and retain the process knowledge developed during delivery and onboarding.

Support occupant transition and establish clear ongoing responsibilities for facility operations and delivery closeout. Transfer controlled records and agreed routines to the functions responsible for maintaining them.

Review both the asset’s performance under operating demands and the delivery processes, focusing on onboarding arrangements, communication channels, and handoffs. Identify process gaps and their causes rather than assessing individual employees.

Use the findings to refine enterprise standards, onboarding materials, and delivery procedures. Test and authorize changes before adopting them more broadly so future projects can benefit from both improved asset requirements and better-documented ways of working.

A mentoring and cross-functional coordination mechanism can connect onboarding with active delivery. Bring relevant disciplines together to investigate routine issues close to their source, document the reasoning, and escalate decisions that exceed delegated authority. The following cross-functional delivery team arrangement is one proposed way to organize this work.

Stage 5: Documented Playbooks: Institutionalize organizational learning, standardize successful workflows, and transition the newly built delivery team from ad-hoc execution to repeatable enterprise operations.

Codify tribal knowledge. Translate the practical insights, problem-solving methods, and "double-interacts" developed during project execution and team onboarding into standardized, written playbooks.

Integrate the lessons learned from managing task uncertainty and hierarchical exceptions (drawing from Jay Galbraith's Information Processing Model) into updated standard operating procedures. Ensure that future teams do not have to reinvent lateral coordination mechanisms or mentoring pods from scratch.

Use the completed playbooks as structured training modules for incoming staff and future project managers, dramatically compressing their learning curve and scaling the organization's information-processing capacity for subsequent initiatives.

1.6.4 Cross-Functional Delivery Team

In conclusion, a cross-functional delivery team brings together incoming internal managers or employees and experienced external advisers or designated senior leaders to carry out assigned project work. Team members coordinate across disciplines and develop practical knowledge through mentoring during delivery. The team works within its documented mandate and does not create separate approval authority.

1. Structuring the Teams: Include the roles needed for the assigned work, for example, an internal project manager, an architectural or programming specialist, and an experienced mentor. Define each participant’s responsibilities and the team’s interfaces with the wider project team.

Give the team discretion to resolve routine issues only within its documented mandate and approved schedule, requirements, and budget limits. Meeting a target does not itself confer authority to change scope, commit funds, or waive a requirement. Route those decisions to the designated authority.

2. Embedding Mentoring in the Workflow: Combine practical participation with guidance as issues arise. For a design conflict or site constraint, the mentor helps participants define the issue, test assumptions with stakeholders, and compare options. Proposed requirements change remain subject to specialist review and formal approval.

Use shared digital tools and co-location where appropriate to make current information and decision rationale accessible. Record key outcomes so onboarding does not depend solely on informal conversations.

3. Escalating Issues Beyond Delegated Limits: Escalate proposed scope changes, cost variances, and other issues beyond the team’s mandate through the approved governance route. The steering committee coordinates review where assigned; the designated decision maker retains approval authority.

Use escalations as opportunities to explain options, constraints, and decision rationale with the team lead. Mentoring supports the resolution process but does not delay required decisions or replace formal authorization.

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.

© 2026 Strategic Predesign Association

Domain: pred-int.org

Powered by Wild Apricot Membership Software