10.2 Determining Client & User Needs: Fact Gathering, Interviews & OPR

10.2 Determining Client & User Needs: Fact Gathering, Interviews & OPR

[!NOTE] Pre-Design Client & Stakeholder Analysis: Determining user needs requires navigating complex organizational structures, eliciting unspoken requirements, resolving departmental conflicts, and codifying performance targets. On the ARE 5.0 Programming & Analysis division, candidates are tested on selecting appropriate fact-gathering tools (surveys, interviews, behavioral mapping, charrettes), establishing the Owner's Project Requirements (OPR) in compliance with ASHRAE Guideline 0 and building commissioning standards, aligning the OPR with the Basis of Design (BOD), and applying objective decision-making models to resolve competing stakeholder demands.

A building rarely serves a single monolithic user. An institutional client comprises diverse stakeholder groups with divergent—and often diametrically opposed—priorities. The chief financial officer focuses on capital expenditure and return on investment; the facility maintenance director demands indestructible finishes and generous mechanical clearance; the department head seeks prestige and expansive square footage; and the frontline occupants struggle with thermal discomfort, visual glare, and acoustic distraction. Effective architectural programming requires disciplined stakeholder segmentation and structured engagement.

---

Stakeholder Identification & Governance Tiering

Architects must categorize project stakeholders into distinct operational tiers, deploying tailored engagement tools for each group:

+-------------------------------------------------------------------------------------------------------------------+
|                                 Multi-Tiered Stakeholder Engagement Framework                                     |
+-----------------------+----------------------------------+------------------------------+-------------------------+
| STAKEHOLDER TIER      | PRIMARY FOCUS & STRATEGIC GOALS  | TYPICAL BLIND SPOTS          | PRIMARY ENGAGEMENT TOOL |
+-----------------------+----------------------------------+------------------------------+-------------------------+
| **1. Executive /**    | Capital budget limits, financing | Daily operational friction,  | Visioning charrettes,   |
| **Client Leadership** | schedule, institutional mission, | technical maintenance needs, | executive interviews,   |
|                       | market branding, public prestige | frontline ergonomics         | high-level KPI reviews  |
| --------------------- | -------------------------------- | ---------------------------- | ----------------------- |
| **2. Facility**       | Lifecycle operating costs, MEP   | Initial aesthetic impact,    | Maintenance audits, MEP |
| **Management**        | access, equipment durability,    | organizational mission,      | walkthroughs, equipment |
|                       | custodial logistics, spare parts | spatial brand experience     | cut-sheet reviews       |
| --------------------- | -------------------------------- | ---------------------------- | ----------------------- |
| **3. Department**     | Workflow efficiency, staffing    | Whole-building energy caps,  | Departmental matrix     |
| **Heads / Managers**  | headcounts, inter-departmental   | site-wide budget trade-offs, | workshops, space-use    |
|                       | adjacencies, specialized gear    | long-term building lifecycle | surveys, task mapping   |
| --------------------- | -------------------------------- | ---------------------------- | ----------------------- |
| **4. End Occupants /**| Ergonomics, thermal/acoustic     | Construction cost realities, | Behavioral mapping,     |
| **Frontline Users**   | comfort, natural daylight, task  | municipal code limits,       | anonymous surveys, user |
|                       | storage, personal privacy        | corporate financial returns  | journey focus groups    |
| --------------------- | -------------------------------- | ---------------------------- | ----------------------- |
| **5. Community &**    | Traffic congestion, stormwater   | Internal functional needs,   | Public town halls,      |
| **Public Entities**   | runoffs, building height/scale,  | private operational mandates,| open-house exhibitions, |
|                       | historic neighborhood character  | project economic viability   | municipal hearings      |
+-----------------------+----------------------------------+------------------------------+-------------------------+

---

Fact-Gathering Methodologies: Deep Comparative Analysis

Programmers deploy a spectrum of quantitative and qualitative investigation tools. NCARB frequently presents real-world scenarios requiring candidates to select the most effective, cost-efficient, and methodologically sound investigative technique:

                       FACT-GATHERING METHODOLOGY SPECTRUM

     QUANTITATIVE (Broad / Statistical)             QUALITATIVE (Deep / Contextual)
     ┌───────────────────────────────┐              ┌───────────────────────────────┐
     │    QUESTIONNAIRES & SURVEYS   │              │     INDIVIDUAL INTERVIEWS     │
     │ - Large sample size (100-1000)│              │ - Deep personal insight       │
     │ - Standardized metric data    │              │ - Confidential / sensitive    │
     │ - Low per-user cost           │              │ - Time-intensive & costly     │
     └───────────────┬───────────────┘              └───────────────┬───────────────┘
                     │                                              │
                     ▼                                              ▼
     ┌───────────────────────────────┐              ┌───────────────────────────────┐
     │     BEHAVIORAL MAPPING        │              │         FOCUS GROUPS          │
     │ - Objective empirical reality │              │ - Departmental interaction    │
     │ - Traces actual user movement │              │ - Brainstorming synergy       │
     │ - Identifies desire paths     │              │ - Risk of dominant voices     │
     └───────────────────────────────┘              └───────────────────────────────┘

1. Questionnaires & Surveys

• Application: Gathering standardized, quantitative baseline metrics across large occupant populations (e.g., polling 2,000 university students on study habits or 500 corporate staff on commuting modes).
• Strengths: Broad statistical validity, rapid data aggregation, automated cross-tabulation, low labor cost per participant.
• Limitations: Inflexible questions; cannot capture subtle emotional nuances, unspoken workflows, or body language; vulnerable to self-selection and response bias (occupants with extreme grievances respond disproportionately).

2. Individual Stakeholder Interviews

• Application: Engaging key decision-makers, senior department directors, specialized equipment operators, and confidential stakeholders.
• Strengths: Rich qualitative depth; allows the interviewer to ask probing follow-up questions ("Why is that workflow step necessary?"); provides a safe, confidential environment to discuss political friction, staffing redundancies, or executive concerns that cannot be voiced publicly.
• Limitations: Highly labor- and time-intensive; small sample size; vulnerable to interviewer bias; risks over-weighting the preferences of articulate or assertive individuals.

3. Focus Groups

• Application: Convening 6 to 12 occupants representing a specific operational cross-section (e.g., triage nurses, paralegals, laboratory technicians) to discuss shared challenges and workflow adjacencies.
• Strengths: Interactive dynamic; participants trigger ideas in one another, revealing group consensus and cross-departmental friction points.
• Limitations: High vulnerability to "groupthink"; outspoken or hierarchically superior individuals (e.g., senior managers) often intimidate or silence junior staff; requires an experienced, neutral architectural facilitator to maintain equity.

4. Direct Observation & Behavioral Mapping

• Application: Verifying reported workflows against empirical reality by physically shadowing users, counting occupancy rates, and mapping movement paths.
• Techniques:
  • Time-Motion Studies: Timing how long specific tasks take and measuring physical travel distances.
  • Tracing "Desire Paths": Documenting unpaved footpaths worn across lawns, tape marks on floors, or improvised signage indicating that formal architectural circulation has failed.
  • Informal Adaptations: Photographing cardboard boxes propping open fire doors, post-it notes taped to light switches, or personal space heaters under desks—all of which reveal acute functional, acoustic, or thermal deficiencies.

[!IMPORTANT] The Hawthorne Effect: When occupants know they are being observed, their behavior temporarily alters to conform to perceived management expectations. Experienced programmers counter this by conducting observations unobtrusively, across multiple shifts, and cross-referencing observations with objective data (such as electronic keycard badge swipes and occupancy sensor heatmaps).

5. Participatory Visioning Workshops & Charrettes

• Application: High-energy, collaborative design sessions bringing together diverse stakeholders to establish project goals, build consensus, and resolve conflicts.
• Techniques:
  • Card Sorting: Providing stakeholders with cards representing functional rooms, asking them to categorize spaces into "Essential," "Desirable," and "Discretionary" tiers.
  • Gaming Simulations & Block Allocation: Providing physical scaled wooden blocks or digital tiles representing Net Square Footage, challenging departments to arrange blocks within a fixed building footprint envelope.

---

The Owner's Project Requirements (OPR)

Under ASHRAE Guideline 0-2019 (The Commissioning Process) and NIBS Guideline 3-2012, the Owner's Project Requirements (OPR) is the foundational pre-design document that establishes the functional benchmarks and performance expectations of the facility.

+-----------------------------------------------------------------------------------------------------------------+
|                                 Anatomy of the Owner's Project Requirements (OPR)                               |
+-----------------------+-----------------------------------------------------------------------------------------+
| OPR SECTION           | MANDATORY TECHNICAL BENCHMARKS & PERFORMANCE METRICS                                    |
+-----------------------+-----------------------------------------------------------------------------------------+
| **1. Project Vision** | High-level organizational goals, intended facility lifespan (e.g., 50 vs. 100 years),   |
|                       | corporate brand identity, and community contextual integration.                         |
| **2. Spatial Use &**  | Hours of operation, occupancy schedules, anticipated occupant densities, future        |
| **Occupancy**         | expansion allowances, and programmatic room allocations.                                |
| **3. Indoor Environ.**| Specific quantitative criteria:                                                         |
| **Quality (IEQ)**     | - *Thermal Comfort*: Winter/summer dry-bulb setpoints (e.g., 68°F–74°F ± 2°F), RH 30–60% |
|                       | - *Indoor Air Quality (IAQ)*: Minimum outdoor air CFM/person (ASHRAE 62.1), MERV rating |
|                       | - *Acoustics*: Max ambient Noise Criteria (NC-30 offices, NC-25 auditoriums), STC ratings|
|                       | - *Lighting*: Target foot-candles (IESNA), CRI ≥ 80–90, daylight harvesting limits      |
| **4. Energy &**       | Energy Use Intensity targets (EUI: kBtu/ft²/year), carbon reduction goals,             |
| **Sustainability**    | renewable energy generation percentages, and green building certification (LEED/WELL).  |
| **5. Building Envel.**| Maximum overall U-factors for roofs and walls, fenestration Solar Heat Gain            |
|                       | Coefficients (SHGC), and mandatory air barrier tightness limits (e.g., ≤0.25 CFM/ft²).  |
| **6. Durability &**   | Expected equipment life cycles, custodial maintenance standards, resistance to heavy    |
| **Maintenance**       | cart impact, standardized replacement parts, and centralized BMS integration.           |
| **7. Commissioning &**| Mandatory training hours for facility maintenance staff, seasonal testing protocols,   |
| **Training Scope**    | warranty period operational reviews, and digital O&M manual deliverables.               |
+-----------------------+-----------------------------------------------------------------------------------------+

OPR vs. Basis of Design (BOD): The Critical Distinction

Candidates must never confuse the OPR with the Basis of Design (BOD):

                           OPR vs. BOD PROCEDURAL RELATIONSHIP

     OWNER'S PROJECT REQUIREMENTS (OPR)              BASIS OF DESIGN (BOD)
     - Authored by Owner (assisted by CxA/Arch)     - Authored by Design Team (Arch & Engineers)
     - States WHAT the facility must achieve        - States HOW the design satisfies the OPR
     - Owner's performance benchmarks               - Technical calculations & system selections
     - Developed during PRE-DESIGN / PROGRAMMING    - Developed during SCHEMATIC / DESIGN DEV
               │                                              ▲
               │                                              │
               └───────────── TRANSLATES & VALIDATES ─────────┘

---

User Personas & Spatial Journey Mapping

To translate abstract functional surveys into human-centered spatial experiences, programmers synthesize user data into Personas and Journey Maps.

+-----------------------------------------------------------------------------------------------------------------+
|                             Anatomy of a User Spatial Journey Map (Healthcare Clinic)                           |
+----------------+---------------------+---------------------+----------------------+-----------------------------+
| SPATIAL STAGE  | 1. SITE ARRIVAL     | 2. CHECK-IN         | 3. WAITING / SUB-WAIT| 4. EXAM / CONSULTATION      |
+----------------+---------------------+---------------------+----------------------+-----------------------------+
| **User Touch-**| Drop-off canopy, ADA| Biometric kiosk,    | Acoustic quiet zone, | Ergonomic exam table,       |
| **points**     | ramp, parking garage| reception counter   | daylight vista, seats| doctor desk, family seating |
| **Pain Points**| Long travel distance| Visual confusion,   | Noisy children, glare| Drafty airflow, lack of     |
|                | in rain, ice hazard | lack of privacy     | from south glazing   | acoustic speech privacy     |
| **Programmatic**| Covered vestibule,  | Staggered queue,    | Sound masking system,| STC 50 walls, sound seals,  |
| **Response**   | snowmelt pavement   | ADA height counter  | motorized solar shade| localized thermal controls  |
+----------------+---------------------+---------------------+----------------------+-----------------------------+

Journey mapping tracks an occupant's emotional, cognitive, and physical experience chronologically through space, identifying critical touchpoints where poor spatial organization generates operational friction or distress.

---

Resolving Conflicting Stakeholder Requirements

When stakeholder priorities clash, the architect must deploy structured, objective decision-making models rather than yielding to political pressure or personal aesthetic preferences.

                        THE PROJECT IMPERATIVE HIERARCHY

         ▲  1. STATUTORY & LIFE SAFETY (Non-Negotiable: IBC, NFPA, ADA, OSHA)
        ╱ ╲
       ╱   ╲ 2. CORE INSTITUTIONAL MISSION (Fundamental reason project is funded)
      ╱     ╲
     ╱       ╲ 3. LIFECYCLE & OPERATIONAL VIABILITY (Durability, maintenance, energy)
    ╱         ╲
   ╱           ╲ 4. OCCUPANT CONVENIENCE & WORKFLOW (Adjacencies, ergonomics)
  ╱             ╲
 ╱               ╲ 5. INDIVIDUAL PREFERENCE & STATUS (Personal aesthetic, perks)
 ─────────────────

1. Multi-Criteria Decision Analysis (MCDA)

When choosing between competing design directions or programmatic allocations, the architect establishes a weighted scoring matrix:

$\text{Total Weighted Score} = \sum_{i=1}^{n} (\text{Weight}_i \times \text{Score}_i)$

1. Establish explicit, measurable criteria (e.g., Capital Cost, Energy Efficiency, Acoustic Privacy, Operational Flexibility).
2. Assign a percentage weight to each criterion based on agreed project goals (e.g., Capital Cost = 30%, Acoustic Privacy = 40%, Flexibility = 30%).
3. Score competing options on a standard scale (1 to 5).
4. Calculate the weighted total to reveal the most balanced, objective solution.

2. Root Cause Analysis: Distinguishing Root Needs from Surface Demands

Often, stakeholder conflicts arise because users demand a specific physical solution (a surface want) rather than expressing their underlying functional problem (a root need). By applying the "Five Whys" technique, the architect uncovers the root driver and discovers alternative solutions that satisfy all parties.

• Example: An executive demands a massive private office with solid wood doors (surface demand). Probing reveals the executive frequently conducts confidential termination reviews and experiences acute speech privacy anxiety (root need). By engineering high-STC double-glazed demountable walls with sound masking, the executive achieves absolute speech confidentiality while the facility preserves natural daylight penetration for interior staff.