Order matters because scope decisions made before daily contact are guesses, and feedback collected before shipping is speculation. This sequence moves from one compressed sentence, through two weeks of daily contact, into a deliberately small version you can actually finish, and only then into other people's opinions.
Step 1: Name the idea in one sentence
Fifteen minutes is not a productivity trick here; it is the constraint that keeps an idea small enough to survive thirty days. Before the timer starts, compress the idea into a single sentence with a subject and a beneficiary — "a printable weekly meal plan for people cooking for one," not "something around food." If the sentence needs an "and," cut one half. Then start the timer and spend the whole fifteen minutes only on that sentence: read it aloud, trim adjectives, name who it is for. What usually goes wrong is writing an ambition instead of an idea. "Start a food blog" has no finish line, so day two has nothing to do. A sentence that names an artifact and a person hands step two something to sketch, write, or collect.
Step 2: Do one tiny thing every day
Days two through fourteen are where the project either becomes real or becomes a story you tell at dinner. Each day, do the smallest unit that can be finished in one sitting and left visibly done — one rough screen, one paragraph, three collected examples. Use the sentence from step one as a filter: if a task does not move that sentence forward, it waits. A trap that catches most people is batching. Skipping four days and then working an hour on Saturday feels productive, but it breaks the daily cue and turns the whole thing into a chore with a growing backlog. Keep every session short enough that starting tomorrow is not a decision you have to make again.
Step 3: Shrink it to the smallest version
Two weeks in, you have a pile of sketches, notes, or half-screens, and the pull is to build something that uses all of them. Resist that. By now the original sentence has probably drifted, so reread it and ask what single version would deliver its promise to one person, once. If step one said "printable weekly meal plan," the smallest version is one week, one page, one PDF — not an app with saved preferences and a shopping list export. Write the small version down as its own sentence, and list what it deliberately excludes. Shrinking is a scope decision, not a quality compromise, and that distinction is where people stumble: they cut features but keep identical standards for polish, then miss the date. Give the small version a finish line you can point at.
Step 4: Put it where someone can find it
Sharing sits at the end of week four because a deadline with an audience is what forces the last round of decisions; without it, polish has no stopping point. Choose one place and one moment: a post with a photo and a link, a PDF sent to five people, a repo made public on a Tuesday morning. Say in one line what it is and who it is for, using the phrasing you settled on in step three. The most common delay is cosmetic — waiting on a domain name, a logo, or a bigger launch day to feel legitimate. The version you chose in week two was deliberately small enough that it needs none of those. Ship the small one, keep the link, and note the date. That date anchors the feedback conversation in the next step.
Step 5: Ask three people, thank them precisely
Ask three people, and ask a question that returns information rather than comfort: "what did you expect this to do that it didn't?" That phrasing surfaces the gap between their assumption and what you shipped in week four, which beats a general opinion. Pick people who resemble the "for whom" in your step one sentence; feedback from outside that group mostly describes the wrong user. A non-obvious thing about feedback: much of it is about the person giving it, so look for what two of the three mention independently and let the rest go. Thank them by naming the exact thing they said and what you did with it — "you pointed out the checklist had no starting point, so I added one" — because generic thanks leave them unable to tell whether they helped.
A phone reminder disappears the moment you dismiss it, leaving no trace of the days behind it, while a paper strip taped where you work visibly gets shorter each time you cut a line and stays there until the last step is gone. Print it, tape it up, and cut one line per finished day.