The Philosopher
The question, as posed, contains a false binary worth dissolving before answering it. "AI auto-scheduling" and "deliberate manual planning" aren't really opposites—they're operating at different levels of the same activity, and the more interesting question is which decisions you're willing to delegate and which you're not.
What automated scheduling is genuinely good at
Tools like Motion excel at constraint satisfaction: given fixed meetings, deadlines, task durations, and stated priorities, they can find a defensible arrangement faster than you can, and—crucially—they can re-optimize when something shifts, without the friction and dread most people feel toward replanning a disrupted day. This solves a real problem: decision fatigue. Every "what should I do next" is a small withdrawal from a finite reserve of willpower, and outsourcing that arithmetic can meaningfully improve follow-through, especially for people who struggle with executive function or who have highly reactive, meeting-dense jobs where the sequencing problem is genuinely complex.
What it can't do, and what manual planning is actually for
The deeper issue is that scheduling has two components that get conflated: the optimization (where does this task go, given constraints) and the valuation (what even counts as a priority, and how much). An algorithm can be excellent at the first and is structurally incapable of the second—it can only reflect the weights you gave it. If you haven't done the harder work of deciding what matters and why, the AI isn't making that judgment for you; it's making it invisibly, via default priority scores or whatever heuristic the product encodes, and you may not notice the substitution has happened.
There's also a phenomenon Eisenhower pointed to: "plans are worthless, but planning is indispensable." The value of manually reviewing your day isn't really the resulting calendar—it's the five minutes of friction where you notice the important-but-not-urgent thing that keeps sliding, or catch that you've let three consecutive days fill with other people's priorities. That noticing is a byproduct of the process, not the output, and it's hard to get if the process is invisible to you.
Two more considerations that don't get enough attention:
- Ownership and reactance. People tend to follow through on plans they authored, and resist plans imposed on them—even when the imposition is one they nominally set up themselves ("Future Me" delegating to an algorithm can feel a lot like "someone else" to "Present Me"). This is empirical and personality-dependent, but real.
- Illegible variables. How you actually feel today, subtle political considerations about when to approach someone, the fact that this deep-work block needs to happen in the morning specifically because you're jetlagged—these are things you know and the algorithm doesn't, unless you're diligently feeding it real-time state, which most people aren't.
What this suggests practically
I'd resist the framing that one is "better" in general, because the right split depends on:
- Type of work. Highly reactive, meeting-heavy, logistically complex schedules benefit more from automation. Deep, creative, or ambiguous work resists timeboxing regardless of who's doing the boxing.
- Cognitive style. If planning is where you do your real thinking about priorities, automating it removes something valuable. If planning is where you procrastinate on actually working, automating it removes something toxic.
- Life stage / volume. More obligations, more benefit from optimization; fewer, higher-stakes decisions, more benefit from deliberation.
A reasonable synthesis: keep the valuation layer manual and recurring—a weekly (not daily) act of deciding what actually matters, what to protect, what to say no to—and let automation handle the placement layer, i.e., where the resulting commitments actually land in a given day, with disruption handled algorithmically rather than through your own renegotiation each time. Retain veto power and actually use it occasionally, as a check that the tool's choices still track your stated values rather than just its own defaults. If you notice you've stopped questioning what it produces, that's the signal you've drifted from delegation into abdication—which is the real risk, not automation itself.