Summary Brainstorming - G33-Moviles-2026-1/Wiki GitHub Wiki
Brainstorming Process and Resulting Solutions
1) Brainstorming Objective
The goal of the brainstorming session was to generate possible solution ideas to address the problem of students not having clear, reliable information about which classrooms/spaces are available between classes, and the resulting wasted time, stress, and overcrowding in common areas.
2) Brainstorming Method and Procedure (C2)
We followed a structured brainstorming flow:
-
Restate the problem clearly
We started by aligning on the core problem: students need to quickly find a suitable available space (study/rest/work) during gaps between classes. -
Divergent ideation (“Yes, and…”)
Each participant proposed a feature/idea starting from a simple base concept and then expanding it with the “Yes, and…” technique to encourage quantity and variety of ideas, without judging feasibility at this stage. -
Capture ideas as solution components
Every idea was written down as a potential function or requirement (e.g., reporting incorrect availability, filters, favorites). The focus was on collecting ideas rather than selecting them immediately. -
Group and synthesize
After generating ideas, we clustered them into themes (availability + validation, room details, personalization, sharing, etc.). This step helped us turn many scattered suggestions into a small set of coherent solution directions. -
Derive solution proposals from clusters
Finally, we converted the clusters into “solution packages” (sets of features that work together) that could later be prototyped and tested.
3) Solutions Derived from the Brainstorm (Synthesized)
From the collected ideas, we derived the following solution directions (each one combines multiple brainstormed features into a coherent concept):
Solution A — Real-Time Room Finder + Reliability Layer
A system that shows which rooms are available right now, while also improving trust in the information through user feedback.
Included ideas: empty room listing; user reporting when a room is not actually free.
Solution B — Room “Profile” Information for Better Decisions
Room availability alone is not enough; students need to know whether a room fits their needs (study vs. group work vs. rest).
Included ideas: capacity/seats; power outlets/chargers; projector/multimedia support.
Solution C — Personalization Based on Schedule, Location, and Habits
Students should not have to search manually every time; the system can anticipate their needs during gaps.
Included ideas: upload schedule to detect free gaps; recommend closest rooms; show frequently used rooms (history); favorites list.
Solution D — Coordination and Sharing Within the Student Community
Finding a room is often social (friends or group work), and coordination reduces repeated searching.
Included ideas: share an available room with friends; (optional) reservation to signal occupancy to others.
4) How These Solutions Were Derived (Traceability)
| Brainstormed Idea | Cluster/Theme | Resulting Solution(s) |
|---|---|---|
| Show which rooms are empty | Real-time availability | Solution A |
| Report when a room is not actually free | Trust / validation | Solution A |
| Show room capacity | Room details | Solution B |
| Show outlets/chargers | Room details | Solution B |
| Show projector/multimedia | Room details | Solution B |
| Upload schedule to find rooms in gaps | Personalization | Solution C |
| Filter by building/floor | Search & navigation | Solution C (and supports A) |
| Recommend closest rooms | Location-based relevance | Solution C |
| Show frequently used rooms | Personalization / history | Solution C |
| Favorites list | Personalization | Solution C |
| Share available room with friends | Social coordination | Solution D |
| Make reservations | Coordination / signaling | Solution D |