Dev Mode vs Normal Mode: designing one screen for two audiences

Every screen in Trasys serves two different readers. One is an engineer who wants the raw span payload, the exact SQL that ran, the unrounded numbers. The other is a product manager or support lead who wants to know, in one sentence, whether something is wrong and how bad it is.

Building two separate products for those two audiences is expensive and they drift apart over time. Instead, every screen has a Normal Mode and a Dev Mode toggle. Normal Mode summarizes: 'Checkout latency is elevated, likely tied to a database change deployed 20 minutes ago.' Dev Mode shows the same data as trace waterfalls, raw JSON, and query output.

The rule we settled on: Normal Mode should never require domain knowledge of Trasys internals to understand. Dev Mode should never hide information Normal Mode summarized. If a number appears in Normal Mode, its full precision and source are always one toggle away.

This dual-mode approach has drastically improved cross-functional collaboration. When a support agent escalates a ticket, they can simply share a link to the Normal Mode view. The responding engineer can open the same link, toggle to Dev Mode, and immediately start diagnosing the underlying issue without needing further explanation.

Designing for two distinct user personas within a single interface was challenging, but the payoff in organizational alignment and shared understanding has been immense. It ensures that everyone, regardless of their technical background, is looking at the same ground truth.