WORK / 01
Role
First UX designer shaping protected workflow maps, wireframes, mockups, and prototypes that cannot be published because the system and operational context were classified.
Problem
Operational teams needed to move sensitive flight information through complex decisions without relying on unclear handoffs, tribal knowledge, or interface assumptions that could not be safely validated in public.
Approach
I converted stakeholder descriptions into structured flows, identified decision points and exceptions, and used prototypes to help product, operations, and engineering agree on what needed to be built.
Outcome
The work improved shared understanding: teams could see what needed attention, what could move forward, where handoffs needed to be explicit, and which details had to remain protected.
Confidential UX leadership
Turned complex operational concepts into usable, buildable product direction.
This page intentionally does not include visuals. For recruiters, the signal is the work behind the artifacts: protected-domain reasoning, stakeholder translation, flow clarity, usability judgment, and development-ready communication.
Became the design bridge between operational stakeholders and the development team.
Converted sensitive workflow requirements into wireframes, mockups, and prototype decisions.
Kept the work grounded in usability, clarity, and buildable scope despite classification limits.
How the protected work is represented
01 Translate constraints
Worked from stakeholder concepts, operational needs, and protected system constraints rather than publishable screenshots.
02 Shape the workflow
Organized complicated actions into clearer steps, decision points, and handoffs that could be reviewed and built.
03 De-risk delivery
Used prototypes and structured conversations to reduce ambiguity before development decisions hardened.
Classified systems judgment
Stakeholder translation
Build-ready UX handoffs