Skip to main content
All work

Handoff command center

Status: NDA-safe reconstruction

Orbit: every handoff in view

A request and approval workspace rebuilt from my DoD correspondence workflows. Ownership, exceptions and the next action stay visible.

Client
NDA-safe rebuild of DoD ServiceNow work
Role
Product designer and front-end developer
Scope
Request, review, approval, exception
Built with
Figma, React, Storybook
Platforms
Desktop workspace and mobile queue
Rebuilt with fictional data; the delivered application stays under NDA.
The problem
Intake, review and approval happened in different places. Nobody could see who owned a request or why it was stuck.
My part
Designed and coded this rebuild: workflow model, interaction and visual design, component states and the React prototype.
Result
A working prototype, not a shipped product. Every request shows its owner, status and next step. Faster handoffs are the intent, and nothing here has been measured.
Why it mattered
A stalled request costs time nobody sees until it is late, and the people accountable for it find out last.
The main decision
A command center that leads with exceptions. Instead of a neutral list where urgent and routine work look the same.
What I took from it
If a handoff can fail, design the recovery before the happy path.
4
workspace views from command center to activity
1
click from an exception to its full record
2
layouts: desktop workspace and mobile queue

Orbit Operations

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

Context lost at handoff

  • Ownership invisible between steps
  • Blocked requests found too late
  • Evidence separated from the decision

The decisions

A command center that leads with exceptions

The first screen counts open, in-review and exception work, so the urgent request is never buried.

Instead of a neutral list where urgent and routine work look the same.

The record travels with the request

Owner, evidence, status and the next action share one panel. Reviewers decide without opening another tool.

Instead of separate tools for evidence, status and approval.

The queue works on a phone

Field reviewers get the same record and actions in a single column, not a shrunken desktop table.

Instead of a shrunken desktop table.

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

  • Workflow model and information architecture
  • Interaction and visual design
  • Component states in Figma and Storybook
  • Working React prototype

Try the working prototype

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

Pick up any request

  • Every request shows its owner, status and next step
  • Exceptions surface first, with a path to recovery
  • The same patterns shipped in the DoD applications

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.