Todoist Implementation: 30/60/90 Rollout That Sticks

Write three outcomes Todoist must change — status visibility, owner accountability, or time-to-update — and who owns each. 1. Name the job: personal and small-team task lists. Explicitly exclude a company work OS or a Gantt portfolio.

1. Pick three measurable rituals (example: Friday status lives in Todoist, not Slack).
2. Name the admin owner and the weekly users.
3. List nice-to-haves you will refuse until day 61. Worked example: Northline Founders (a five-person leadership list) freeze “replace the status spreadsheet” as the only 90-day outcome. Portfolio dashboards wait.

Configure one shared project, labels you will filter, and a daily review habit. Success looks like: capture tasks, assign one shared project, and complete a daily review without a second tool. 1. One live container of work with real owners.

1. No marketplace apps except the connectors the loop needs. Research names Slack, Google Calendar, Microsoft Teams, and Zapier on the Todoist side — confirm the connectors your work loop depends on.
2. A manager can see status without asking for a screenshot.
3. Log every “can we also…” request for day 61. Worked example: Northline Founders (a five-person leadership list) delays optional AI and extra hubs until the core loop has a week of real use. Week-one marketplace apps are treated as a failure mode.

Train the people who must update Todoist every week — not a one-time all-hands. Our snapshot flags a trial on Pro and Business without a published length — confirm the window on the Todoist pricing page. 1. Role-based sessions: contributors vs managers vs guests.

1. Include one sceptic so adoption risk shows up before speeches.
2. Practice a teammate completes an assigned task and you see it without being the project admin live — no slideware-only training.
3. Capture every question as a training-cost line, not a feature request. Worked example: Northline Founders (a five-person leadership list) includes one sceptic user in training so “I still ping the owner in Slack” shows up while you can still fix the ritual.

Check whether the core loop is actually used. Only then add automations, extra hubs, or AI. 1. Count weekly active updaters vs invited seats.

1. Confirm managers stopped asking for spreadsheet status.
2. Review watch-outs. Research flags: Not a Work OS; Thin reporting; Limited team depth vs Asana.
3. Unlock one extra: automations or a dashboard — not both in the same week. Worked example: Northline Founders (a five-person leadership list) reviews whether capture tasks, assign one shared project, and complete a daily review without a second tool happened for four consecutive weeks before expanding scope. Empty dashboards mean the rollout is not done.