Product design: responsibilities and practical exercise
Product design connects a usage problem with decisions that shape a feature. It compares solutions against needs, implementation constraints and available feedback. The expected result is a reasoned, testable decision, which may also mean simplifying or deferring a feature.
These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.
Improve search for a catalog by examining requests and searches without result.
Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.
Formulate the problem and the expected decision before choosing a function.
Study several variants with the same tasks and constraints.
Define the necessary returns to evaluate the use after delivery.
Document what is retained, deferred and still uncertain.
Deliverable and checks
For catalogue search, collect the observed problem, reviewed queries and alternatives considered. Present the chosen prototype with rejected options, known constraints and the signal that would trigger a review after use.
Compare alternatives using the same task and retain no-result cases. Explain why the solution addresses the problem more effectively without equating visual preference or extra features with successful search.
Adding a feature does not guarantee improvement. A decision must remain related to the initial problem and the available observations.
Collaboration to explore: UX research.
Fictional deliverable excerpt : A comparison plan connects the observed problem, hypothesis, variant to try and decision after testing. A visual preference is not presented as evidence of use.
What passes between the roles : Share the visual proposal and the question to check together: mock-up version, target task, constraints and observations. Agree who continues the tests and who decides on changes.
Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.
Sample excerpt
Problem: enquiries arrive from outside the service area.
Hypothesis: the area is not visible before contact.
Chosen option: state the area before the form.
Deferred option: add a location check.
Review: inspect enquiries after clarifying the copy.
What the author should be able to explain
The solution starts with an explicit hypothesis.
A deferred option retains its rationale without becoming a promised feature.
Review allows the decision to change if the problem remains.
Why not add an automatic check immediately?
First verify the cause and the quality of service-area data. Automation may help, but it introduces failure cases and maintenance that need to be justified by the task.
Assess the quality of the work
In the exercise, users do not know whether a request was received. Compare a clearer state explanation with adding a feature. Product design should connect the observed obstacle, proposed response and evidence that could change the decision; a prototype examines that relationship before more costly implementation.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
Assess the quality of the work
Skill
Evidence to examine
Failure to spot
Observable problem
Describe the task, context and obstacle using available evidence. Separate the need for confirmation from the solution being considered.
The need is expressed as “add a dashboard” without explaining which uncertainty the interface should resolve.
Testable comparison
Prepare two responses to the same problem, including a simple option, with a comparable task and observable outcome. State what the prototype simulates.
The demonstration explains only one solution or merely asks which looks more modern without checking understanding of the actual state.
Trade-off
Compromises, constraints and remaining questions are recorded.
One result is presented as universal validation.
Design hypothesis
Link a change to an observed problem and state what evidence would make the team reject it.
The test can disprove the proposal; a liked prototype alone does not establish that it solves the need.
A focused next step
Replay the same scenario with each proposal and record misunderstandings, including evidence against your initial preference. Explain the chosen option, constraints and next uncertainty to investigate. A local result may justify another trial without constituting general validation of the product.
Within one process, previously supplied information must be auto-populated or available to select, subject to the criterion’s exceptions. Browser autocomplete alone is insufficient; the site must offer the information already received or avoid requesting it again.
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
A review case to reproduce
A prototype confirms too early
Situation to examine
A mock-up confirms an appointment while the business process only receives an enquiry. Visual and operational decisions diverge.
Proposed check
Map received, under review, accepted and refused states. Identify owners and information needed at each transition. Test understanding through a task without explaining the expected answer.
Evidence to retain
A documented journey connects visible state, business state and next action. Test findings distinguish observations from unresolved questions.
Fictional finding example
Case DEMO-17 is “under review” internally, but the prototype says “Appointment confirmed”. Nobody has accepted the slot.
Interpret this outcome
Replace confirmation with enquiry received and explain who decides next. The prototype should represent a business state that can actually occur.
Three complementary checks
Fictional cases: adapt these expectations to your test contract and retain the limits of the check.
1Business state
2Identified owner
3Explained transition
Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.
Scenario variations and expected evidence
Variation to test
Expected result in this case
Evidence to hand over
The request awaits review
Show receipt without confirming an appointment
Visible state and tracking state
The slot is rejected
Explain rejection and the next choice
Business decision and recovery screen
The request is withdrawn
Show withdrawal under the chosen contract
Transition, actor and consequence
Decision to hand over : Have transitions approved before turning the prototype into an operational commitment.
In-depth exercise: Improve a research path where visitors do not know how to differentiate categories. Formulate the problem before choosing an interface. Propose two tracks: clarify categories or modify filtering. For each, describe the people concerned, the dependencies and how to check the effect. Make a prototype limited to the useful course. A decision must be able to be explained by a need and an observation, without transforming a personal preference into a demonstrated result.
What to deliver with your work
Description of the problem and context of use
Assumptions and Comparative Solutions
Priority course prototype
Journal of Decisions and Validation Conditions
Acceptance criteria
These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.
The solution responds to a problem formulated before design.
Unverified hypotheses are identified.
The prototype allows you to perform the main task until its result.
The final decision indicates the evidence used and its limits.
Share selected choices, discarded tracks and open questions with the production team. Link acceptance criteria to uses rather than just screenshots. Specify how a new data can put a decision under discussion. After delivery, compare the observed behavior to the starting hypothesis; The publication of the prototype does not constitute a validation of its usefulness.
Design may address an observed difficulty or explore a new capability. Separate these goals so that an expected correction is not compared with an untested hypothesis.
Improvement of an existing workflow
When to choose it
Suitable for a problem supported by usable observations. Define the affected users and the action that has become difficult.
What to plan for
Keep a baseline and identify possible side effects. A local improvement can move a difficulty elsewhere.
Exploration of a new solution
When to choose it
Useful when the need is plausible but the response uncertain. State hypotheses and choose a prototype that supports discussion.
What to plan for
Define what the trial can teach you. Positive intentions are not evidence of sustained use or profitability.
A risk to anticipate
A feature list does not explain a workflow’s value. Link each proposal to a task, constraint and expected outcome.
How to decide
Present alternatives and available information. Explain what justifies the trial, what remains unknown and what would prompt reconsideration.
Compare the problem, alternatives and decision criteria. An exploratory prototype differs from a delivered feature that is instrumented and monitored.
Recurring operation
Specify feedback follow-up and review frequency. Define who decides changes and who delivers them; a prototyping subscription does not replace design work.
Exit and handover
Retain hypotheses, decisions, limits and prototype sources. Handover should explain choices and support further testing rather than merely open the last screen.
How should the first hypothesis to test be chosen?
Link each hypothesis to a decision that would genuinely change the project. Consider uncertainty, the consequences of being wrong and the effort of a test. An essential, weakly supported assumption deserves checking before polishing an already drawn solution.
What if the prototype works but the service behind it does not?
Identify the dependency: availability, human handling, payment or another real operation. The prototype may test understanding of a journey; it does not validate operational capacity. Arrange a separate check with the responsible team before presenting the whole service as ready.
How should a solution never used in production be presented?
Identify it as a prototype or exploration. Describe hypotheses, people consulted and tasks observed. Separate observed results from expected effects: the document supports a decision without promising unmeasured outcomes.