A technology idea can be tested before anyone writes code. Paper screens and fictional data let young people investigate whether an interface makes sense, while avoiding unnecessary accounts, spending and collection of personal information.
These nine ideas are hypothetical learning projects, not claims about businesses created by particular young founders. Choose one familiar problem and test a small part of the proposed solution.
Nine prototypes to explore
- A club equipment tracker. Sketch a way to show which items are available. Use invented item codes and test whether a user can record a return without confusion.
- A homework planning screen. Show a fictional set of tasks and deadlines. Test whether a learner can find the next action. Do not collect real school or account information.
- A simple materials calculator. Use a spreadsheet or paper formula to estimate card needed for a batch. Check the answer manually and include units.
- An event guide. Create a mock screen showing approved session information. Test navigation and readability before considering a public version.
- A repair reminder. Prototype a checklist for looking after a familiar, non-specialist item. Adults should approve any safety-related instructions.
- A product comparison page. Help a fictional customer compare two offers using the same criteria. Distinguish checked facts from assumptions.
- A low-waste packing planner. Arrange paper shapes to explore material use. Measure the difference rather than claiming an environmental benefit without evidence.
- An accessible instruction viewer. Present the same simple task with text, pictures and a step-by-step layout. Ask users which format helps them, without assuming one suits everyone.
- A stock warning board. Show imaginary quantities and a clear indication when an item needs checking. Test what happens at zero, a missing value and an unexpected entry.
Ask a question the prototype can answer
“Would people use this app?” is too broad for a paper screen. “Can a familiar tester find the return button?” is something you can observe.
Give a short task, watch without guiding and record where confusion occurs. Then change one feature and try again. A small number of tests offers useful clues, not proof of demand across a whole market.
Keep development proportionate
If the idea progresses, an adult should review platform age rules, account ownership, privacy, security, accessibility and costs. Avoid adding location tracking, public chat or automated decisions simply because the technology makes them possible.
The enterprise skill is connecting a useful problem with an understandable solution and evidence. Our innovation guide helps frame that problem before the design begins.
