My design process

How I design

Design is how I make sense of complexity.

This is a living document — evolving with a changing tech environment and design medium.

I work in complex enterprise environments, where users operate under pressure and every decision has operational consequences. My role is about helping teams understand problems, align around outcomes, and make complexity easier to navigate.

My process today
  1. Research
  2. Repository
  3. AI exploration
  4. Validation
  5. Regeneration
  6. Continuous improvement
01
My design practice

A framework I call
My Nuance List.

A personal checklist that grew into a repeatable way of approaching ambiguity. I understand before I solution.

Every project starts with four questions. Before opening any design tool, I want to understand the problem from multiple angles. These questions help uncover context, constraints, and operational reality before solutioning begins.

inputs — orienting questions
  1. Q1.

    Who is affected by this problem?

  2. Q2.

    What is happening operationally today?

  3. Q3.

    What does success look like for the people doing the work?

  4. Q4.

    What constraints are already shaping the solution?

Once I understand the landscape, I begin mapping the system.

Most design challenges are not hidden in the primary flow. They appear in edge cases, conflicting priorities, operational constraints, and moments of uncertainty.

To avoid designing only for the happy path, I document the layers that influence the experience.

Register A Understanding the system
  • Primary use cases
  • Secondary use cases
  • Mental models
  • System constraints
  • Error scenarios
  • Collaboration touchpoints

These are the elements I use to understand how the system behaves as a whole — revealing who the workflow serves, how users think, where constraints exist, and where complexity emerges.

Register B Where quality hides
  • Information hierarchy
  • Recovery paths
  • Interaction patterns
  • Empty states
  • Edge conditions
  • Handoffs
  • Decision moments

This is where the difference between functional and exceptional experiences lives. Users rarely notice these details when they work well — they notice them immediately when they don't. The small nuances that make the difference.

Once I have confidence in the people, operational reality, constraints, and hidden nuances, designing becomes significantly easier.

02
AI-driven design

I bring selective intelligence and accountability,
in the age of AI.

AI as a design collaborator, not a shortcut.

AI sits at the intersection of refining the problem statement and determining the kind of design delivery a project needs.

wiring — one living system
Research
Documentation
Claude
Figma
AI as collaborator
Product
Engineering
Design systems
AI workflows
evolution track
2019 Fundamentals
  • Wireframes
  • User interviews
  • Manual documentation
  • Traditional handoffs
2022 Complex domains
  • Cybersecurity expertise
  • SOAR systems
  • Research maturity
  • Design systems
2026 Repository-first & AI
  • Agentic idea execution
  • Repository-first design
  • Progressive decision records
  • MCP tool integrations
  • Vibe-coding the repo
  • Documentation ecosystems
process — before & after
before
Research Design Handoff
after
Research Repository AI exploration Validation Regeneration Continuous improvement

Structured documentation matters more than prompting. The future of product design is designing systems where humans and AI collaborate.

03
Designing complex systems

Many moving parts.
One coherent experience.

I'm drawn to environments with multiple stakeholders, competing priorities, technical constraints, and high-stakes decisions.

fig.01 — where the work lives
01Enterprise systems
02Operational workflows
03Investigative environments
04Multi-stakeholder
coreOne coherent
experience
parts list — domains designed for
  • D1Cybersecurity operations
  • D2SOAR platforms
  • D3MDR systems
  • D4Investigation workflows
  • D5Rule management
  • D6Enterprise dashboards
operating model — what I study
ThinkHow people reason under load
DecideHow they make high-stakes calls
RecoverHow they bounce back from mistakes
CollaborateHow they coordinate under pressure

Subject matter is often the design material.

04
Building design culture

Some of the work I'm proudest of
shipped as alignment.

Influence — not hierarchy, not management. I build frameworks, workshops, and rituals that help teams work together.

Aligned teams

UX Ticketing Framework

C
Requirements arrived vague and inconsistent.
A
Built a shared structure for capturing UX needs.
O
Cleaner handoffs, fewer rework loops.

Design Workshops

C
Teams aligned late, after decisions hardened.
A
Ran workshops to surface assumptions early.
O
Shared understanding before a screen exists.

Accessibility Advocacy

C
Accessibility treated as a final checklist.
A
Wove it into patterns and reviews from day one.
O
Inclusive defaults across the system.

Cross-functional Alignment

C
Product, eng & design spoke different languages.
A
Simplified the conversation around the problem.
O
Decisions made together, not in silos.

Documentation Systems

C
Knowledge lived in people's heads.
A
Turned decisions into reusable documentation.
O
Context that outlasts any one project.

Knowledge Sharing

C
Designers solved the same problems alone.
A
Created rituals for sharing what we learn.
O
Teams that learn faster, together.
05
Current explorations

An active practice,
not a finished portfolio.

Learning is a permanent part of the job. Right now I'm exploring:

Last updated · May 2026
IDExplorationStatusCurrent focus
E01 Repository-First Design Active Structured documentation and AI collaboration.
E02 AI + Product Design Active Where human judgment remains essential.
E03 Coding Literacy Ongoing Reading and shaping code, not just specs.
E04 Research Synthesis at Scale Exploring Turning scattered insight into shared knowledge.
E05 Enterprise Design Systems Active Consistency across dense, high-stakes workflows.
E06 Complex Workflow Optimization Ongoing Making messy operational paths feel effortless.
An evolving practice

There is no final version
of a design practice.

Only the next iteration.

The tools will change The technologies will change The interfaces will change

What stays constant is curiosity — the desire to understand how people work, and the challenge of making difficult things easier to navigate.