TL;DR A milestone tempts you to celebrate the number and then re-run the same streak. I did something else with the journal after post 100: I redefined what the next hundred are for. Three moves you can run on any recurring output you own, whether posts, releases, or weekly updates. Widen the surface past the label you started with, put one stealable tool in every unit, and turn the broadcast into a room. Post 101 starts here.
Last week, I published my hundredth post and wrote a retrospective about what a hundred essays actually taught me. Then I opened a blank file for the next one and felt the pull every milestone creates. Do it again. Same cadence, same lane, keep the streak alive. Post 101, then 102, all the way to 200.
I almost did exactly that. It is the comfortable move, and it is a trap, and not just for writing.
A round number feels like a finish line, so you cross it again. But a hundred of anything is really a pile of evidence about what the next hundred should become. The streak proves you can produce. It says nothing about whether you are producing the right thing, at the right width, for the right people. I had two years of proof that I could hit publish every week. I had almost no deliberate answer to the question sitting underneath it: publish what, for whom, to do what?
Operators walk into this everywhere, not just on a blog. You hit a rhythm on releases, on weekly updates, on the standup, on your own role, and somewhere in the rhythm, you start mistaking the cadence for the goal. The machine runs. Nobody stops to ask if it is pointed at anything worth hitting. Continuing is the path of least resistance. Redefining is the work.
The PM lesson
A milestone is not a finish line to re-cross. It is a checkpoint to redefine the mission. The output proves you have capacity. The next batch needs a purpose you set on purpose, or it drifts into more of the same as what you already did.
So I sat down and rewrote the brief for the journal. Three changes, and they generalize to any operator sitting on a streak. I call the move the next-100 reset.
Move 1: Widen the surface
I had quietly labeled this a product management blog. By post 100, that label was a lie of omission. The actual job stopped being narrow product management somewhere in year one: hiring, deciding what not to do, holding focus, sitting in a Level 10 meeting, keeping a small team out of the weeds. Pretending the journal was only about roadmaps left out most of what the work really is.
The next hundred lean into the whole operator craft. Same thinking tool, bigger surface area.
Here is the part that is not about me. The label you picked at unit one is almost always too narrow by unit one hundred, because you chose it when you understood less. Your product’s story, your role, and the remit of your roadmap: each was scoped based on what you could see at the start. Widening the surface does not mean losing focus. Focus is about the core idea you keep returning to. The surface is which problems you let that idea touch, and it should grow as you do.
Move 2: Ship something they can steal
Too many of my posts stopped at the insight. Insight is cheap. The expensive part is the thing a reader can actually run on Monday morning. So the rule for the next hundred is blunt: every post ships at least one thing you can steal, a checklist, a template, a decision rule, a worked example. If you cannot lift it and use it this week, I have not finished the post.
Let me prove the rule inside the post that announces it. Here is the first stealable tool, and it comes from the least flattering number I own.
I publish constantly. Until last week, I had captured zero email subscribers on a list I own, against about 274 followers on LinkedIn. The signup links never fired, and I never caught it because I only ever saw my own site while logged in. Owning your distribution is operator work, not a marketing footnote, which is Move 1 in action. The tool is what I now call the stranger test, and it takes about ten minutes:
- Strip your state. Log out, open a private window on a device that has never seen your site, and arrive carrying nothing.
- Do the one action that matters, for real. The signup, the checkout, the booked call, with a real address you can check, clicking the button that a stranger clicks.
- Verify and record where it landed; count it. Not a success message on a screen. The actual row in the actual list.
Run it on whatever turns attention into something you keep. Mine broke at step two: a hundred front doors, and not one opened from the outside. Steal the test. It is the cheapest hour of QA you will run all quarter.
Move 3: Turn the broadcast into a room
A hundred posts of me talking are plenty. The best thinking I have done here happened in the replies, from a few dozen operators and founders who write back with the sharpest disagreement I get anywhere. I was optimizing for a megaphone, and what I actually needed was a mirror that talks back.
So the next hundred pull that feedback loop into the work itself: guest essays from operators I steal ideas from, reader questions answered in full, and arguments I am losing laid out fairly so someone can finish beating me.
For anyone who ships updates or specs, the same move is smaller than it sounds. Your documents probably announce when they can invite. A broadcast asks for attention. A room asks for correction, and correction is where the value hides. End the spec with the decision you are least sure of, not a tidy summary. Ask for the specific disagreement you actually want from the people most likely to have it.
What to do this week
You do not need a blog to run the next-100 reset. Pick any output you produce on a recurring schedule and point it to something better.
- Name the label. Write down what you called this work when you started: the roadmap, the weekly update, the release notes, the one-on-one agenda.
- Widen the surface. Name one adjacent area you have been excluding out of habit, and let the next unit cross into it on purpose.
- Make the next unit stealable. Put one thing in it that a colleague could lift and use without you: a checklist, a template, a rule. If they cannot, you shipped a status update, not a tool.
- Trade the summary for an invitation. End it with the question or the decision you are least certain about, aimed at the person most likely to correct you.
- If you own a signup or a funnel, run the stranger test on it before you promote one more thing.
Do the first two even if you skip the rest. Most stale output is not low-quality. It is pointed at a target you set a hundred units ago and never revisited.
A worked example: the weekly update, reset
Let me run the reset on the most common recurring output there is, the weekly update, so the three moves land on something you actually produce.
Most weekly updates read like this. “Shipped the export feature. Started the billing migration. Blocked on design review. Let me know if you have questions.” It is a broadcast of activity, and it is forgettable by Friday because it leaves the reader with nothing to keep.
Here is the same update after the reset.
Widen the surface. The update stops being only a list of what engineering shipped and adds what I chose not to build: “I cut the CSV export from this release. It served nine accounts and was delaying billing for everyone.” The choice is the operator’s work. The activity is just the receipt.
Make it stealable. I add one line a reader can lift: “The rule I used to cut it: if a feature serves fewer accounts than the release it delays, it waits.” Now everyone on the thread has a decision rule they can run on their own cut this week.
Turn the broadcast into a room. I delete “let me know if you have questions” and replace it with the real one: “The call I am least sure of is holding billing another sprint to get it right, versus shipping the rough version now. [Name], you argued for shipping. Change my mind.”
Same five minutes to write. The reset version teaches a decision, hands over a rule, and opens an argument. The original just reported the motion.
Steal the skeleton:
- What moved this week.
- What I chose not to do, and why.
- One rule, checklist, or template a teammate can reuse.
- The decision I am least sure of is aimed at one person by name.
FAQ
What is the next-100 reset? A move you run at a milestone in any recurring output you own. Instead of re-running the streak, you redefine the next batch: widen the surface past your original label, put a stealable tool in every unit, and turn the broadcast into a conversation.
Isn’t widening the surface just losing focus? No. Focus lives in the core idea you keep returning to. The surface is which problems you let that idea touch. You can hold a tight spine and still let it reach wider as you learn more about the real job.
What actually makes something “stealable”? A reader can lift it and use it this week without you in the room: a checklist, a template, a decision rule, a worked example. An insight the reader admires but cannot apply is not stealable, and by this rule, it is not finished.
How do you turn a broadcast into a room without just bolting on a comment box? Design for correction, not applause. Invite a specific disagreement, answer real reader questions in full, and hand the mic to a guest whose take is sharper than yours. A comment box is passive. A real question aimed at the right person is not.
Does this only apply to writing? No. The examples here are posts because that is my streak. The move is for any recurring output: releases, weekly updates, reviews, even how you scope your own role. Anywhere you have a cadence, you have a target worth resetting.
What is the one thing to do this week? Take your most repetitive output and put one genuinely stealable thing in the next unit. That single rule drags the other two moves along with it.
What I’m doing this week
Concretely, before next Sunday, I am going back through the archive and tagging every post that contains a genuinely reusable tool. I expect the count to be lower than I would like, and that number is the honest starting line for the stealable rule. I am drafting the open call for the first guest essay. And I wrote this post, 101, with the rule already switched on: insight, then the thing you can run on Monday, or it does not ship.
A hundred posts proved I can keep a streak. That was never the hard part, and it was never the point. The next hundred are for pointing the streak at something that helps you more than it flatters me. Your streak has the same question waiting underneath it, whatever you produce on repeat. The milestone is not the moment to run it back. It is the moment to answer, on purpose, what the next hundred are for.
Leave a Reply