Challenge selection
A draft decision framework for choosing the track where your team has the best odds.
The first principle
The best challenge is not always the most exciting one. It is the challenge where your team can produce the clearest proof under the constraints of the event.
You are choosing an arena. The arena should reward what your team can actually make visible.
Score the challenge
| Signal | Strong | Weak |
|---|---|---|
| Problem clarity | The user and painful moment are obvious within the first hour. | The team needs a long explanation before the problem makes sense. |
| Proof path | A small prototype can prove the main claim. | The claim requires scale, partnerships, or behavior change to be credible. |
| Team edge | The team has relevant skills, context, or taste for this arena. | The team is learning the domain and the tooling at the same time. |
| Judge fit | The judging criteria reward the kind of evidence you can show. | The rubric rewards things you cannot build or validate this weekend. |
Choose with constraints in mind
Ask what the team can make real by the judging deadline. A technically ambitious idea is fine if the visible proof can be narrow. A broad platform idea is dangerous if the judges only see a half-connected dashboard.
Draft selection prompt
Write one sentence before committing:
We should choose this challenge because we can prove [claim] for [user] by showing [demo evidence] before judging.
If the sentence is vague, keep searching or shrink the idea.