From Idea to Working Prototype: What a Typical Hackathon Day Looks Like
Arriving With a Problem, Not a Pitch
A typical hackathon day at MS Hackathon does not begin with a polished idea. It begins with a team gathered around a table, a vague frustration, and a shared sense that something could work better. Teams are asked to bring a problem statement rather than a product concept, because a problem survives contact with reality far longer than a pitch does.

In the first hour, each team writes its problem on a shared board and reads it aloud. The goal is simple: make the problem small enough to test within a day. A problem like "communication is broken" becomes "new members cannot find the right channel in their first week." That shift from broad to specific is the first real deliverable of the day.
"If you cannot describe who has the problem and when it happens, you are not ready to build yet."
Morning: Testing the Assumption Before the Code
Before any prototype work starts, teams run a short validation round. They sketch a one-page problem canvas, list three assumptions, and mark which one would hurt most if it turned out to be wrong. Mentors rotate through the room and ask the same question to every team: what evidence do you already have?
Teams then collect quick signals. Some interview two or three people in the venue, others check existing tools, and a few simply time how long a task takes today. The output is a short list of findings written in plain language, not a slide deck.
- Who experiences the problem, and how often
- What people currently do instead
- The single assumption the prototype must test
Midday: Building the Smallest Useful Prototype
After lunch, the room shifts into build mode. Teams aim for the smallest prototype that can answer their main question, whether that is a clickable screen, a script, or even a paper mockup used in a live conversation. Fancy technology is optional; a clear test is not.
Timeboxes keep the afternoon honest. Teams work in focused blocks and regroup at fixed checkpoints, where they report what changed and what is still untested. The table below shows how a typical day is paced.
| Time | Activity | Output |
|---|---|---|
| 09:00 | Problem framing | One-sentence problem statement |
| 10:30 | Assumption testing | Short list of findings |
| 13:00 | Prototype build | Working demo or mockup |
| 16:30 | Peer review | Written feedback notes |
Afternoon: Showing the Prototype to Real Users
The most valuable part of the day is when teams put their prototype in front of someone who did not build it. They observe, stay quiet, and write down what confuses people. This is not a demo contest; it is a test session with a friendly audience.
Teams capture feedback in a structured way so nothing gets lost. A simple routine works well:
- Show the prototype without explaining it first.
- Ask the person to complete one task.
- Note where they hesitate or ask questions.
- Write one sentence on what you would change next.
Leaving With Notes You Can Keep Using
The day ends with a short closing round. Each team shares its problem statement, what it tested, and what it learned. Nobody is graded on how finished the prototype looks. The measure of success is whether the team leaves with notes that still make sense a week later.
Those notes become the real takeaway: a validated or challenged assumption, a list of observed friction points, and a clear next experiment. Many teams continue after the hackathon precisely because the notes point to the next question. The prototype may be thrown away; the learning is designed to be kept.
