My best work tends to show up in six dimensions: Structure, Judgment, Understanding, Influence, Follow-through, and Builder.
These aren’t steps in a process, these are primary skills. Different problems call for different combinations and each case study below focuses on one skill dimension demonstrating how I operate as a Principal Product Designer.
I'm most useful when a product problem crosses system boundaries: when the workflow is bigger than the screen, the requirements hide unanswered questions, or Product and Engineering need a clearer model before they can move.
I like learning difficult domains, making the problem concrete, and co-creating the solution with the people who have to build and operate it. I care about craft, but I care even more about whether the idea survives contact with real users, real data and real implementation constraints.
I do my best work when Design is involved early enough to help shape the problem, with trusted ownership of the design process inside close Product + Engineering collaboration.
The role I'm looking for is one where that breadth is expected rather than treated as going outside the design lane.
