Operating Evidence 03 · Execution Visibility

Building Cross-Functional Execution Visibility Without Formal Authority

Three departments tracked in-progress work through incompatible systems. Ownership drift was the default. Front desk staff made commitments from unconfirmed information, and recovery exposure accumulated.

Environment
Hotel Unique · São Paulo
Signal
3 tracking systems → 1 shared state
Mechanism
ALICE implementation + handoff governance
~40%
Duplicate handling reduced

Through shared ownership standards and unified request tracking.

70%
Data integrity improvement

Cross-department request accuracy within 90 days.

3 → 1
Tracking systems

Consolidated into a single shared state across departments.

Post-adoption
Compliance held

Governance rules transferred, not only technology.

Ownership drift is the default in multi-department operations.

Housekeeping, maintenance, and front office each tracked in-progress work through separate channels. The front desk absorbed escalation pressure without the information required to resolve it.

The intervention was not only a tool rollout. It was governance transfer: what gets captured, when ownership changes, what qualifies as handoff-ready, and when SLA progression requires visibility.

Three partial records became one shared state.

Before

  • Housekeeping whiteboard visible only inside the department.
  • Maintenance shift-change memory with no audit trail.
  • Front office desk log inconsistent and incomplete.
  • Guest commitments made from partial visibility.

After

  • One shared request state visible across departments.
  • Owner and handoff readiness criteria defined.
  • SLA progression surfaced unresolved work.
  • Commitments grounded in verified state.

Swipe to see the full operating flow.

Actor
Request
Owner
Start
Handoff
Delay
Update
Closure
Guest
Need is raised
Sees owner
Sees progress
No repeat explanation
Receives delay reason
Gets status
Confirms resolution
Front Office
Captures request
Assigns owner
Monitors
Transfers with criteria
Escalates
Communicates
Closes record
Ops Team
Receives state
Accepts owner
Executes
Updates dependency
Explains blocker
Updates status
Confirms work

Implementation succeeded because governance moved with the tool.

MapIdentify duplicate tracking and ownership drift.
DefineShared state, ownership, and handoff criteria.
Parallel runOperate old and new system during adoption.
TransferRules become department standard.
StabilizeData integrity and compliance hold after rollout.
Product-facing translation

Manual cross-department coordination degrades at scale. The validated product requirement is a shared request state visible to all actors, ownership assignment logic with handoff criteria, SLA-triggered escalation, and a data integrity audit trail that does not rely on individual compliance.