UX / Design / Beginner

Redesign a campus library desk-booking flow

Redesign a study-desk reservation flow for a fictional campus library. Make your research assumptions visible rather than presenting them as findings from real users.

Start with this brief Example submissions

First 30 minutes

Before you start

Paper, pencil, or a simple drawing tool is enough. Low-fidelity work is welcome; you do not need real user research or polished visual design.

First 30 minutes

Write the problem and your assumptions for a fictional campus library desk-reservation service. On paper, draw the first three screens and connect them with a simple flow.

A sufficient small-scope submission

A page states the problem and its assumptions.A problem and assumptions note
A user flow and low-fidelity wireframes show the path.A user flow or wireframe
Three main screens or a prototype demonstrate the concept.Sketches of three primary screens
A note explains design decisions and limitations.A decision and boundary note

Extend it if you want

Try a second flow for changing or canceling a reservation, then record which part became clearer or more complicated.

Example file layout

problem-notes.md
reservation-flow.png
screen-sketches.png
decision-log.md

Example presentation

This hypothetical student example presents a low-fidelity concept for reserving a desk in a campus library. The student begins with an assumption that a visitor wants to see a date, available time, and confirmation without learning a new system. Three paper screens show selection, review, and confirmation, while arrows show the proposed flow. The presentation labels open questions instead of describing research that was not done. It is a format example, not a completed real service, client deliverable, or claim about user behavior.

Representative concept example; not real client work or your personal work. Learn the format and write your own decisions.

A starter template is not a completed submission. Produce your own evidence.

01Scenario

Imagine that a campus library wants a calmer way for students to reserve a study desk. You are working from desktop research assumptions about needs and constraints, not from interviews or observed behavior.

Goal

Show a considered path from choosing a time to confirming a desk. Use a small prototype to make the problem, assumptions, decisions, and remaining questions easy to follow.

02Scope and limits

Do not claim to have conducted real user research, interviews, or usability tests.
Keep the flow to a small number of screens and state every research assumption.
Use a fictional library and reservation data; do not present the concept as a live service.

03Production steps

1
Write a problem statement and list the desktop-research assumptions behind it.
2
Map the reservation flow and sketch low-fidelity wireframes.
3
Create three main screens or a clickable prototype with clear states.
4
Review each decision against the assumptions and record limitations and open questions.

04Evidence to submit

A page states the problem and its assumptions.
A user flow and low-fidelity wireframes show the path.
Three main screens or a prototype demonstrate the concept.
A note explains design decisions and limitations.

05Ask yourself

Which assumption has the greatest effect on the flow?
Where could a student become uncertain or stuck?
What would you test first if real research were possible?

06Sources and licensing

Use screens, type, icons, and other materials that you created or that have a suitable open license. Record each license name and source URL. Disclose team or AI contributions, and do not treat an uncredited internet image as open material.

Read the ethical presentation guide