Orbiz — Employee app & manager dashboard

Orbiz

Interactive prototype · both surfaces

Every frame is live. Tap through them — the check-in flow, the poll, the toggles and disclosures all work, and each frame keeps its own independent state.

Two rules are enforced in code, not just in copy. The employee app contains no personal score, chart, streak or history of any kind — there is deliberately no screen that could function as a personal dashboard. And any aggregate shown to an employee is suppressed below 5 responses, so a small group can never be reverse-engineered into individuals.

Manager & HR

The other side of the same data

Fully navigable — use the sidebar. The controls in the top-right of the window switch role, plan tier and organisation state, so the permission gates, the Enterprise features and the empty states are all reachable.

The same two rules hold on this side, and they are what make the product defensible. No screen anywhere in the dashboard resolves to an individual — there is no employee list and no per-person drill-down, for managers, HR or admins. Any figure computed from fewer than five people is suppressed rather than rounded, and exports inherit the same rule, so a leadership deck can never carry what the screen refused to show.

The one screen that names people is the wearable fleet table, which is device logistics on a separate permission tier and holds no wellbeing data at all — only device ID, battery, sync and firmware.