Case study 02Confidential clientEnterprise integrationGxP

Designing a governance-aligned integration UX.

An enterprise reporting platform needed to retrieve controlled documents as sources and publish generated outputs back as draft versions — under strict compliance constraints. I led the experience strategy that made the integration safe, explainable and recoverable.

Role

Senior Product Designer (UX strategy)

Domain

Enterprise integration · GxP

Surface

Retrieval · Compare · Publish · Audit

TL;DR

Problem
Integration workflows can quietly violate compliance if UX doesn't enforce governance.
My role
Experience strategy and interaction design for retrieval, compare, push and audit.
Result
Safer flows that prevent risky actions and clearly communicate system state.

01 · Context

Two regulated systems, one workflow

The platform needed to work with an enterprise document system in two directions:

Inbound — retrieve the latest controlled documents for reference and comparison.
Outbound — publish generated reports back as draft / minor versions, never as final.

This required designing for traceability, role validation, controlled publishing and failure recovery — without permanently storing controlled documents inside the platform.

02 · Challenge

Integration UX fails when users can't answer the basics

What version did I pull?
What changed between this version and the previous one?
What exactly will be published, and where?
If this fails, what do I do next?

In regulated settings, vague answers translate directly into operational and compliance risk.

03 · Strategy

Three principles for a boring-on-purpose integration

Make state and provenance explicit — versions, timestamps, authorship surfaced inline, not hidden in tooltips.
Force safe steps — comparison before publish, role checks, confirmations on irreversible actions.
Support operational recovery — controlled retries with audit events and meaningful error states.

04 · Key Decisions

Decisions that locked in safe behaviour

Default to latest-version retrieval, but always show full version context (number, date, author).
Require a comparison output before enabling 'push' — no silent overwrites.
Gate publishing through role validation (e.g. author permission) rather than relying on after-the-fact audits.
Designed retry as a controlled, auditable action — no silent auto-retries that obscure cause and effect.
Avoided permanent storage of controlled documents; persisted only allowed metadata and comparison artefacts.

05 · Outcomes

Reduced risk, faster confidence

A clear inbound / outbound integration journey adopted by engineering, QA and the document-system owners.
UI patterns for status, progress, failure and action gating — reusable across future integrations.
Audit-aware event surfaces (retrieval, comparison, publish, retry, failure) that supported faster sign-off.
Lowered compliance and operational risk by structurally preventing unsafe actions in the UI.

06 · Learnings

The strongest integration UX is boring on purpose

Predictability beats cleverness — constrained, explainable flows earn trust from QA and validation.
State and provenance are first-class UX, not metadata footnotes.
Designing for failure paths upfront prevents rework and protects compliance posture.

Next case study