Skip to main content
All work

Shared record · permission layers

Status: NDA-safe reconstruction

Nexus: one shared case

A shared case record rebuilt from my DoD pattern library. Actions change by role; the record never splits.

Client
NDA-safe rebuild of DoD ServiceNow work
Role
Product designer and front-end developer
Scope
Permissions, lifecycle, reusable states
Built with
Figma variables, React, Storybook
Platforms
Desktop and mobile case
Rebuilt with fictional data; the delivered application stays under NDA.
The problem
Reviewers, managers and requesters needed different actions on the same case. Each team invented its own buttons and states.
My part
Designed and coded this rebuild: role and permission model, reusable states in Figma variables, Storybook docs and the React prototype.
Result
A working prototype, not a shipped product. One case model across four roles and seven reusable states, built on the direction DoD leadership adopted.
Why it mattered
When every team invents its own states, the program pays for the same design and QA work again, and silent failures make people doubt the record.
The main decision
Show the role, then show the actions. Instead of restricted actions that fail silently.
What I took from it
A design system earns adoption when the next team can use it without you.
4
roles on one record: reviewer to viewer
4
case views: overview, workspace, documents, activity
7
documented component states

Nexus Case Management

Rebuilt with fictional data; the delivered application stays under NDA.

One record, no rules

  • Permission boundaries were invisible
  • Every app styled states differently
  • Restricted actions failed silently

The decisions

Show the role, then show the actions

A banner states what your role can do, and the actions change with the role you choose.

Instead of restricted actions that fail silently.

One record, one lifecycle

Received, assigned, in review, resolved. Every role sees the same progress bar and the same history.

Instead of a separate version of the case for each role.

States designed once, used everywhere

Seven states are specified with Figma variables and coded in Storybook for engineering and QA.

Instead of each team styling its own states.

Illustrative design evidenceConceptual reconstruction / fictional data
  1. 01

    Foundation

    Semantic tokens, type, spacing, and focus

  2. 02

    Component

    Editable content and explicit states

  3. 03

    Pattern

    Context, permissions, and recovery

  4. 04

    Product

    Workflow and service responsibilities

Inspect Figma, code, and Storybook

How this work fits my practice

This interactive reconstruction makes my approach to enterprise interaction design and front-end implementation inspectable. The shipped program case documents team adoption, user feedback and operational outcomes.

  • Enterprise interaction design
  • Front-end implementation
  • Inspectable behavior
The shipped programModernizing DoD workflows3 apps, 500+ users, 1–2 months to 1–2 weeks

What I owned

  • Reusable components and states
  • Role and permission model
  • Figma variables and variants
  • Storybook documentation and React prototype

Try the working prototype

This is a real, clickable build of Nexus with fictional data. Nothing you do leaves your browser.

Consistency teams reuse

  • One case model across every role
  • Seven states specified once, reused everywhere
  • The basis of the direction DoD leadership adopted as the program standard

From sketch to shipped

The same screen at four stages, redrawn to show the progression. These are not recovered project files.

  1. Sketch

    A rough flow on paper: who does what, and in what order.

  2. Wireframe

    Structure before style. Every state gets a place.

  3. First build

    Real components and real data, rough edges included.

  4. Shipped

    Polished, tested and in people's hands.