Design a clearer college event signup.

Practice brief: a fictional college is running a free, two-hour portfolio workshop, Saturday 17 October, 11am–1pm, in Seminar Room 2. Registration asks for a name and email only. The workshop has a capacity of 30; treat that as a scenario constraint, not a live attendance claim.

List what a student needs to know before registering and sketch the journey from event details to confirmation. Include already registered, full capacity and connection failure states. Identify assumptions and open questions. Desk research is optional; do not fabricate interviews or describe your own guesses as user findings.

Submit a document, images, presentation or spreadsheet with the flow, information hierarchy and assumptions. Review criteria: the event details are accurate, each failure has a useful next step, and the form requests only necessary information.

Create five connected screens or states: event details, registration, field validation, confirmation and full capacity. Use a design tool of your choice or carefully drawn wireframes. Keep one dominant action per screen, visible form labels, comfortable tap targets and legible text.

Make the confirmation state state exactly what has happened. Do not add a payment step, fake testimonials, unnecessary profile fields or an unavailable waitlist. A prototype may use invented names, labelled as sample content; never include another person's contact details.

Submit a document, images, presentation or spreadsheet with the screens, a prototype link if available, and notes on keyboard, text size and loading behavior. Review criteria: the flow can be followed without explanation, errors preserve entered information, and the visuals remain consistent across states.

Walk through the prototype as a first-time student who wants the time, location and confirmation of registration. If someone volunteers to try it, obtain permission and record observations without names or recordings. Otherwise run a structured self-review and label it clearly.

Document three friction points and improve the design. Consider a slow connection, a longer name and enlarged text. Explain which changes came from observed behavior and which are design judgments.

Submit a document, images, presentation or spreadsheet with before/after screens, the review method, findings and a concise decision log. Review criteria: evidence is honestly described, changes address specific problems, and remaining uncertainties are visible. No invented usability scores or interview quotations.