My membership had a launch date. August. It sat near the top of my strategy doc in bold, and every time I opened the file it looked like a plan.
It was not a plan. It was a guess wearing a calendar.
What the date was actually measuring
Here is the thing a date does for you. It lets you feel like you are moving without telling you whether you are moving toward anything. I could build kits all summer, check them off, watch the folder fill up, and arrive at August having done a lot of work. The date would be satisfied. It does not ask the only question that matters, which is whether anyone is waiting on the other end.
So this week I deleted it. In its place I wrote a gate: 50 newsletter subscribers before the membership launches. Not a date I picked because August felt about right. A number that has to be true for the launch to mean anything.
Then I did the part that is easy to skip. I went and checked the current count.
Four.
One of them is me.
The number stung, which is how I knew it was the right one
A date never stings. That is exactly why it is so comfortable to keep on a roadmap. You can carry “August” around for two months and feel fine, because a date makes no claim about reality. It just sits there being a date.
A subscriber count does make a claim. Mine said four, and four told me the truth the date had been hiding all along. The product was never the constraint. I have a clean site, a real publishing system, kits I am proud of. The audience is the constraint. August was going to be a launch into an empty room, and the date was never going to warn me about that. It is not built to.
A date measures time passing. A gate measures whether anyone showed up.
That reframe did something the planning never did. It pointed every hour I have this month at the one thing that is actually behind: get the list from four to fifty. Building more kits into an empty room is not progress. It just feels like it, the same way the date did.
The same mistake, wearing a different costume
The launch date was not the only thing I deleted this week. I also killed a drip-release scheme I had built for the membership.
The idea sounded responsible. Stop someone from joining, downloading every kit in a single weekend, and canceling. Release the kits on a schedule so they cannot grab everything and run. I had a whole mechanism for it.
Then I looked at what I was actually protecting. The kits are text. Anyone who wants to copy text can copy text. The drip stopped no one who was determined, and it made the product worse for every member who was going to stick around, just to inconvenience the few who were not. I was optimizing against a hypothetical bad actor instead of for the real subscriber.
Same mistake as the date. I was measuring the wrong thing and calling it a plan. The drip measured “how hard is it to steal from me,” when the question that pays the bills is “how good is this for the person who stays.”
What to do with this
If you are building something on the side, go find the date on your roadmap that is standing in for a number you have been avoiding. Most roadmaps have one. Replace it with the single measurable thing that has to be true for the milestone to mean anything, and then go look at that number today.
If it is honest, it will sting a little. Mine said four. That sting is the information. It is the part the date was protecting you from, and it is the only part worth knowing.
I would rather launch late into a room with fifty people in it than on time into a room with four.