Product Design for Complex Workflows
Mockup-first design for queues, dashboards, routing, scheduling, and clinical or operational workflows. Clickable prototypes iterated with the people who do the work, then handed to engineering with implementation briefs, or built by the same hands.
Operational software fails in the details: who sees what, what happens when nobody answers, how a hot item jumps out of a list of forty. This engagement designs those details in clickable HTML prototypes reviewed with your stakeholders and end users, records every decision and why it was made, and delivers a spec your engineers can build from without guessing.
Problems this solves
- Requirements arrive as a spreadsheet of fields and a meeting transcript, and nobody can picture the screen
- Stakeholders keep changing their minds because they have never seen the workflow end to end
- The current process runs on web forms, email, and a shared spreadsheet, and it is starting to cost real money
- Designers hand over static pictures and engineers rebuild the logic from scratch, twice
- Edge cases such as timeouts, handoffs, and concurrent edits are discovered in production
- Every past mockup was a prettier version of the old screens instead of a rethink of the work
How it runs
- Learn the work first: short sessions with the people who do it, mapped against what the system actually stores
- Prototype in the browser, not in slides: clickable HTML mockups with real states, real data shapes, and your brand
- Iterate with a decision log: every change records who asked and why, so decisions stay made
- Hand off implementation briefs, not pictures: per-feature notes on data, edge cases, accessibility, and reuse, anchored to your codebase
- Build it if you want: the engineer who designed it can ship it, or pair with your team while they do
Frequently Asked Questions
Why HTML prototypes instead of Figma?
Because operational UIs live or die on states: empty, loading, error, timed out, forty rows, one row. A browser prototype shows all of them with your tokens and real interactions, and it becomes the reference the build is checked against. Figma is fine for visual exploration; it is a poor contract.
How long does a design sprint take?
Two to four weeks for a workflow of moderate complexity, including two or three review rounds with stakeholders. Larger products are broken into sprints by workflow.
Do you need access to our end users?
Yes, a few of them for short conversations. Designing a queue or a dashboard without the people who stare at it all day produces something management likes and users work around.
What does the handoff include?
The prototype, a decision log, implementation briefs per feature, and an API or data contract when the backend needs to change. If WyattGo also builds it, the briefs become the plan.
How is this priced?
Design sprints are fixed fee, scoped by workflow. If the build follows, it is quoted as a fixed-fee phase from the briefs, so there is no surprise between design and delivery.
Related Services
UI Modernization for Legacy Applications
Design sprints often reveal that the fix is a new surface inside the existing app.
Turn an interface that looks like it was built fifteen years ago into a modern, fast, accessible product. Delivered in phases inside the app your team already runs, so nothing stops while it improves.
Learn moreHealthcare Workflow Software
Multi-tenant brands, permissions, audit trails, and clinicians who cannot stop to learn.
Design and engineering for the software clinicians and support teams actually use: virtual care, clinical support queues, telehealth meeting interfaces, and multi-tenant platforms serving national health systems. Ten-plus years in the ecosystem.
Learn moreEngagement
Paid discovery / audit
Typical timeline
2-4 weeks per workflow
Starting at
Custom scope
Who this is for
Product owners and clinical or operations leaders who know the work is broken but cannot yet describe the fix, and engineering teams who want a spec they can trust. Not for brand or marketing design.
Related work
- Replaced a forms-and-email intake with a live clinical support queue
A national health system's clinical informatics team handled clinician support requests through web forms and email. They got a real-time queue with routing, coverage, and escalation, and the platform got its first modern design language in the process.
- Designed an in-app telehealth meeting to replace a vendor popup
Clinicians ran video visits in a third-party popup with a camera panel nobody owned. A research and design engagement produced a verified capability map, an in-app meeting design built from the platform's own primitives, and forty implementation briefs anchored to the codebase.
Talk it through
Describe what you're working with and you'll get an honest read on scope, cost, and whether this is the right fit.
Fixed fee per sprint. A sprint ends with a reviewed prototype, a decision log, and implementation briefs, whether or not the build continues with WyattGo.