Fieldwork is an invented furniture repair studio. This is a design experiment, not a completed client study. No analytics, interviews, customer research or usability testing took place.
The question behind the design.
A visitor has a chair with a loose joint. They are interested in repair but do not yet know whether the studio handles this kind of work. This proposed journey assumes they need basic eligibility information before contacting the business. No customer behavior has been observed.
The central idea.
A useful journey answers the questions in the order they become necessary. First: can you help with this kind of object? Then: what information do you need? Finally: what will happen after I provide it? Each step should prepare the next decision rather than merely move someone to another screen.
Can you repair this?
Repair categories and limitations.
What should I send?
Photos, condition, and relevant details.
What happens next?
An assessment before any agreed work.
Source: original ELCQ demonstration, 12 October 2026. Text and visual proposals for a fictional subject. Numbers correspond to the complete explanations below.
Explain eligibility before asking for effort.
The proposed first page shows the repair categories and states important limitations. It also offers a route for an uncertain owner to ask about their specific object.
Reason: Someone should not have to prepare a detailed inquiry merely to discover that the studio cannot accept their work. The service information can help them make an informed first decision.
Possible friction: An exhaustive list can overwhelm the page or sound like a rejection. For a real studio, exclusions should be accurate, plainly written, and paired with a useful way to resolve uncertainty.
Ask for what changes the assessment.
The proposed inquiry requests clear photos of the object and the damaged area, a short condition description, and any relevant context. This demonstration does not implement uploads or collect customer data.
Reason: Every requested detail should have a reason. The business should be able to explain how it helps assess the work or identify the next question.
Possible friction: Too many required details can make an initial inquiry burdensome. Upload limits, accessibility, privacy, and alternatives for someone who cannot provide a photo need to be agreed. A real form requires a connected, tested destination.
Separate an inquiry from a commitment.
The proposed next-step explanation says the studio will assess the information before agreeing any repair work. Price, timing and the work itself would be confirmed separately.
Reason: The owner needs to know what selecting the action does—and what it does not commit them to. A confirmation should describe the actual delivery state and the real next step.
Possible friction: Do not promise a response time or successful submission without operational support. If a request fails, preserve the entries and explain a recovery path. A button label cannot make the underlying process reliable.
What needs evidence?
The sequence is a proposed design, not a validated funnel. We do not know repair capacity, assessment procedures, customer access needs, data retention rules, or response ownership. A real review would ask the studio to verify the process and invite representative customers to try the uncertain steps.
For a real review, I would agree the business question and pages first, request the relevant evidence, then test the uncertain parts rather than treating the visual proposal as proof.
Answer the next real question.
Trace one customer task on your own site. At every step, write the question someone must answer before continuing. Check whether the page answers it, asks for necessary information, and explains what the next action will do.
Fictional Fieldwork concept. Prepared 12 October 2026. No commercial relationship, client outcome or outside subject. Suggest a correction.