Pronto Xi NTS — Unified Platform Experience
From six disconnected systems to one connected USER experience
NEW TECH STACK (NTS)
Enterprise transformation · Product direction · Journey architecture · Cross-functional leadership · Technical collaboration · Delivery at scale
ONE CONNECTED EXPERIENCE
Employee onboarding was spread across six Pronto Xi systems, creating fragmented journeys, manual handoffs and email-driven approvals. I reframed the problem from a screen redesign to a platform transformation, proposed a new experience layer over the existing ERP, and led the UX through 60+ Agile sprints over 2+ years.
SCOPE
Stakeholder Interviews · Business Requirements · Product Vision Alignment · Digital Transformation Journey · User Pain-Point Analysis · Workflow Analysis · Current/Future-State Mapping · Operational Analysis · Product Audit · Technical Feasibility · Data & Analytics Review · Success Metrics · IA · User Flows · Interaction Design · Prototyping · User Testing · Design System · Engineering · QA
IMPACT
45% reduction in onboarding administration time
60+ Agile sprints · 2+ years
6 connected Employee/HR/ Payroll/ Manager workflows
5 user groups brought into one platform
0 email-based approvals remaining in the redesigned flow
THE BUSINESS PROBLEM
WHEN AN ONBOARDING JOURNEY SPANS SIX SYSTEMS
Offer → Onboarding → Identity → Payroll → Approval → Timesheets
Each system worked in isolation, but the employee journey did not. Information moved between systems, people and emails; HR chased approvals, payroll corrected incomplete data, managers lacked visibility, and employees often started without everything they needed.
"The business logic was sound. The experience was fragmented"
DISCOVER → REFRAME
I mapped the journey before designing the screens
The original request focused on improving employee onboarding within Pronto Xi. I stepped back to understand the experience across the people, systems and processes involved.
What I investigated
​
Stakeholders
HR · Payroll · Managers · Employees · Product · Technology
Business & Operations
Business requirements · Operational analysis · Existing processes · Pain points
Product & System
Product audit · Workflow analysis · Technical constraints · Data and integration dependencies
User Experience
User pain-point analysis · Interviews · Journey mapping · Current-state / future-state mapping · Usability validation
NTS — a new experience layer over the existing Pronto Xi platform
I proposed separating the experience layer from the existing ERP business logic—allowing Pronto Xi to retain its proven data and rules while creating a modern, connected employee experience.
THE PIVOT
I challenged the brief
EXPECTED: Redesign the onboarding screens
DISCOVERY: Six technically functional systems were creating one broken journey.
PROPOSED: Build a new experience layer
A modern employee experience and workflow layer sitting over the existing Pronto Xi ERP.
Why leadership approved the direction
​
Replacing the ERP backend would have required years and significant investment. Redesigning six screens would have preserved the underlying fragmentation. I proposed separating the experience layer from the business-logic layer—preserving Pronto Xi's existing rules and data while redesigning how people interacted with them.
THE PRODUCT ARCHITECTURE
I redesigned the experience without replacing the business logic that powered the ERP.
CORE SYSTEM OF RECORD
Six Connected Workflows. One Unified Platform Experience.
NTS unified the experience layer while Pronto Xi remained the core system of record for master data and existing business logic.
Modern experience on top → trusted ERP foundation underneath.
DESIGN PRINCIPLES
FOUR PRINCIPLES GOVERNED THE PRODUCT
​
Progressive disclosure
Give users the next thing they need—not the entire workflow at once.
​
Single source of truth
One shared status across employee, HR, payroll and managers.
​
Experience separated from business logic
Modernise interaction without rewriting proven ERP rules.
​
Reusable enterprise patterns
Carbon-influenced components and shared patterns created consistency across the platform.
DESIGN ↔ ENGINEERING
UX → Product → Architecture → Data → Service / API → Frontend → Infrastructure → QA
Unified Employee Workspace
A role-based workspace bringing onboarding progress, priority tasks and next actions into one unified experience.
GUIDED ONBOARDING WORKFLOW
A single workflow makes progress, ownership, dependencies and the next action visible—without requiring users to understand the underlying systems.
MANAGER DECISION WORKSPACE
A role-specific approval experience that brings readiness, exceptions and relevant employee context together before the manager makes a decision.
DELIVERY AT PROGRAMME SCALE
60+ SPRINTS · 2+ YEARS · CROSS-FUNCTIONAL DELIVERY
NTS was delivered incrementally. Each sprint produced a validated product increment, with usability findings feeding into subsequent sprint decisions. Technical POCs were used in staging before committing complex work.
RISKS & TRADE-OFFS
THE TRADE-OFFS
​
Replace the ERP or preserve it?
Preserved proven business logic; transformed the experience layer.
​
Six redesigns or one platform?
Chose a shared architecture to eliminate repeated fragmentation.
​
Design everything upfront or validate incrementally?
Used POCs, research and sprint-level validation to reduce delivery risk.
​
Maximum capability or manageable complexity?
Used progressive disclosure and role-based experiences to control cognitive load.
OUTCOME
​​
45% - Reduction in onboarding administration time
​
0 - Email-based approval workflows remaining
​
6 - Previously disconnected workflows unified
​
5 -User groups connected through one platform
​
2+ years - Continuous product development across 60+ sprints
Then separate the outcomes:
​
USER -Guided onboarding, clearer progress, fewer handoffs.
​
OPERATIONAL - Less manual follow-up and fewer incomplete handoffs.
​
BUSINESS -Created a new licensing opportunity for HR and Payroll.
​
STRATEGIC - The experience/business-logic separation became a reusable transformation principle for later Pronto initiatives, including Supply Chain and i18n.
THE DESIGN IMPACT
I didn't redesign six systems.
I changed the architecture of the experience connecting them.
NTS demonstrated that a legacy ERP could retain its proven business logic while evolving into a modern, connected product experience.