Balance

Most hybrid policies answer 'how many days' without ever asking 'for what'. Balance inverts the question: it assesses when presence produces value — for the individual, the team and the organisation — and when it does not. It examines task types, team interdependency, required overlap, collaboration intensity, knowledge exchange, leadership proximity, commute cost and capacity constraints as one system. The output is not a policy number; it is the evidence structure from which presence logic can be legitimately built in Define.

• In Diagnose, after the Dynamics Assessment establishes reported work patterns
• When an existing hybrid policy produces attendance without overlap, or compliance without conviction
• Before any capacity, sharing-ratio or portfolio modelling — presence assumptions drive all of them
• When leadership presence expectations and workforce reality have visibly diverged

• Full in-scope workforce via the structured assessment
• Team leads validating team-level interdependency findings
• Leadership team reviewing the individual–team–organisation value framework
• HR/People confirming policy constraints; CRE confirming capacity constraints

• Dynamics Assessment output: reported patterns, locations, activities
• Business Needs Interviews: interdependency and collaboration structure per function
• Commute data and location constraints from Data Requests
• Current policy constraints and capacity ceilings
• Assessment dimensions: individual autonomy, team cohesion, organisational connection, interdependency, required overlap, collaboration intensity, knowledge exchange, leadership proximity, task type, location requirements

1. Assess presence value at three levels separately: individual (autonomy, focus conditions, commute economics), team (cohesion, interdependency, required overlap), organisational (connection, knowledge exchange, culture transmission). These levels conflict; measuring them together hides the conflict.
2. Map task-type structure per team: which work benefits from co-presence, which is degraded by it, which is indifferent.
3. Quantify required overlap: not how often people attend, but how often the people who need each other attend simultaneously.
4. Weigh commute cost against presence value — a two-hour commute changes the value equation for the same task profile.
5. Layer capacity and policy constraints onto the value analysis: what the evidence supports versus what the building and policy permit.
6. Surface the conflicts explicitly: teams whose internal optimum undermines organisational connection, individuals whose autonomy optimum breaks team cohesion.
7. Hand the value structure — not a policy recommendation — to Hybrid Balance in Define.

• Attendance without overlap: acceptable presence rates with near-zero simultaneous team presence — the signature failure of day-count policies
• Teams reporting high collaboration value but structuring work asynchronously — reported value versus operational reality
• Presence driven by leadership proximity signalling rather than task value
• Commute-cost asymmetries inside teams that any uniform rule will convert into fairness conflict
• Organisational-connection value invisible at team level — the level most day-count policies never measure

• Three-level presence value analysis (individual, team, organisation)
• Required-overlap map per team and interdependent team cluster
• Task-type presence profile across the organisation
• Conflict register: where the three levels pull against each other
• Capacity and policy constraint overlay

This is the primary evidence input to Hybrid Balance in Define, which converts value analysis into presence principles and team agreements. Required-overlap findings drive Sharing Ratio peak assumptions and Calibration attendance assumptions. The conflict register becomes explicit trade-off material for the leadership team. In Recalibrate, the Hybrid Work Review re-tests these value assumptions against observed behaviour.

The assessment structures the evidence; it cannot decide whose value wins. When individual autonomy, team cohesion and organisational connection conflict — and they will — the resolution is a governed leadership trade-off, not an analytical output. Judging how much organisational-connection value justifies overriding team-level optima is a strategic decision the platform deliberately refuses to automate.

• Extracting a day count from the analysis and calling it done — the output is a value structure, not a number
• Assessing only team-level value and discovering the organisational-connection deficit after implementation
• Ignoring commute asymmetry, then wondering why the fair policy feels unfair
• Treating current attendance behaviour as revealed preference rather than adaptation to current policy
• Running Balance during a live return-to-office conflict and reading negotiation positions as value evidence

A consultancy with a struggling three-day mandate ran Balance across 900 staff. Findings: project teams already exceeded three days when co-located with their engagement teams; the mandate was binding only on internal functions, where task analysis showed presence value concentrated in two specific weekly rhythms. The eventual presence logic dropped the uniform mandate for overlap-based team agreements — attendance fell slightly, simultaneous team presence rose 40%.