Implemented product scope, not user-research or impact metrics.
Actual product interface · User Research / Research Strategy
01Learn02Practice03Decision Lab
01 / CONTEXT & CHALLENGE
How can a research tool develop judgment without reducing research to a checklist?
The challenge
UXR Forge combines method guidance, practice exercises, a Decision Lab, study planning, and synthesis. Its displayed studies are synthetic teaching material—not research conducted with participants.
Key design decision
Retain stable record IDs and direct finding-to-observation navigation.
Implemented result
The product implements planning, synthesis, downloadable resources, and authored research-reasoning exercises. No participant findings or measured research-training outcome is claimed.
Designed for Aspiring and practicing researchers developing research judgment.
The constraint
Authored feedback can explain tradeoffs but cannot grade the quality of an open-ended research judgment. The product avoids scores, certificates, and simulated AI critique.
This case study analyzes the current implementation. Rationale describes the design implications of observable choices; it does not claim undocumented interviews, historical alternatives, or measured improvements.
RESEARCH DECISION MODEL / NOT A COMPLETED STUDY
Start with what the decision needs.
01Product decision
What uncertainty could change the direction?
02Research question
What do we need to learn?
03Method & plan
Choose an approach, then define tasks and recruitment.
04Evidence & synthesis
Separate records from their interpretation.
05Recommendation
State the tradeoff and the next check.
Questions and interpretations can send the work back to an earlier stage. This is a reasoning model, not a mandatory sequence.
02 / INFORMATION ARCHITECTURE
A structure for different intentions.
METHOD ORIENTATION / NOT A SELECTION ALGORITHM
The question changes the method.
What people report
Interviews / Surveys
Interviews can explore meaning in depth. Surveys can describe response patterns when the sample and question design support that inference.
What people do
Usability tasks / Contextual inquiry
Observe task behavior or work in context. Usability studies may collect qualitative explanations and quantitative measures.
Attitudinal/behavioral and qualitative/quantitative are useful lenses, not fixed boxes. Sampling, context, ethics, and the decision determine suitability.
Product areas from the repository. This is an orientation model, not a tested linear user journey.
03 / DESIGN REASONING
The choices behind the experience.
DESIGN DECISION / 01
Keep evidence traceable
Observed in the product
Study records link observations to themes, insights, recommendations, and counterexamples.
Design response
Retain stable record IDs and direct finding-to-observation navigation.
Rationale
Separating observation from interpretation lets a reader inspect what supports a conclusion and what challenges it.
Tradeoff
More explicit relationships increase authoring effort and demand validation of references.
An interpretation with supporting and challenging records
04Recommendation
A proposed response, tradeoff, and validation plan
All displayed study data is synthetic. The visual describes relationships, not participant findings.
DESIGN DECISION / 02
Explain method choices rather than score them
Observed in the product
Practice activities provide approach-specific feedback and ungraded written reflections.
Design response
Present costs and assumptions behind defensible approaches.
Rationale
A usability task can reveal interaction breakdowns; a survey answers a different kind of question. Method choice should follow the decision to be informed.
Tradeoff
Authored feedback cannot respond to every contextual detail in a learner’s reflection.
Implementation reference: README.md: Learning and practice release
A fresh planner capture. Question framing precedes study design in the actual workspace.
01
Frame before choosing
Decision and research-question fields establish what the study needs to inform.
02
Separate stages
The plan divides framing, study design, and preparation instead of displaying one undifferentiated form.
03
Make storage boundaries explicit
Local-draft notices distinguish browser persistence from shared or cloud storage.
DESIGN DECISION / 03
Keep practice and research provenance visible
Observed in the product
Every displayed study is labeled as synthetic; planner exports identify unexecuted drafts.
Design response
Carry provenance into both the interface and exports.
Rationale
An observation count is not a population estimate, and a teaching dataset is not participant evidence. Labels reduce the risk of confusing practice with completed research.
Tradeoff
Repeated labeling adds content, but removing it could create a materially misleading impression.
Implementation reference: README.md: Research status; Local storage and exports
Synthesis uses explicit evidence relationships. Practice content is authored teaching material, not completed research.
04 / VISUAL & INTERACTION SYSTEM
Give the structure a visual expression.
The product separates learning, practice, and toolkit destinations. Within synthesis, observation IDs and supporting or challenging evidence maintain a readable chain from source material to interpretation. The portfolio presents that chain as the research competency—not the existence of templates.
05 / INCLUSIVE INTERACTION
Behavior matters as much as appearance.
The implementation documents native select-based evidence assignment, keyboard journeys, recoverable drafts, and explicit confirmation before resets. Automated checks are documented in the source repository; assistive-technology testing and practitioner sessions remain separate validation needs.
06 / OUTCOME & REFLECTION
What exists. What remains to learn.
The product implements planning, synthesis, downloadable resources, and authored research-reasoning exercises. No participant findings or measured research-training outcome is claimed.
What works
Evidence relationships remain inspectable rather than collapsing into a confidence score.
What remains limited
Authored scenarios and feedback cannot reproduce the ambiguity of a live research engagement.
What I would explore next
Research tools need to preserve uncertainty. A structured workflow helps expose reasoning, but it should not make a recommendation appear more certain simply because every field is filled.
CONTRIBUTION & EVIDENCE
Scope, decisions, and the evidence behind them.
Role & collaboration
The role presented in this case study is UX Designer, with a focus on User Research, Research Strategy, Interaction Design. Individual ownership boundaries and collaborator contributions are not documented in this implementation review.
User feedback & iteration
No participant-feedback record is included in this case study, so the design changes are not attributed to user testing. The next validation question is: Do learners distinguish observations, interpretations, and proposed recommendations?
Constraints & priorities
Authored feedback can explain tradeoffs but cannot grade the quality of an open-ended research judgment. The product avoids scores, certificates, and simulated AI critique. A concrete tradeoff: More explicit relationships increase authoring effort and demand validation of references. This describes a product tradeoff; no stakeholder disagreement is claimed.
Evidence of benefit
Evidence relationships remain inspectable rather than collapsing into a confidence score. This is observable product behavior. Whether it helps the intended audience remains a question for validation: Trace an insight to evidence, identify a counterexample, and explain a method choice without treating synthetic data as real findings.
Verified implementation scope
Reasoning exercises
8
Decision Lab stages
6
Downloadable resources
11
These counts describe the implemented product. They do not measure usability improvement, participant satisfaction, or business impact.
07 / PROPOSED RESEARCH · NOT CONDUCTED
The next questions to test.
Proposed tasks
Frame a question, justify a method, inspect a counterexample, and recover a saved draft.
question
Do learners distinguish observations, interpretations, and proposed recommendations?
method
Proposed moderated synthesis exercise followed by explanation and navigation tasks.
participants
Early-career researchers and practitioners reviewing research plans.
signal
Trace an insight to evidence, identify a counterexample, and explain a method choice without treating synthetic data as real findings.
TOOLS & WORKFLOW
Tools supporting the design.
Prototype implementation
React
TypeScript
Vite
Evaluation
Playwright
axe-core
Vitest
Versioning
Git
Project tools confirmed by source configuration. Figma, Sketch, and Adobe XD belong to my overall toolkit; their use on this specific project has not yet been documented.
