Problem Lab / Submit
You noticed
something.
The people who see a problem clearly are usually the people living with it. You do not need a solution, a team or a technical background to write one down — a precise description is the hard part.
What makes a good submission
Specific beats broad
“The library catalogue does not include past question papers” is workable. “The library should be better” is not.
Describe the problem, not the app
Jumping to a solution narrows what a team can consider. Say what goes wrong instead.
Consequences matter
Who loses what, and how often? That is what decides whether anyone should spend a term on it.
You can be wrong
A submission that turns out to be a misunderstanding is still useful — it tells us where things are unclear.