30 Days of Build in Public
Thirty small actions that move from a private intention to one honest public launch. No audience or finished product required.
How the challenge works
Complete one small action each day. Most days should take less than thirty minutes beyond the work itself. If you miss a day, continue with the next action. This is practice, not a streak contest.
Keep private information private. You may complete a day in a private scratchpad when publishing would be unsafe or premature.
Week 1: Give the work a shape
Day 1: State the beginning
Write one sentence: “I am beginning to work on...” Keep it literal.
Day 2: Name the person and situation
Describe one person who experiences the problem. Do not use “everyone.”
Day 3: Define the first proof
Write what can exist after seven days that does not exist now.
Day 4: Create the README
Use the project README template. Publish only what is true today.
Day 5: Show one artifact
Share a sketch, commit, paragraph, screenshot, test, or prototype. Remove private details first.
Day 6: Write your boundaries
List what you will share and what will remain private.
Day 7: Publish a weekly note
Record what changed, what did not work, and the next smallest outcome.
Week 2: Learn to explain the work
Day 8: Explain one decision
Name two options and why you chose the current one.
Day 9: Show before and after
Place an earlier artifact beside today's version. Explain the reason for the difference.
Day 10: Report a failure
Describe one approach that did not work and the evidence that changed your mind.
Day 11: Teach one small thing
Explain a command, design choice, customer question, or workflow you learned while building.
Day 12: Remove one vague sentence
Review your project page and replace marketing language with a literal statement.
Day 13: Make one limitation visible
Add a “does not yet” statement to your README or project page.
Day 14: Write the second weekly note
Compare the week with your original assumption. Do not measure only reactions.
Week 3: Invite useful feedback
Day 15: Ask one focused question
Tie the question to a decision you need to make this week.
Day 16: Find the relevant room
Identify one community where people already experience the problem. Read its rules before posting.
Day 17: Watch someone try it
Observe one person using the artifact. Do not explain unless they cannot continue.
Day 18: Record feedback without obeying it
Write the situation, evidence, interpretation, and possible decision separately.
Day 19: Find the underlying problem
Group different feature requests by the difficulty behind them.
Day 20: Close one loop
Show what changed because of feedback, or explain why you chose not to change it.
Day 21: Write the third weekly note
Name the strongest signal and the loudest distraction from this week.
Week 4: Prepare something to launch
Day 22: Define the launch boundary
Write what this version includes and what it intentionally excludes.
Day 23: Choose one primary action
Decide whether the visitor should try, install, read, contribute, contact, or buy.
Day 24: Test the path
Open the project as a new visitor on mobile and desktop. Fix the first point of confusion.
Day 25: Make a real demonstration
Capture a short demo or a sequence of screenshots showing the actual outcome.
Day 26: Write the launch note
Explain the problem, current solution, evidence, limitation, and invitation.
Day 27: Choose the launch room
Select one place containing relevant people. Adapt the context to that community.
Day 28: Ask one person to review
Request a clarity and privacy check, not praise.
Final two days
Day 29: Launch something small
Publish the current version and stay available for questions, bugs, and conversations.
Day 30: Write the retrospective
Record the goal, actions, results, surprises, failures, and next decision. Thank people who helped without turning the result into a victory speech.
Completion is not the goal
At the end, keep the pieces that helped your work: perhaps a weekly note, a decision log, or one trusted community. Remove rituals that existed only to complete the challenge.
The useful habit is not posting every day. It is making, noticing, explaining, listening, and continuing.