From Chaos to Clarity: My Experience with an AI Time Management Strategist
A candid look at what it's really like to hand your calendar over to an AI β the stumbles, the breakthroughs, and what I'd tell anyone thinking about trying it. π± How It Started Like most people who work in product and project management, I didn't have a time problem β I had a prioritization problem. My task list was technically complete. Every to-do was captured, tagged, and sitting in a Notion database. But every morning I'd open the board and feel the same low-grade dread: Where do I even start? That's what led me to build and deploy a custom AI agent directly inside my Notion workspace β one wired into my task database, my Google Calendar, and a set of structured instructions about how I actually want to work. I called it the Time Management Strategist . What followed was several months of iteration, frustration, small wins, and eventually, a genuine shift in how I spend my days. βοΈ What the Agent Actually Does At its core, the agent does three things: Plans my day or week by pulling tasks from my Notion database, reading their priority, energy level, and estimated duration, then building a realistic time-blocked schedule. Exports that schedule to Google Calendar β one event per task, with the task's Notion URL embedded in the location field so I can jump back to context with one tap. Runs a nightly sync on weekdays at midnight, automatically cleaning up stale calendar events when task due dates change or tasks get marked done. Under the hood, it uses an energy-aware scheduling model. Every task in my database carries an energy tag β π΄ Deep, π‘ Medium, or π’ Light β and the agent slots deep work into my peak focus hours and lighter admin tasks into the afternoon dip. It also protects a hard lunch block from 1β2 PM and flags any day where I've overcommitted before it ever hits my calendar. πͺ¨ The Challenges Getting the profile right The agent is only as good as the context I give it. The first version of my personal profile β work schedule, peak energy hours, recurring commitments, non-negotiables β was vague and optimistic. I told it my peak hours were 8 AMβnoon. In reality, I don't hit my stride until closer to 10 AM after I've cleared Slack and had coffee. It took two or three weeks of the plans technically being correct but feeling wrong before I revisited the profile and tightened it up. The lesson: garbage in, garbage out. The AI isn't psychic β it plans based on what you tell it about yourself. Trusting the reject Early on, I had a habit of just accepting plans without pushing back. The agent always ends a proposed schedule with a simple prompt: accept to push it to calendar, or reject to revise. I kept accepting out of some weird social pressure β as if declining the AI's suggestion was impolite. Eventually I learned to use the reject loop aggressively. "Move the deep work block to Tuesday, I have a client call Monday afternoon." The agent rebuilds the plan in seconds. That back-and-forth is actually where the most value lives. Overdue task accumulation This one stung. For a while I was using the agent to plan forward without ever cleaning up the backlog. Tasks that were 3 weeks overdue sat in the database and occasionally surfaced in plans in awkward ways. The agent has a rescheduling feature β it uses a tiered formula to push overdue tasks forward based on how late they are and their energy level β but I wasn't using it. Once I built a habit of running a weekly reschedule pass (usually Sunday evening), the plans became dramatically more accurate and achievable. π The Successes The plan actually fits the day The single biggest win is mundane but profound: I stopped overbooking myself . The agent counts available hours, accounts for lunch and breaks, and flags overcommitment before it schedules anything. When it tells me a task needs to move to tomorrow, I believe it β because it's done the math. Energy-matched focus Pairing task energy level with time