About

Data visualization is my home ground: an MS in it from Parsons, a U.S. patent for flight event iconography, and a decade of dashboards and analytics platforms in finance and aerospace. I design for behavioral impact over output, with research and accessibility from the first draft. With AI, I design how much it does alone, what it asks first and what it explains, so trust is earned.

Tools: Figma, Figma Make, Design Systems on variables, React and Next.js, Claude, Coder, VS Code, GitHub.

EmailLinkedIn (opens in a new tab)Resume

Roles by year. Bright pink bars are senior roles, light pink ones earlier roles. Each dot marks a degree or a case study: point at a case study to see it, or select it to open it.

Working with me means

Six habits. Hover or tap a card to turn it.

  • Strategy built on the whole system

    Before screens, I map the whole system: who touches the work, what each step depends on, and what people feel and fear. Strategy built on that map holds when the edge cases arrive. On Groundwork, “AI drafts, a person approves” came from why sellers stop trusting their CRM.

  • People, then data, then opinion

    I start with why people act as they do: what they want, fear and skip. Then the data: logs, interviews, a spreadsheet of complaints. Opinions come last, and when we disagree, we look at the same evidence together.

  • Divergent and convergent, with real users

    My process runs divergent and convergent thinking in a loop: many directions, then one decision, then open again when something new turns up. However much AI is in the work, I still interview people, talk with them and watch them use it live. That is where the surprises are.

  • Accessible from the first draft

    Contrast, focus and screen readers get checked as I go, not in an audit at the end. Every text color on this site passes WCAG AA, in light and in dark. It matters because everyone needs it some day, with tired eyes, a phone in bright sun or a broken wrist, and what helps them makes the product clearer for all.

  • Scrapped often, rebuilt stronger

    I share work while it is still cheap to change, scratch it and go again. I don’t shy away from throwing out a whole direction; the rebuild after it is usually the strongest version. You will hear “I don’t know yet” from me, and then I go and find out.

  • AI drafts, people decide

    AI made me faster and moved where my time goes: early directions, prototypes in hours, the code behind this site. The judgment hasn’t changed. Years of experience have built strong instincts for decisions in the user’s best interest, and for when a person, not a model, should decide.

How I work with AI

AI makes me faster. The decisions stay mine.

The judgment calls

Where intervention mattered

  1. 01

    A chart that told the wrong story

    A radial chart sized by radius made the big airlines look far worse. A square root scale fixed it.

  2. 02

    Real companies in made up data

    AI used real company names and tickers. I replaced every one before anything went public.

  3. 03

    A chat window as the whole product

    Sales reps scan more than they ask, so a chat box became a command bar over the dashboards.

  4. 04

    A market gap too good to be true

    A scan found no competitors. Asked to prove the idea existed, AI found six, and the pitch narrowed to trust.

  5. 05

    A pipeline nobody would see

    A generated layout hid the pipeline below a long list. It now sits beside the list, in view.

  6. 06

    An overlay that hid the result

    A dim overlay hid the cart total the panel exists to change. Without it, the total updates in view.

Packaged for a team

My process as a kit any team can run: a prompt for each stage, a checkpoint where a person decides, and checks on every change.

The kit on GitHub (opens in a new tab)It in use: Groundwork’s decisions (opens in a new tab)

  1. Stage 1

    Research

    I decide which problems are real

  2. Stage 2

    Prove it isn’t built

    I decide where the gap is

  3. Stage 3

    Structure

    I choose the flows to build

  4. Stage 4

    Directions

    I pick one and say why

  5. Stage 5

    Build

    I read every change

  6. Stage 6

    Check

    I decide if it ships