Spatial and Cultural Needs

Spatial solutions fail when the need was cultural; cultural programmes fail when the need was spatial. Teams asking for more meeting rooms may need better meeting discipline; teams asking for collaboration culture may need adjacency. This method takes the aligned demand position and separates its components: what requires space, what requires behaviour and norms, and what requires both in sequence. It prevents the two classic misallocations — capital spent on cultural problems and change programmes launched at spatial ones.

• In Define, after Dynamics Alignment, before spatial translation in Taxonomy Alignment
• When demand findings could plausibly be answered by either space or behaviour
• When budget pressure creates temptation to reclassify spatial needs as 'cultural' (free) or ambition creates the reverse
• Before change scoping: this method effectively writes the change programme's demand side

• Workplace project team and strategist
• Change lead as co-owner
• Community group representatives testing classifications against ground truth
• Culture specialist where the culture assessment flagged high-risk dimensions

• Aligned demand position with priorities
• Culture assessment: enacted culture, safety variance, territoriality findings
• Targeted Insights resolutions — many contradictions resolve precisely into this spatial/cultural split
• Sentiment map from Sentiment Alignment

1. Take each structural demand finding and interrogate its mechanism: if we provided the space, would behaviour follow? If we changed the norms, would the need dissolve? Run both thought experiments explicitly.
2. Classify each need: spatial (supply solves it), cultural (norms and behaviour solve it), coupled (space enables, culture activates — the largest and most important category).
3. For coupled needs, define the dependency direction and sequence: does the space precede the norm (focus rooms before quiet-hours norms) or the norm precede the space (sharing behaviour before ratio reduction)?
4. Test classifications against the culture assessment: a spatial answer that assumes psychological safety the culture doesn't have is a coupled need misclassified as spatial.
5. Price the cultural side honestly: change capacity, leadership modelling, time. Cultural answers are not free; they are differently expensive.
6. Produce the paired requirement set: every spatial requirement annotated with its cultural dependencies, every cultural requirement with its spatial enablers.

• Spatial requests that are actually norm failures (meeting-room shortage that is meeting-discipline shortage)
• Cultural ambitions with unacknowledged spatial preconditions ('collaborative culture' across three disconnected floors)
• Budget-driven reclassification in either direction — the classification must follow the mechanism, not the funding
• Coupled needs planned without sequence, so space arrives before the behaviour that makes it work
• Territoriality findings ignored in sharing-related classifications

• Classified needs register: spatial, cultural, coupled
• Dependency and sequencing map for coupled needs
• Cultural requirements brief for the change workstream
• Annotated spatial requirements for Taxonomy Alignment

Annotated spatial requirements flow into Taxonomy Alignment and later the Kit of Parts, each carrying its cultural dependencies. The cultural requirements brief scopes the change programme in Deliver. Sequencing maps inform the implementation roadmap in the Workplace Strategy. In Recalibrate, failed settings are diagnosed against this register: was the space wrong, or was its cultural dependency never delivered?

Mechanism classification is judgement at its purest: the evidence rarely announces whether a need is spatial or cultural, and misclassification in either direction is expensive. Experience across organisations — knowing which spatial answers have historically failed against which cultural conditions — is the discriminating asset.

• Classifying by cost instead of mechanism
• Treating all needs as spatial because the project has a spatial budget and a spatial team
• Treating coupled needs as either/or instead of sequenced both
• Writing cultural requirements nobody owns — every cultural answer needs a named owner and resources
• Skipping the method and letting the Kit of Parts inherit unexamined cultural assumptions

An engineering firm's demand data showed intense cross-team collaboration need. The spatial reflex was a collaboration hub. Mechanism analysis reclassified it as coupled with culture-first sequencing: the culture assessment showed teams didn't collaborate because project incentives penalised it — a hub would have been an expensive empty room. The incentive redesign led; the hub followed a year later, into demand that now existed.