Why the busiest executives at IBM, Amazon, and Google dedicate an hour a day to deliberate learning and how I rebuilt my career using the same framework
The Wake‑Up Call
Three years ago, I was sitting in a conference room in Seattle, walking a client through a plan to automate their legacy business processes. It was familiar territory. BPM tools. Workflow diagrams. Efficiency gains.
I’d given some version of this talk dozens of times.
Then someone at the far end of the table asked, almost casually:
“How does this integrate with the new GPT models everyone’s talking about?”
I remember the pause. Not a dramatic one but just long enough to feel it.
I knew what GPT was. I’d read the headlines. I’d skimmed a few blog posts. But in that moment, I realized something uncomfortable: I had been so busy delivering work that I had stopped learning how the work itself was changing.
That night, after my family were asleep and the house was quiet, I opened my laptop again. Not to answer email but to do something I hadn’t done in a while. I audited my own learning.
The result surprised me.
In the previous month, I’d spent maybe two hours on deliberate skill development. Two hours. In an industry where tools, architectures, and expectations were shifting faster than ever, I was running on knowledge that was quietly depreciating.
The irony hit hard. I was helping clients “re‑imagine work with AI,” while my own learning habits were stuck a few years in the past.
That week, I started tracking something simple: one hour a day, five days a week, dedicated entirely to learning. No email. No mandatory training modules. No pretending that half‑attention counted.
I didn’t call it anything at first. Later, I started referring to it as the 5‑Hour Rule.
Eighteen months later, I was a library of AI assistants, tools, and application using IBM’s AI services platform (Consulting Advantage) and writing regularly about LLM architecture. The change didn’t feel dramatic day‑to‑day but looking back, it was undeniable.
It wasn’t magic. It was math.
The Compound Interest of Knowledge
The 5‑Hour Rule isn’t new.
Benjamin Franklin practiced a version of it centuries ago. Warren Buffett has said he spends most of his day reading. Bill Gates still takes solo reading weeks. Jeff Bezos has talked openly about how ideas from management theory viz. “two pizza team” shaped Amazon long before they showed up in execution.
What is new is the environment we’re operating in.
We’re living through one of the fastest technological shifts in history. Skills that made you valuable a few years ago are now table stakes. I’ve seen developers who once stood out for mastering a single framework suddenly competing with people who can reason across systems and orchestrate AI agents.
The rule itself is almost boringly simple:
- One hour per day
- Five days per week
- Deliberate, distraction‑free learning
That’s roughly 260 hours a year over six full work weeks of pure skill development.
In an era where people like to say, “AI won’t replace you, but someone using AI might,” those hours aren’t self‑improvement. They’re insurance.
But this is where most people get it wrong.
They think consumption equals learning. Scrolling LinkedIn. Watching conference recordings while half‑responding to Slack. Saving articles they never revisit.
Real learning has three parts:
- Input – absorbing new ideas
- Reflection – connecting and questioning them
- Experimentation – applying, building, or teaching
Miss any one of those, and you’re not building capability you’re just staying busy.
How I Actually Use the 5‑Hour Rule
After a year and a half of trial and error, this is the version that works for me while juggling a demanding job, a family, and a calendar that fills itself if I let it.
Hour 1: The Reading Block
Monday and Wednesday mornings, 6:00–7:00 AM
I used to read opportunistically an article here, a paper there. Now I treat reading like a meeting with my future self. It’s on the calendar. It’s protected.
I use a simple rhythm: 25 minutes of deep reading, five minutes of notes, repeated twice. Phone in another room.
I rotate between:
- Technical: ArXiv papers on LLM architecture (currently studying reasoning capabilities in multi-agent systems)
- Business: Strategy books (just finished “The Innovator’s Dilemma” classic but relevant to AI disruption)
- Adjacent fields: Behavioral economics, decision theory (helps with client consulting)
Don’t just read about your job. The best insights come from cross-pollination. I learned more about enterprise AI adoption from studying investor psychology than from technical manuals.
Hour 2: The Reflection Block
Tuesday and Thursday, split across lunch and evening
This is where most learning systems fall apart.
On Tuesdays, I ask myself three questions:
- What surprised me this week?
- What do I need to unlearn?
- How does this connect to what I already know?
On Thursdays, I organize notes just enough that they don’t disappear. Not for aesthetics—for retrieval. The goal isn’t a perfect system. It’s a memory that compounds.
Hour 3: The Experimentation Block
Friday afternoons, 4:00 – 5:00 pm
This is the part most people skip and the part that matters most.
If you’re not building, you’re not really learning.
Some Fridays, that meant building small AI agents that failed in interesting ways. Other weeks, it meant re‑implementing parts of research papers or writing internal notes explaining a concept I thought I understood until I tried to explain it.
The rule is simple: ship something, even if it’s ugly.
Hours 4 & 5: Weekend Deep Dives
Saturday/ Sunday, Flexible
Weekdays maintain momentum. Weekends create breakthroughs.
Saturday is for deep, uninterrupted work. Sunday is for review and planning. Deciding what to study next and turning private learning into public thinking. That’s often when posts like this one take shape.
The Proof: From BPM to AI in 18 Months
The early months were uncomfortable. I worried I was falling behind on “real work” to study things that felt theoretical.
Then connections started forming.
A paper on transformer architecture suddenly explained why an implementation was struggling with context limits. We adjusted. It worked.
Over time, learning accelerated. Concepts that once took days started clicking in hours. I found myself translating between technical constraints and business outcomes more fluidly.
The difference wasn’t intelligence. It was preparation.
A Question Worth Sitting With
If you invested just five hours this week in deliberate learning, what would actually move the needle for your career?
Not what’s trendy. Not what you “should” learn. What would genuinely change your trajectory?
For me, it was understanding the intersection of enterprise architecture and LLM capabilities. For you, it might be:
- Studying negotiation psychology
- Learning to build AI agents
- Understanding financial modeling
Whatever it is, block it on your calendar right now. Treat it like a meeting with your most important client because it is.
That client is your future self.
One final thought: You can either be green and growing or ripe and rotting. The choice is yours. But in the AI age, standing still isn’t standing still, it’s moving backward.
The executives who will thrive in the next decade aren’t necessarily the smartest or the most connected. They’re the ones who never stopped learning.
Start your 5 hours this week.
What are you learning right now and what’s getting in the way? I’d love to hear.
