The busier I feel, the less real work I get done. When I run a business alone and hit overwhelm, I build tools instead of using them, because building feels like progress. Here is the one-page file and the single question that keep me shipping the thing that actually grows the business.
The Problem
When I get overwhelmed, I build things. Not the business. Tools for the business. A new dashboard, a new script, a new system to manage the other systems. It feels like progress, because I’m making something and the screen fills up with output. Then the day ends and nothing shipped, nobody heard from me, and the email list didn’t move. I’ve run this pattern for a year. The tell is always the same: the busier I feel, the less of the real work gets done.
The Workflow
- One file, opened first. Every morning I open one file before anything else. It’s not an app. It’s a page of plain text. At the top is the only rule that matters: every day, move the email list. Publish something, or build the thing that publishes. Everything below that rule exists to answer one question, what do I do right now.
- The two-minute orient. I say “good morning” to Claude and it reads my logs, my commitments, and the calendar, then hands back a short list: today’s date, the three or four things that actually have to happen, and one suggested first move. Two minutes. I don’t plan the day. The day is already planned. I just have to read it.
- Do the have-tos in order. The list is ordered and I work down it. I don’t pick the fun one first. Most days the whole job is one piece of content published and one commitment cleared. That’s a good day. I used to think a good day was building something impressive. It’s doing the boring thing again, on the day I didn’t feel like it.
- The one question, when I feel the pull. When the day starts to feel like too much and I catch myself wanting to “quickly set up” something, I ask one thing before I touch it: is this publishing or selling, or is it setup? Publishing or selling, go. Setup, on a day that isn’t my build day, stop. That question has killed more bad afternoons than any productivity app I’ve ever installed.
- Tinker after, not instead. Here’s the part that makes the rule livable. Once the have-tos are done, I can build whatever I want. The file doesn’t ban tinkering. I like tinkering. It just moves it to after the list. Clear the have-tos, and the afternoon is yours.
That’s the whole system. A page of text and a question. I kept waiting for the part where it needed to be more complicated, and it never came.
What Broke
The same week I leaned on that one-page file, I built the exact thing it warns me about. I spent two days on what I started calling the dashboard to end all dashboards. A command center for my one-person business. Live chat windows wired to my AI tools. A goals list. A journal. A bar across the top that pulsed like an oscilloscope whenever the AI was working. It looked incredible. I was proud of it.
Then I asked the AI to review whether it earned its place, and to be honest instead of nice. The answer took about thirty seconds. The chat window did the same job as a tool I already used, worse. The goals and the journal were things I already had in two other places. The vault-writing duplicated something another tool already did, and that overlap could quietly corrupt the one asset I can’t afford to lose. The pulsing bar was, and I am quoting myself here, dopamine. I had spent two days rebuilding three tools I already owned, wrapped in a light show.
So I froze it. Wrote a short note at the top of the project that says, in plain terms, do not add features to this. It still runs. I just don’t touch it.
The Result
Two days building the dashboard. It moved the business exactly zero. Nobody on my email list will ever see it. No one will ever buy anything because of it.
Now I spend two minutes each morning running “good morning,” and I get the list that actually matters. Two days versus two minutes. The two-day version produced nothing. The two-minute version is the reason I published anything at all this month.
Here is the part I keep having to relearn. Success at this doesn’t come from the revolutionary build. It comes from doing the unglamorous thing every single day, on schedule, whether I feel like it or not. The dashboard was me trying to win the week in one heroic swing. The one-page file is me showing up on the days I would rather not. One of those actually grows a business, and it isn’t the one that looks impressive in a screenshot.
The Prompt
Two things make this work, and you can steal both today.
The first is the question, sitting at the top of your own version of the file:
Before I start anything: is this publishing/selling, or is it setup? If it’s setup and it isn’t my dedicated build day, it’s probably avoidance. Do the next item on the list instead.
The second is the prompt that saved me two more wasted days later on. When you have built something and you are not sure it is worth keeping, don’t ask your AI to improve it. Ask it to kill it:
Here’s what I built: [describe it]. My actual constraint right now is [the one thing that matters, e.g. growing my email list]. Be honest, not encouraging. Does this earn its place against that constraint, or is it a distraction I talked myself into? If it’s a distraction, say so plainly.
A good AI teammate will build whatever you ask. A better one tells you to go write the post instead.
Take It Further
Want the exact structure of the file, the four sections and the one rule in each? Reply and tell me what your version’s single rule would be. The answers I get back are already sharper than the one I started with.