SMALL-PROGRESS PLANNER
A Buildside resource for side project builders
https://www.buildside.app/build-in-public/side-project-builders

Use this when you want to make one useful step visible. There is no daily posting target.
Copy the blank version into your notes and return whenever you have time.

1. THE NEXT USEFUL SLICE
What is the smallest useful change I want to finish?
Who would use it, and for which task?
What is outside this slice?
How much time do I actually have for this session?
If the slice is too large, what can I remove?

2. WHAT WOULD SHOW PROGRESS?
What should someone be able to do afterward?
What would I observe to know it worked?
Evidence I can safely share: screenshot / demo / short explanation / other
What did I try, and what happened?
What remains uncertain?

3. MY RETURN-TO-WORK NOTE
Where did I stop?
Where is the relevant file, design or task?
What is the first action I should take next time?
What blocker or decision should I remember?
Keep private details in your own notes rather than in the public update.

4. ONE QUESTION, IF USEFUL
Who has relevant experience?
What exactly do I want to understand?
What context would help them respond?
Is a public question appropriate, or should I talk privately with a user?

5. OPTIONAL PUBLIC UPDATE
I am building [product] for [person or task].
This session I [specific change or experiment].
Here is what happened: [observation, with no invented result].
Next I am trying [small step].
My question is [focused question, if one would help].

Before sharing, remove credentials, private customer details, and employer/client material.
Use examples you are entitled to share. A draft can stay a draft until it is useful to publish.

ILLUSTRATIVE FILLED EXAMPLE
Project: PocketHabit, a fictional habit check-in tool.
Next useful slice: Save one check-in and display it after refresh.
Outside this slice: Reminders, accounts, streaks, payment and social features.
Evidence: A short local demo showing a saved check-in after refresh.
Observed: The sample check-in appears again after refresh in this local prototype.
Uncertain: How to help someone return after a missed day.
Return note: Open the missed-day message draft and try a kinder version.
Question: If you miss a day in a habit app, what would help you start again?
Public update: "The check-in now survives a refresh. Next I am working on a kinder
restart message. If you miss a day in a habit app, what would help you start again?"

IF YOU TAKE A BREAK
Save your next action, not an apology.
On return, reread the note, confirm what still matters, and choose a fresh small slice.
An update can say where you left off and what you are trying now.
The planner is an editorial resource, not a Buildside calendar or task-management feature.