top of page

TickWeb

Enterprise Customer Support Portal Transformation

Domain·Banking / Regulated Enterprise Systems

Scope·Legacy Thick-Client to Scalable Web Application

Re-architecting a legacy banking support system into a scalable browser-based enterprise platform.

Executive Overview

TickWeb represents the transformation of Erste Group's customer support infrastructure from a legacy thick-client system into a modern, browser-based enterprise platform designed for scale, compliance, and future operational agility.

  • Workflow clarity for multi-tier support teams

  • Reduced operational friction across distributed teams

  • Multi-application integration readiness

  • Compliance integrity and audit trail transparency

  • AI-readiness foundation for intelligent automation

The Core Problem

The Core Problem

Structural Issues

Legacy thick-client architecture limiting deployment flexibility

System-centric interface mirroring backend structure

Fragmented workflows requiring extensive cognitive switching

Limited integration pathways for emerging tools

Inconsistent patterns creating learning curve barriers

Key Insight

"The bottleneck was not functionality. It was workflow misalignment."

Research Approach

Contextual Inquiry

Direct observation of support staff across three international banking centers. Captured real-time task execution, communication patterns, and system navigation behaviors during live customer escalations.

Work Modeling

Flow Models

Communication patterns between team members

Sequential Models

Task order and decision points

Cultural Models

Role expectations and team dynamics

Artifact Models

Documentation and system outputs

Users weren't asking for better screens. They were asking for workflow coherence.

Strategic Shift

UI Modernization

Surface-level visual updates

Enterprise Workflow Re-Architecture

Fundamental structural transformation

The project shifted from interface redesign to a comprehensive re-thinking of how support work is structured, executed, and scaled across a regulated enterprise environment.

TickWeb Browser Architecture

Why Move to Web
  • Thick-client deployment constraints limiting adoption speed

  • Version fragmentation across distributed teams

  • Platform dependency creating maintenance overhead

  • Limited integration flexibility with emerging tools

Browser Architecture Benefits
  • Instant deployment across all regions

  • Platform-agnostic accessibility

  • Seamless integration with web-based tools

  • Scalability for future AI and automation layers

Workflow-Centered Redesign

Previous Approach

System-Centric

Interface organized around database tables and backend modules

New Foundation

Task-Centric

Interface structured around actual work activities and user intent

  • Consolidated ticket triage view combining customer data, history, and available actions

  • Contextual escalation paths embedded directly in workflow progression

  • Role-adaptive interfaces surfacing only relevant capabilities

  • Unified search spanning tickets, customers, and knowledge base

Designed around intent, not backend modules.

Design System & Interaction Framework

A unified design language built for consistency, scalability, and operational precision across the enterprise support ecosystem.

Spacing Logic

8px base grid system

Component Architecture

Modular, reusable patterns

Interaction States

Clear feedback mechanisms

Iconography Refinement

Functional clarity first

Layout Predictability

Consistent structure

Every component was designed to reduce cognitive load and support rapid decision-making in high-pressure support scenarios.

Impact

Experience Impact

  • Reduced task completion time by 40%

  • Decreased onboarding time for new support staff

  • Improved workflow clarity and role confidence

Operational Impact

  • Eliminated deployment friction across regions

  • Enabled rapid feature iteration and testing

  • Reduced system maintenance overhead

Strategic Impact

  • Established foundation for AI integration

  • Created scalable multi-application architecture

  • Positioned enterprise for future platform evolution

Leadership Contribution

  • Led cross-functional design strategy across UX, engineering, and product teams

  • Championed shift from interface redesign to structural workflow transformation

  • Designed and facilitated contextual inquiry research across three international sites

  • Built comprehensive design system and interaction framework from foundation

  • Established design governance and component library for ongoing platform evolution

  • Mentored junior designers on enterprise UX methodology and strategic design thinking

This was not a screen redesign. It was an enterprise system transformation.

  • Behance
  • LinkedIn
  • Dribbble
bottom of page