Operational Blueprint
Strategic Definition
I do not wait for requirements. I help define them. I partner with Product and Engineering before the PRD is written, so we solve the right problems rather than the easy ones.
I champion simplification over compromise. When deadlines are tight, we cut scope, not quality.
Insight Architecture
Pragmatism over perfection. I match the research rigour to the business risk.
I work flexibly: lean studies run solo for rapid validation, or deeper discovery alongside dedicated Researchers when the problem is high-stakes.
When speed is critical, I am comfortable shipping an informed assumption to unblock the team, provided we measure the impact in production and iterate.
Leading from the Front
I lead the team first: setting the standard, running structured critique, and growing the designers around me so the work gets better whether or not I am in the room.
I stay close enough to the craft to be credible. I still build, but I am deliberate about where: the architectural decisions, the high-stakes flows, the problems where my judgment moves the work forward fastest. Direction is the job. Building is how I keep the direction honest.
Removing friction
I do not toss designs over the wall. I treat my Figma files as the single source of truth, detailing UX copy, edge cases, and tracking specs.
I keep a constant feedback loop with engineering, so build fidelity matches design intent.
Augmented Intelligence
I treat AI as a sharp assistant: brainstorming variants, generating mock data, building realistic prototypes, sanity-checking logic, while I hold the architecture.
The Red Line: I never outsource strategy. AI supports the thinking. It does not replace it.