01 / Explore
Together, list 3–5 ideas around your topic. Who could each idea help? Bring examples or links to explain the need.
Aim for → a shortlistYOUR HACKATHON FIELD GUIDE · 01
Build together. Help people with a real need.
Try a simple version you can share.
Facilitator’s suggested plan • Sacramento, October 19, 2026
THE RUN OF SHOW · 02
Suggested 12:45–3:45 PM Pacific sprint.
Follow the organizer’s actual demo deadline.
Together, list 3–5 ideas around your topic. Who could each idea help? Bring examples or links to explain the need.
Aim for → a shortlistGive everyone a few quiet minutes to think. Share your favorites, then choose an idea to try as a team.
Aim for → one problemDraw what someone would see and do. Make up an example, such as a question they might ask.
Aim for → a sketch of the stepsWork together on the main task your idea helps with. Check in at 2:10 and 2:40. Simplify or ask for help if needed.
Aim for → a first versionTry your idea together, save screenshots, and practice showing it. Unfinished parts are okay—explain them.
Aim for → a clear storyWHEN THE TEAM IS STUCK · 03
A little quiet thinking time helps everyone bring their ideas to the team.
Each person writes their top 3 ideas. For each: who needs it, what hurts, and what a useful result looks like.
One minute each to explain. Give 3 points to your favorite, 2 to second, 1 to third. Highest total wins.
If you are tied, try the idea that is easiest to show with made-up examples. Agree as a team to explore it for today.
MAKE THE WORK SMALL · 04
A question, a sample letter, or a job description. Have one example ready.
What will your idea help them do? For example, explain a letter or find a resource.
A clear answer, a next step, and the source or uncertainty behind it.
I am building a three-hour civic hackathon prototype. Our user is [person], their problem is [problem], and our desired outcome is [outcome]. Here is the event brief: https://luma.com/h4h-sacramento. Propose the smallest end-to-end flow with sample input and output, three acceptance checks, and what to cut. Use fictional data. Clearly label simulations and assumptions. Ask only the questions that would change the build.
THE IDEA SHELF · 05
Pick one. Remix it. Make it local.
These are starter concepts, not official challenge tracks.
Quick start: SOQ Coach for a text-only flow, or SMS Resource Finder with a small sample dataset. Try voice only if your team already has the setup working.
SHOW THE CHANGE · 06
A demo is a short walkthrough of your idea.
Try 90 seconds for practice; follow the organizer’s time on stage.
“This is Sam. They’re trying to ___, but ___ gets in the way.”
Use made-up information to show the steps. Describe what someone would do and how your idea helps.
What became easier? Which parts are working, and which are examples? What would you ask someone who might use it?
KEEP THESE HANDY · 07
Keep this page open and refresh when your facilitator announces an update.
sacramento-ideas.jacksonthedev.chatgpt.site/guideYOUR TEAM’S FOCUS
Suggested schedule · Pacific time · Follow your facilitator’s instructions