UX research: understand before designing.
UX research helps teams make evidence-based decisions: understand users, align stakeholders, identify friction points and turn learnings into concrete product actions.
A structured way to reduce blind spots.
Before producing screens, you need to understand the context: who uses the service, which tasks must be completed, which constraints weigh on the project and which decisions need to be secured.
I structure this research phase, collect the useful signals and restore them in a form directly usable by product, design, business and development teams.
Services
Interventions adapted to the maturity of the project.
Research can frame a new initiative, inform a redesign, explain a conversion issue, prepare user testing or align several teams around the same understanding of the need.
Discovery and framing
Clarify objectives, assumptions, target audiences, business constraints and research questions before design starts.
Qualitative research
Run user interviews, stakeholder interviews, framing workshops and observations to understand usage and friction points.
Quantitative research
Set up surveys, analyse user feedback, read the available analytics signals and prioritise the detected issues.
Classic methods
A simple, robust and actionable methodological base.
Depending on the context, I combine the most relevant UX research methods to avoid decorative research and support useful decisions.
- User interviews.
Understand the needs, expectations, blockers, vocabulary, habits and decision criteria of end users.
- Stakeholder interviews.
Gather business objectives, operational constraints, project risks and sometimes diverging internal visions.
- Surveys and questionnaires.
Collect signals at a larger scale, validate trends and complement the qualitative learnings.
- Journey analysis.
Formalise user flows, user journeys, journey maps, touchpoints and critical steps of a service.
- Personas and segmentation.
Synthesise profiles, motivations, barriers and needs to help teams design for real situations.
Field experience
My role in your UX analysis and research phases.
Across my missions, I have conducted user interviews, interviewed the various stakeholders of a project, set up surveys and turned these learnings into decision-support material.
These engagements produced user flows, personas, user journeys, insight synthesis, UX recommendations, problem prioritisation and framing elements for the rest of the design work.
Formalise journeys
User flows, target journeys, usage scenarios and friction points to make visible the steps to simplify or secure.
Share a common understanding
Personas, interview synthesis, key learnings and recommendations to align teams on the real user needs.
Process
A readable mission, from research question to decisions.
The format can be short or integrated into a larger UX mission. What matters is framing what needs to be learned, then restoring the results in language that is useful to teams.
1
Frame
Define the objectives, assumptions, audiences to interview and questions to document.
2
Collect
Run the interviews, surveys, observations or analyses needed according to the project context.
3
Synthesize
Group the learnings, identify recurring patterns and separate facts from interpretations.
4
Model
Produce the useful assets: personas, user flows, journey maps, prioritisation or UX recommendations.
5
Decide
Share the results with teams and translate research into design decisions or a prioritised backlog.