How I work, in five lines.
These principles show up in every case file. They're how I move teams from ambiguity to outcome — across banking, ad-tech, marketplaces, and operations.
Start with the real problem, not the requested solution
Stakeholders rarely arrive with the problem — they arrive with a proposed fix. My first job is to dig until the underlying user, business, or operational need is clearly stated, then decide together whether the requested solution still fits.
Make ambiguity visible
Unclear scope, unknown assumptions, and unaligned definitions are the quiet causes of bad outcomes. I name them out loud, write them down, and turn them into decisions the team can actually make.
Use data as a decision tool, not decoration
Dashboards are not the product. I instrument the questions we actually need answered, push back on vanity metrics, and design measurement to change behavior — not to make slides look better.
Build systems that help teams move
A good Jira board, a clear intake, a tight weekly rhythm — these are product surfaces too. When the operating system around the work improves, everything downstream gets faster and calmer.
Design for trust, clarity, and adoption
Anything we ship — a feature, a dashboard, a process — only counts if people actually use it and trust the output. I design for the human at the other end, not for the demo.