All work
EMPLOYEE SELF-SERVICEDesign exploration

Havells · IT Service Desk

Turn “I need help” into a clear next action.

THE THINKING BEHIND THE INTERFACE

Turn “I need help” into a clear next action.

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

  1. Identify the need
  2. Choose an incident or request
  3. Review existing work
  4. Find knowledge or assets
  5. Provide feedback
PROCESS & ARTIFACTS

How the problem becomes an interface.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

View the original screen
Load original Figma frame
WHY IT IS DESIGNED THIS WAY

Every choice has a reason.
And a trade-off.

Use recognizable task labels

Labels such as Log New Incident and My Assets communicate a concrete destination instead of an abstract system feature.

THE TRADE-OFF

Incident and request can still be confusing. Short examples and task-based testing should verify that employees choose the correct route.

Support both scanning and repeat use

The central service cards provide a visual overview while quick navigation offers a direct path for familiar tasks.

THE TRADE-OFF

Repeated destinations can create clutter. Each navigation layer should have a clear purpose, particularly on mobile.

Keep the brand subordinate to the task

Red active states and the Havells identity make location and ownership visible within otherwise neutral service surfaces.

THE TRADE-OFF

Brand red can be confused with an error state. Use text and icons to distinguish active navigation from warnings; assess the banner’s space cost.

BEHIND THE FINISHED SCREENS

Design presentations2 pages

Explore project presentations in Figma, without opening the working design file.

ENTERPRISE EXPERIENCE

Havells · IT Service Desk

A responsive service workspace with its supporting visual foundations.

Read the UX process & rationale
  • Why this page exists
    Purpose
    Give employees a clear route to IT help.
    UX rationale
    Service categories and common-task shortcuts support both first-time discovery and repeat visits.
    Next check
    Test incident-versus-request comprehension and fix compressed card content before implementation.
  • Why this page exists
    Purpose
    Define the shared foundations behind the service desk.
    UX rationale
    Color, typography, spacing, radius, and effects turn isolated styling choices into repeatable rules across screens.
    Next check
    Check contrast, semantic use of red, text scaling, and whether spacing accommodates real content.
Browse all case studies
GOOD THINGS START WITH A CONVERSATIONKerala, India · Working everywhere

Have something
in mind?