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.

Every procedure’s lifecycle status, from the dashboard
Enter the access password to view the ARES case study.
← Return to Selected WorksI led UX and UI design on ARES end to end, working alongside the product owner, procedure authors and the development team.
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.
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.
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.
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.
Every procedure passes through review before it can be deployed. Status, comments and approvals needed to live with the procedure, not in email threads.
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.
I spoke with authors and reviewers and walked through how a procedure moved from first draft to sign-off using the existing tools.
The value is in their engineering knowledge. Time spent handling markup and tooling was time taken away from the content.
Drafts were passed around for comment, and it wasn’t always clear which version was current or where a procedure sat in the process.
Problems with a procedure’s structure often only surfaced after it had been handed on, adding a round trip back to the author.
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.
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.
Experts write and structure the procedure in the browser, with validation as they go.
Reviewers comment and request changes until the procedure receives final sign-off.
Approved procedures are released for use in assembly, integration and testing.
Released procedures are carried out step by step by the people doing the work, including on the International Space Station.
What happens during execution is recorded and fed back, so the next version of a procedure starts from real use.
Organised by the problem each one solves.
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.

Every procedure’s lifecycle status, from the dashboard
1
2
3
4
Close-up · Procedure lifecycle
Authors work with steps, conditions and verifications as visual blocks, while the platform handles the underlying XML. Why: keeps experts focused on the content.
1234Authoring a procedure in the browser
Structural issues are flagged inline as the author works. Why: catching problems before review removes a round trip.

Issues flagged at the point of authoring
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.

Review panels and review deadlines, scheduled in ARES
A token set and component kit so authoring and review screens share the same patterns, aligned to ESA’s brand palette.
Heading, Space Grotesk
Subheading, Medium
Inter Regular for interface and procedure text, sized for long authoring sessions.
8px base step, 8 / 16 / 24 / 32 / 48
AIT-0417The 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.