I had just arranged a padel game. Putting it on the calendar could have meant capturing a reminder, processing it later, and editing the event. This time I sent a voice note to my agent through Telegram. Nine seconds. I asked it to add the game to my calendar.

The agent told me the event already existed, and it updated the location. I checked the date, the time, the location, and that the event had already been there. Capture, clarification, and organization folded into one request and one reply. Nine seconds is the length of the voice note.

I used to open each app and do the work myself. Now an agent adds calendar events for me, pulls schedule information, and helps me process tasks. The apps still exist. I specify the outcome and I review the result.

My own agent setup is advanced. Connections, permissions, and setup decide what it can touch. Your tools may behave differently.

Have you ever saved a note and then failed to find it?

For years I had capture destinations in OmniFocus, Evernote, Apple Notes, and Drafts. A thought showed up and I had to decide where it belonged. Later I would search several of those places to get it back. I never measured that scavenger hunt, and I haven’t finished a single inbox. What I do now is pick one default capture destination and write down the exceptions. A note with a clear reason can live somewhere else. Everything else goes to the default.

A tool can cover more than one job. Uncertainty about where something belongs is the actual problem.

A Nine-Second Voice Note Replaced My Calendar Routine

I map the stack before I try to change it

My audit has eight categories: capture, tasks, calendar, notes, files, communication, AI, and automation. For each one I list what I actually use. Then I look for redundant tools, unclear destinations, and missing capabilities. A one-page map is enough. Circle one unnecessary overlap. That circled item is the improvement.

Keep that map separate from the task lifecycle: capture, clarify, organize, prioritize, execute, and review. Those are stages. The eight categories are the tools.

When I want a change to stick, I give it seven days and one workflow. Map the tools. Remove the duplication you don’t need. Clarify which inbox receives what, and where finished items go. Do the workflow by hand once. Write the steps down. Automate it, then test it against the same list. The checklist is the acceptance test. If the automation skips a line, it failed.

My target is one high-leverage tweak at a time

Removing a redundant tool counts. Simplifying capture counts. You can stop there.

Ever delegated work to another person? An agent needs that same shape. I call it 10-80-10. The first 10% is defining the outcome. The middle 80% is execution. The final 10% is reviewing the work and giving feedback. Those numbers are a heuristic I use to explain where attention goes. Review can take several rounds.

Your attention sits on the brief and on the quality check. The intermediate steps run against that brief.

Try it on one recurring task. Write the brief and the acceptance checklist before you hand it off. If you want something smaller, ask for a schedule summary, or an email draft you approve before it gets sent.

The brief works better when the agent can see what you care about this quarter. I keep a plain Markdown file with my top three priorities and what I’m trying to focus on. While the agent works, it can reference that file. That is explicit context for prioritization. Left alone, it infers what matters from whatever information it happens to run into.

Creating the file is the start

The workflow has to give the agent access to the file, and the task has to tell the agent to use it. Skip that and the document sits there while the agent never opens it.

Meeting prep went through the same path, manual first and automated after. I learned what I needed by preparing the slow way, checking previous emails and researching attendees right before the call. Once that process was repeatable, I automated it. These days an email lands around 7:30 a.m. with that day’s meetings, the context, and background on the people involved.

Got a meeting coming up? Test this on one of them

Define the brief first. Fields I find useful are the purpose of the meeting, what you discussed last time, background on the attendees, and the open questions. Treat those as a starting list. Your exact format can be different. Pull from sources you are allowed to use, and review the generated context for errors.

What if the best task manager changes once an agent operates it? I stayed with OmniFocus for years. A new tool had to be 10 times better before I would switch. That threshold is my personal rule. When my AI workflows needed easier access, I moved to Todoist, then to Airtable, as tasks, meeting notes, preparation documents, and saved articles started living together. I was choosing integration and shared context.

OmniFocus may have integration options I wasn’t using. I’m describing my sequence. Before you leave an app you trust, test whether the workflow you want can reliably read it and update it.

Simplify how information moves between them

A productive stack is the system whose tools work together with the least friction. Give each tool a clear job.  Add AI after that. Add it earlier and you can spend more time managing your productivity tools than doing the work. That was the core thesis of my July 2026 masterclass. Before another app goes in, find one point where your current tools create unnecessary work.

Write your top three quarterly priorities in a plain-text document. Include that file in the next task you delegate, and tell the agent to use it.

Recommended for you

Want the full system? 25X is the flagship productivity system we teach.

Explore 25X →

You may also Like

Last Updated: November 13, 2026

Read More
Read More

ABOUT THE AUTHOR

Thanh Pham

Founder of Asian Efficiency where we help people become more productive at work and in life. I've been featured on Forbes, Fast Company, and The Globe & Mail as a productivity thought leader. At AE I'm responsible for leading teams and executing our vision to assist people all over the world live their best life possible.


Leave a Reply


Your email address will not be published. Required fields are marked

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}