PRISMaudit

I mapped the auditor's experience across four stages — Awareness, Engagement, Execution, and Review — tracking actions, feelings, pain points, and opportunities at each step. The auditor starts curious but uncertain when a new assignment lands, gets focused as they log in and review details, grows confident while completing tasks on-site, and feels relieved on submission. Surfacing this arc made the friction obvious: unclear scope, confusing navigation, hard-to-track progress, and no closing feedback loop — each one a direct brief for the interface.

PRISMaudit runs on a tailored design system — color tokens tuned to the client's brand, a typographic scale built for dense forms, status colors that read instantly in the field, and component primitives that scale across question types, attachments, and review states. The system gave the development team a clear, consistent foundation and kept the product visually coherent as new question types and workflows were added.

Before designing screens, I traced every path an auditor and a manager could take through the product — from template creation, through assignment, on-site capture, submission, review, and the loop back when an audit was returned. Locking the flow early exposed where status needed to be communicated, where attachments belonged, and where the interface had to stay out of the way.

Grayscale wireframes let me validate layout, hierarchy, and interaction patterns without the distraction of color or polish. Each screen was reviewed against real audit workflows, then iterated until the skeleton held up under field conditions: capturing evidence one-handed, scanning a long checklist, and reviewing a returned audit at a glance.