

From Kid Who Drew to Designer Who Delivers
As a kid I painted nonstop, took gadgets apart, and read about psychology. That mix of visual discipline, curiosity for how things work, and how minds work never left. Design was the obvious home for it; now it shows up as crisp problem framing, working prototypes, and small shipped slices that move a metric.
Off-Canvas Me
The inputs that shape my taste.




How it feels to work together
Let’s make the room calmer and the product clearer.
In kickoff: I ask the question we’re avoiding. Then I park it on a card so it stops wandering.
In the messy middle: you’ll get two real options, what each costs, and a decision we can live with.
On deadlines: we cut with care. We ship the slice that proves the point and we measure it.
With engineering: I don’t throw Figma over the wall. I help and guide the team until launch.
With stakeholders: I keep the temperature low and the decisions documented.
With users: I listen, watch, and let behavior set the roadmap.
Principles I don’t negotiate
Short list. Long memory.
- Truth over mystery — if something is uncertain, the interface should say so.
- Undo everywhere — people trust what they can reverse.
- Accessibility from day-one — tokens, labels, keyboard paths designed in, not swept in.
- Dashboards over decks — if we can’t see the impact, we didn’t finish.
- Calm defaults — good systems are boring in the right places.
When I work, it goes beyond design
How work goes from “fuzzy” to shipped
01 • Culture (inside the team)
I joined an engineering org building internal systems; as their first UX hire and made “how we decide” as visible as the code
- Brought UX rituals that stuck: 5 quick user checks per slice, 15-min screen-reader smoke test each sprint.
- Shifted reviews from slides to working demos with clear “keep/kill/iterate.”
- Result: fewer back-and-forths, clearer builds, faster merges and calmer releases.
02 • Product & business (with founders/PMs)
Applied UX beyond screens; I partner on the business trade-offs so we ship what matters now.
- Translate constraints into two real options with price/risk, plus a recommendation.
- Align experience quality to cost of getting it wrong (not just what looks good).
- Time-box proof with “prove it by Friday” prototypes so we learn before we bet big.
03 • Building (with engineering)
I don’t stop at prototypes. I code proof-of-concepts.
- Clickable flows with real states and data stubs; no mystery gaps.
- Weekly pairing to unblock edge cases; small PRs over big reveals.
- Handoff includes content rules, accessibility labels, analytics IDs not just frames.
- Result: fewer surprises, fewer rollbacks, and slices that teach us fast.
Perks of working with me
Good vibes, clear heads, done work.
Chai stand-ups. Ten minutes, two decisions, one good laugh.
Good food policy. New feature shipped → homemade snack appears.
Focus playlists. Ambient sets for deep work; zero lyrics during naming debates.
Neat repos. README first; names that age well; fewer “what is this?” Slacks.
Paint breaks. 90-second sketch reset before tough reviews. Everyone breathes better.
Cheerful bug bounties. The donut budget correlates with fewer regressions.
Warning: contacting me boosts clarity and trust in your products.
We’ll label uncertainty, add undo, and ship a slice that puts users in control.
© All rights reserved.