DimArn — ideas that work.
← Euroclear portfolio
Euroclear / Retrospective case study

SelfServiceCenter · Files & status.

UI/UX & Applications

How can clients upload information, understand processing status and recover from exceptions without unnecessary support requests?

Based on archived designs: context, design intent, observable work and available evidence.

Sector perspective & sources
Current sector perspective · 15 November 2026

Why this matters today.

Scale & operating context

Global financial-market infrastructure. More than €43 trillion in assets under custody at the end of 2025; this is custody volume, not company valuation or market share.

Publicly documented scale

Today's priorities

At this scale, operational and cyber resilience are central concerns. The National Bank of Belgium also identifies the move towards a shorter settlement cycle as a major industry priority.

Design perspective

For interface design, this suggests a strong focus on readable data, visible status, clear exception handling and dependable workflows. These are present-day design considerations, not a claim that the historic projects addressed a 2026 programme.

Sources & editorial note

Sector facts come from the sources below. Design implications are editorial analysis. This current perspective is not the original project brief and does not establish historical objectives, methods or results.

01 / Context & contribution

The starting point.

SelfServiceCenter combines access, service guidance, file upload, upload history and processing status. The interface addresses clients managing an operational submission.

Design contribution shown
UX/UI interface design
Design consideration
Clear guidance throughout file processing
02 / Design intent

What to make clearer.

Make self-service dependable: show what to do, what has happened and what needs attention, so routine questions do not always require a support exchange.

03 / Method & feedback

Iterate. Listen. Refine.

Agile / ScrumIterative designFeedback loops

Follow the upload lifecycle in successive iterations. Bring normal, waiting and failure states into Agile reviews, then refine guidance from user questions and technical feedback.

A methodological reading, informed by the visible work and professional practice; not a reconstructed log of workshops, tests or sprints.

04 / Observable design

Read the design.

  • Explicit processing states and file-history tables.
  • Task navigation for upload and history.
  • Related service information alongside operational tools.

Explore the archived screens and applications. Select an image for a closer look.

UX 41 · Original portfolio material
UX 42 · Original portfolio material
UX 43 · Original portfolio material
UX 44 · Original portfolio material
UX 45 · Original portfolio material
UX 46 · Original portfolio material
UX 47 · Original portfolio material
UX 48 · Original portfolio material
UX 49 · Original portfolio material
UX 50 · Original portfolio material
UX 57 · Original portfolio material
05 / Results & evidence

Define what success means.

Success criteria

Intended improvements to assess, rather than historical performance claims.

  • More uploads completed independently
  • Fewer helpdesk issues about processing progress
  • Higher satisfaction with status information
Documented evidence

Upload history and dashboard screens make the proposed status hierarchy and relationship between files and actions directly inspectable.

Archived survey results, approval rates and support statistics are not available for this case.

Your next assignment

Let's work
together.

Discuss your project