The Workflow
My membership had a launch date this week. By the end of the week it didn’t.
The date was August. It lived at the top of my strategy doc in bold, and for two months it looked like a plan every time I opened the file.
It was a guess wearing a calendar. A date 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, and arrive at August having done real work, and the date would be perfectly satisfied. It never asks whether anyone is waiting on the other end.
So I deleted it and wrote a gate in its place: 50 newsletter subscribers before the membership launches. Not a date that felt about right. A number that has to be true for the launch to mean anything.
Then I checked the current count. Four. One of them is me.
The number stung, which a date never does. That is the whole reason a date is so easy to keep. Four told me the truth the calendar had been hiding: the product was never the constraint, the audience is. August was a launch into an empty room, and the date was never built to warn me about that.
The full version of this reframe, and the second decision it triggered, is on the blog: I replaced my launch date with a subscriber count.
What Broke
The launch date was not the only thing I killed this week. I also tore out a drip-release scheme I had built for the membership.
The idea sounded responsible. Stop a member from joining, downloading every kit in one weekend, and canceling. Release the kits on a schedule so nobody can grab everything and run. I had the whole mechanism built.
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 would have stayed, all to inconvenience the few who wouldn’t. 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.”
Time Ledger
- Time saved: None this week. There is nothing to save. This was a deleting week, not a building one.
- Time added: Maybe an hour to rip out the drip mechanism and rewrite the launch criteria.
- Net: The real cost was the weeks before this, spent building into a room with four people in it because the date told me that was progress.
The gate does not save me time. It redirects it. Next month’s hours now point at one number instead of a calendar.
The Prompt File
Point this at any roadmap that has dates on it. It turns the dates back into the numbers they were standing in for.
You are a skeptical operator reviewing my project roadmap.
Here is my roadmap, with milestones and target dates:
[PASTE ROADMAP HERE]
Task 1: For each milestone, ignore the date. Identify the single
measurable precondition that must be true for that milestone to mean
anything (e.g. "50 subscribers", "3 paying customers", "5 completed
interviews"). One number per milestone.
Task 2: For each milestone, tell me which is really driving it: the
date, or the number. Flag every milestone where the date is standing
in for a number I have not been tracking.
Return: a table with columns milestone, current date, the real number,
and a one-line note on what I am actually waiting for.The output you want is the row where the date looks fine and the number is empty. That is the one the calendar was protecting you from.
Manager’s View
Ask your team this week: “Which date on our roadmap is standing in for a number we’re afraid to check?”
Every roadmap has at least one. A launch date, a “go-live,” a target quarter that everyone repeats and nobody pressure-tests. The date feels like accountability. Often it is the opposite, a comfortable object you can carry for months because it makes no claim about reality.
Ask it in private, not in the planning meeting. In the meeting you get the date everyone agreed to say out loud. One-on-one you get the number nobody wanted to look up, which is the one that tells you where the project actually is.
Field Notes
- The count was four. I have been telling people “a couple” for weeks. Four is the honest version, and it changed what I did with the next month faster than any plan did.
- Deleting the drip-release scheme felt like losing a feature. It was losing a tax I was charging my own future members.
- The August date is gone from the strategy doc. Nothing replaced it except the number 50 and a note that says “then.”