Employees usually arrive with a practical need, not knowledge of IT service terminology. The workspace needs to distinguish reporting an incident, requesting something new, checking existing work, and finding self-service help.
DESIGNED FOR
Employees reporting IT issues, requesting services, or checking assigned assets
A UX reading of the supplied artifacts. The sequence below explains the design logic, not a verified chronology of research. Intended benefits and proposed tests are not measured outcomes.
The user's path
Identify the need
Choose an incident or request
Review existing work
Find knowledge or assets
Provide feedback
PROCESS & ARTIFACTS
How the problem becomes an interface.
01
Separate the core service intents
Incidents, requests, assets, and knowledge are visible as distinct destinations. This gives the information architecture a task-based starting point.
02
Offer direct routes to common work
The service console exposes Last 5 Incidents, New Requests, Open Requests, Knowledge Record, My Assets, and Log New Incident. These shortcuts reduce the need to search through deeper navigation.
03
Connect the interface to shared foundations
The accompanying design-system page documents color, Inter typography, spacing, radius, and effects. These rules provide consistency across dashboard and interaction states.
04
Review the working-frame issues
The inspected desktop frame shows compressed card content and a prominent promotional banner. Before shipping, review card heights and whether that banner helps employees complete an IT task.
THE ORIGINAL SCREEN
Havells · havells-desktop
1440 × 900 · Exact source frame, not a recreated mockup.
A downloadable screenshot is not available in this portfolio yet. Open the original frame, or load its Figma preview below. Figma may require sign-in or block embedding.