Restarting the Writing Experiment
I have a confession: I’ve started and abandoned more “writing habits” than I can count.
Notion weekly reflections. Twitter threads. WeChat articles. Journaling apps. Every time it starts the same way — a burst of motivation, two or three solid entries, then the gap between posts stretches from a week to two weeks to “I’ll get back to it.” I never get back to it.
The pattern is so predictable it’s almost funny. Week 1: “This time is different!” Week 3: the Notion page is still open but I haven’t typed anything. Week 5: I quietly archive the template and pretend it never happened.
I’m restarting this experiment. Again. But this time, instead of relying on willpower — which has a well-documented track record of failing me — I’m trying to design a system that works with my laziness, not against it.
The framework is simple: increase positive feedback and reduce friction. That’s it. Two levers. Let me explain what I mean.
Why We Quit
First, an honest diagnosis of why “consistent writing” is so hard for people like me.
The feedback loop is broken. You write a weekly reflection. Nobody reads it. You write another one. Still nothing. There’s no signal telling your brain “this was worth the effort.” And without that signal, motivation decays exponentially. You’re running on a treadmill in a dark room — technically making progress, but it doesn’t feel like it.
The friction is too high. Opening Notion, finding the right page, remembering the template, figuring out what to write about, writing it well enough to not feel embarrassed — each step is a tiny barrier. Individually they’re nothing. Stacked together, they’re enough to make “I’ll do it tomorrow” the path of least resistance. Every. Single. Time.
Here’s the thing I finally realized: these two problems aren’t independent. They feed each other. Low feedback makes you less motivated, which makes even small friction feel insurmountable. High friction slows you down, which means fewer reps, which means less chance of getting the feedback that would keep you going.
It’s a doom loop. And you can’t break it by “trying harder.”
Lever 1: Increase Positive Feedback
The first question I asked myself: what would make writing feel rewarding before anyone reads it?
Because here’s the trap — if your feedback depends on external validation (likes, comments, readers), you’re at the mercy of algorithms and audiences you can’t control. The first few posts will get zero traction. That’s just math. And if zero traction = zero reward, you’ll quit before the flywheel ever has a chance to spin.
So I need intrinsic feedback loops — rewards that come from the act itself, not from the response.
Make progress visible
One of the simplest tricks: just seeing a growing list of posts is rewarding. I set up this site as a digital garden — a book-index-style list of everything I’ve written. Every time I publish something, I see the list get one line longer. It’s a tiny dopamine hit, but it’s real.
This is the same psychology behind GitHub contribution graphs and streak counters. You’re not doing it for the green squares. But the green squares make you not want to break the chain.
Write to think, not to perform
My past attempts failed because I was unconsciously writing for an audience. Even in a private Notion doc, I was editing sentences, worrying about structure, trying to sound smart. That’s not journaling — that’s performing.
The reframe: writing is thinking made visible. If I wrote something and my own understanding of a topic became clearer, the writing already succeeded. The audience is future me. That’s it. Anything beyond that is a bonus.
This isn’t just a mindset shift. It changes what I write. Instead of polished essays (high effort, high expectations, low output), I can write rough observations, half-formed hypotheses, questions I don’t have answers to. The bar drops from “publishable” to “useful to me.”
Connect ideas across time
One thing that makes writing compound: seeing patterns across your own thinking. When you write down an observation in January and it connects to something you noticed in March, that’s genuinely exciting. It feels like your brain is building something, even if no one else can see the blueprint yet.
This is why I like the digital garden format over a chronological blog. Blog posts are events — they happen and recede. Garden entries are nodes — they connect and grow. Revisiting an old entry and adding a link to a new one is its own reward.
Lever 2: Reduce Friction
The second lever is more mechanical but arguably more important. Motivation fluctuates. Friction is constant. If the process is easy enough, you’ll do it even on days when motivation is at zero.
Lower the quality bar (seriously)
My biggest friction wasn’t technical — it was psychological. The voice in my head that says “this isn’t good enough to publish.” That voice has killed more writing habits than any software limitation ever could.
The fix: explicitly give myself permission to publish rough work. Not every post needs to be a 2,000-word essay with subheadings and a thesis. A 200-word observation is fine. A single paragraph with a question mark at the end is fine. An incomplete thought tagged as “draft” is fine.
The goal is reps, not masterpieces. You don’t get better by writing one perfect essay a year. You get better by writing fifty imperfect ones.
Shorten the path from thought to published
Every step between “I have a thought” and “it’s live on the site” is friction. So I mapped the pipeline and cut everything I could:
Before (the old way):
- Have a thought
- Open Notion
- Find the right page
- Figure out the format
- Write
- Edit
- Second-guess
- Close the tab
- Never publish
Now:
- Have a thought
- Tell my AI copilot: “write about X”
- Review the draft
- Say “publish”
- It’s live
The technical details: this site runs on Astro with Markdown files in a Git repo. My AI copilot has a publishing skill that creates the file, adds the frontmatter, commits, and pushes. The entire publish flow is one conversation. No context-switching, no template-hunting, no deployment pipeline to manage.
Is this “cheating”? I don’t think so. The thinking is still mine. The ideas, the observations, the connections — those come from my brain. The copilot helps me get them out of my head and into a format that’s publishable, without the friction of formatting, file management, and deployment being the reason I give up.
Make capture effortless
The best insights don’t come when you’re sitting at your desk with “Write Weekly Reflection” on your calendar. They come in the shower, on a walk, in the middle of a meeting. If capturing them requires opening a specific app and following a template, most of them evaporate.
My approach: capture first, structure later. I jot down raw thoughts whenever they hit — in a chat with my AI agent, in Apple Notes, in a voice memo. The bar for capture is “would I understand this tomorrow?” Not “is this ready to publish?” Once I have a pile of raw captures, turning one into a post is much easier than staring at a blank page.
The Meta-Experiment
Here’s what I’m actually testing with this restart:
Hypothesis: If I reduce friction enough (< 10 minutes from idea to published post) and create intrinsic feedback loops (visible progress, thinking-as-reward), I can sustain a writing practice longer than my previous attempts.
Success metric: Still publishing at least once a week, 8 weeks from now. Not word count. Not quality. Just consistency.
Why 8 weeks: My longest streak was about 5-6 weeks. If I’m still going at 8, something is genuinely different this time.
I’ll be honest — I’m not confident. The track record is what it is. But I think the framing is different this time. I’m not trying to build a “content habit.” I’m trying to build a thinking practice that happens to leave a trail. The public artifact is a side effect, not the goal.
And if I quit again? That’s data too. I’ll know the two-lever framework isn’t sufficient, and I’ll need to find a third lever — or accept that writing just isn’t my medium.
But I don’t think that’s true. I think the problem was never motivation. It was design.
Let’s see.