Dynamics Alignment

Diagnosis produces evidence; strategy requires an owned position. Dynamics Alignment is where the organisation moves from 'the data shows' to 'we accept and prioritise'. It walks leadership and the project team through the diagnosed demand structure — sentiment, spatial and cultural needs, schedules, activities, experience priorities, environmental conditions — and forces explicit acceptance, challenge or rejection of each finding. Evidence that is never formally owned gets silently relitigated in every later workshop. This method converts evidence into commitment.

• At the opening of Define, once the Diagnose evidence base is consolidated and Targeted Insights has resolved the material contradictions
• Before Hybrid Balance, Taxonomy Alignment and Persona Development, which all require an owned demand position
• Whenever new evidence arrives late enough to threaten already-aligned positions — re-align explicitly rather than patching silently

• Leadership team as the accepting body
• Workplace project team presenting the evidence structure
• Community group representatives providing interpretation context
• HR/People lead specifically for the employee value proposition implications

• Consolidated Dynamics Assessment output: sentiment, spatial needs, cultural needs, schedule, activities, experience priorities, environmental conditions
• Occupancy triangulation results and resolved Targeted Insights findings
• Culture assessment three-gap analysis
• Strategic tension register from the Visioning Session

1. Structure the demand evidence into decision-sized findings: not dashboards, but discrete statements the leadership team can accept, challenge or reject ('measured focus demand is 45% of activity time and current supply provides for 20%').
2. Walk each demand dimension in sequence — sentiment, spatial needs, cultural needs, schedule, activities, experience priorities, environmental conditions — presenting reported evidence, observed evidence and their reconciliation together.
3. For each finding, record one of three positions: accepted, accepted-with-context (and what the context is), or contested (and what evidence would resolve it).
4. Force prioritisation: which accepted demands are structural (the strategy fails without them) versus desirable (trade-off candidates). Rank; do not list.
5. Surface the employee value proposition implications explicitly: which demand findings, if ignored, carry attraction and retention consequences — with HR owning that assessment.
6. Confront the leadership team with findings that contradict the vision framework, and record how each contradiction is handled: ambition revised, change investment committed, or tension registered for scenario work.
7. Publish the aligned demand position as a signed document — the demand side of every model built from here.

• Selective acceptance: leadership embracing findings that support prior views and contesting the rest — make the pattern visible in the room
• Findings accepted verbally but not prioritised — unranked acceptance is deferred rejection
• The EVP implications being treated as HR decoration rather than demand evidence
• Contested findings without a resolution route — every contest must name the evidence that would settle it
• Alignment fatigue: sessions that accept everything to end the meeting; test with forced-ranking exercises

• Aligned demand position: accepted findings, priorities, contested items with resolution routes
• Structural-versus-desirable demand ranking
• EVP implication register owned by HR
• Updated strategic tension register

The aligned demand position is the authoritative demand input to Hybrid Balance, Taxonomy Alignment and Persona Development. Its priority ranking drives Workshop II's key criteria. Contested items with resolution routes feed Calibration's assumption register. The signed position prevents the single most expensive failure mode in Define: rebuilding the evidence argument in every subsequent session.

The platform consolidates the evidence; it cannot make an organisation own it. Facilitating leadership through genuine acceptance — distinguishing real agreement from meeting-room compliance, deciding when a contested finding warrants further evidence versus a leadership call — is the strategist's craft. Prioritisation itself is a value judgement no dataset resolves.

• Presenting dashboards instead of decision-sized findings, producing discussion without positions
• Allowing acceptance without prioritisation
• Letting contested findings die silently instead of assigning resolution routes
• Skipping the method entirely and treating Diagnose outputs as self-evidently agreed — the root cause of most Develop-phase relitigation
• Excluding HR from the EVP implications, then discovering the retention argument during the business case

A telecoms firm's alignment session processed 34 findings. Twenty-eight were accepted, four accepted-with-context. Two were contested — including measured focus demand, which the sales director attributed to a temporary reorganisation. The resolution route: a targeted re-measurement of the affected teams within six weeks. It confirmed the original finding, and because the resolution route had been agreed in advance, the contested item converted to accepted without a second debate. Total relitigation time in Develop: zero.