Motion

Then decide your project and workspace structure before you pour tasks in. Keep it shallow: a workspace per context (your own company, a client, personal), and projects only where a body of work genuinely needs its own home. Resist the urge to mirror an elaborate Notion hierarchy here, because Motion rewards a flat structure that the scheduler can reason about cleanly. Finally, set sensible defaults for new tasks (a default duration, a default priority) so that capturing a task is fast and you are not forced to fill in five fields every time.

How to actually use it

The core loop is capture, prioritise, let it schedule, then trust the plan. Capture every task with three pieces of information that the scheduler actually uses: how long it will take, when it is due, and how important it is. Those three inputs are what turn Motion from a pretty calendar into an engine, so a task with no duration and no deadline is a task Motion cannot place well.

Once tasks are in, let the auto-scheduler build your day rather than dragging blocks around yourself. The whole point is to stop hand-arranging your calendar, so when Motion lays out your day, work it top to bottom instead of second-guessing the order. When something slips, and it will, mark the task done or not, and let Motion replan around the slip automatically. The replan is the feature, not a bug: a missed task does not blow up your week, it just gets reslotted.

Bring meetings into the same surface. Use Motion for scheduling links and booking where it fits, so that the meetings other people book land directly in the calendar the scheduler already respects. The order to adopt it in is: calendars first, then daily task capture, then auto-scheduling, and only once those are habitual do you layer in booking links and team features. Try to switch everything on at once and you will bounce off it.

Power moves

The pros lean hard on accurate task durations, because the scheduler is only as good as the estimates you feed it. Get into the habit of estimating realistically and then correcting your estimates when reality disagrees, and within a few weeks your plans stop lying to you. Use deadlines as a forcing function: Motion warns you when your committed work no longer fits before its due dates, which is an early-warning system for overcommitment that most people never get until it is too late.

Protect deep work with hard blocks the scheduler must respect, so that the important-but-not-urgent work gets defended rather than endlessly bumped by meetings. On the team side, assign tasks to people and let Motion balance load across the team, which surfaces who is actually underwater before a deadline does. And use priority deliberately: if everything is high priority, nothing is, so reserve the top tier for the genuinely cannot-slip work and let the engine sequence the rest.

Where it fits your stack

Motion sits at the calendar layer of a growth and operations stack, so it pairs naturally with whatever holds your meetings already (Google Calendar or Outlook) and becomes the single planning surface on top of them. Connect your video-conferencing so booked meetings carry their join links, and connect your communication tools where Motion supports it so that task creation does not force a context switch.

Think of the division of labour like this: your knowledge base and long-form docs live in a tool like Notion, your conversations live in Slack or email, and Motion owns the question of what you do next and when. It is not trying to replace your CRM or your project wiki, it is trying to be the one place that turns all of that intent into a scheduled day. Where it connects to other tools through automation platforms, use that to push tasks in from the systems where work actually originates, so capture happens at the source rather than as a manual re-entry step.

Pitfalls to avoid

The biggest mistake is treating Motion like a manual calendar and dragging blocks around yourself, which defeats the entire reason to pay for it. The second is feeding it tasks with no duration or no deadline, leaving the scheduler nothing to optimise against. The third is lying about your working hours, which guarantees every plan is wrong before you start.

Avoid over-structuring early: a deep nest of projects and labels slows you down and gives the scheduler nothing extra. Do not ignore the overload warnings, because they are the most valuable signal the tool produces and the temptation to dismiss them is exactly when you most need to listen. And give it a real fortnight before you judge it, because Motion only proves its worth once it has enough of your real commitments to plan against, and the first few days always feel like extra work before they feel like less.