Todos
When a project slips, fix the task system first
A delay is not an actionable problem by itself. This worked example turns “why did I miss the date?” into observable causes and next-week corrections.
Example disclosure: this is a synthetic case written to demonstrate the method. It is not a user testimonial or a claim about results from Todos. It targets freelancers balancing client work and their own product. Owner: Adrian Stark; based on a manual walkthrough of current task, due-date, priority, and completion fields; reviewed 2026-08-28.
Scenario: a launch slips for two weeks
A freelancer planned to launch a portfolio redesign on Friday. The list had 17 tasks; nine used titles such as “improve the home page” that had no clear finish state, and six were overdue. Two client deliveries were already promised, but the plan still assumed a completely free week.
Step 1: write facts, not personality judgments
- Planned capacity: five workdays. Actual capacity: about two.
- Nine tasks had no single deliverable and still required decisions before work could begin.
- “Wait for client copy approval” was not tracked separately, hiding a dependency that blocked three tasks.
Task data or a calendar can verify these facts. “I lack discipline” cannot tell you what to change next.
Step 2: give each cause one corrective action
- Unrealistic capacity: schedule only 70% of next week's available time.
- Oversized tasks: replace “improve the home page” with “choose one positioning sentence” and “publish three project screenshots.”
- Hidden dependency: make “ask the client to approve the copy” high priority and move blocked production work out of this week.
- Unclear acceptance: define done as “three case-study pages open on both phone and desktop.”
Step 3: delete instead of postponing everything
Ask of every item: “Does this still serve the one outcome for this week?” Delete it or move it to “Later” if the answer is no. The example keeps positioning, three screenshots, mobile checks, and deployment; animation, blog migration, and multilingual support do not enter this iteration.
Step 4: review only two numbers next week
Record the number of tasks promised and the number completed on time, plus the single biggest blocker. A complex dashboard is unnecessary with a tiny sample; four weeks of observations provide a better basis for changing capacity.