How Research Becomes Product Decisions
How research becomes product decisions.
Great products do not begin with wireframes. They begin by understanding how people work, where they struggle, what information they need, and the decisions they are trying to make.
My process connects research, product strategy, interaction design, validation, and measurement so teams can move from assumptions to evidence-based product decisions.
Most product problems are understanding problems first.
A confusing interface is often a symptom of a deeper issue: unclear workflows, missing information, competing priorities, fragmented systems, or assumptions that were never validated.
Research helps teams understand the problem before committing to a solution. It creates a shared view of user needs, business requirements, technical constraints, and the decisions the product must support.
My role is to turn that understanding into clear product direction: what to prioritize, what information to surface, how workflows should behave, and how success will be measured.
Product decisions become stronger when multiple sources of evidence point in the same direction.
I combine qualitative research, behavioral data, workflow analysis, stakeholder knowledge, and usability findings to understand both what people say and what they actually do.
User Conversations
Interviews reveal goals, frustrations, expectations, workarounds, and the reasoning behind user behavior.
Influences needs and prioritiesWorkflow Observation
Contextual inquiry and field observation show how work actually happens across people, systems, tools, and interruptions.
Influences flows and interactionsAnalytics and Behavior
Product data helps reveal where people hesitate, abandon tasks, repeat actions, or struggle to find information.
Influences prioritizationBusiness Context
Stakeholder interviews clarify goals, constraints, risks, operational dependencies, and measures of success.
Influences product strategyUsability Testing
Testing exposes unclear language, missing information, broken expectations, and interaction patterns that require refinement.
Influences design iterationPost-Launch Feedback
Support requests, user feedback, adoption data, and performance metrics create another source of product insight.
Influences continuous improvementTurning observations into clear product direction.
Research becomes valuable when it changes what a team understands, prioritizes, designs, or measures.
Learn how the work happens today.
I begin by understanding users, workflows, environments, business requirements, technical constraints, and existing product behavior.
- Stakeholder and user interviews
- Contextual inquiry and field observation
- Analytics and product-data review
- Current-state workflow mapping
Find where friction affects performance and confidence.
I look for patterns that create unnecessary effort, delays, errors, uncertainty, repeated work, or incomplete information.
- Workflow bottlenecks
- Information gaps
- Unclear responsibilities
- High-risk decision points
Turn individual observations into meaningful patterns.
Research findings are organized into themes that connect user needs, behavioral patterns, business impact, and product opportunities.
- Affinity mapping and thematic analysis
- Journey maps and service blueprints
- Research summaries and opportunity areas
- Evidence-based design principles
Decide which problems are worth solving first.
I work with product, engineering, and business stakeholders to balance user value, business impact, risk, effort, and technical feasibility.
- Opportunity prioritization
- Product requirements and scope
- Experience principles
- Success criteria and measurement plans
Translate insight into workflows and product experiences.
Research findings guide the information architecture, interaction patterns, content hierarchy, workflows, and interface decisions.
- User flows and information architecture
- Wireframes and interaction concepts
- High-fidelity interfaces
- Interactive prototypes
Test assumptions before they become expensive.
Prototypes create a shared artifact that users, stakeholders, product managers, and engineers can evaluate before development.
- Moderated and unmoderated usability testing
- Workflow and concept validation
- Stakeholder design reviews
- Accessibility evaluation
Carry the research intent through implementation.
I collaborate with engineering and QA throughout implementation to preserve the reasoning behind the design and respond to technical discoveries.
- Detailed design specifications
- Component and interaction documentation
- Engineering and QA collaboration
- Implementation review
Use outcomes as the next source of product insight.
Launch does not end the research process. Product behavior, feedback, adoption, and performance create evidence for the next round of decisions.
- Post-launch interviews and feedback
- Behavioral and performance analytics
- Support and operational insights
- Continuous product iteration
Every research finding should influence a product decision.
I connect research evidence to the specific parts of the product experience it should change.
Users cannot see critical information at the right moment.
The issue is not simply visual hierarchy. It may indicate fragmented data, unclear priorities, or a workflow that does not match how decisions are made.
Surface context within the decision-making workflow.
Reorganize the information architecture, define priority content, reduce unnecessary navigation, and clarify the next action.
Faster decisions with greater confidence.
Validate whether users complete the task more efficiently, make fewer errors, and feel more confident in the information provided.
Different industries. The same evidence-driven approach.
The users, environments, and business models change. The need to understand behavior before designing remains consistent.
Helping dispatchers find critical load information faster.
Interviews, workflow observation, surveys, journey mapping, and usability testing revealed that dispatchers were searching across multiple areas for load history and status information.
Create a chronological load timeline, prioritize critical alerts, reduce map dominance, and reorganize information around dispatch decision-making.
The redesigned transportation workflow contributed to an 18% improvement in load assignment efficiency.
Making academic programs easier to discover and compare.
Usability testing, analytics, content review, and journey mapping showed that prospective students struggled to find programs and understand the path toward application.
Simplify the information architecture, improve program discovery, clarify enrollment actions, and organize content around student questions.
The redesigned experience increased Apply Now engagement by 24% and reduced time to find a degree by 32%.
Creating scalable workflows for distributed business users.
Workflow reviews, stakeholder input, user feedback, and system analysis revealed the complexity of creating approved advertising across multiple brands and local markets.
Create reusable interface patterns, guided workflows, clear approval states, and flexible templates that could scale across different organizations.
The resulting product framework supported enterprise platforms for nationally recognized brands and distributed user networks.
The questions that shape better product decisions.
These questions help move a project beyond surface-level interface requests and toward the underlying user and business problem.
What decision is the user trying to make?
What information do they need at that moment?
Where does the current workflow slow them down?
What creates uncertainty, errors, or repeated work?
Which assumptions have not been validated?
What happens when the user makes the wrong decision?
How will we know the experience improved?
Research does not end when the product launches.
Every release creates new evidence. Feedback, adoption, performance, support requests, and user behavior help teams understand what to improve next.
Better research creates better product decisions.
Better product decisions create clearer experiences, more confident users, stronger adoption, and better business outcomes.
