Two surfaces, one record

Deciding and doing are different reading distances

A multi-brand enterprise runs two kinds of work at the same time. Operators close today's loops: the approvals waiting on them, the exceptions at their location, the schedule that needs a decision before noon. Executives read the whole board: which brands are trending, where exceptions concentrate, which pending decisions carry money with them.

Both are looking at the same business. They are not looking at it from the same distance, and a surface built for one distance fails the other. A dashboard of portfolio trends is noise to a location manager at 7 a.m. A queue of location tasks is noise to a regional director reviewing the quarter.

The frontline surface

The operator surface is organized around the next action. It answers, in order: what needs my decision, what is blocked, what changed since I last looked. Context is narrow by design — one brand, one location or department, one queue. Approval gates sit inside the flow of work, because the person who can release a gate is usually the person staring at the exception. The product shape of this surface is documented at operator console.

Speed here is not about animation budgets. It is about not making someone with a line out the door navigate a portfolio hierarchy to find the one record they are allowed — and expected — to act on.

The executive surface

The executive surface is organized around comparison and trend. Exceptions matter in aggregate: which locations accumulate them, which workflows stall at the same gate, where the pattern is structural rather than incidental. Pending approvals appear with their financial context attached, because a gate decision made without the number behind it is a coin flip with a signature.

What the executive surface should never become is a shadow operational queue. The moment executives act on individual location records directly, two things break: the frontline loses ownership of its exceptions, and the audit trail starts recording decisions made at the wrong distance.

Why one record and not two systems

The traditional way to serve an executive is a second system: exports into a reporting database, a BI layer on top, a reconciliation meeting when the numbers disagree. We have written separately about what the copy-and-reconcile pattern costs. The short version: every copy is locally plausible and globally unverifiable, and the meeting becomes about whose number is right instead of what to do.

Two surfaces over one shared record sidestep the argument. The trend line an executive reads and the queue an operator works are the same underlying facts, carrying the same brand and location context, at different reading distances. When the executive asks "which location is this?", the answer is one step away and it is the live record — not last Tuesday's export.

Boundaries do not relax at altitude

Seniority is not a data boundary. An executive sees across locations and brands only through explicit, reviewed grants — the same per-brand isolation that constrains everyone else, enforced at the database, failing closed. The audit trail does not distinguish between an operator's action and an executive's; both are recorded with actor, context, and approval.

The public previews of these surfaces follow the same rule as everything else on our marketing pages: they are honest previews of the authenticated console, not a second product and not a staged mock. What an executive sees on the public site is a faithful, bounded picture of what the console renders with real grants and real data.

What we will not claim

We will not claim one screen serves everyone, and we will not put a number on time saved that we have not measured in your operation. The claim is structural: two personas, two surfaces, one record — and no reconciliation meeting about which copy is right.