A simple four-week build cycle with one mission, one deliverable, and one feedback loop each week.
Updated 1d ago
The fellowship uses a simple rule: freedom inside a clear frame.You choose what you build. The program gives you deadlines, deliverables, feedback, and a way forward when you get stuck.
Week 1 — Define
Choose a problem, curiosity, or idea small enough to finish.Your deliverable:
one sentence describing what you want to make
who it is for
what the smallest useful version looks like
what success would mean after four weeks
If you cannot explain the project in 30 seconds, make it smaller.
Week 2 — Build the rough version
Make the first version real. It can be ugly, incomplete, and technically simple.Your deliverable:
something that works or can be demonstrated
a link, screenshot, video, or physical prototype
a short note describing what works and what does not
Do not polish something that does not work yet.
Week 3 — Get reality into the loop
Show the project to at least three real people who could use, understand, or react to it.Your deliverable:
what you showed them
what confused or surprised them
the one or two changes you will make next
AI feedback is useful, but it does not replace showing your work to people.
Week 4 — Improve and ship
Make the important changes, publish the project, and close the loop.Your deliverable:
the final version
a short explanation of what changed
what you learned
what you would do next if you continued
Finished beats ambitious.
Every week
Each session answers three questions:
What did you make?
What got you stuck?
What are you doing next?
Progress is judged by evidence, not by sounding impressive. A tiny finished project is better than an ambitious project that never leaves your notes.
