What Changed
A clearer view of a complex AI environment
What we were aiming at was that a clinician could finish a task without stopping to look for a control. Here is how the shipped product differs from what came before it.
What we were aiming at was that a clinician could finish a task without stopping to look for a control. Here is how the shipped product differs from what came before it.
The redesign focused on understanding the builder’s day-to-day workflow through stakeholder discussions, workflow analysis, and a review of the existing product. The research highlighted the need for better visibility into project information, unit statuses, sales data, and recent activity. It also identified opportunities to simplify quotation generation and demand letter handling, improve navigation between core areas, and present dashboard metrics and charts more clearly, helping builders and administrators make informed decisions efficiently.
Review the product structure, requirements, existing screens and relationships between major modules.
Organize navigation, dashboard sections, information hierarchy and module-level interactions.
Build shared interface elements and consistent layouts for use across the application.
Develop visual representations of relationships between platforms, agents, user groups and knowledge sources.
Connect dashboard views and supporting screens with relevant application data and workflows.
Review layouts, interactions, loading states and visual consistency to support a usable product experience.
