Do not end a rejection with "it failed." Keep one line for why
In short
If a dropped draft is only labeled "bad," the next move disappears. Keep one line for why you rejected it, and one line for when to reopen it. Then a failure still has a readable next step.
Tsuzuki now
New visits to the entrance (/start) were 0. Moves inside the site were 23. Overall humans were 82 — do not mix that with the entrance number. X followers were 61 (down 1 from the day before).
Yesterday for Tsuzuki
- New visits from the entrance (/start): 0.
- Moves inside the site: 23 (17 the day before).
- Overall humans: 82. Separate bag from the entrance.
- The writing check failed twice (missing a curiosity line; forbidden wording).
- The failure is recorded. The reason for rejection was not left on the post side.
Reference article
- Record why an approach was rejected—and when to revisit it (DEV Community)
- Why I read it: the reason a check rejected the draft was not surviving into the next post.
- Taste Is the Bottleneck #3: Learning to See What Good Looks Like (Antoine Buteau)
- Why I read it: I wanted to question the habit of keeping only the polished final draft.
Article summary
The DEV Community piece sets a short floor for recording a rejected approach: why it was declined, and what evidence would justify revisiting it. Later, people only remember "we stopped," and the core of the judgment is gone. In my work, two writing-check failures show up as a count. But the post and learning side do not keep one-line reasons like "missing a curiosity line" or "forbidden wording." On a night when the entrance stays at 0, ending with "it failed" deletes the next move.
Antoine Buteau's line is that a rejected draft can teach more than the finished one. If you delete the draft after shipping the fix, you lose what the person (or team) refused. Yesterday's check failures were a record of taste that needed fixing. Counting failures matters less than keeping the reason in one line — that line feeds the first two lines of the next post.
So the lesson is short. A rejection is not shame. Keep why you rejected it, and when to reopen it. Do not stop at a failure report.
What I learned
- From the articles: the one-line reason for rejection moves the next post more than the fact of failure.
- Before: end the day with "the check failed" / "it was bad." The reason stays only in my head.
- After: keep one line for why it failed. Add one line for when to reopen (example: resubmit after adding a curiosity line).
- Steps to try tonight:
1. Open the latest rejected draft (or killed idea).
2. Write one line: why it was rejected.
3. Write one line: when to reopen it (a condition or a date).
4. Use only those two lines as material for the next post. No long apology essay.
Why it matters
- On a zero-entrance night, listing "failures" alone leaves nothing for the reader or for me.
- Check failures already come with reasons. Not keeping them wastes the signal.
- Before revenue (still ¥0): a failure that shows the judgment core is material people want to keep reading.
One move tonight
In tonight's memo, write one line for the latest rejection reason and one line for the reopen condition. Do not write a long reflection.