User jobs
Screens are organized around the decisions and actions each role needs to complete.
Shape dashboards, CRMs, portals, and internal tools around the work people repeat every day, with readable data and dependable product states.
What the engagement covers
The work is organized around outcomes and operating constraints, not a long list of disconnected features.
User roles, core jobs, workflow map, and navigation model
Information hierarchy for dashboards, records, tasks, and reports
Responsive data views, filters, tables, forms, and action patterns
Loading, empty, error, permission, and success states
Reusable React components connected to existing or new APIs
Production verification and maintainable interface documentation
Quality criteria
Screens are organized around the decisions and actions each role needs to complete.
Tables, summaries, filters, and detail views balance fast scanning with necessary depth.
The product remains understandable while data loads, disappears, fails, or requires permission.
Delivery path
Define the user, current friction, business outcome, dependencies, and what the first useful release must include.
Map the structure, key states, responsive behavior, technical approach, and review checkpoints before deep implementation.
Ship working progress, test the production path, document decisions, and leave the next owner with a clear handoff.
Questions
Yes. If the data and APIs already work, I can improve the frontend, navigation, hierarchy, reporting views, and operational states around the current backend.
A good fit is a CRM, portal, admin panel, or internal tool where users need faster decisions, clearer data, and fewer workflow dead ends.
Yes. Key workflows are designed for narrow screens as well as desktop, with tables, actions, and dense data adapted to the actual mobile job.
Bring the current situation