JIO WORKSMART

WorkSmart began with a fragmented HR exception process: requests, supporting documents, follow-ups, and decisions moved between corporate and regional teams. My design problem was to keep a request understandable as responsibility changed hands.

As the product designer, my scope covered role-based interfaces, workflow mapping, clarification paths, decision support, and operational completion. I framed the work around three questions: what does this person need to know, what can they decide, and who needs to act next?

I used role and responsibility mapping to organize the experience. The reporter needs to raise and follow up; the validator needs to check evidence; the approver needs to decide; the Action Owner needs to execute. Request viewers and the central team need visibility without the same decision controls.

The design tension was consistency versus relevance. I kept a recognizable request summary across roles, then changed the available actions and overview information according to responsibility. That preserved context without presenting every control to every person.

A straight approval flow was insufficient for requests that arrived with incomplete evidence. The design needed to preserve the work already done while making the missing information someone’s next action.

I treated clarification as a sequence with four connected parts: a question addressed to a person, a visible response task, a reply with evidence, and a return to review. The original question and received response remain together so the reviewer can recover context.

The approval screen contains a system recommendation, but the design still has to support a person making a consequential decision. I placed the recommendation with the request facts rather than making it the sole focus of the page.

The hierarchy keeps the incident summary, requested days, leave status, and supporting detail near the decision. Approval, rejection, and requesting more information remain explicit choices. The separate confirmation gives remarks a deliberate place in the interaction.

Mapping the downstream work exposed a crucial distinction: an approval does not itself make the operational change. If the interface treated approval as the endpoint, it would hide the remaining responsibility.

I gave the Action Owner a separate completion action and a confirmation that explicitly asks whether the required changes have been made. The wording, remarks, and success feedback reinforce a different endpoint from approval.

The request card needed to support quick scanning; the case record needed to explain how the request arrived at its current state. I separated those levels of information rather than asking one screen to do both equally.

The list keeps the request recognizable, while the detail view carries roles, dates, remarks, and clarification events. This is progressive disclosure applied to decision history: enough context to find a case, then enough detail to understand it.

I extended the interaction language to filtering, attachments, and unavailable pages. These states matter because reviewers need to find evidence, reduce a queue, and recover when a destination fails—not only move through an ideal request.

The final design set shows grouped filters with Apply and Clear all, a dedicated attachment dialog, and a recovery action on the error screen. Together they make the supporting interactions explicit enough to carry through implementation.

The identity exploration considered workplace, collaboration, and checklist symbols. The resulting mark combines a person with a checklist, tying the visual identity to the same people-and-responsibility theme as the interaction design.

The exploration board and standalone mark show this part of the design process directly. I present them separately from the interface decisions: an identity can make the product recognizable, while clarity still depends on the workflow and hierarchy.

WorkSmart was implemented and is used internally at Jio. My contribution was the design structure behind that experience: distinct responsibilities, a clarification loop that preserves context, and a completion state beyond approval.

The final screens demonstrate the interaction model; they do not establish a measured reduction in handling time or errors. I would evaluate those outcomes through clarification turnaround, repeated requests for the same evidence, and the time between approval and operational completion.

The lesson I carry forward is to map uncertainty and handoffs as carefully as the main flow. A clear screen matters, but continuity between screens—and between people—is what makes the design coherent.