Designing Resilient Device Configuration UX

Printer setup and replacement help tickets were among the highest-volume support issues across Toast hardware products (60% in hardware category). Restaurants could complete the physical installation and still discover that orders were not printing where expected.

The problem was not one broken screen. It was a fragmented path across hardware installation, POS setup, routing, configuration, and support.

The final step of hardware installation was actually setup and configuration on POS. That hand-off created a mental-model mismatch between install and setup, especially when users had to decide between setting up a new printer and replacing an existing one.

Different restaurant states introduced additional edge cases: missing prep stations, changes to existing prep stations, multi-location management, and backup-printer logic.

I started the design by leading the positioning and creation of the installation guide, replacing verbose, error-prone instructions with step-by-step visual guidance.

The experience connects hardware installation directly to POS setup or replacement, so users understand what is complete, what still needs attention, and where to act next.

When a primary printer goes offline, a configured backup printer can take over automatically. I led the experience logic for explaining the offline state, identifying its cause, and guiding recovery without interrupting restaurant operations.

Alerts were moved closer to the affected printer information, creating a clearer relationship between the warning, its source, and the next action.

While designing the information hierarchy on the Printer Details page, I also realized the troubleshooting experience does not exist from the system workflow.

Instead of routing users directly to support, the product uses system diagnostics to identify whether an issue comes from the network, the POS connection, or the printer itself.

Selecting Fix Connection then starts a progressive troubleshooting flow tailored to the detected cause.

Users expected to see the information needed to identify a printer and understand its status without extra clicks. Early cards placed too much detail into a small area and did not scale across devices.

I used abbreviations, iconography, grouped information, and restrained status indicators to reduce cognitive load while preserving the detail operators need.