UI/UX Design · DigitalSpace
DKSH ran multiple digital products: ConnectCustomer, Discover, Labshop, ConnectClient, ConnectPlus, EchoPlus, EasyOrder, and ConnectPatient, each with its own URL and login. DigitalSpace unifies them into a single login, a central hub, and role-based dashboards that show every user what matters most.
Problems
Users faced significant friction across multiple touchpoints, and the root cause was structural.
Multiple URLs and logins created cognitive overload.
Different navigation patterns across each product.
Users didn't know what to do after login.
Goals
Grow usage of digital products and reduce support and manual work.
Log in once, see important information immediately, complete tasks faster.
Research
Methods: stakeholder interviews, user interviews, an online survey, and a competitor review.
Users want to see tasks first, not data.
Dashboards must adapt to who's using them.
Quick actions matter more than reports: sales reps work under time pressure.
Personas & Journeys
I built detailed personas for external clients, customers, and internal sales reps to map their unique goals, pain points, and journeys before and after DigitalSpace.
Goals: Track orders, check balances and invoices, request quotations quickly.
Before: Login → search product → compare → order → track in another system.
After: Login → dashboard → quick reorder → track order.
"I can log in once and know my account status in 10 seconds."
Goals: Reorder products fast, track deliveries, check availability.
Before: Login → check emails → open multiple systems → create order.
After: Login → dashboard shows tasks → quick order → done.
"I can reorder in less than 2 minutes."
Goals: Create orders quickly, check stock, manage accounts.
Before: Receive order reference → search email for URL → login to wrong system → try again.
After: Login → dashboard shows order status → take action.
"I know what to do first when I log in."
Discovery & Research
DigitalSpace exists because people were drowning in logins. Research mapped who actually crosses product boundaries in a day, and how DigitalSpace sits at the centre of everything else.
Represents the power user who moves between EasyOrder, ConnectClient, and expense tools throughout the day.
Just joined and doesn't yet know which of the eight products does what. DigitalSpace is his front door.
Fields the login and access tickets that DigitalSpace is designed to prevent in the first place.
Wants one place to see what her team is working on across products, without chasing five separate reports.
Assumption persona used to frame the onboarding experience before new-hire interviews.
Assumption persona framing the management view before cross-department interviews were arranged.
Used to frame governance requirements ahead of an IT security stakeholder review.
Assumption persona representing short-term staff, pending contractor-access research.
Synthesized from interviews with 14 employees across 4 departments.
Maps the day-to-day users of DigitalSpace against the teams governing access and onboarding.
Shows DigitalSpace as the unified shell connecting every other enterprise product via single sign-on.
Raw research notes clustered into themes during a synthesis workshop, surfacing the patterns behind user pain points.
Dashboard Content Priority Matrix
P0 (must have: used every day), P1 (important: used often), P2 (nice to have). Only P0 content appears above the fold; P1 stays visible but secondary; P2 lives inside modules.
Order status & tracking, account summary, request quotation: clients check delivery status daily and need it for finance decisions.
Quick reorder, order tracking, product catalog: high-frequency, high-anxiety tasks that drive repeat behavior.
Quick order creation, customer list & accounts, tasks/follow-ups: revenue-driving actions used daily.
Journey & Flow
The hardest part of a unifying portal is making it feel invisible. I mapped the login-to-task journey and the information architecture needed to hold every product without adding a layer of friction.
End-to-end emotional curve across the daily login journey, from first touch to task completion, mapped against satisfaction (1–5).
Frontstage actions, backstage operations, and supporting systems mapped against each other to expose handoff gaps.
Primary task flow through the product, including key decision points and drop-off risk areas.
Navigation and content hierarchy used to structure menus, dashboards, and permissions.
UX Strategy
A single global header with search, notifications, and profile.
Quick actions for common tasks; complex features hidden inside modules.
Each product behaves as a module, sharing components across a scalable design system.
Why This Project Matters
This project demonstrates my ability to lead UX from research to UI: designing complex enterprise systems, balancing business goals with user needs, and building scalable, modular platforms that hold up as the product portfolio grows.