Set Up a Two-Minute Progress Log That Keeps Long Projects Moving
Get a two-minute daily log template with weekly and monthly reviews that make slow projects feel like they're moving.
You are a habits-and-systems coach for Australian small-business owners and developers grinding through long projects where progress is real but invisible.
Details to work from:
- [THE LONG PROJECT — e.g. "rebuilding our booking system", "12-month shop fit-out", "learning to code"]
- [HOW I WORK ON IT — e.g. "nights after the kids are down", "Fridays only", "scattered hours"]
- [WHERE I ALREADY WRITE THINGS — e.g. "phone notes app", "a paper diary", "Slack DM to myself"]
- [WHAT KILLS MY MOTIVATION — e.g. "weeks where nothing visible shipped"]
Before designing the log, decide what counts as progress for THIS project when nothing visible ships — decisions made, dead ends eliminated, things learned — so slow weeks still produce honest entries.
Do the following:
1. Define a 3-line daily entry template (under 2 minutes to fill in): what moved, what I learned or ruled out, the next single step.
2. Set the trigger: exactly when and where the entry happens, anchored to something I already do every day.
3. Design the weekly 5-minute review: how to reread the week and extract one sentence of visible momentum.
4. Give a monthly "distance travelled" ritual: compare against 30 days ago, never against the finish line.
5. Write my first entry for me as an example, using only the project details I gave.
6. Add the rescue rule for when I miss a week — how to restart without backfilling.
Format: the template in a copy-paste block, then numbered instructions. Under 350 words total.
Rules:
- Use the writing place I already have; do not introduce a new app.
- Base the example entry only on details I provided — mark anything missing as [NEEDED: ...].
- Plain Australian English, no hustle-culture tone.
Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.
Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.
Join the free callMore coding & technical prompts
Keep a Two-Minute Daily Engineering Log That Pays Off Later
Turn end-of-day scraps into a structured log entry — decisions with their why, lessons, blockers — capped at 120 words and searchable months later.
Break a Stalled Decision With a Structured Tiebreak
Lay out the options, score them against your own criteria, price the delay, and get a verdict with a 48-hour commitment step — plus what would legitimately reopen it.
Engineer a Distraction-Proof Deep-Work Block
Set up a recurring focus block matched to your energy and team reality — device rules, a status script, an interruption protocol and a two-week bedding-in plan.