Last updated: 2026-09-17

I keep running into the same assumption. Someone spends an afternoon with AI, sets up a few prompts, and expects the scramble to stop.

It doesn’t.

Proactivity is a skill. A habitual mindset you have to develop. Every day you’re choosing how to spend your time, energy, and attention. That’s the T Framework. The skill is consistently choosing important-but-not-urgent work over urgent-but-not-important distractions. AI can help you set that up. It cannot run the habit for you in one afternoon.

Does this sound familiar? Your Slack is lighting up, your calendar is other people’s priorities, and you feel like you’re failing at productivity because you haven’t flipped from reactive to proactive yet.

You’re not failing. You’re underwater.

Give yourself 4 to 8 weeks

If you’re currently underwater and reactive, do not expect to become proactive in one week. From coaching, I can tell you it takes 4 to 8 weeks of consistent system implementation to build the flywheel of momentum and clear the backlog of reactive clutter.

A significant scheduling backlog doesn’t close in a week. You close it by running the same system, week after week, until the reactive pile actually shrinks.

So if you’ve been at this for a few days and you still feel behind, that’s normal. The timeline is 4 to 8 weeks. Patience is part of the work. A slow flywheel is not a personal failure.

Respond on your terms

Brooks made a distinction I want you to use.

A proactive person still handles interruptions. They handle them on their own terms.

Picture a Slack request landing while you’re in the middle of something that actually matters. The reactive move is to drop your current focus immediately. The proactive move is to acknowledge the request, park it in a task manager, and return to your priority.

You can be responsive without being reactive. Same message. You choose the timing.

Next time a non-urgent request shows up, use this script: “I’ll get to this after my current priority.”

Try it once this week. Park the request. Keep your block.

Spend 30 minutes on something that isn’t due for 30 days

This is the tactic I want you to leave with.

Spend 30 minutes a week on a task that is not due for the next 30 days.

The first session will feel unsatisfying. There’s no immediate payoff. The work isn’t on fire, so it feels like you’re wasting a block you could have spent on something urgent.

Do the 30 minutes anyway.

That small, consistent investment is what prevents the tax-filing panic of last-minute deadlines. You build a buffer of progress in the background. When the due date arrives, you’re already ahead of the game. The relief shows up later. That’s why the first weeks feel pointless even when they’re working.

Can you name one important-but-not-urgent thing you’ve been postponing because nothing is due yet? Block 30 minutes for it this week. Put it on the calendar.

Look 2 to 3 days ahead

Brooks uses a look-ahead habit to manage weekly podcast production. You can run the same move on any kind of work.

On Tuesday, open your calendar or task manager and look 2 to 3 days ahead. What will you need on Thursday or Friday? Set reminders now to lay the groundwork for those future tasks.

Here’s the thing. You’re shifting the mental load from decision making at the moment of execution to preparation in advance. Thursday stops being a scramble. It becomes a continuation of work you already started.

Less decision fatigue. Less anxiety.

Set a recurring Look-Ahead reminder on Tuesdays. When it fires, scan the next 2 to 3 days and plant the reminders. That’s the whole habit.

Let AI handle the donkey work

Brooks brought up a useful phrase: donkey work.

That’s the tedious administrative setup of being proactive. Creating calendar entries by hand. Breaking a high-level goal into weekly milestones. Setting a stack of reminders. You define the outcome and the constraints. An LLM handles the scheduling and task creation.

This lowers the friction of getting the system in place. You still have to show up for the 30 minutes. You still have to look ahead on Tuesday. The donkey work just stops being the thing that keeps you from starting.

Copy this prompt and fill in your goal:

“ I have a 30-day goal:. Constraints: I can spend 30 minutes per week, and I want those 30-minute blocks on my calendar. Break this into weekly 30-minute blocks for the next 30 days. For each week, give me one 30-minute block with a specific task, a suggested day, and a reminder to set 2 to 3 days before that block so I can lay the groundwork. Output calendar entries and tasks I can copy into my calendar and task manager. “

Run it once. Then put the blocks on the calendar.

Decide the destination before the day starts

Want a historical picture of this? Benjamin Franklin.

He meticulously planned his day to maximize virtue and productivity. He defined his destination and strategic goals before the day began, rather than drifting reactively through notifications.

That’s intentional living, applied to a calendar.

Brooks recommended two books for this: Benjamin Franklin: An American Life, and 12 Week Year. If you want a structured way to practice this kind of proactivity, start with one of those.

Define where the day is going before the notifications do.

One block this week

Identify one important-but-not-urgent task that is not due in the next 30 days. Block 30 minutes for it this week.

Keep that block for 4 to 8 weeks. That’s how the flywheel starts.

Recommended for you

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

Explore 25X →

You may also Like

Last Updated: September 17, 2026

Read More

Last Updated: September 28, 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"}