productivityhabitsthinking

Your routine is the one thing AI cannot optimize for you

Alex, senior software engineer and author of Alex's Whiteboard blog

Alex

· 7 min read

Person in a coworking space holding a sign that reads Be Calm and Stay Productive

I've been using AI tools in my work for about two years. Writing, code review, research, planning. Some of it has been a real productivity gain. Some of it made me a more sophisticated procrastinator.

The bottleneck doesn't disappear when the tools get faster. It moves. Before AI, I lost time to slow execution. After AI, I started losing it to unclear thinking at the front end. Output was faster but less aimed. More drafts of the wrong things.

The fix wasn't a better prompt. It was going back to boring, manual, non-automated structure. A daily routine that forced certain kinds of thinking before I opened any tool.

Why routines matter more now, not less

There's an argument that AI makes routines less important. If a tool can handle scheduling, summarizing, drafting, and deciding, then rigid daily structure is just overhead. Be flexible, respond to what the AI surfaces.

I tried this for a month. The result was a lot of activity with unclear direction. Days were full, but I couldn't trace the progress back to anything I'd actually decided.

A morning review isn't about loading your calendar into your head. It's about deciding what matters today before external inputs start deciding for you. That decision is still yours. AI surfaces options well. It doesn't know which option is load-bearing for you, this week, given what only you know about the situation.

The more you have amplifying your output, the more it matters to have clear input. That's what routines are for.

The specific threat AI tools pose to routine

It's not that AI tools are distracting the way social media is distracting. They're more insidious.

They're useful. Each individual request makes sense. You're writing a document and the tool suggests a better structure. You're planning a sprint and it generates tickets. You're researching a topic and it summarizes six papers. None of this is waste.

But the cumulative effect is that your days start to be shaped by the tool's suggestions rather than your own judgment. You're reacting, not directing. The work feels productive. The direction gets blurry.

I noticed this by comparing two kinds of mornings. Ones where I opened a chat interface before I'd done any thinking of my own, and ones where I did a fifteen-minute planning block first. On AI-first mornings, I did more but felt less certain at the end of the day that I'd done the right things. On thinking-first mornings, I used the tools for execution and kept the judgment.

The routine is what keeps the judgment yours. Without it, the tool fills the space.

What the actual routine looks like

I keep mine short because it has to survive real conditions. Three things.

A morning look-ahead: ten minutes, no tools, just a notebook and one question. What is the one thing that, if I did it today, would move the week forward? I write one sentence. That sentence is what I do first, before I've talked to anyone or opened any interface. The five-minute morning board check is a version of this I've been doing with a whiteboard lately and it works well for externalizing the decision.

A midday check around 1pm: five minutes. What did I actually do this morning? Was it the thing from the morning? If not, does the reason hold up to thirty seconds of scrutiny? Usually this takes less than two minutes. Once in a while it has saved me an entire afternoon of working on the wrong thing.

An end-of-day capture: ten minutes. What do I want to have available tomorrow that I learned today? Three to five points, written by hand, not processed through any tool. The manual writing step matters. Writing things down changes how you encode them in a way that dictating to a summarization model does not.

None of this is original. The value is that it runs on my judgment, not the tool's inference, and I do it every day.

AI works inside the routine, not in place of it

The shift that helped was treating AI as an execution tool, not a thinking tool.

Once I've done the morning look-ahead and decided what matters, the tool is useful for exactly what it's good at: draft this section, summarize these notes, flag inconsistencies in this plan. It speeds up work I've already decided to do.

Where it breaks down is when it's also making the higher-level calls. Should you be writing this document at all? Is this the right problem this week? Does this approach fit what you've already committed to? That reasoning requires context only you have, and it happens before the tool enters the picture.

Activity and progress are not the same thing

Working with AI tools makes it easy to feel productive without actually moving the right things. A full day of AI-assisted output is still a day that could have been aimed at the wrong target.

I check for this by asking at the end of the week: what changed because of my work? Not what did I produce. What actually changed. That question is harder to answer with AI-generated artifacts than with clear decisions and visible movement on the things that actually needed to move.

The weekly review is a good place to catch this drift. Whatever format you use, the question that matters isn't how much you did but whether you moved the things that needed to move.

When the answer is vague, the problem usually isn't that I used AI too much. It's that I let the tool stand in for front-end thinking that only I can do. The routine forces that thinking. When I skip it, I can tell within two days.

When tools are new, protect the routine harder

There's a specific period worth watching: right after you've adopted a new AI tool, when it's still novel. The outputs are better than you expected and it's easy to over-index on using it.

This is when routines are most at risk. Not because the tool is bad, but because novelty is a distraction by itself. Everything the tool does looks important because it's new and working. The routine looks like overhead because it's familiar and slow.

I try to pick up new tools during weeks when I've already committed to keeping the rest of my structure intact. The new tool goes into the execution layer. The planning and review structure stays the same until the tool is actually integrated and I can tell what it's genuinely contributing.

Slow adoption ends up being faster. The boring parts of the day are where the real work happens, and you don't lose the thread on your thinking when you've protected time for it.