Welspun — Internal Management System
Designed an internal management system for Welspun that turned scattered requests, approvals and team tracking into simple, guided workflows.
Client
Welspun
Industry
Manufacturing & Textiles
Services
UI/UX Design, Enterprise UX, Internal Tool Design, Design System
The Challenge
Processes that worked, spread across tools that did not
Internal requests, approvals and team updates were moving through emails, calls and several disconnected tools. Employees didn’t know where their requests stood, managers had no single view of pending work, and new staff needed training just to find their way around.
How this compounds at scale
In a large manufacturing organisation these problems multiply rather than add. A request raised by email has no status, so the only way to check it is to ask — which generates more email, which makes the next check harder.
Managers end up reconstructing their own pending list from an inbox, which means the list is always slightly wrong. And approvals sit not because anyone refused them, but because nobody could see they were waiting. The process was never broken; the visibility was.
The cost rarely appears as a single number. It shows up as follow-up calls, duplicated requests, decisions delayed for no reason, and new employees spending their first weeks learning which tool and which person each process depends on. None of that is measured, and all of it is paid.
Why enterprise rollouts usually fail
Welspun needed one internal system that people could use without a manual — which for a rollout across departments is a harder requirement than it sounds.
Internal tools are typically adopted under obligation rather than enthusiasm. If using the system is slower or more confusing than the email it replaces, people quietly revert, and the organisation ends up maintaining both. The usability bar is therefore not a nice-to-have; it decides whether the project works at all.
What needed to be solved
One system replacing email threads, calls and scattered tools.
Visible status on every request, so checking does not require asking.
A single view of pending approvals for managers.
Role-appropriate views for employees, managers and admins.
An interface simple enough that new staff need no training.
A consistent design system so the tool could grow department by department without fragmenting.
Clear ownership at every step, so nothing could stall unnoticed.
What We Did
We turned complex processes into simple, guided steps.
Our approach
The design brief was unusual for an enterprise tool: assume the user has had no training and no introduction. Every decision was tested against whether someone could complete the task correctly on their first attempt.
That standard is what protects adoption. A system that needs explaining will be used inconsistently no matter how capable it is.
01 — Workflow mapping
We mapped end-to-end processes with department heads and employees to understand who raises what, who approves it, and where things usually get stuck.
The stuck points were the most useful finding of the whole engagement. Almost none were policy problems — they were visibility problems, where a request was waiting on someone who did not know it was waiting.
That shaped the entire system. Status and ownership became the structural priority rather than features added later, because they were the actual cause of the delays.
Mapping with employees as well as department heads also surfaced the informal workarounds people had built around the gaps. Those workarounds are usually where the real process lives, and ignoring them is how internal tools end up describing a process nobody follows.
02 — Guided request & approval flows
Each process was simplified into clear steps with visible status at every stage, so employees always know what happens next.
Guided flows do more than reduce confusion — they reduce incomplete submissions, which are a common and under-recognised cause of approval delay. A request that arrives complete can be decided immediately instead of bouncing back for more information.
03 — Role-based dashboards
Personal dashboards for employees, team and task views for managers, and reporting views for admins — three roles, each focused on the actions that role needs to take.
For managers specifically, the aim was that pending approvals should never need to be remembered or searched for. If a system has to be checked deliberately, it will be checked inconsistently — so the pending list had to be the first thing a manager sees.
For employees the priority was the opposite: knowing where their own request stands without contacting anyone, which is what removes the follow-up calls entirely.
04 — Enterprise design system
A shared component library and design guidelines kept every module consistent, so the system can grow department by department without feeling like separate tools.
This is what makes a phased enterprise rollout survivable. Each new department added gets the same patterns and the same behaviour, so familiarity carries across modules and training stays unnecessary.
Without that consistency, a phased rollout produces exactly the fragmentation it was meant to fix — a collection of internal tools rather than one system.
Services delivered
UI/UX design
Enterprise UX
Internal tool design
Design system
The Outcome
One place for every request and approval.
Requests are now raised and tracked in a single system with a clear status. Managers see pending work instantly and act on it faster, and the interface is simple enough that new employees become productive with very little training.
The email threads, calls and disconnected tools that previously carried internal process were replaced by one system with visible ownership at every step.
1 system
Replacing emails and scattered tools with a single place for internal process, so the organisation is no longer maintaining several versions of the same workflow.
3 roles
Employee, manager and admin views, each built around that role’s actual tasks rather than a shared screen with permissions layered on top.
1 design system
Consistent components across every module, so the system can expand department by department without fragmenting into separate tools.
Employees
Raise and track requests without follow-up calls.
Managers
See team tasks and pending approvals at a glance, without reconstructing a list from an inbox.
Admins
Reports and visibility across departments.
What this unlocked
A design foundation that lets further departments and processes move onto the same system without a new tool, a new interface or a new round of training.
Replacing emails & scattered tools
Employee, manager & admin views
Consistent across every module
