Workplace Design
Project-based professional services where design authority, owner approval, and multi-discipline coordination determine delivery.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome Discovery
Align on strategic drivers, occupancy constraints, stakeholders, and measurable success signals for the portfolio change.
Discovery Questions
Why this moment matters
- Tell me briefly what triggered your decision to review office space now.
- When does your next major lease expiration occur?
- Who will need to sign off on any capital spend to change the portfolio?
- How many buildings or sites are in scope for this initiative?
- Describe the one outcome leadership would celebrate as success in the first 12 months.
The single strategic driver that will move the needle
- If you had to pick one strategic driver that would make leadership greenlight a portfolio change immediately, which would it be?
- How is your headcount plan changing over the next 24 months?
- Which organizational KPI will your CFO treat as the single levers for approval (pick one)?
- Who in your organization typically raises the alarm when occupancy forecasts are wrong, and what is their first action?
- List the space types leadership considers non-negotiable today (private offices, dedicated desks, large conference rooms, etc.).
Where occupancy assumptions break and the risk lives
- Identify the single occupancy assumption that, if proven false, would make you stop the project immediately.
- Tell me about the data sources you currently use to estimate occupancy, and which you trust most.
- Count the distinct datasets you have that tie to person-level movement, such as badge records, calendar logs, or desk sensors.
- When was the last time you validated those datasets against employee survey responses or manual headcounts?
- What downstream problems occur when occupancy is overestimated by roughly 20 percent (cost, space mismatch, employee friction)?
The alternatives on the table and why they might hold
- What alternative solution would you choose today if you had to skip external help?
- Select the type of incumbent or partner you have engaged most recently about this problem.
- List the conditions under which you would keep your current approach rather than change (data quality, cost, internal capability, timing).
- Has anyone inside proposed solving this without an outside partner?
- If you stayed with the incumbent, what new evidence or timeline would make you switch to a different partner?
Who matters, who resists, and how decisions will be made
- Name the person on your team who will present the occupancy case to the CFO, and which single metric will they use?
- List the stakeholders who must be involved in pilot acceptance decisions, and indicate who holds final veto.
- Rank or pick the top two criteria you will use to evaluate proposals: cost, utilization confidence, employee adoption, speed to deploy.
- Identify the single operational obstacle that would block approval even if the pilot meets targets.
- Assuming the pilot meets the agreed utilization target, name the one remaining barrier that would prevent signing within seven days.
Pilot design, evidence that convinces finance, and failure modes
- Specify the acceptance metric from a pilot that would convince finance to release funds.
- Describe the pilot boundary you prefer: single floor, neighborhood, entire building, or cross-site.
- Select the data sources you expect to provide for pilot analysis.
- Please indicate the maximum pilot monitoring window that still meets your internal decision deadlines.
- Choose how you would respond if badge data proved unavailable during the pilot.
Operational readiness: systems, access, and gating constraints
- Please list the systems or approvals that would block deployment if not in place by kickoff.
- Do you have existing badge vendor or sensor provider contracts we would need to integrate with?
- Provide the team or role that controls API and integration access inside your organization.
- Rate the cleanliness of your historical occupancy data for analysis.
- Are there any legal, union, or privacy approvals that could stop us from collecting badge or sensor data?
Timeline, budget holder, and the decisive move to rollout
- Assuming pilot targets are met, what would accelerate your signature to within two weeks?
- On what timeline do you need the first neighborhood live?
- Specify the budget holder and approval threshold for the pilot.
- Name the decision or meeting that moves this effort from pilot to full rollout.
- Given the pilot hits targets but adoption lags, indicate whether you would proceed, delay for change management, or cancel.
- Please provide the name and role of the person to schedule the pilot scoping meeting with.
-
Solution Experience
Walk through how utilization analytics, pilot findings, and design options deliver the buyer's productivity, cost, and culture outcomes.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost
- You confirm the current state and accept the described cost and risk as the core urgency for this project.
- Deliver a tailored pilot analysis comparing your current occupancy model to the measured pilot results within five business days.
- You confirm that the pilot findings either validate or invalidate the key occupancy assumptions that drive the capital decision.
- Review pilot findings and what they proved
- Provide badge-data extract and sensor logs for the pilot floors covering the past 12 months within three business days.
- Map analytics to outcomes
- You agree on the specific evidence and acceptance metrics needed to present a defensible case to the CFO and move toward mutual commit.
- Confirm the two pilot floors and the stakeholder list who will approve acceptance criteria within three business days.
- Validate this maps to your needs
- Agree next evidence to reach mutual commit
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define deliverables, responsibilities, pilot boundaries, phased rollout modules, and measurable acceptance criteria.
Scope Configuration
- Install and Calibrate Occupancy Sensor Network
- Integrate Badge Access Feed and Anonymize Data
- Deploy Utilization Analytics Dashboard and Exports
- Deliver Permit-Ready Construction Documents
- Execute Pilot Floor Fit-Out and Furniture Installation
- Furnish Activity-Based Neighborhoods (FF&E Install)
- Install Collaboration AV and Hybrid Meeting Systems
- Update CAD/BIM Models with As-Built Layouts
- Execute Post-Occupancy Monitoring for Pilot Period
- Run Employee Change Workshops and Manager Training
- Deliver Neighborhood Usage Playbooks and Policies
- Coordinate IT Power and Data Cabling Relocation
Scope Questions
Install and Calibrate Occupancy Sensor Network
- Which pilot floors or zones should receive occupancy sensors (refer to your as-built CAD floor names)?
- How many individual workstations and collaboration spaces exist on the selected pilot floor(s) per your latest CAD count?
- Do you require ceiling-mounted passive infrared sensors, desk-edge presence sensors, or a mix to match your utilization granularity needs?
- Who on your facilities or operations team will provide site access and coordinate on-floor staging and power availability for sensor installs?
- Specify the calibration tolerance for occupancy counts compared to badge events (for example +/-5%, +/-10%) that you will accept for pilot analysis.
- Are there any lockout/tagout or site-specific safety procedures (e.g., LOTO, mechanical room access windows) we must follow during sensor installation?
Integrate Badge Access Feed and Anonymize Data
- Provide the badge access log export type your security team can deliver for the pilot (format or transport).
- How many badge readers and controlled entry points cover the pilot floor(s) according to your access control point register?
- Indicate the anonymization approach you require for badge identifiers (for example irreversible pseudonymization, reversible token with key management).
- Who will be the named contact to provide the initial badge data sample and to approve mapping of reader IDs to CAD zones?
- State the required retention period for badge-derived occupancy records for pilot analysis and reporting (in months).
- Are there corporate privacy regimes or legal controls we must observe for badge data (for example GDPR, regional privacy policy) that affect anonymization or storage?
Deploy Utilization Analytics Dashboard and Exports
- Which KPIs must appear on the pilot dashboard for your finance and CRE stakeholders (select up to five)?
- Provide the export formats required by your finance team for lease-modelling and CFO review.
- Indicate whether you need role-based dashboard views (for example separate views for real estate, HR, and IT) with controlled access to PII.
- Confirm the minimum update frequency for live utilization metrics during the pilot that your stakeholders expect.
- Who will validate analytics definitions (for example the operational definition of 'occupied desk' or 'neighborhood adoption') before we lock dashboards?
- Identify any internal BI or data warehouse endpoints we must export analytics to for further financial modelling (name the system or describe the integration endpoint).
Deliver Permit-Ready Construction Documents
- Specify the local code references or authority having jurisdiction items that must be called out on the permit set (for example local fire marshal notes, occupancy classification).
- Select the engineering stamps or specialist calculations required with the permit submission.
- Provide the target permit submission package type for landlord review (for example full permit set, plan-only, tenant improvement packet).
- Who on your side signs off on permit-ready drawings and coordinates with landlord or base-building plan sets?
- Indicate site-specific constraints that must appear on drawings such as sprinkler head locations, column grid restrictions, slab penetrations, or tenant riser locations.
- Confirm whether coordination with landlord-provided base building drawings is required and whether you will provide as-built base plans.
Execute Pilot Floor Fit-Out and Furniture Installation
- Indicate the target split of the pilot floor to be converted to activity-based neighborhoods versus retained assigned seating.
- Provide counts for planned installed furniture types according to your move plan: open desks, touchdown stations, focus rooms, and huddle spaces.
- Identify any site rules for deliveries and installation such as elevator reservation windows, loading dock restrictions, or staging area limitations.
- Who on your team approves the physical mockup or sample neighborhood before we proceed with full furniture installation?
- What acceptance criteria will confirm the pilot fit-out is installed to spec (for example layout matches as-built CAD, power and data at each workstation, FF&E defect threshold)?
- Specify your preferred outcome for removed furniture: we handle disposal, you handle disposal, or items are donated/reused.
Furnish Activity-Based Neighborhoods (FF&E Install)
- Provide the required furniture finish palettes and ergonomic standards from your corporate design guide that must be used in the pilot neighborhood.
- Indicate the target mix of touchdown stations versus dedicated desks for the pilot neighborhood.
- State whether acoustic treatments or privacy screens must meet a specified sound transmission class (STC) or other acoustic metric.
- Who on your procurement or facilities team will be the approver for FF&E delivery inspection reports?
- Estimate lead times for any long-lead FF&E items you expect us to order (select the appropriate band).
- Indicate whether fixed landlord-provided millwork or casework exists that the FF&E must integrate with.
Install Collaboration AV and Hybrid Meeting Systems
- Which meeting room types should receive AV equipment during the pilot (for example huddle rooms, medium rooms, large conference suites)?
- Specify the audio performance target for hybrid meetings you expect (for example speech intelligibility target or specified dB SNR).
- Confirm whether calendar integration is required so room presence and booking indicators reflect utilization in the dashboard.
- Who will provide network ports, VLAN and QoS requirements for AV endpoints and coordinate with IT for firewall rules?
- Indicate whether centralized AV management and remote monitoring is required during the pilot window.
Update CAD/BIM Models with As-Built Layouts
- Do you have existing BIM or CAD files to update and in which formats (Revit, DWG, IFC)?
- Select the level of as-built detail you require in the updated model (for example partitions only, MEP penetrations, full FF&E placement).
- Who will provide access and accompany our as-built walkthroughs for markups and verification?
- Indicate whether you require clash detection reports between tenant improvements and base building MEP in the delivered BIM model.
- Provide the coordinate or datum standard to align the BIM model to if your landlord uses a specific base coordinate system.
Execute Post-Occupancy Monitoring for Pilot Period
- Specify the monitoring window length required to validate occupancy assumptions (choose weeks).
- Which data sources should be correlated during monitoring (sensor telemetry, badge events, meeting calendars, employee survey responses)?
- Identify the minimum data completeness rate you require for an analysis to be considered valid (for example percent of time with no sensor outages).
- What acceptance metrics will confirm pilot occupancy assumptions (for example average desk utilization threshold, meeting room actuals vs bookings, neighborhood adoption rate)?
- Who will review and sign off on the pilot monitoring results before we recommend progression to phased rollout?
- Indicate whether you want automated outage alerts for sensor or badge feed interruptions during the monitoring period.
Run Employee Change Workshops and Manager Training
- Provide the desired number of employee workshops and manager training sessions during the pilot.
- Identify which employee segments should be prioritized for sessions (for example leadership, hybrid teams, reception staff, facilities).
- Select the training artifacts you want included: neighborhood usage playbook, etiquette guide, reservation workflow tutorials.
- Who on your HR or change team will be the primary contact to provide attendee lists and schedule approvals?
- Indicate whether training materials must be provided in additional languages or accessible formats for employees.
Deliver Neighborhood Usage Playbooks and Policies
- Which policy areas must the playbook cover (desk booking rules, focus room etiquette, cleaning protocols, security procedures)?
- Indicate whether the playbook must be integrated into your intranet or employee portal for distribution.
- Who must approve neighborhood policies before they are published (for example legal, HR, security)?
-
Pilot Floor Evaluation
Execute a pilot with sensors, badge-data analysis, and employee surveys to validate occupancy assumptions against agreed acceptance metrics.
- decision_readiness
- stakeholders
- current_state
- desired_state
- success_criteria
- gaps
- success_criteria
- decision_readiness
- desired_state
- gaps
- current_state
- stakeholders
- success_criteria
- gaps
- desired_state
- stakeholders
- decision_readiness
- current_state
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Mutual Commit
Finalize commercial and legal terms, confirm the SOW and data-access authorizations, and lock governance and timing.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Commercial Summary and Order Form
- Data Access and Processing Authorization
- Data Processing Agreement (DPA)
- Project Governance and Timing Agreement
- Change Order Agreement
- Implementation Acceptance and Handover Criteria
- Regulatory Compliance Addendum (conditional)
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm owners, site access, IT prerequisites, communication plans, and sequencing before execution begins.
Pre-Deployment Questions
Environment and site access
- Which sites/locations are in scope for this deployment? List each site name exactly as it should appear on the schedule (so we can create site-specific workbooks).
- Is the site's network ready to support occupancy sensors and backend integrations (VLAN/SSID, PoE power, firewall exceptions)? Choose the option that best reflects the current overall state.
- Are physical access approvals, visitor policy exceptions, and an on-site staging/location for equipment secured for each listed site? If not all sites are approved, list which ones and the approval status.
Data and configuration
- Which source categories will be provided for occupancy correlation and reporting? (Select all that apply.)
- For the selected data sources, what is the overall access readiness state (do not paste credentials — we only need approval status and availability date)?
- If you answered Partial/Blocked/TBD above, list which data sources are affected and the earliest date each will be available for integration (this sets our integration milestones).
People and ownership
- Who is the primary buyer-side deployment owner (name and role) responsible for day-to-day decisions and approvals during rollout? This person will receive the deployment plan.
- Provide the named IT lead and facilities/building lead (name + role) who will approve network changes and site access; if different by site, list per site.
- Who will perform on-site installations and take responsibility for hardware acceptance? Choose the single best option and we will ask for the lead contact if needed.
Timing and constraints
- What is the target start date for on-site deployment per site? If you plan a staggered rollout, list start dates per site (these dates drive resource bookings).
- Are there blackout windows, building move days, corporate events, or regulatory constraints that block installation or testing at any site? If yes, list the date ranges and affected sites.
- Has a communications lead and an approved employee announcement schedule been assigned for the pre-deployment and go-live notifications? (We use this to lock communication milestones.)
-
Configuration Details
Lock exact configuration values the delivery team will use — sensor placements, data integrations, network requirements, and handoff checklists.
Configuration Details
Environments & Endpoints
- Enter the production data ingest endpoint URL for sensor and badge data (format: https://... ; default: https://ingest.example.com/api). This value is consumed by the Data Ingest service.
- Select the badge-system integration type the deployment will use (Default: Badge system (cloud API)) — selects the connector variant consumed by the Integration Connector.
Sensors & Physical Placement
- Select the primary sensor type to install on pilot and rollout floors (Default: Ceiling-mounted people-counting sensors). This drives procurement and mounting templates.
- Sensor density target (numeric: sensors per 1000 sqft). Default: 2.0 — used by the Placement Plan to calculate counts per floor.
Data Mappings & Retention
- Enter the canonical badge ID field name used by your badge system (exact column/header name). Default: badge_id. This exact string is used in the Badge Data Mapping.
- Enter retention period for raw sensor and badge data in days (numeric). Default: 365. This value is applied by the Data Pipeline retention policy.
Network, Handoff & Acceptance
- Should sensors use DHCP or Static IP addressing for deployment? (Default: DHCP). This setting is used by Network Provisioning.
- Enter the name and role of the person who will own integration credentials and act as the technical handoff contact (DO NOT paste secrets; e.g., "Alex Gomez, IT Security"). This value is used on the Credential Handoff Checklist.
-
Program Deployment
Execute the phased rollout: neighborhood builds, IT integrations, change-management activities, and occupancy monitoring with named owners and milestones.
-
Implementation Acceptance
Formal client sign-off checklist confirming delivered spaces, utilization targets, and adoption milestones required for final acceptance and billing.
Checklist items
- Submit as-built deliverables
- Close final punchlist
- Validate sensor and badge-data quality
- Obtain utilization acceptance sign-off
- Confirm adoption milestones achieved
- Execute operational handover
- Transfer data access and credentials
- Accept SLAs, warranty, and support terms
- Deliver known-issues register and remediation plan
- Receive written authorization to invoice
-
-
Success
Measure outcomes against success criteria, run adoption and utilization reviews, and track issues and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Outcome Measurement (weeks 4-10)
- Post-Acceptance Realization Review (around day 90)
- Quarterly Realization and Optimization Review
Issues & Enhancements
- Perform and record a sensor and badge-data integrity audit before the next quarterly review.
- Archive or migrate legacy occupancy data and set legacy system to read-only if decommissioning is approved.
- Publish a one-page evidence package that ties the presented metrics back to the Solution Scope targets for the Implementation Acceptance team.
- Restate acceptance deliverables and current status
- Confirm meeting room utilization rate and employee satisfaction progress relative to Solution Scope targets and note any persistent gaps.
- Close or schedule all remediation items with owners and firm dates.
- Prioritize the enhancement backlog into next-quarter deliverables and operational items.
- Complete outstanding remediation items and update the shared closure log.
- Schedule implementation windows for approved enhancements and publish impact expectations.
- Circulate the updated metric dashboards showing meeting room utilization and employee satisfaction to stakeholders.
- KPI trend review
- Confirm the average daily desk utilization rate and neighborhood adoption rate are within acceptable variance of Solution Scope targets or document required interventions.
- Ensure all persistent blockers have an assigned owner and remediation timeline.
- Approve the quarter's enhancement work and confirm scheduling and expected impact.
- Implement scheduled enhancements and report interim impact on selected metrics.
- Resolve documented persistent blockers and update the issue tracker with closure evidence.
- Re-confirm success criteria and owners
- Confirm the deployment is functioning against the configuration recorded in Solution Scope and handoff checklist.
- Establish an early baseline dataset and list of critical open issues with owners and due dates.
- Agree next data-capture cadence and timing for the First Outcome Measurement meeting.
- Resolve high-priority deployment defects and document fixes in the shared tracker.
- Confirm and publish the owner roster for each success metric recorded in Solution Scope.
- Schedule data export and dashboard access for the First Outcome Measurement meeting.
- Present first measurement data against targets
- Determine whether average daily desk utilization rate and peak occupancy percentage are on track to meet Solution Scope targets, with documented evidence.
- Document a prioritized remediation plan with owners and firm completion dates to close any gaps before Implementation Acceptance.
- Verify the legacy system wind-down plan is complete or on a track with milestones to avoid dual-system use.
- Execute agreed remediation tasks to correct sensor coverage, badge-data mappings, or change-management activities.
- Present outcome data for selected metrics
- Persistent blockers and operational issues
- Deployment and integration validation
- Root-cause diagnosis for any gaps
- Remediation burn-down
- Early adoption signals and usage patterns
- Enhancement backlog review and scheduling
- Incumbent wind-down verification
- Data quality and sensor integrity check
- Enhancement request triage
- Open issues and blockers
- Agree corrective actions, owners, and due dates
- Confirm timeline to Implementation Acceptance
- Agree owners and timeline for remaining items
- Short checklist and next steps
- Agree immediate remediation actions