DEV Community

Cover image for Weekly review that lies: write what did not move before you list wins
Lo An
Lo An

Posted on

Weekly review that lies: write what did not move before you list wins

Meta description

A solo-business weekly review that only lists wins hides stalled work. Force three empty lines first: what did not move, why, and the next stop rule. Soft pointer to Idea2Wealth case reading.

Tags

solopreneur, productivity, indiehackers, ai

Most weekly reviews are vanity mirrors: shipped screenshots, busy calendars, and “learned a lot.” That format rewards motion and hides stalls. If you run a one-person business, the expensive question is not what looked good — it is what stayed stuck while you stayed busy.

Borrow the Idea2Wealth (https://aifafa.com.cn) habit of reading cases for fields you can fill. Before you write any win, force three empty lines:

  1. What did not move — a named workstream, not a mood.
  2. Why it stalled — waiting on a buyer, unclear scope, missing acceptance, or you avoided the hard call.
  3. Stop / shrink rule — the condition that ends another week of polite delay.

If you cannot fill those three, your “wins” section is entertainment.

A 20-minute Friday template

  • 5 minutes: list open promises to customers or yourself.
  • 5 minutes: mark each as moved / stalled / dead.
  • 5 minutes: write one stop rule for the worst stall.
  • 5 minutes: only then list what actually shipped.

Idea2Wealth-style case libraries help when you compare your stall pattern to someone else’s documented failure mode — not when you copy their ending sentence.

Boundaries

This is a judgment habit, not a promise that empty-line reviews create revenue. Do not invent fake stalls to look rigorous. Do not use the stop rule as self-punishment; use it to protect attention. Soft observation only — no “join us” pitch here.

Uploading image

Uploading image

Uploading image

Top comments (0)