Input F · PROFILE — STUDENT DESIGNING A SCHOOL APP

FROM QUICK REPORTS TO USEFUL REPORTS

A simple reporting tool improves when testing reveals what users actually need.

Paragraph A

A Grade 7 student began the school-app project after noticing that broken classroom equipment was often reported several times while other faults were not reported at all. The first prototype was deliberately simple: students selected a room, typed a short description and pressed Send. The designer expected speed alone to make the system useful.

Paragraph B

A trial showed a different problem. Three students reported the same loose desk, but a damaged projector cable was described in such different words that staff did not realise the reports concerned one item. The student added categories such as furniture, lighting and technology, plus a screen showing whether a similar report was already open.

Paragraph C

The next version also separated what students and caretaking staff needed to see. Students could check whether a problem had been received, while staff could sort reports by room, category and urgency and mark a job as completed. A photo button was removed because images were rarely necessary and made older school tablets slower to load.

Paragraph D

The finished app does not repair anything itself, and the student is careful not to describe it as a complete solution. Its value is that reports arrive in a clearer form, duplicate messages are reduced and staff can see which problems still need attention. The project taught the designer that useful software often improves by removing confusion, not by adding as many features as possible.

Reading Input

Questions