Hybrid Balance

The Balance diagnosis established when presence creates value; Hybrid Balance decides what the organisation does about it. This is where evidence becomes policy architecture: presence principles, attendance logic, the team-agreement framework, and the honest confrontation of capacity, fairness and leadership consequences. It is deliberately a governance method, not an analytical one — because the hardest hybrid questions (whose value wins when levels conflict, how much variance between teams is tolerable) are decisions, and pretending the data makes them is how hybrid policies lose legitimacy.

• In Define, after Dynamics Alignment has produced an owned demand position and Balance has produced the value structure
• When an existing policy needs evidence-based replacement rather than enforcement escalation
• Before Sharing Ratio and Calibration — presence logic is the assumption they consume
• Revisited in Recalibrate when the Hybrid Work Review shows the logic and the behaviour diverging

• Leadership team as the deciding body
• HR/People as policy owner
• Team leads for the team-agreement framework design
• Works council or employee representation where presence policy is consultation-relevant
• CRE for capacity consequences

• Balance output: three-level value analysis, required-overlap map, conflict register
• Aligned demand position and culture assessment findings on autonomy and trust
• Schedule and Activities rhythm model, including artefact rhythms available for redesign
• Capacity constraints and portfolio context
• Legal and policy constraints per jurisdiction

1. Convert the value evidence into presence principles: statements of when presence is expected because it creates value, not statements of how many days are required. Principles must survive the question 'why?' with an evidence answer.
2. Design the attendance logic architecture: what is organisationally fixed (minimum connection moments, all-team events), what is team-governed (overlap patterns, anchor rhythms), what is individually autonomous. The three-level structure from Balance maps directly onto this.
3. Build the team-agreement framework: the structured format through which teams convert principles into their own overlap commitments — with guardrails, not blank cheques.
4. Confront the conflict register: where team optima undermine organisational connection, leadership decides — explicitly, recorded, with the reasoning. This is the method's governance core.
5. Model capacity implications of the emerging logic against the rhythm model: which presence patterns the building survives, which require rhythm redistribution, which require supply change.
6. Define the leadership implications honestly: what leaders must model, what proximity signalling the logic tolerates, what management-by-visibility habits it retires.
7. Stress-test for fairness: commute asymmetries, role asymmetries (roles with no location choice), and how the logic explains itself to both.
8. Document the presence logic with its evidence chain — every principle traceable to findings.

• Day-count nostalgia: pressure to collapse the logic back into a number because numbers are easy to enforce
• Team agreements without guardrails, producing thirty incompatible micro-policies
• Organisational-connection requirements asserted without evidence — connection value must be demonstrated, not invoked
• Capacity constraints silently writing the policy (the building deciding what the evidence should have)
• Leadership endorsing autonomy in the room while scheduling presence-signalling meetings outside it

• Presence principles with evidence chains
• Three-level attendance logic: fixed, team-governed, autonomous
• Team-agreement framework with guardrails
• Decided conflict register with leadership reasoning
• Capacity implication model and rhythm redistribution plan
• Leadership behaviour brief

The attendance logic and rhythm redistribution feed Sharing Ratio and Calibration as their presence assumptions. The team-agreement framework becomes an activation instrument in Deliver. The leadership behaviour brief enters the change programme. In Recalibrate, the Hybrid Work Review tests observed overlap and connection against these principles — the evidence chain built here is what makes that review decidable rather than rhetorical.

The platform models capacity consequences and maintains the evidence chain; it cannot decide whose value wins. Every entry in the conflict register is a leadership decision about organisational priorities. Judging how much team variance the organisation can govern, and how fast leadership behaviour can realistically change, is human strategic work — automating it would be exactly the overreach this methodology exists to prevent.

• Publishing a day count with the evidence as decoration
• Delegating everything to team agreements and calling the resulting incoherence 'empowerment'
• Ignoring roles without location choice, embedding a fairness fault line
• Designing the logic for the building's capacity rather than testing capacity against the logic
• Treating the presence logic as permanent — it is an assumption set with a review cycle

A financial services firm replaced a contested three-day mandate using the Balance conflict register. Leadership decided two conflicts explicitly: organisational connection justified one fixed monthly all-company day (evidence: cross-team knowledge-exchange scores), and client-service teams retained scheduling autonomy despite low office presence (evidence: their presence value sat with clients). Teams set overlap agreements within guardrails. Twelve months on, the Hybrid Work Review found overlap up, disputes down — and two team agreements failing, which the framework's review cycle corrected without reopening the policy war.