# Seven days after a hackathon

Use this sheet with a teammate to test the prototype you showed on demo day. Keep one copy per week so you can compare versions and decisions.

Project ____________________  Week beginning ____________________

## Day 1. Save the working path

- Prototype version or demo link ____________________
- Test owner ____________________
- The person using it is ____________________
- Their starting situation is ____________________
- They finish when I can observe ____________________
- The steps our team still does manually are ____________________

## Day 2. Invite people who face the problem

Aim for five relevant invitations through a route each person has agreed to use. A role or short participant code is enough for this sheet. Count each person once.

| Participant code | Relevant role or recent experience | Invitation sent | Replied | Conversation held |
| --- | --- | --- | --- | --- |
| A | | | | |
| B | | | | |
| C | | | | |
| D | | | | |
| E | | | | |

Conversation opener you can adapt — “I’m working on [task]. Would you have ten minutes to walk me through the last time you did it?”

## Day 3. Understand one recent example

Repeat this block for each conversation you actually have.

- Participant code ____________________
- What triggered the task? ____________________
- Which steps and tools did they use? ____________________
- Where did the current process work well? ____________________
- What effort or delay did they describe or show? ____________________
- What would make our proposed solution unnecessary? ____________________

## Day 4. Design a fair test

Write the rule before a participant sees the prototype.

- The situation I will read to each person ____________________
- The sample data or fresh starting state ____________________
- A correct outcome I can observe ____________________
- What counts as help ____________________
- Minimum number of attempts for this decision ____________________
- If I see ____________________, our next action will be ____________________.
- If the same obstacle appears ____________________ times, we will ____________________ first.

## Day 5. Record attempts and assistance

Use the same task for all attempts in one test. Mark the version used. Fill the results with “unaided finish,” “assisted finish,” or “did not finish.”

| Participant code | Version | Result | First point of confusion | Hint given, if any |
| --- | --- | --- | --- | --- |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |

Unique people invited ____ · replied ____ · tried the task ____ · completed unaided ____ · completed with help ____.

## Day 6. Check the next opportunity

- Participant code ____________________
- Their next occasion to do the task ____________________
- Follow-up they agreed to, if any ____________________
- When that occasion happens, record observed use, no use, or unknown ____________________
- Any change made to the prototype and its new version ____________________

## Day 7. Choose the next week’s work

- The rule we wrote on day four was ____________________
- Our strongest observation was ____________________
- The observation that challenged our assumption was ____________________
- We still need to learn ____________________
- Our decision and the evidence behind it ____________________
- The next task, its owner, and review date ____________________

## What can your prize actually pay for?

Copy this receipt once for each benefit. If a deadline or condition is missing, write “unknown” and name the person who will confirm it.

- Event, award tier, and link to the organizer’s terms ____________________
- Benefit and amount, with unit or currency (cash, provider credits, or an interview) ____________________
- Recipient and usable account (team representative, individual, or project) ____________________
- Award date, claim deadline, and usable period or expiry ____________________
- Conditions, permitted costs, or next interview step ____________________
- What has actually arrived, and on what date? ____________________
- Cash received and available to this team for the next test ____________________
- Next test expense the credit will cover ____________________
- Next test expense that still needs cash ____________________

For example, at VibeCon San Francisco on October 24–25, 2026, each builder’s account received 2,000 Emergent credit units for the event. Only the lead’s account funded the shared build. After judging, each top-ten finalist received $1,000 in Emergent credits plus partner perks. The first-place team received $10,000 cash and a YC interview for a future batch. Keep the invitation as its own receipt until you know the interview outcome. [VibeCon team and credit rules](https://vibecon.com/rules) · [Emergent’s prize results](https://www.webwire.com/ViewPressRel.asp?aId=363611)

For Google Cloud’s GKE Turns 10 hackathon, submissions ran from August 18 to September 22, 2025. The grand prize included US$15,000 cash and US$3,000 in credits for a Cloud Billing Account. The rules assigned team cash to the representative to allocate and excluded cash redemption for the credits. A team member would need the allocation and payment details to fill in their own cash receipt. [Google Cloud prize announcement](https://cloud.google.com/blog/topics/training-certifications/join-the-gke-turns-10-hackathon) · [GKE prize and delivery rules, section 9](https://gketurns10.devpost.com/rules)

[Read the free guide and fictional worked example](https://creditable.vc/guide/after-the-hackathon).
