Dynamics Assessment

Interviews reach dozens; the organisation is thousands. The Dynamics Assessment scales the demand question across the full workforce, capturing what each employee reports about their work patterns, activities, locations, preferences and experience — analysable from individual to team to organisational level. It is the systematic record of reported demand. Its power is breadth and comparability; its limit is that it captures what people report, which is why it must be triangulated with observed behaviour, never substituted for it.

• Once in Diagnose as the demand baseline, after interviews have generated hypotheses to test
• When leadership claims about work patterns need testing against workforce-level evidence
• Before Hybrid Balance, Persona Development and Taxonomy Alignment, which all consume its output
• Repeated in Recalibrate to detect demand shift over time

• The full in-scope workforce, or a defensible stratified sample
• Project team configuring scope with the strategist
• Data protection officer confirming privacy configuration before launch
• Community group previewing the instrument for comprehensibility and tone
• Team-level results require the aggregation threshold: no cohort below five employees

• Organisational structure and team mapping from Data Requests (determines analysis units)
• Hypotheses from Leadership and Business Needs Interviews
• Communication protocol from Kick-off — how the assessment is announced determines response quality
• Privacy configuration: aggregation thresholds, consent settings, suppression rules

1. Configure the assessment scope: work patterns, work locations, activity profiles, reported presence, workplace and environmental preferences, workplace experience, commute, culture, collaboration and concentration demand, reported occupancy.
2. Map the instrument to the organisational structure so results aggregate correctly from individual to team to function to organisation.
3. Embed the interview-derived hypotheses as testable items rather than generic questions.
4. Launch with sponsor-led communication explaining purpose, privacy protections and what respondents will get back — reciprocity drives response rates.
5. Monitor response rates by team during fielding; target under-responding populations specifically rather than extending deadlines generically.
6. Analyse at three levels: organisational patterns, team-level variance, and demand-cluster structure across the workforce.
7. Flag every finding that requires triangulation: reported presence versus badge data, reported crowding versus measured occupancy, reported collaboration versus observed space use.
8. Report back to participants in aggregate — the assessment is also a trust transaction.

• Team-level variance hiding under acceptable organisational averages — the average is where demand insight goes to die
• Reported presence exceeding observed presence (typically by 10–20%) — a triangulation flag, not a finding
• Concentration demand consistently outranking collaboration demand while leadership invests in collaboration space
• Response-rate skew: which populations did not answer says as much as the answers
• Preference questions answered as policy negotiation rather than demand description — instrument framing matters

• Reported demand baseline across work patterns, activities, locations, preferences and experience
• Team-level variance analysis with aggregation-threshold compliance
• Demand-cluster structure feeding Persona Development
• Triangulation register: reported findings requiring observational verification

The demand baseline is the primary input to Dynamics Alignment, Hybrid Balance and Persona Development in Define. The triangulation register scopes the Occupancy Assessment and Targeted Insights. Cluster structure feeds Taxonomy Alignment's spatial translation. In Recalibrate, a repeated assessment measures demand drift against this baseline.

The instrument reports; it does not interpret. Judging whether a team's reported concentration demand reflects task structure, poor acoustics, or hybrid-policy anxiety requires reading results against interview evidence and organisational context. Deciding which variances matter for spatial strategy — and which are noise — is analytical judgement the platform deliberately leaves to humans.

• Treating the assessment as the workplace strategy — it is one evidence stream among several
• Reporting organisational averages and skipping team-level variance
• Launching without communication groundwork, then blaming the response rate
• Reading reported presence as actual presence
• Fielding preference questions during an active policy dispute and mistaking negotiation for demand

A 4,000-person energy company's Dynamics Assessment showed 68% organisational satisfaction with concentration conditions — apparently unproblematic. Team-level analysis revealed engineering functions at 31%, masked by high scores in field-based operations that rarely used the office. The engineering variance, triangulated with occupancy data showing their avoidance of open zones, redirected the Kit of Parts toward focus settings — a conclusion the organisational average had made invisible.