← All work

06 / User Research / Hardware & Software

UXR Forge

A research practice workspace for hardware and software experiences. The design connects study planning, human factors, and evidence synthesis through examples such as a headset and its companion app.

UXR Forge: hardware and software research homepage with a connected-headset example
Actual product interface · User Research / Human Factors
01Learn02Practice03Decision Lab

01 / CONTEXT & CHALLENGE

How can researchers examine the whole interaction—from a physical control to the software behind it?

The challenge
Hardware and software can tell conflicting stories: a headset button may suggest the microphone is muted while its companion app shows it is on. UXR Forge uses examples like this to help learners consider physical actions, feedback, and context when planning research. Method guidance, practice exercises, study planning, and synthesis share one workspace. The examples use fictional practice data.
My contribution
Product direction, the learning experience, and research workflows connecting planning, observations, synthesis, and recommendations.
Key design decision
Link each finding to its supporting observations so readers can check the reasoning.
Current result
The working product connects planning, synthesis, resources, and practice exercises. Whether it helps people make better research decisions still needs evaluation.

Designed for Aspiring and practicing researchers developing research judgment.

The constraint

Written feedback can explain a method’s strengths and limitations, but it cannot account for every detail of a research situation. Exercises therefore use explanation and reflection rather than a score that could imply there is one correct answer.

The design review focuses on the working product. Participant research and usability evaluation are planned next.

RESEARCH DECISION MODEL / NOT A COMPLETED STUDY

Start with what the decision needs.

  1. 01Product decision

    What uncertainty could change the direction?

  2. 02Research question

    What do we need to learn?

  3. 03Method & plan

    Choose an approach, then define tasks and recruitment.

  4. 04Evidence & synthesis

    Separate records from their interpretation.

  5. 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 / RESEARCH PLANNING

Choose a method that fits the question.

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.

The method guide helps learners consider the evidence they need before building a study plan.

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
Link each finding to its supporting observations so readers can check the reasoning.
Rationale
Separating observation from interpretation lets a reader inspect what supports a conclusion and what challenges it.
Tradeoff
Linking findings to observations takes more work, and each reference needs to be checked.
FROM OBSERVATION TO RECOMMENDATION

Check the evidence behind a finding.

  1. 01Observation ID

    The original practice observation

  2. 02Theme

    A grouping of observations

  3. 03Insight

    An interpretation with observations that support or challenge it

  4. 04Recommendation

    A proposed change, its tradeoffs, and a plan to evaluate it

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
Explain what each approach can answer, what it cannot answer, and what it requires.
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
Written feedback cannot respond to every detail in a learner’s reflection.
UXR Forge planning workspace with research decision, questions, and plan stages

The planner begins with the research question before asking for study details.

UXR Forge planning workspace with research decision, questions, and plan stages
The planner begins with the research question before asking for study details.
  1. 01

    Frame before choosing

    Decision and research-question fields establish what the study needs to inform.

  2. 02

    Separate stages

    The plan divides framing, study design, and preparation instead of displaying one undifferentiated form.

  3. 03

    Explain where drafts are saved

    Draft notices explain that work is saved in this browser, rather than shared with a team or stored in the cloud.

DESIGN DECISION / 03

Distinguish practice examples from completed research

Observed in the product
Study examples are labeled as practice data; exported plans are marked as drafts.
Design response
Label practice data and untested study plans in both the interface and exported files.
Rationale
Practice observations cannot establish how real users behave. Clear labels help learners understand what the examples can teach and what still requires a study.
Tradeoff
Labels take up space, but they need to remain visible when examples are shared or exported.
UXR Forge synthesis workspace using the connected-headset hardware and software practice study

Each finding links to the observations behind it. This screen uses fictional practice data.

UXR Forge synthesis workspace using the connected-headset hardware and software practice study
Each finding links to the observations behind it. This screen uses fictional practice data.

04 / VISUAL & INTERACTION SYSTEM

Make the reasoning easy to follow.

Learning, practice, and planning have separate destinations. In synthesis, each finding stays connected to supporting observations and examples that challenge it. This lets a reviewer follow the reasoning behind a recommendation and question it.

HARDWARE & SOFTWARE / PRACTICE EXAMPLE

One action. Two places to check the result.

The connected-headset example asks whether a physical mute button, a status light, and a companion app communicate the same microphone state. It also explores what happens when the connection drops.

  1. 01Physical action

    Press the headset’s mute control.

  2. 02Software feedback

    Check whether the app reports the same microphone state.

  3. 03Research question

    Can someone explain what the other caller can hear?

  4. 04Next evaluation

    Test timing, feedback, and recovery on working hardware.

05 / INCLUSIVE INTERACTION

Behavior matters as much as appearance.

Native selection controls support evidence assignment without dragging. Draft recovery and confirmation before resets protect work in progress. Assistive-technology testing and sessions with researchers are still needed.

06 / OUTCOME & REFLECTION

What exists. What remains to learn.

The working product connects planning, synthesis, resources, and practice exercises. Whether it helps people make better research decisions still needs evaluation.

What works

Readers can open the observations behind a recommendation and check evidence that challenges it.

What remains limited

Practice scenarios cannot reproduce the changing constraints and unexpected responses of a live study.

Next questions

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

My contribution and the next questions.

My contribution
Product direction, the learning experience, and research workflows connecting planning, observations, synthesis, and recommendations.
Next user study
Participant testing is planned. The central question is: Do learners distinguish observations, interpretations, and proposed recommendations?
Constraints & priorities
Linking findings to observations takes more work, and each reference needs to be checked.
What the design supports
Readers can open the observations behind a recommendation and check evidence that challenges it. The next evaluation will look for: Observe whether participants can trace a finding to its observations, recognize evidence that challenges it, and explain why a method fits the question. Record hesitation, requests for help, and confusion between practice examples and completed research.

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.
Research question
Do learners distinguish observations, interpretations, and proposed recommendations?
Method
Moderated task sessions with a fictional study brief and practice observations. Ask participants to choose a method, group observations, and explain a recommendation. Observe their first attempt before asking follow-up questions.
Participants
Recruit people who are learning to plan or synthesize research. Include practitioners who review research plans to check whether the reasoning is understandable to another reader. These sessions have not been conducted.
What to observe
Observe whether participants can trace a finding to its observations, recognize evidence that challenges it, and explain why a method fits the question. Record hesitation, requests for help, and confusion between practice examples and completed research.

Observe first. Ask without leading.

The proposed sessions would test whether learners can explain their decisions using the workspace. Completing every field would not, on its own, show that the reasoning is sound.

Prepare the session
Explain the purpose, obtain consent, and make clear that the product is being evaluated. Ask about access needs and use fictional materials so participants do not need to share confidential research.
Facilitate without teaching
Give participants the same brief and allow time to work before offering help. Use neutral prompts such as “What led you to that choice?” Record where help was needed and distinguish independent actions from prompted ones.
Turn observations into changes
Separate difficulty using the interface from difficulty understanding a research concept. Compare observations across sessions, retain conflicting examples, and prioritize problems that prevent someone from checking or explaining a finding. Test revised guidance and interactions in a follow-up round.

TOOLS & WORKFLOW

Tools supporting the design.

Prototype implementation

  • React
  • TypeScript
  • Vite

Evaluation

  • Playwright
  • axe-core
  • Vitest

Versioning

  • Git
Next case study

NeuroMode

NEUROMODE / NATIVE iOSA smaller start.
A way back.

Support that makes room
for the person.

Initiation · Sensory comfort · Continuity
NeuroMode Today: direct actions for starting, focus, and less stimulation.Quiet Room opens with optional comforts collapsed and a clear Finish control.