Product thinking · UX research · Design delivery
I help teams move from a broad business challenge to a clear, testable product direction. The work connects customer needs, business outcomes, and technical realities, so product managers and delivery teams can decide what to learn, what to build, and how to measure progress.
The approach
The sequence is a flexible framework, not a rigid waterfall. Teams can revisit earlier questions when research or testing reveals new information, while keeping decisions and learning visible.
Clarify the challenge, context, intended business outcome, constraints, and what success could look like before committing to a feature.
Combine direct research and available evidence to understand users’ goals, behaviours, needs, pain points, and environments.
Turn findings into opportunity areas. Make assumptions explicit, agree priorities with product partners, and choose the riskiest questions to resolve first.
Run idea sessions with product managers and stakeholders, then translate promising directions into flows, wireframes, and prototypes.
Use usability studies and lightweight experiments to learn whether a concept is understandable, useful, feasible, and worth further investment.
Specify interaction details and states, align with engineering, and use post-release signals to guide the next improvement cycle.
A shared PM and UX tool
The canvas helps product, design and development talk about the same thing. Teams fill in the business problem, possible solutions, goals, users, benefits, assumptions and the next test. A vague request becomes an idea you can test.
The complete worksheet set supports structured product conversations from framing through learning and validation.
Systems thinking
Application cartography connects products to the people, processes, and technical domains around them. It gives product and technology partners a shared view of dependencies, overlaps, and service boundaries, helping teams frame the right problem and coordinate change across a complex environment.
Map where a user-facing task depends on internal applications, data, and operational processes before deciding where a change belongs.
Use one landscape view to support discussion across product, business, design, and technical stakeholders.
Use the map to identify adjacent services, clarify boundaries, and bring the relevant owners into planning.
Research and measurement
The methodology distinguishes exploratory research from evaluative work and combines qualitative context with behavioural evidence where available. Research questions, methods, and measures are selected to fit the decision at hand, not applied as a one-size-fits-all checklist.
Interviews, observation, usability sessions, and feedback help explain needs, motivations, barriers, and why a task succeeds or fails.
Analytics, task measures, and product metrics help show patterns over time and indicate where deeper investigation may be useful.
From learning to making
The work moves from research and problem definition into user flows, wireframes, visual design, and interactive prototypes. Testing helps expose gaps before teams commit to implementation, and findings feed the next design iteration.
How I partner with product teams
Clarify outcomes, compare options, expose assumptions, prioritize learning, and connect roadmap choices to user value.
Keep evidence, user needs, and design rationale visible, then translate findings into flows, prototypes, and criteria for evaluation.
Bring implementation partners into discovery and validation early, align on constraints, and reduce ambiguity before handoff.
Create a common language for discussing users, business goals, risks, scope, and what the team will learn next.
Working materials
These screens show the tools I use in this process.
I work with product managers and their teams to find the right problem, learn from users and turn what we learn into a clear plan.