Xinator Central
Making complexity usable.
- ROLE
- UX/UI Design · Frontend Development · Information Architecture · Workflow Design
- PRODUCT TYPE
- Enterprise scheduling and operations software
- COMPANY
- Xceleran · Remote (USA) · 2024 – present
- STACK
- ASP.NET Web Forms 4.6/4.8 · C# · SQL Server — modernizing to .NET 10 · React · TypeScript · Tailwind CSS
- TOOLS
- Figma · Adobe XD · shared component system
- NOTE
- Confidential product — selected interface details omitted. All visuals are abstract representations.
AT A GLANCE
+25%
User engagement
Core web app flows redesigned at Xceleran
9
Xceleran projects I work on
Central, CEC, Franchisor, FSM, MSF, TPM, Announcement Creation, Rating & Review, Recruiting Path
3
Core workspaces
Schedule · Operate · Configure
1
Shared component system
Used across the ecosystem’s screens
THE CHALLENGE
Scheduling is not just calendars. It's a web of rules.
Xinator Central sits at the operational core of Xceleran's enterprise ecosystem. It's where scheduling, team coordination, configuration and operational oversight converge — a system that field operations teams and administrators depend on daily.
The challenge wasn't just making it look better. It was making interlocking business rules — availability windows, role assignments, conflict detection, multi-tenant configurations — feel navigable to people who don't have time to read a manual.
The interface had to carry real operational weight without hiding complexity behind false simplicity. Enterprise users know their domain. The interface needs to meet them where they are.
Part of a larger system
Xinator Central is one product within Xceleran's broader ecosystem — a family that includes CEC, FSM, MSF, TPM and the Franchisor products, mostly built on ASP.NET Web Forms 4.6/4.8. Central is the shared scheduling and configuration layer, and one of the products being modernized to a .NET 10 API with a React + TypeScript front end.
Understanding that context — which data flows where, which users touch which system — shaped every information architecture decision. A scheduling surface designed in isolation would have created inconsistency across the ecosystem.
- Calendar view
- Shift assignment
- Conflict detection
FOR · DISPATCHERS & PLANNERS
Today’s state first. Conflicts appear inline on the lane instead of in modals, so the schedule stays scannable.
Crew 04 is double-booked. The conflict is flagged right on the lane — no modal, no hunting.
Information density without overwhelm
Scheduling interfaces carry a lot of data. The problem: how do you show everything an operator needs without making every view feel like a spreadsheet?
Configuration that doesn't require a manual
Business rules — tenants, roles, permissions, availability windows — needed to be configurable by administrators who aren't engineers.
Conflict detection that's visible, not buried
When a scheduling conflict arises, the system knew about it. The interface didn't make that visible in a way operators could act on quickly.
Consistency across a multi-product ecosystem
Users move between Xinator products. Inconsistent patterns mean re-learning. The design language needed to hold across all surfaces.
MY ROLE
Design, architecture, and implementation
UX & UI Design
Designing interface flows, hierarchies, and visual systems for scheduling and configuration views.
Information Architecture
Structuring navigation, data groupings, and progressive disclosure for information-heavy surfaces.
Workflow Design
Mapping operational workflows — from schedule creation through conflict resolution and dispatch — into navigable UI sequences.
Frontend Development
Building in Web Forms today and in React + TypeScript with Tailwind CSS for the modernization, so the designed system holds together in the actual browser.
Component Systems
Building reusable component architecture so the interface scales across the ecosystem without drifting.
API & Data Integration
Connecting UI to backend data — making sure scheduling state, conflicts, and configuration reflect real system state.
The decisions below follow a Problem → Exploration → Decision → Result framework. Each one reflects a real constraint of building scheduling software for enterprise users.
PROBLEM
Scheduling views were overwhelming. Too many data points competing for attention.
EXPLORATION
Tried progressive disclosure layers, a master/detail split, and density controls. None felt natural for operators who need to see the full picture.
DECISION
Adopted a lane-based view with clear hierarchy: the current day's state first, conflicts surfaced as inline indicators, not modals.
RESULT
Operators could scan the schedule at a glance and identify what needed action without navigating away from the primary view.
PROBLEM
Configuration screens required IT involvement for changes that administrators should own.
EXPLORATION
Mapped all configuration actions by frequency and user role. Most pain came from 3–4 high-traffic setup flows buried in nested menus.
DECISION
Redesigned configuration as a focused setup flow with contextual help, separating 'first-time setup' from 'day-to-day adjustment'.
RESULT
Administrators could complete common configuration tasks independently, reducing operational bottlenecks.
PROBLEM
Component patterns varied across screens, creating inconsistency as the product grew.
EXPLORATION
Audited the existing UI, identified repeated patterns (status indicators, data tables, form layouts), and noted where each had diverged.
DECISION
Formalized a component system with documented variants. New screens draw from this system rather than inventing new patterns.
RESULT
Screens stopped drifting apart, and new features shipped faster because the building blocks already existed.
CONFIDENTIAL PRODUCT — SELECTED INTERFACE DETAILS OMITTED
Admins start from a named rule, not a nested settings menu.
ENGINEERING
Design ↔ implementation
Working across design and frontend means the gap between a mockup and the browser is something I actively close — not hand off across.
Web Forms → React · TypeScript
Working in the Web Forms product while building its React + TypeScript successor with strict typing. Complex scheduling state managed predictably.
.NET 10 APIs
Worked with backend engineers on API contracts and performance so scheduling views stay fast with real data volumes.
Component system
Reusable, documented UI components. Design tokens for consistent spacing, color, and typography across the ecosystem.
Data-driven views
Scheduling surfaces fetch real operational state. UI reflects conflicts, availability, and status as they exist in the system.
Responsive behavior
Field operators and office administrators use the system in different contexts. The interface adapts without losing functionality.
Figma → code
Wireframes, high-fidelity mockups, and interactive prototypes in Figma and Adobe XD, implemented by the same person who designed them.
Accessibility
Contrast, focus states, and clearer hierarchy — part of the refinements behind the 25% engagement lift.
OUTCOME
A shared operational surface
Xinator Central became a more coherent scheduling and configuration surface — one that field operations teams could operate under pressure without hunting for what they needed.
The component system created a consistent foundation that reduced design drift as the product continued to grow. Configuration flows became self-service for administrators rather than requiring engineering involvement.
Most importantly: the interface got out of the way of the work.
Complexity needs respect, not simplification for its own sake.
Scheduling is genuinely complex. The instinct to hide complexity is wrong — the goal is to make it navigable, not invisible.
System-level thinking before screen-level design.
Individual screens make sense only in context. Understanding how Xinator Central fit within the wider ecosystem prevented local decisions from creating global problems.
A component system is infrastructure, not overhead.
The investment in formalizing the component system paid back faster than expected. Consistency is compounding.