Prove
All outcomes
Skills

Build a Writing Habit (365 Consecutive Days)

52 weeks · 0 milestones

Write and publish at least 200 words every day for 365 consecutive days — public log or newsletter as proof.

Milestone map

Milestone map

3 milestones

Design the writing practice and complete first 30 days

30 days

Before day 1, define exactly what format your writing will take, what counts as a completed writing session (minimum word count or time), where the work will be recorded, and how timestamps will be preserved. Public writing (blog, newsletter, GitHub repository for technical writing) is the preferred format because it produces self-verifying timestamped evidence without any additional documentation burden. Private journaling is acceptable but requires a timestamped app (Day One, Obsidian with git commits, or equivalent) rather than a paper notebook.

Proof required

Submit your writing practice specification (format, daily minimum, platform or app, timestamp method) alongside your evidence for days 1–30: 30 URLs with publication dates (public writing), a screenshot gallery of the app's monthly calendar view showing all 30 days marked (journaling app), or a git log showing 30 daily commits (technical writing). A gap in the first 30 days restarts the streak from the last continuous day.

What gets checked

  • Platform choice produces self-evidencing timestamps — a public blog post URL with a published date, a git commit date, or an app calendar view with dates checked; 'I wrote in a notebook' without any timestamped evidence is not acceptable
  • Daily minimum is specific and appropriate for daily habit formation — 200 words or 20 minutes is a sustainable minimum; 'as much as I feel like' is not a defined minimum
  • First 30 days show no gaps — streak continuity from day 1 is the core proof standard; a gap means the streak restarts

Common mistakes

  • Selecting a private format without planning the timestamp evidence in advance — a paper journal produces no verifiable timestamps; decide on the timestamp method before day 1, not when it comes time to provide proof
  • Setting a daily minimum that is too ambitious — a 1000-word daily minimum is unsustainable alongside other commitments; a sustainable minimum is one you can meet even on your worst day of the year

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Ask the submitter to show the first and last post/entry of the 30 days — confirm the timestamps are 30 consecutive days, not 30 posts spread across a longer period.
  • Ask what they do when they miss a day — the answer should be 'I restart the streak'; if they say 'I don't miss', ask what their recovery plan is for travel, illness, or emergency.
  • Ask what the writing is about — tests that it is genuine work, not placeholder text or AI-generated content.

You'll sign in first, then come straight back here.

Complete days 31–180 — the attrition zone

150 days

The period from day 30 to day 180 is where almost all multi-month habit attempts fail. The initial novelty and motivation have worn off but the identity shift of being 'a daily writer' has not yet solidified. Completing this stretch requires a streak-defence system: a rule for what to do when you have almost no time (a one-sentence minimum to preserve the streak), a make-up protocol for near-misses, and deliberate engagement with the writing community if the format is public. The evidence standard for this milestone is the same as M1 — timestamps for every single day.

Proof required

Submit evidence for days 31–180 in the same format as M1 (URLs, app calendar screenshots, or git log). The evidence must show no gaps in the streak. Include a 300-word written reflection on what changed in your writing practice between day 30 and day 180 — what became easier, what remained difficult, and one specific thing you learned about your own writing.

What gets checked

  • Streak evidence covers the full 150-day window with no gaps — the same timestamp standard as M1 applies throughout; a gap means the streak restarts from the last continuous day
  • Reflection is specific and personal — not generic ('it got easier') but a named specific change ('my daily session time shifted from morning to evening after the first month because I realised I was arriving at morning sessions too tired to write well')
  • Reflection mentions at least one specific thing the writing produced — a piece of work, a habit, or an insight that would not exist without the streak

Common mistakes

  • Abandoning the streak at the first gap rather than resetting the counter — resetting from the most recent continuous day and continuing is not failure; quitting entirely when a gap occurs is the real dropout pattern
  • Writing placeholder content to preserve the streak without genuine engagement — 'I wrote today' as a single line preserves a streak record but does not develop a writing practice; the daily minimum should produce genuine work

Resources

What a verifier looks for

  • Sample five random dates from within days 31–180 and ask the submitter to show the entry or post for each — random sampling tests that the coverage is complete, not just the first and last day.
  • Ask about the most difficult week in the 150-day stretch and how they got through it — tests genuine sustained effort.
  • Read or ask about the reflection — confirm it names a specific change, not a generic summary.

You'll sign in first, then come straight back here.

Complete the year and write a year-in-review

185 days to complete + 1 week to write the year-in-review

Complete the final 185 days and write a year-in-review reflection of at least 1000 words. The year-in-review must do more than summarise the streak — it must curate the best or most significant work produced, identify how the writing changed over the year, and make a specific claim about what the sustained practice built that could not have been built another way. This is the public-facing artifact that makes the outcome sharable and credible.

Proof required

Submit evidence for days 181–365 (same timestamp format) plus your year-in-review document (1000+ words). The year-in-review must include: a count of total words or posts produced over the year, links to or excerpts from at minimum three pieces you consider your best or most significant work, a specific description of how your writing at day 365 differs from day 1, and one claim about what the year of writing built that you would not have had otherwise.

What gets checked

  • Evidence covers days 181–365 with no gaps — the same streak-continuity standard applies to the finish as to the start
  • Year-in-review names three specific pieces of work from the year with explanation of why each was significant — not 'I wrote about lots of things' but named, citable work
  • The 'what this built' claim is concrete and non-generic — not 'I became a better writer' but 'I now write my first draft without editing, which reduced the time to publish from 4 hours to 90 minutes' or 'the streak produced a 40,000-word first draft of a book'

Common mistakes

  • A year-in-review that is a summary of topics covered rather than a reflection on the practice and what it built — the review must evaluate the outcome of the habit, not just catalogue the output
  • Treating the year-in-review as an afterthought — the year-in-review is the proof artifact that makes the streak credible to a reader who did not follow it; it should be written with the same care as the best work produced during the year

Resources

What a verifier looks for

  • Ask the submitter to share one piece from the year that they are most proud of and explain why — confirms genuine investment in the work, not mechanical compliance with a daily minimum.
  • Ask how the writing practice has changed their relationship to the subject they write about — tests whether the habit produced something beyond output volume.
  • Verify the timestamp evidence covers the full 365-day period — random-sample five dates across all three milestone windows.

You'll sign in first, then come straight back here.

We use analytics to improve Powstik. No ads, ever.