Motion Implementation: 30/60/90 Rollout That Sticks

Write three outcomes Motion must change — status visibility, owner accountability, or time-to-update — and who owns each. 1. Name the job: AI calendar and auto-scheduled tasks. Explicitly exclude a full work OS for 50-person portfolio reporting.

1. Pick three measurable rituals (example: Friday status lives in Motion, 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 Leads (PMs drowning in calendar tetris) freeze “replace the status spreadsheet” as the only 90-day outcome. Portfolio dashboards wait.

Configure one calendar connection, one task list, and auto-schedule rules you will live with. Success looks like: capture tasks, let the calendar place them, and prove a meeting plus task day still holds. 1. One live container of work with real owners.

1. No marketplace apps except the connectors the loop needs. Research names Google Calendar, Google Workspace, and Zapier on the Motion 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 Leads (PMs drowning in calendar tetris) 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 Motion every week — not a one-time all-hands. Our snapshot flags a trial on Pro AI and Business AI without a published length — confirm the window on the Motion 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 user completes an auto-scheduled task and the calendar reflows without an admin live — no slideware-only training.
3. Capture every question as a training-cost line, not a feature request. Worked example: Northline Leads (PMs drowning in calendar tetris) 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: Premium seat vs ClickUp/Asana; No free plan; Collaboration thinner than Work OS peers.
3. Unlock one extra: automations or a dashboard — not both in the same week. Worked example: Northline Leads (PMs drowning in calendar tetris) reviews whether capture tasks, let the calendar place them, and prove a meeting plus task day still holds happened for four consecutive weeks before expanding scope. Empty dashboards mean the rollout is not done.