Every morning at 8:00 a.m. I get a briefing. It covers my meetings, who I’m meeting, why we’re meeting, and what we should discuss. The weather is in there. So is guidance on how to manage my energy.

I want the practical context gathered in one place before the day gets busy. The energy guidance is a planning aid. I’m no doctor, and I don’t treat it as a medical assessment.

Start with a simple morning-brief template that uses your calendar events and your preparation notes. Once that format proves useful, automate the information gathering.

I led a masterclass around one argument. The biggest AI productivity gap is the skill of using the tools well. Three skills are worth developing: clear inputs, workflow thinking, and curiosity. Together, they help you move from occasional AI conversations to repeatable work you can delegate.

Clear inputs

Know the feeling of a blank prompt box and no idea what to type? When I can’t write a clear prompt, I let the AI interview me. I describe the goal, then I add, “Ask me questions before we proceed.” I call it flipping the script.

For a newsletter, those questions might clarify the audience, the tone, the length, the scope, and the visuals. Answering concrete questions is easier than inventing a perfect brief from a blank screen. Repeated use teaches you which details to include upfront.

Try the interview prompt on one unfinished draft or one planning task.

Editing an AI-written email only in your email app hides your most useful feedback from the AI. Bring those corrections back into the drafting process. Explain which wording you changed, what sounded wrong, and what you prefer instead. The goal is to turn repeated edits into reusable writing instructions.

Compare one AI draft with the version you actually sent. Capture the differences in a reusable style brief. Keep that brief in saved instructions, in a few examples, or in the conversation itself. Corrections do not automatically train a model, and they do not persist across chats on their own.

Organizing files. I know. Much of the client implementation work I do happens before I introduce any automation. I clean the data. I organize the files. I label the information.

A focused set of relevant documents, paired with a constraint, gives the AI a clearer assignment than an indiscriminate document dump. I use lines like “use only these sources” and “keep the answer to one page.” Cleaning the sources will not eliminate bad answers, and no single document count fits every task.

Clean up the source folder for one recurring task. Specify the permitted sources and the output format.

The 8:00 a.m. Briefing I Actually Read

A repeatable path

Workflow thinking starts with a familiar productivity skill: breaking a goal into actionable steps.

I use it for scripts. I give the workflow a topic, and it produces a draft that follows my established outline, my wording preferences, and my storytelling style. I keep a repeatable path from input to output.

Read the draft. I won’t claim an exact copy of my voice. If the draft tells a story, treat that story as generated until you’ve verified it as a real experience.

What does done look like? Write the input, the intermediate steps, and the desired output for one recurring task before you choose an automation tool.

A meeting transcript becomes much more useful when it leads to prepared follow-through. Here’s a workflow I want you to pilot. Extract the action items. Add the tasks to the appropriate system. Place a follow-up email draft in your inbox. You receive work organized for review and action.

Pilot it on one meeting. Review the owners, the deadlines, and the wording before anything is sent or assigned. Get recording consent before you record. Keep confidential meeting data confidential. Approve anything external before it happens. I don’t have measured results from a deployment of this.

You may want more than one AI perspective on an idea. Moving the concept between several models, carrying each model’s suggestions into the next conversation, can surface different possibilities. Useful, and repetitive. That comparison can be started as a single repeatable step.

Test one nonconfidential idea with a second model. Compare the useful differences before you automate that process. Verify factual claims yourself. Perspectives from several models are not an independent fact check.

Check the bad answer

Before I abandon a disappointing answer, I ask which files the AI used, what assumptions it made, and why it chose that approach. Those questions can reveal a missing source or a misunderstood instruction I can correct on the next attempt.

Curiosity becomes a practical troubleshooting skill when you use it that way. Treat the explanation as a claim. Check it against the files and the instructions you gave. Investigate the mistake you can see. An explanation is not reliable access to the model’s internal reasoning.

On the next disappointing output, ask for the sources and the assumptions before you rewrite the entire prompt.

Then make it repeatable

I describe three levels of AI use. Assistance helps you produce an answer through conversation. Workflows connect repeatable steps so you reach the outcome faster. Agents can run delegated work without you initiating every step. I teach these labels as a sequence you can apply to one real task.

Master one useful task. Make it repeatable. Only then consider running it with less supervision. For an agent, set permissions, keep review points in the path, and monitor what it does. A run you are not watching still has to be checked.

Identify your current level for one task, and define the next manageable step.

Pick the weakest of those three skills. Practice it on one recurring task this week. Just one.

Recommended for you

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

Explore 25X →

You may also Like

Last Updated: November 19, 2026

Read More

Last Updated: November 17, 2026

Read More

Last Updated: November 3, 2026

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"}