01
Map the mess
Gather screenshots, storyboards, bugs, requests, business notes, and observed system behavior.
What this page proves
I don’t just design screens. I map the operating model under the screen — rules, roles, states, exceptions, handoffs, data dependencies, and failure points — then turn that complexity into something teams can see, test, and improve.
How I turn workflow chaos into usable systems
The pattern is repeatable: expose the hidden workflow, identify the pressure points, prototype safely, validate with scenarios, and convert the strongest decisions into reusable patterns.
02
Expose the model
Separate roles, statuses, validations, permissions, dependencies, and handoffs.
03
Find pressure points
Look for ambiguity, duplicate effort, unclear states, hidden rules, and high-friction decisions.
04
Build the sandbox
Create a safe prototype space using sanitized scenarios and controlled workflow examples.
05
Test future state
Compare proposed flows against current-state behavior, scenarios, edge cases, and expected outcomes.
06
Translate to build
Turn the strongest decisions into patterns, requirements, acceptance criteria, and dev-ready guidance.
Where I create leverage
This is the lane: senior enterprise UX, workflow architecture, design systems, front-end-aware prototyping, and AI-assisted analysis.
Workflow before wireframes
Design decisions are stronger when the team can see the rules, states, edge cases, and downstream consequences.
Prototype close to implementation
I can move between UX strategy, Figma-level thinking, and front-end prototype logic to reduce translation loss.
Use AI to structure ambiguity
I use AI to summarize inputs, generate scenarios, pressure-test logic, and accelerate analysis while keeping judgment human.
CASE 01
Accounting UX Sandbox / Digital Twin
A controlled prototype environment for selected accounting workflows: current-state mapping, future-state exploration, scenario testing, validation guidance, and AI-assisted workflow analysis before production investment.
Accounting workflows were too complex to evaluate through static notes alone. Business logic, validations, roles, exceptions, and downstream impacts needed a more concrete decision surface.
Build a UX sandbox that made selected workflows visible, clickable, scenario-driven, and safe to discuss without exposing proprietary data.
Inputs
Collected the operational evidence
Business storyboards, feature requests, bugs, QA screens, screenshots, and observed system behavior became the raw material.
Model
Translated workflow into structure
Roles, screens, permissions, validations, scenarios, expected outcomes, and edge cases were turned into a visible model.
Prototype
Created a future-state viewer
The sandbox framed selected workflows as prototype components so the team could compare behavior and discuss change more concretely.
AI Layer
Used AI as a workflow accelerator
AI helped summarize inputs, generate scenarios, pressure-test logic, and convert scattered information into clearer design direction.
Value
Reduced ambiguity before build
The team gained a clearer way to evaluate assumptions, review workflow behavior, and discuss changes before deeper engineering commitment.
NDA boundary: This case study avoids proprietary systems, internal screenshots, customer data, confidential accounting logic, and private workflow details. The focus is process, structure, and transferable UX method.
CASE 02
Package List Workflow App
A list-heavy operational workflow concept focused on visibility, scanability, prioritization, and clearer movement from overview to action.
Operational lists break down when priority, ownership, state, exceptions, and next actions are hard to scan. Users lose time reconstructing context.
Reframe the list around decisions: what is this, why does it matter, what changed, what state is it in, and what should happen next?
Audit the list
Study how users scan, filter, prioritize, and act on records.
Expose state
Make status, exceptions, and ownership easier to read at a glance.
Preserve context
Support movement from overview to detail without losing workflow position.
Clarify action
Reduce ambiguity around what needs attention and what happens next.
NDA boundary: This summary keeps the Package List workflow generalized. It shows process, judgment, and transferable enterprise UX skill without exposing confidential internal operations.