
You can spend ten hours researching a newsletter, complete every planning task, and still have no idea whether anyone wants to read it. The work may be necessary. The decision about progress needs another kind of evidence.
Define what “on track” means before you start. Write down the outcome you want, the early signs you can observe and the date you'll look at them. Make the checkpoint early enough to change what you do next.
Start with the thing that will exist or be true when the goal is achieved. Then identify an intermediate artifact someone could inspect. Add one measure that helps you understand what it cost or where it got stuck. Choose measures you can collect without turning the project into an administrative job.
Maya, a fictional freelancer, wants to learn whether a short newsletter would help her stay in touch with designers who care about her work.
| Question | What Maya will track |
|---|---|
| What will exist? | Three pilot issues sent to the people who've agreed to receive them |
| What's the early milestone? | One sample shown to three interested readers before committing to the pilot |
| What tells me whether it can continue? | Time spent per issue and feedback about what readers found useful |
| When will I act on it? | After the third issue, schedule another cycle, change the format, or close the pilot |
A goal can have different kinds of evidence. A project might have an approved brief, a draft or a release. A routine might have a consistent record of follow-through and notes on unusual weeks. A learning goal might have a small project someone else can use. Matching the evidence to the goal matters more than using the same score for every project.
Write a rule you can explain. “If the sample is ready and feedback points to a clear topic, start the pilot. If the sample is ready but feedback is missing, extend the decision only long enough to get it. If the draft keeps slipping, check what work is taking the planned block.”
Treat missing information as a question. If nobody has responded, maybe the question you asked was vague or the sample hasn't been read. Capture what you know and what you need before changing the plan.
In SelfManager.ai, Maya can put the milestone and decision date on the calendar of her work, then keep the sample, notes, and relevant comments on the dated tables. Tracked hours can help explain why an issue was expensive to produce. A comment can record what the reviewer actually said, so a completed task has context behind it.
At a checkpoint, use AI → AI Review to describe what moved over the week, month or quarter. Ask the review to distinguish completed tasks from evidence of the outcome. Add relevant documents or images as context when they're useful. Compare the answer with the actual milestone before deciding. AI Review and context options.
If a checkpoint shows the plan needs to change, use the monthly replanning process to update scope and dates while keeping the old decision visible.

Plan smarter, execute faster, achieve more
Create tasks in seconds, generate AI-powered plans, and review progress with intelligent summaries. Perfect for individuals and teams who want to stay organized without complexity.
Get started with your preferred account