A little more possibility. A better way to bid.

Make the next step feel obvious.

An auction asks people to make decisions under uncertainty. For this demonstration, the design question is simple: how might we make the current price, the next bid, and the outcome easier to understand?

In a real case study, replace this hypothesis with a specific problem supported by research you are permitted to share.

Design question: What does a person need to know before they feel ready to bid?

A clear account of the contribution.

Use this section to explain what you personally owned, what you influenced, and what the wider team delivered. This sample does not claim involvement in Mercari’s product.

Example scope: framing the flow, exploring interaction patterns, documenting edge cases, and collaborating on implementation details.

Understand. Explore. Refine.

A proposed process starts by mapping the journey from discovery to confirmation. Identify what a bidder needs at each step, then compare ways to communicate price, timing, and commitment.

Document the research you actually conducted, the alternatives you considered, and how feedback changed the design. Add approved artifacts rather than a list of methods.

1. 01 / Map the journey
2. 02 / Explore the interaction
3. 03 / Check comprehension

Confidence lives in the details.

Keep the current bid and minimum next bid together, so people do not have to calculate the next step themselves.

Show a review step before a bid is committed. State the amount and explain what happens next.

Give success, outbid, and ended states equally clear treatment. The experience should still make sense when the preferred outcome does not happen.

From intention to implementation.

This placeholder is a concept, not a shipped result. The interface above illustrates a possible direction using fictional content.

Replace it with approved production screenshots, the release scope, and a clear description of any differences between the proposal and the implementation.

Evidence, not invented numbers.

No performance claims are attached to this sample. In your published case, connect the original problem to verified evidence: usability findings, an approved product metric, or a documented qualitative outcome.

If you cannot share numbers, describe what you learned, the observable change, and the limits of the evidence.

Add only outcomes you can substantiate and are allowed to publish.