What to do after a hackathon
You have a weekend demo. Give it to someone who faces the problem, watch one task, and use what happens to decide whether to spend another week on it. This seven-day plan and worksheet are free to use with your team.
Download the sprint worksheetOne job for each day after demo day
Save the demo someone can actually try
Keep a working copy of the version you showed the judges. Write down where a new user starts, which steps your team performed by hand, and what the user should have when they finish. Put one teammate’s name beside the test.
Find five people who do the task
Write down the role you need and where you can reach someone in that role. Ask five people if they have time to walk you through a recent example. Give each person a way to decline. Schedule a prototype trial only with people who want to try it.
Learn how the job gets done today
Ask one person to take you through the last time the problem came up. What triggered it? What did they check? Where did they lose time? Record one concrete workaround and one detail that challenges your idea. Use the conversations you have this week and record how many took place.
Choose a task and write the decision rule
Give the tester a starting situation and an observable finish. Decide what counts as an unaided finish, what counts as help, and which result would justify another week. Write the rule down before the first trial.
Watch someone use the prototype
Give each participant the same task and a fresh starting state. Let them choose their own route. If you give a hint, note the exact moment and mark the result as assisted. Ask what they expected at the first point of confusion.
Check the next real opportunity
Ask when the person will face the task again. If they want the prototype for that occasion, agree on a way to try it and follow up. Log the invitation, the agreement, and any actual return separately. Keep the original trial notes if you make a fix.
Decide what earns another week
Read the rule you wrote on day four. Choose one next action, the person who owns it, and the date you’ll review the result. If the trial never happened, record what prevented it. A scheduling delay leaves the product question open.
For help running day five, the UK Government Service Manual explains how to give neutral task instructions and when to step in during a session. Read its moderated usability testing guide.
Would a tool library use the demo on Saturday?
This fictional example follows a team that built a checkout screen for volunteers lending tools. Their demo worked when a teammate picked a drill everyone knew was available.
- What changed after an interview
- A volunteer described checking three drill cases against a paper reservation sheet while a borrower waited. The team made duplicate drill models and a reservation part of its trial.
- What the team asked people to do
- “A borrower needs a drill until Monday. Using this sample inventory, show which drill they can take and record the loan.” The sample included one drill reserved for Sunday. A correct loan left that drill on the shelf.
- Rule written before testing
- After three attempts, offer a real-shift trial if at least two volunteers finish correctly without help and someone asks to use it on an upcoming shift. If two volunteers stumble over the same label, fix that label and retest first.
- What happened in the example
- Five volunteers were invited. Four replied and three tried the task. Two recorded a correct loan unaided. Two of the three initially selected the reserved drill. One caught the conflict and corrected it. The other needed a hint.
- What the team decided
- One volunteer asked to try it on Saturday. The repeated confusion triggered the fix first. The team put the reservation date beside the drill name and booked a fresh trial with sample data. Saturday use was still unobserved.
Write the week-two decision
Leave a note your teammates can act on. Include how many people you invited, how many tried the task, what they did without help, what surprised you, and who will run the next test.
- Keep testing the working path when people complete the task and have a specific upcoming occasion to use it. Agree on what you can observe at that time.
- Fix one obstacle when people describe a real problem but repeatedly get stuck at the same step. Keep the task and the success rule stable when you retest.
- Revisit the problem when people show you an existing workaround that already handles it well. Ask where their process still takes effort.
The free course includes more customer conversation exercises. When you have results to share, the pre-seed pitch worksheet helps you describe what the prototype demonstrated.
What can your prize actually pay for?
Before you budget for another week, split the award into the things your team can claim. Two past events show why the recipient and the unit matter.
- VibeCon San Francisco · October 24–25, 2026
- During the event, each builder’s account got 2,000 Emergent credits. A four-person team still started with 2,000 usable credits for its shared project because it ran on the lead’s account. After judging, each top-ten finalist received $1,000 in Emergent credits plus partner perks. The first-place team, Manceps, won $10,000 cash and an interview for an upcoming Y Combinator batch. Admission still depended on YC’s decision. VibeCon’s team and credit rules · Emergent’s prize results
- Google Cloud’s GKE Turns 10 · August–September 2025 submissions
- The grand prize included US$15,000 cash and US$3,000 in Google Cloud credits for a Cloud Billing Account. The rules directed a winning team’s cash to its representative, who would decide how to allocate it among members. The credits could cover eligible cloud use and had no cash redemption. Google Cloud’s prize announcement · GKE prize and delivery rules, section 9
Make a receipt for your next test
Use one worksheet entry per benefit. Record the recipient or account, the amount and unit, the claim deadline and expiry, and any conditions still open. For an interview, record the invitation and next step. For a cash award, record what has arrived and who can spend it. Compare that available cash with the costs your provider credits cannot cover.
Share what you’re building
Send a working title and a short description for private review. Add a deck if you have one.
Open the short applicationApplying creates no commitment.