SubjectNest resource library

Year 11 / Digital Solutions / Term 1 / Weeks 01 02

Development draft · local review needed

Clean learner cards · fictional web-application problemsYear 11 Digital Solutions · T1 W1–2 · Learner Cards

Download editable text

All people, venues, messages and evidence below are invented for practice. No real user was interviewed. Your task is to reason from the given facts and say what you would still need to check. You may write, explain aloud with notes captured, or make a labelled diagram with a dictated explanation. Every route targets the same thinking.

Card A · Rehearsal-room information (Day 1)

At the fictional North Pier Music Hub, a paper timetable hangs inside the building. A visitor planning a journey cannot see it before arrival. A team member proposes: “Build a live room-availability web app.” No one has said who would update live occupancy.

Task: Write the visitor's need without naming an app feature. Name one existing information source, one missing fact, and one reason “live availability” is an untested proposal. Sketch the smallest web page that could help if the timetable can be updated reliably.

Card B · A route through an exhibition (Day 2)

A fictional gallery's current page says “Follow the usual route.” The temporary entrance is on the ground floor this week. A reader may be unfamiliar with the building. The card gives no visitor interview or accessibility test results.

Task: State two possible reader questions, the confirmed route fact, and one information gap. Draft a user-need statement without assuming every reader needs the same route. Mark any proposed accessible feature as something to test with people rather than a validated claim.

Card C · Returns at a repair bench (Day 3)

A fictional community repair bench lends demonstration tools. Each tool has a paper code such as T-04; the volunteer writes “on table” or “back in case” on a sheet. A proposed web page would show tool status, but it must not identify visitors.

Task: Break the problem into input, update, display and human check. Which step could become stale? Choose one piece of data the page needs and one it does not. Draw arrows between volunteer, record and visitor view.

Card D · A seed-share schedule (Day 4)

A fictional seed-share group runs three workshop sessions. Its paper poster lists each session time and location. A volunteer proposes adding plant-care advice, live stock counts, bookings and translations to a first web page. The team only has time to update workshop times weekly. No language review or stock process has been arranged.

Task: Sort each proposal into “first version”, “later if verified” or “outside current scope”. State the current constraint and one ethical reason not to publish an unchecked translation or stock count. Name one piece of information needed to decide whether bookings matter.

Card E · A prop-collection list (Day 5 practice)

A fictional theatre has a shared prop shelf. The paper list says a prop is either “ready” or “being checked”. A designer says the web page must let crew find a prop code before rehearsal. Another person asks for a public comment wall. The crew has no moderation plan and the page will not store names.

Task: Identify the human need, a required search or filter behaviour, a sensible scope limit and a testable criterion. Explain why the comment wall is not automatically part of the first version. The fresh check uses a different case.

Card F · Compare existing approaches (Day 6)

At a fictional community cinema, a printed sheet near the entrance describes Friday's demonstration headset trial. A static web page could publish the same details before travel, but the team has no way to update headset availability during the evening. A proposed form would ask visitors to enter their names; nobody has explained why names are needed.

Task: Compare paper sheet, static page and name form for the visitor's actual need. Which solves pre-travel information? Which needs a new process? Identify an unnecessary data request and a question to ask before choosing a solution.

Card G · Who carries the impact? (Day 7)

A fictional board-game club wants a web page for meeting times. Printing fewer posters might save volunteer time. Some members read the existing paper notice at the venue and have unreliable mobile data. The club has a small weekly update window; no cost figures or survey results exist.

Task: Describe one possible personal, one social and one economic impact of a web-only page. For each, name who is affected and how. Recommend a first-version communication mix and one observation the club should gather before claiming benefit.

Card H · New technology or simple filter? (Day 8)

A fictional museum has 30 short, already approved object descriptions tagged by five broad topics. Staff want visitors to find a description. One idea is a five-topic web filter; another is a machine-learning suggestion tool. No training set, accuracy study, maintenance budget or consent process is described.

Task: Compare the two ideas against the current need. What facts support trying the simple filter first? What would need to be known before claiming the suggestion tool helps? Name one possible error or impact of an incorrect suggestion. Do not claim either tool has been tested.

Card I · Criteria for an art-fair map (Day 9)

A fictional art fair has a paper map and a planned static web map. Visitors need to find the workshop tent. The paths are unchanged during the event, but mobile coverage at the site is uncertain. The team can publish one labelled map before opening; it cannot track visitors or update routes live.

Task: Sort the given facts into need / constraint / missing information / testable criterion. Propose one observable paper trial of the static web map, with a reader, task and success condition. Try the optional offline framing lab or sort four paper strips: “find tent”, “uncertain coverage”, “coverage test absent”, “find tent in a timed trial”. Do not record a real visitor's location.

Card J · Make a narrow recommendation (Day 10 practice)

A fictional costume-loan shelf uses a paper list of ten item codes. Volunteers can update that list once each morning. A web page might let a visitor search by code, but it cannot promise that an item remains on the shelf all day. There is no evidence that a barcode scanner or public comment feature is needed.

Task: Give a first-version recommendation: human need, two requirements, a constraint, one testable criterion and one impact to watch. Write a sentence that avoids claiming live availability. The fresh Check B is a new case.