Revapost

Context

Postal and logistics operations run on intricate workflows — routing, compliance, exceptions, handoffs between systems that were never designed to talk to each other. Operators develop tacit knowledge to keep things moving. That knowledge rarely survives turnover or scale.

Challenge

How do you make a complex operational system understandable without oversimplifying it? The goal wasn’t a dashboard. It was clarity: helping people see where things are, what’s blocked, and why.

Approach

We started by mapping the actual workflow — not the org chart version, the version operators described at 11pm when something was stuck. That map became the backbone for a system that surfaced state, exceptions, and dependencies in plain language.

The technical work followed the human work. Interfaces were designed around questions operators already asked, not around data models that happened to exist.

Outcome

A platform that reduced time-to-diagnosis for operational issues and made onboarding new team members meaningfully faster. More importantly, it gave operators a shared picture of the system they were running.

Lessons learned

• Start with the workflow, not the schema. Data models that don’t reflect how work actually happens become liabilities.
• Legibility is a feature. In operational systems, understanding is throughput.
• Respect tacit knowledge. The people closest to the work often have the best model — your job is to make it visible.