What "Productive" Should Actually Mean
Glissez pour afficher le menu
"Productive" in most people's heads means — got a lot done. Crossed off items. Stayed busy. Looked busy. Felt busy.
Here's the test. Take any productive day from last month. Three months later, does anyone remember what you did? Did it move anything that mattered?
For most people, the honest answer is no. The thing that felt productive was just motion.
Sarah
Sarah is a senior product manager. For two years she felt incredibly productive — 60-hour weeks, 47 unread Slack channels, 12 OKRs at any given time. She got a "Top Performer" rating.
She also gained 20 pounds, lost her marriage, and burned out so hard she took 4 months off. The company quietly replaced her in a week.
The output that mattered from those two years? Maybe 4 projects. Everything else was Slack threads nobody re-reads.
The Two Real Metrics
- Did you do the right things — the ones that actually move your job, your goals, your life?
- Can you sustain this pace for another decade?
If yes to both → productive.
If no to either → busy.
That's the definition this whole course operates from.
Doing the small number of things that actually matter, well, in the time available, at a pace that lasts. Not crossing 47 things off a list nobody asked for. Not staying online until 11 PM to prove dedication. Not optimizing your second monitor setup.
The next twelve chapters build a system around this definition. Section 2 is the practical system. Section 3 is what makes it sustainable. Let's go.
1. According to this chapter, what does it actually mean to be productive, rather than just busy?
2. What does Sarah's story reveal about the consequences of her approach to productivity, and what does the chapter teach about sustainable work pace?
3. According to the chapter, which approach best defines what it means to be truly productive?
Merci pour vos commentaires !
Demandez à l'IA
Demandez à l'IA
Posez n'importe quelle question ou essayez l'une des questions suggérées pour commencer notre discussion