Protected Case Study

This project is password-protected.

Enter the access password to view the ARES case study.

Incorrect password. Please try again.

← Return to Selected Works
← Selected Works

Enterprise
SaaS

ARESARES

An online AIT platform for authoring, reviewing and deploying spacecraft procedures, replacing a desktop XML workflow.

Year

2025 to 2026

Client

European Space Agency (ESA)

Role

Lead UX/UI Designer

I led UX and UI design on ARES end to end, working alongside the product owner, procedure authors and the development team.

Responsibilities
Discovery and synthesis, information architecture and interaction design, UI and the design system, prototyping and developer handoff. Backend architecture and the procedure schema sat with engineering.
Product
An online AIT platform for the European Space Agency, covering the authoring, review and deployment of spacecraft procedures.
Users
Authors, the engineers and domain experts who write procedures, and reviewers, who check, comment on and sign them off.

Moving procedure authoring out of desktop software and onto the web.

ARES is an AIT (Assembly, Integration and Testing) platform. Subject-matter experts use it to author complex procedures, send them through review until final sign-off, and deploy them for use in spacecraft and satellite builds. Procedures produced in ARES are currently being delivered to the International Space Station. These procedures guide real assembly and test work on flight hardware, so they have to be correct, reviewed and traceable before anyone uses them.

The Challenge

A complex desktop workflow, rebuilt for the browser

Procedures had long been written in desktop XML software. The job was to keep the structure and rigour that workflow enforced, while making it accessible in a browser and connecting authoring directly to review.

Content

Procedures are not documents

A procedure is structured content: nested steps, conditions, verifications and references. The editor had to support that structure without asking authors to think in markup.

Legacy

Leaving xMetaL behind

xMetaL needed local installs and licences, and some familiarity with XML. Work moved between people as files, which made review and version tracking harder than it needed to be.

Process

Review until sign-off

Every procedure passes through review before it can be deployed. Status, comments and approvals needed to live with the procedure, not in email threads.

Fidelity

No loss in translation

The underlying schema and validation rules still applied. The web platform had to respect them, while keeping the XML out of the author’s way.

What that asked of the design

  • An editor that reads as a procedure, not a markup tree.
  • Validation shown while authoring, not at the end.
  • Clear status for every procedure as it moves through review.
  • Familiar enough for experienced xMetaL users to switch over.
Discovery & Insights

Learning how procedures actually get written

I spoke with authors and reviewers and walked through how a procedure moved from first draft to sign-off using the existing tools.

01

Authors are domain experts, not XML specialists.

The value is in their engineering knowledge. Time spent handling markup and tooling was time taken away from the content.

02

Review was disconnected from authoring.

Drafts were passed around for comment, and it wasn’t always clear which version was current or where a procedure sat in the process.

03

Structure errors were found late.

Problems with a procedure’s structure often only surfaced after it had been handed on, adding a round trip back to the author.

Design Strategy

Organise everything around the procedure lifecycle

Every procedure moves through the same three stages. Making those stages the backbone of the product gives authors and reviewers a shared picture of where any procedure stands.

The ARES procedure cycleA cycle of five stages: Authoring, Review, Deployment, Execution and Reporting, returning to Authoring. All five stages are shown.01Authoring02Review03Deployment04Execution05ReportingARESIntegrated end-to-end suite

ARES is an integrated, end-to-end suite that takes a procedure from authoring through review, deployment, execution and reporting. This case study covers the first three stages.

Stage 01

Authoring

Experts write and structure the procedure in the browser, with validation as they go.

Stage 02

Review

Reviewers comment and request changes until the procedure receives final sign-off.

Stage 03

Deployment

Approved procedures are released for use in assembly, integration and testing.

Stage 04

Execution

Released procedures are carried out step by step by the people doing the work, including on the International Space Station.

Stage 05

Reporting

What happens during execution is recorded and fed back, so the next version of a procedure starts from real use.

Key Decisions

Four decisions that shaped the product

Organised by the problem each one solves.

Lifecycle status on every procedure

Each procedure shows where it is in Authoring, Review or Deploy. Why: it answers ‘which version is current, and who has it?’ without leaving the platform.

ARES dashboard: procedure counts by lifecycle stage and a table of procedures, each with its status

Every procedure’s lifecycle status, from the dashboard

Close-up of the ARES procedure lifecycle map, with the current authoring stage highlighted 1 2 3 4

Close-up · Procedure lifecycle

  1. 1The current stage is the only solid element on the map, so ‘where is this procedure?’ is answered at a glance.
  2. 2Stages already passed stay in dark outline, showing the route the procedure has taken.
  3. 3Stages still ahead are faded, so the remaining path is visible without competing with the present.
  4. 4Side routes such as Withdrawn and Dismissed sit off the main path, so exceptions are visible without cluttering it.

A structured editor, not an XML editor

Authors work with steps, conditions and verifications as visual blocks, while the platform handles the underlying XML. Why: keeps experts focused on the content.

  1. 1Authoring elements
  2. 2Code and tag view panel
  3. 3Preview panel
  4. 4Procedure navigator
ARES procedure editor: block toolbar, XML code panel, live preview with caution, note and warning callouts, and a steps outline1234

Authoring a procedure in the browser

Validation while you write

Structural issues are flagged inline as the author works. Why: catching problems before review removes a round trip.

ARES procedure editor flagging one error: a caution placed after the action it applies to, explained in a tooltip and marked in the steps outline

Issues flagged at the point of authoring

Review and sign-off inside the platform

Reviewers comment in context and approve or return a procedure, with a clear record of each decision. Why: keeps the review trail attached to the procedure itself.

ARES panels schedule: a month calendar of panel discussions and procedure review deadlines

Review panels and review deadlines, scheduled in ARES

Design Language

A consistent component library

A token set and component kit so authoring and review screens share the same patterns, aligned to ESA’s brand palette.

Palette
Deep space
Azure
Warning
Approved
Error
Surface
Typography

Heading, Space Grotesk

Subheading, Medium

Inter Regular for interface and procedure text, sized for long authoring sessions.

Spacing

8px base step, 8 / 16 / 24 / 32 / 48

Core Components
Primary button
Secondary button
Text input
Procedure title
Dropdown
Reviewer
Card
In review2 comments open
Data table row
Thermal vacuum testAIT-0417
States
Default
Hover
Disabled
Focus
Principles
ConsistencyOne pattern per job, across every stage.
ClarityRelevance over completeness, always.
ScalabilityNew procedure types reuse existing parts.
Outcome

Procedures authored and reviewed in ARES are now being delivered to the International Space Station.

The challenge in ARES was keeping the rigour of a long-established desktop workflow while removing the friction around it: local installs, raw XML, and review that happened outside the tool.

My approach was to make the procedure lifecycle the backbone of the product and let structure do the work. Authors see steps, conditions and verifications rather than markup, problems surface while they write rather than after handoff, and every review decision stays attached to the procedure. That is what lets expert authors leave desktop software behind without giving up the discipline the old workflow enforced.

Get In Touch

Let’s craft something meaningful together.

Contact Me

© 2026 Design by Fergal Keane

Privacy ↗