AI Makes My Job Miserable. How Do I Escape?

🔗 **Source:** [AI Makes My Job Miserable. How Do I Escape?](https://www.youtube.com/watch?v=rsAay1tB1Q8)
> [!note]+ Document Notes
> tags: [workplace-productivity, artificial-intelligence, knowledge-work, pseudo-productivity, busyiness-singularity, digital-minimalism]
> author: Cal Newport
> source: Deep Questions
> reference: https://www.youtube.com/watch?v=rsAay1tB1Q8
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> # 🏷️ Title: AI Makes My Job Miserable. How Do I Escape?
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
## 📝 Summary
- Cal Newport argues that AI won't just take jobs—it will make existing knowledge work jobs miserable by creating a "busyness singularity"
- The root problem is "pseudo productivity"—using visible activity as a proxy for useful effort—which has been amplified by decades of digital technology
- AI reduces the cost of pseudo-productive activities (emails, reports, slide decks) to essentially zero, creating infinite shallow work
- Five strategies to escape: plan weekly, maintain a portfolio, avoid AI-automatable tasks, pursue upskill projects, and write exceptionally well
- The solution requires moving away from busyness-based evaluation toward actual value creation
## 📖 Main Content
Newport presents a compelling alternative to the standard AI discourse focused on job displacement. Instead of mass unemployment, he warns of a "busyness singularity"—where work becomes an endless loop of AI-generated pseudo-productive activities.
### The Evolution of Knowledge Work Problems
The story begins in the 1950s when Peter Drucker coined "knowledge work" and emphasized worker autonomy. This created a management challenge: how do you evaluate autonomous workers? The implicit solution became "pseudo productivity"—using visible activity as a proxy for useful effort.
This worked adequately for decades until digital technology arrived. Computers increased the number of tasks workers could juggle. Email enabled fine-grained demonstration of effort through response times and message volume. Mobile devices made work omnipresent, creating constant pressure to demonstrate busyness.
The result, according to Microsoft data: 117 emails and 153 Teams messages per day, with interruptions every two minutes during core work hours.
### AI as the Accelerant
AI doesn't solve this problem—it makes it exponentially worse. Current AI applications in most knowledge work focus on pseudo-productive activities: writing emails, creating slide decks, summarizing meetings, generating reports. These activities demonstrate effort but rarely create direct value for clients or bottom lines.
When you reduce the cost of pseudo-productive activities to zero while maintaining a system that rewards visible activity, you get what Newport calls a "busyness singularity"—infinite shallow work density that collapses in on itself.
### Five Escape Strategies
1. **Plan Weekly**: Schedule important work like meetings, protecting time for actual value creation
2. **Maintain a Portfolio**: Document valuable accomplishments to provide alternatives to busyness-based evaluation
3. **Avoid AI-Automatable Tasks**: Use the "Claude test"—if AI could do it, spend less time on it
4. **Pursue Upskill Projects**: Continuously develop rare and valuable skills
5. **Write Exceptionally Well**: Differentiate yourself with clear, concise, human-crafted communication
## 🗒️ Notes
#### ⏱️ [00:03:12](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=192) The Busyness Singularity Concept
- AI reduces cost of pseudo-productive activities to zero
- Creates "mad performative dash of button mashing"
- Teams of AI agents producing and consuming each other's outputs
- "Digital blitz of back and forth nothingness"
#### ⏱️ [00:15:30](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=930) Microsoft Work Trend Data
- 117 emails per employee per day
- 153 Teams messages per day
- 57% of meetings are ad hoc
- Interruptions every 2 minutes during core work hours
#### ⏱️ [00:25:45](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=1545) Five Practical Solutions
- Weekly planning prevents reactive pseudo-productivity
- Portfolio approach replaces busyness metrics with value metrics
- AI avoidance test: "Could Claude do this?"
- Upskilling creates defensible value
- Writing well differentiates human output from AI slop
#### ⏱️ [00:35:20](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=2120) Management Advice for Slow Productivity
- Transparent workload tracking
- Work-in-progress limits
- Docket clearing meetings 2-3x weekly
- Daily office hours
- Employee portfolio maintenance
## 📚 References
- [Microsoft Work Trend Index Annual Report](https://www.microsoft.com/en-us/research/uploads/prod/2023/05/Work-Trend-Index-Annual-Report.pdf)
- [The Economist: "Prepare for an AI jobs apocalypse"](https://www.economist.com/)
- [Cal Newport's "Slow Productivity" book](https://calnewport.com/slow-productivity/)
- [Cal Newport's "Deep Work" book](https://calnewport.com/deep-work/)
## 🗣️ Paraphrase
Newport argues that the real AI threat isn't job displacement but job degradation through infinite pseudo-productivity. The core problem traces back to using visible activity as a proxy for useful work—a flawed but manageable approach until digital technology amplified it. AI represents the final acceleration toward a "busyness singularity" where work becomes meaningless activity generation.
The solution requires individual workers to escape pseudo-productivity traps through strategic planning, value documentation, skill development, and exceptional communication quality. This isn't just about surviving AI—it's about reclaiming meaningful work in an age of technological acceleration.
## 📰 Newsletter
**Escaping the AI Busyness Trap: Why Your Job Might Get Worse, Not Disappear**
Cal Newport's latest warning isn't about AI taking your job—it's about AI making your job unbearable. His "busyness singularity" concept hits close to home for anyone drowning in Slack notifications and AI-generated reports.
The WordPress community should pay attention: as AI tools proliferate in content creation and site management, the risk isn't unemployment but endless shallow work. Instead of meaningful development, design, or strategy work, we might find ourselves managing AI agents that create content for other AI agents to consume.
Newport's five escape strategies offer a practical roadmap: plan your weeks around real value creation, document your actual accomplishments, avoid work that AI could automate, continuously develop new skills, and write with exceptional clarity and purpose.
For WordPress professionals, this means focusing on high-level strategy, creative problem-solving, and human-centered design—the work that AI can't meaningfully replicate. The tools are getting smarter, but the need for human judgment, creativity, and authentic communication remains paramount.
**Resources:**
- [Cal Newport's Deep Questions podcast](https://calnewport.com/podcast/)
- [Slow Productivity book](https://calnewport.com/slow-productivity/)
- [Digital minimalism principles](https://calnewport.com/digital-minimalism/)
## ✅ Action Items
#### DevRel
- Audit current AI usage in content creation—identify pseudo-productive activities vs. genuine value
- Develop "AI-proof" developer education formats emphasizing hands-on learning and human judgment
- Create portfolio tracking for developer advocacy impact beyond activity metrics
- Design upskilling programs for advanced WordPress development skills
#### Community
- Establish "no-AI" zones in community discussions to preserve authentic human interaction
- Implement portfolio-based recognition systems for contributors beyond commit counts
- Create mentorship programs pairing experienced developers with newcomers for skill transfer
- Develop clear guidelines for AI usage in documentation and tutorials
#### WordPress
- **Core:** Evaluate AI integration proposals against value creation vs. pseudo-productivity metrics
- **Documentation:** Maintain human-crafted examples and tutorials alongside AI-assisted content
- **Training:** Develop cognitive fitness programs for developers and contributors
- **Marketing:** Emphasize human creativity and problem-solving in WordPress positioning
## 🧪 Hypotheses
1. Organizations implementing Newport's five strategies will show measurably higher job satisfaction and productivity than those embracing unrestricted AI automation
2. Teams with transparent workload management and portfolio tracking will resist pseudo-productivity pressures better than teams using traditional activity metrics
3. Individual contributors who deliberately avoid AI-automatable tasks will develop more valuable and defensible skill sets over 12-18 months
4. Weekly planning rituals will prove more effective than daily planning for knowledge workers in AI-augmented environments
5. Writing quality will become an increasingly important differentiator as AI-generated content proliferates
6. The "busyness singularity" will manifest first in industries with high email volume and meeting frequency
## 📊 Methodology
**Longitudinal Studies:** Track job satisfaction, productivity metrics, and career progression for workers implementing Newport's strategies vs. control groups over 2-3 years.
**Workplace Interventions:** Implement transparent workload management, portfolio tracking, and weekly planning in test organizations; measure stress levels, output quality, and retention rates.
**AI Usage Analysis:** Analyze patterns in AI tool adoption across different roles and industries to identify pseudo-productivity vs. value-creation applications.
**Communication Quality Studies:** Develop metrics for written communication clarity and impact; track changes as AI writing tools proliferate.
## ❓ Questions
- How do we measure "actual value" vs. pseudo-productivity in knowledge work roles where output is inherently subjective?
- What specific skills will remain most defensible against AI automation over the next 5-10 years?
- How can organizations restructure performance evaluation to reward depth over visible activity?
- What role should AI play in knowledge work, if any, without triggering the busyness singularity?
- How do we balance individual strategies with systemic workplace culture changes?
## 🔮 Future Research
- **Cognitive Load Studies:** Investigate the mental health impacts of constant AI-mediated work vs. human-focused approaches
- **Skill Evolution Tracking:** Long-term studies on which professional capabilities remain valuable as AI capabilities expand
- **Organizational Design:** Research optimal team structures and management practices for AI-augmented environments
- **Communication Pattern Analysis:** Study how AI-generated content affects human communication skills and workplace relationships
- **Productivity Measurement Innovation:** Develop better metrics for knowledge work value that resist pseudo-productivity gaming
## 💡 Implications
**Practice:** Knowledge workers need immediate strategies to avoid pseudo-productivity traps before AI makes them inescapable. Organizations must redesign performance evaluation systems.
**Policy:** Labor regulations may need updating to address AI-induced workplace stress and the right to meaningful work, not just employment.
**Education:** Professional development programs should emphasize uniquely human capabilities and cognitive fitness rather than tool adoption.
**Technology Design:** AI tools should be designed to augment human creativity and judgment rather than replace human communication and thinking.
## 🧠 Learning Styles Assessment
**Reading Level:** Grade 12-14 (Flesch-Kincaid estimate). Complex concepts presented with concrete examples and clear structure.
#### 👀 Visual learners
**Present:** Clear section headers, Microsoft data visualization, concept progression diagrams
**Improve:** Add flowcharts showing the pseudo-productivity evolution timeline, decision trees for the five strategies, before/after workplace scenarios
#### 🔊 Aural learners
**Present:** Podcast format with clear verbal explanations and examples
**Improve:** Add chapter summaries, key concept repetition, verbal emphasis on critical points
#### 🗣️ Verbal learners
**Present:** Rich vocabulary, clear definitions (pseudo-productivity, busyness singularity), analogies to familiar concepts
**Improve:** Add glossary of terms, expand metaphors (gravitational pull, singularity physics), more storytelling elements
#### 🧩 Kinesthetic learners
**Present:** Step-by-step five-strategy framework, concrete action items
**Improve:** Add weekly planning templates, portfolio-building checklists, hands-on exercises for each strategy
#### 🧠 Logical learners
**Present:** Clear cause-and-effect progression from Drucker to AI, systematic five-point framework
**Improve:** Add decision matrices for strategy selection, quantified metrics for each approach, logical flowcharts
#### 🧑🤝🧑 Social learners
**Present:** Management advice section, team-based solutions
**Improve:** Add discussion questions for team implementation, peer accountability frameworks, collaborative planning exercises
#### 🧘♀️ Solitary learners
**Present:** Individual reflection prompts, personal strategy development
**Improve:** Add self-assessment tools, private journaling prompts for strategy implementation, solo planning exercises
#### 🌿 Naturalistic learners
**Present:** Organic evolution of work problems, ecosystem thinking about workplace culture
**Improve:** Add environmental metaphors, sustainable work practice concepts, holistic system thinking frameworks
## 📊 Accessibility Assessment
#### Screen reader semantics
**Present:** Clear heading hierarchy, descriptive content structure
**Improve:** Add ARIA landmarks for main content sections, descriptive alt text for any visual elements, table headers for data presentation
#### Keyboard navigation
**Present:** Standard text-based content with logical flow
**Improve:** Ensure any interactive elements are keyboard accessible, add skip links for long content sections
#### Contrast and readability
**Present:** Standard text format with good contrast ratios
**Improve:** Ensure any highlighted quotes or callouts meet WCAG contrast requirements, optimize line spacing
#### Text resizing and reflow
**Present:** Standard responsive text format
**Improve:** Test content reflow at 200% zoom, ensure no information is lost at different text sizes
#### Media and captions
**Present:** Video includes spoken content with clear audio
**Improve:** Professional captions for video content, transcript available for podcast format, audio descriptions for any visual elements
#### Forms and interactions
**Present:** Minimal interactive elements
**Improve:** Any feedback forms should include proper labels and error handling
## 🌍 DEIB Assessment
#### Cultural breadth
**Present:** US-centric workplace examples (Microsoft data, American business culture)
**Improve:** Include global perspectives on work culture, examples from different economic systems, awareness of varying workplace norms
#### Inclusive language
**Present:** Gender-neutral professional language, accessible terminology
**Improve:** Expand examples beyond traditional office environments, include diverse work arrangements and job types
#### Neurodiversity support
**Present:** Clear structure, consistent formatting, concrete strategies
**Improve:** Acknowledge different cognitive processing styles, provide multiple implementation approaches, reduce assumption of neurotypical work patterns
#### Representation
**Present:** Focus on workplace experiences that affect many knowledge workers
**Improve:** Include examples from various industries and roles, acknowledge different levels of workplace autonomy and privilege
#### Psychological safety
**Present:** Respectful framing of workplace challenges
**Improve:** Acknowledge that not all workers have equal ability to implement these strategies, provide alternatives for different power dynamics
## ✅ Logical Validity
#### Strong reasoning
**Deductive strength:** The logical progression from pseudo-productivity → digital amplification → AI acceleration follows clearly from stated premises.
**Historical evidence:** Newport provides concrete data (Microsoft statistics) and traces a believable historical progression from the 1950s to present.
**Causal reasoning:** The connection between measurement systems (pseudo-productivity) and behavioral outcomes (busyness culture) is well-supported.
#### Fallacies
**Potential slippery slope:** The "busyness singularity" concept, while compelling, may overstate the inevitable negative outcomes. Not all AI integration leads to meaningless activity loops.
**Survivorship bias:** The five strategies assume workers have significant autonomy to implement changes—may not apply to all workplace contexts or power dynamics.
**False dichotomy:** Presents AI usage as either pseudo-productive or completely avoided, when nuanced integration might be possible.
#### Tone of voice
**Professional and authoritative:** Newport speaks with expertise derived from academic research and book writing. Uses concrete data and systematic analysis while remaining accessible to general audiences.
## 🛡️ DARVO Analysis
No DARVO patterns detected. Newport presents a critique of workplace systems and technology trends without attacking individuals or reversing victim/offender dynamics. The analysis focuses on systemic issues and individual agency rather than personal blame.
## 🎯 Conclusion
Newport's "busyness singularity" concept provides a crucial reframe for AI workplace discussions. Rather than focusing solely on job displacement, we must address how AI might degrade work quality through pseudo-productivity amplification. His five strategies offer practical individual responses, but the deeper challenge requires organizational transformation away from activity-based evaluation toward value-based assessment.
The core insight—that measurement systems drive behavior—suggests that fixing AI's workplace impact requires fixing how we evaluate knowledge work itself. This makes Newport's analysis essential reading for anyone designing AI tools, managing teams, or trying to maintain meaningful work in an increasingly automated world.
## 🔄 Refactor Appendix — AI Makes My Job Miserable. How Do I Escape?
### 📚 Literature Atoms (H3)
#### Pseudo-productivity creates vulnerability to AI acceleration
> [!quote] ID:transcript_0
> When you set up a work environment in which visible activity is rewarded then you give everyone a machine that can automate those efforts making them essentially free. Well, what's going to happen is work will become a mad performative dash of button mashing.
**Context & use**:
- Core mechanism explaining how AI amplifies existing workplace dysfunction
- Demonstrates why fixing measurement systems is prerequisite to beneficial AI integration
**Tags**: #workplace-systems #ai-acceleration #pseudo-productivity
**Highlight**: [view highlight](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=1200)
<!-- atomicity: 1 idea ✓ -->
#### Digital technology progression amplified pseudo-productivity systematically
> [!quote] ID:transcript_1
> Digital technology, computers to networks to mobile computing played poorly with pseudo productivity. And in the 90s into the 2000s, these jobs got increasingly frantic and busy and all-encompassing.
**Context & use**:
- Historical analysis showing current AI problems have deep roots
- Each technological wave (computers, networks, mobile) increased busyness density
**Tags**: #technology-history #workplace-evolution #digital-transformation
**Highlight**: [view highlight](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=800)
<!-- atomicity: 1 idea ✓ -->
#### Portfolio maintenance replaces activity-based evaluation with value demonstration
> [!quote] ID:transcript_2
> You actually want to keep somewhere like in the document like a professor would with their CV a growing list of the important initiatives, projects or accomplishments that you are responsible for.
**Context & use**:
- Practical strategy for escaping pseudo-productivity evaluation
- Creates alternative narrative to visible busyness for career advancement
**Tags**: #performance-evaluation #value-documentation #career-strategy
**Highlight**: [view highlight](https://www.youtube.com/watch?v=rsAay1tB1Q8&t=1600)
<!-- atomicity: 1 idea ✓ -->
### 🧠 Permanent Candidates (H4)
#### Measurement systems drive behavior more than technology itself
**Claim**: Workplace dysfunction from AI stems primarily from pseudo-productivity measurement systems, not the technology's inherent properties.
**Evidence pointer**: [[#Pseudo-productivity creates vulnerability to AI acceleration]]
**Scope & conditions**: Applies when organizations use visible activity as productivity proxy; breaks down when value-based measurement systems exist
**Links**:
- [[Goodhart's Law]] — because extends the principle that measured metrics lose value as targets
- [[Technology adoption patterns]] — because contrasts with deterministic technology narratives
- [[Performance management systems]] — because applies-in organizational design contexts
<!-- atomicity: 1 idea ✓ -->
### ✏️ Fleeting Queue
- Research historical precedents for measurement system changes in knowledge work — how have organizations successfully transitioned from activity-based to value-based evaluation? #fleeting #research
- Investigate whether "cognitive fitness" programs show measurable workplace benefits — potential validation for Newport's underlying assumptions about human capability development #fleeting #validation
### → Things 3
- [ ] Implement weekly planning ritual starting next Monday — block calendar time for high-value work first #things
- [ ] Create portfolio document template and populate with Q4 accomplishments — alternative to activity metrics #things
---
## Full Transcript
[00:00] There are a lot of concerns in our<br>[00:02] current discourse about work and<br>[00:05] technology. Here, for example, is an<br>[00:07] economist article from just a couple<br>[00:09] weeks ago. The headline reads, "Prepare<br>[00:12] for an AI jobs apocalypse. It is not<br>[00:15] here yet, but government should lay a<br>[00:18] safety net." Yikes. Right now, here's a<br>[00:21] a Times headline from just last week.<br>[00:24] California's governor signs AI order<br>[00:26] aimed at protecting workers. Governor<br>[00:29] Gavin Nuome issued an executive order to<br>[00:31] explore an overhaul of labor policies to<br>[00:33] deal with potential mass job<br>[00:35] displacement from artificial<br>[00:37] intelligence. Now, notice what these<br>[00:40] examples have in common. They're all<br>[00:41] about the potential catastrophic loss of<br>[00:45] jobs that might occur if technology<br>[00:47] automates existing roles. But there's<br>[00:50] another possibility that people haven't<br>[00:52] been discussing as much, but it's a<br>[00:54] possibility that I've increasingly come<br>[00:57] to worry about. What if the real fear<br>[01:00] with new advancements like AI is not<br>[01:03] that these technologies are going to<br>[01:04] take your job, but instead are going to<br>[01:07] make your job miserable? And if this is<br>[01:10] true, what specifically can you do to<br>[01:14] avoid this fate? Well, it's Monday,<br>[01:17] meaning it's time for an advice episode<br>[01:19] of this show, which is the perfect<br>[01:20] opportunity to go seek out some answers.<br>[01:24] All right, so here's the plan. I'm going<br>[01:26] to start by telling you a story. A story<br>[01:29] about how technology has slowly and<br>[01:31] somewhat accidentally made knowledge<br>[01:33] work jobs increasingly worse. And then I<br>[01:36] will talk about how the arrival of AI<br>[01:38] might take this long unfolding process<br>[01:41] and accelerate it to an absurd degree,<br>[01:43] creating what I've taken to calling the<br>[01:46] busyiness singularity. Now, once I've<br>[01:48] told you this tale, I'll then share some<br>[01:50] practical advice about what you can do<br>[01:52] individually to avoid the gravitational<br>[01:54] pole of this grim fate. In more detail,<br>[01:58] I have five important suggestions to<br>[02:01] share.<br>[02:03] Uh, and we will go through each of<br>[02:05] those. All right, so we have a lot to<br>[02:06] cover today, so let's get started. As<br>[02:10] always, I'm Cal Newport and this is Deep<br>[02:14] Questions, the show for people seeking<br>[02:16] depth in a distracted world.<br>[02:24] All right, I want to start by telling<br>[02:26] you a story about the evolution of<br>[02:28] knowledge work. And I should say right<br>[02:29] off the bat, if you want the full<br>[02:31] version of this story, you need to read<br>[02:33] part one of my most recent book, which<br>[02:35] is called slow productivity. This is<br>[02:37] basically sort of the the primary source<br>[02:40] material for a lot of what I talk about<br>[02:42] these days about work on this show. So<br>[02:44] you should have your own copy of it. All<br>[02:45] right. So here is the short version of<br>[02:47] the summary I tell in part one, the<br>[02:48] story I tell in part one of that book.<br>[02:50] In the beginning, we have the notion of<br>[02:53] knowledge work emerge in<br>[02:56] the mid 1950s. Roughly speaking, that's<br>[02:58] when the management theorist Peter<br>[02:59] Ducker actually coins the term knowledge<br>[03:01] work. His job was to help the business<br>[03:05] leaders of America in particular<br>[03:06] understand what knowledge work is and<br>[03:09] how it differs from the industrial work<br>[03:10] that had been driving the American<br>[03:12] economy up to that point. Now, one of<br>[03:14] the key concepts of knowledge work that<br>[03:16] Peter Ducker drilled into the heads of<br>[03:18] American executives was autonomy. Unlike<br>[03:21] assembly line workers, knowledge workers<br>[03:22] are creative and have specific skills.<br>[03:25] They often know more about what they're<br>[03:26] doing than the managers who manage them.<br>[03:28] So instead of trying to give them an<br>[03:29] exact step-by-step checklist to follow<br>[03:31] like you would do if you're building a<br>[03:33] Magneto for a Model T Ford, you need to<br>[03:36] give them autonomy to figure out how<br>[03:39] they're going to work and what they're<br>[03:40] going to do with their work. It's much<br>[03:41] more it's going to need to be much more<br>[03:42] of a hands-off management style. Well,<br>[03:44] this created a problem for managers<br>[03:45] because how do we manage knowledge<br>[03:46] workers if we can't just have a uh a<br>[03:50] pile of widgets we look at and say, "How<br>[03:52] many did you produce today?" If they're<br>[03:53] autonomous, how do we manage them? The<br>[03:56] implicit answer that arose is what I<br>[03:58] call pseudo productivity. It was a<br>[03:59] heristic that says, let's use visible<br>[04:01] activity as a proxy for useful effort.<br>[04:04] The more we see you doing, the more<br>[04:07] useful we'll assume you're being. Now,<br>[04:10] this is not a very precise way to manage<br>[04:12] productivity in the knowledge sector,<br>[04:13] but you know, for decades, it worked<br>[04:15] well enough, right? It was like at the<br>[04:18] water cooler if the boss comes in change<br>[04:20] your conversation from you know the<br>[04:24] latest episode of ALF to instead some<br>[04:26] worklike topic. This was also like the<br>[04:28] madman era like well we'll just be here<br>[04:30] long hours so we look busy but also<br>[04:32] we'll have like full bars in our<br>[04:34] offices. So like pseudo productivity<br>[04:35] wasn't the best way of actually managing<br>[04:37] knowledge workers but it was good<br>[04:39] enough.<br>[04:41] Then digital technology arrives in the<br>[04:44] office environment and this is where<br>[04:47] pseudo productivity begins to take a<br>[04:49] turn for the worst at least when it<br>[04:51] comes to the subjective experience of<br>[04:52] the individual workers. First we get<br>[04:55] computers on the desk. This greatly<br>[04:57] increased the number of different things<br>[04:59] that each individual worker could work<br>[05:01] on. Many of these things would be<br>[05:03] administrative focus. Many of these<br>[05:05] things are sort of neverending. There's<br>[05:06] like endless things you could be doing.<br>[05:08] Well, that created a new level of<br>[05:09] busyness<br>[05:11] uh that didn't exist before we had the<br>[05:14] computer. And in a pseudo productive<br>[05:15] environment where more busyness is<br>[05:17] better than less, we began to feel like<br>[05:20] we had to run after all these different<br>[05:21] things. And suddenly we were switching<br>[05:23] our attention back and forth between<br>[05:25] different meaning more tasks than we had<br>[05:26] been before. Then we get networking<br>[05:28] technology. Weorked up these computers,<br>[05:30] giving us tools like email. Well, this<br>[05:33] increased both the granularity and rate<br>[05:34] at which you could now demonstrate to<br>[05:36] people that you were doing uh visible<br>[05:38] effort, right? It used to be you had to<br>[05:40] just be at the office and kind of hide<br>[05:42] the martini glass when the boss walked<br>[05:44] by. Now, how quickly you respond to an<br>[05:47] email thread is an indication of useful<br>[05:50] effort. How many emails you send to<br>[05:51] people is an indication of effort. So,<br>[05:54] now there was this incredibly fine grain<br>[05:56] granularity at which you could be<br>[05:57] demonstrating that you are pseudo<br>[05:58] productive. And then finally we got<br>[06:00] mobile computing, laptops and then<br>[06:02] smartphones which meant the times and<br>[06:04] locations in which you could be working<br>[06:05] became nearly endless which again in a<br>[06:07] pseudo productive environment was a<br>[06:09] disaster because now every moment that<br>[06:11] you weren't in the office you still were<br>[06:13] navigating this question of should I in<br>[06:15] this moment jump on my phone or my<br>[06:18] laptop answer some emails jump on Slack<br>[06:19] demonstrate some sort of effort because<br>[06:21] the more busyness the better. So it<br>[06:22] became a neverending tension. So digital<br>[06:26] technology, computers to networks to<br>[06:27] mobile computing played poorly<br>[06:31] with pseudo productivity. And in the 90s<br>[06:34] into the 2000s, these jobs got<br>[06:36] increasingly frantic and busy and<br>[06:39] all-encompassing.<br>[06:41] The result of this sort of supercharging<br>[06:44] of busyness has not been great. Uh I'm<br>[06:48] going to bring up on the screen here for<br>[06:49] example this report I like to talk about<br>[06:52] from Microsoft the work trend index<br>[06:54] annual report. This where Microsoft used<br>[06:56] data from their online office products<br>[06:58] uh to figure out what online workers are<br>[07:00] actually doing. There's a chart in here<br>[07:02] that I think is really telling. Here's<br>[07:04] what they found in their uh data. The<br>[07:07] average number of emails received per uh<br>[07:10] per employee each workday is 117. The<br>[07:13] average numbers of Teams messages<br>[07:14] received per workday 153. The portion of<br>[07:17] meetings that are ad hoc called in the<br>[07:19] moment without a calendar invitation<br>[07:20] 57%. The average time between<br>[07:22] interruptions by a meeting, email or<br>[07:24] message during core work hours once<br>[07:26] every two minutes. Right? So what we're<br>[07:29] seeing there is a portrait of work<br>[07:32] getting insane<br>[07:34] and not because of some deep capitalist<br>[07:37] plot to exploit the workers that for<br>[07:38] some reason we weren't implementing<br>[07:40] until we got to the 90s or 2000s. It's<br>[07:42] because technology played poorly with<br>[07:44] pseudo productivity. Um, I'm going to<br>[07:46] load up another headline here. This is<br>[07:48] another natural consequence. This<br>[07:50] headline from Axio says, "Global survey,<br>[07:53] worker burnout reaches new high." This<br>[07:56] is going to be the obvious consequence<br>[07:58] of a work that is now hyper busy. And<br>[08:02] so, this is sort of the story I tell in<br>[08:03] slow productivity. I think it's one of<br>[08:04] the defining stories of office work in<br>[08:07] the 21st century. But all of this<br>[08:10] happened before generative AI began to<br>[08:13] make its move into the workplace. So<br>[08:15] what's the effect of this new technology<br>[08:17] when we add this into the mix? What's<br>[08:19] its effect onto this ongoing story?<br>[08:22] Well, this is where things get even<br>[08:24] worse. People often talk about LLM power<br>[08:26] tools as providing some sort of<br>[08:28] productivity miracle, right? We hear<br>[08:29] reports of computer programmers who are<br>[08:31] handing off the actual writing of<br>[08:34] computer code to AI and we imagine this<br>[08:36] is coming for all of our other main work<br>[08:38] as well and all these other jobs. And<br>[08:40] this gets us either terrified or excited<br>[08:41] about AI's possibility. But what's<br>[08:43] really happening with AI in most<br>[08:45] non-computer programming office jobs<br>[08:47] right now, it's much more mundane. Here<br>[08:50] are the most common uses of AI in most<br>[08:52] non-programming office jobs at the<br>[08:55] moment. Writing long emails<br>[08:56] automatically,<br>[08:58] summarizing long emails, automatically<br>[09:01] creating slide decks, transcribing<br>[09:03] meetings, and turning transcriptions<br>[09:04] into some sort of work product that can<br>[09:06] then be shared, creating verbose<br>[09:08] reports, and trend analyses. So having<br>[09:10] to do some research and then write a<br>[09:11] report. What unifies those examples<br>[09:15] is that they're all more or less pseudo<br>[09:18] productive activities. The type of<br>[09:20] things you do to demonstrate effort to<br>[09:22] show that you're busy, but that bring uh<br>[09:25] not a ton of actual value to the bottom<br>[09:27] line. Clients aren't paying for the<br>[09:30] reports or emails you're sending back<br>[09:31] and forth. So AI right now is often<br>[09:34] being used in the office to support<br>[09:37] pseudo productive activities as things<br>[09:39] you do to show that you are being busy.<br>[09:42] Now the problem is is AI has essentially<br>[09:44] reduced the cost and friction of these<br>[09:46] existing pseudo productivity act pseudo<br>[09:47] productive activities down to zero.<br>[09:50] So what happens when you set up a work<br>[09:52] environment in which visible activity is<br>[09:54] rewarded then you give everyone a<br>[09:55] machine that can automate those efforts<br>[09:57] making them essentially free.<br>[10:00] Well, what's going to happen is work<br>[10:01] will become a mad performative dash of<br>[10:03] button mashing. Who can turn out more<br>[10:05] slop quicker than the next person? As<br>[10:09] soon we'll be managing teams of agents<br>[10:11] that are producing emails and slide<br>[10:13] decks on our behalf while intercepting,<br>[10:14] summarizing, and responding to those<br>[10:16] incoming AI decks that have been<br>[10:18] generated by other people's agents. It<br>[10:20] will be a digital blitz of back and<br>[10:21] forth nothingness. The density of<br>[10:23] shallow work here will become infinite.<br>[10:25] It will collapse in on itself. you will<br>[10:27] end up with a busyiness singularity.<br>[10:30] It's productivity reductto ad absurdum.<br>[10:35] All right. So if we step back here,<br>[10:37] what we're facing is not really an AI<br>[10:39] problem in the sense of oh everything<br>[10:41] was fine and then AI came along and<br>[10:43] created a new problem. Pseudo<br>[10:45] productivity was never the right answer<br>[10:47] for measuring useful effort in the<br>[10:48] knowledge work. And with each new decade<br>[10:50] a new technology came along that made<br>[10:52] these shortcomings even more apparent.<br>[10:54] And it's on this trajectory that when<br>[10:57] you then throw AI into the mix, we now<br>[10:59] are collapsing towards a<br>[11:01] self-destructive<br>[11:03] conclusion.<br>[11:04] This busyiness singularity to me is<br>[11:07] going to have a much more widespread<br>[11:09] negative consequence<br>[11:12] societywide<br>[11:13] than the threats of jobs being fully<br>[11:16] automated. Hey, let's take a quick break<br>[11:18] to hear from some of our sponsors.<br>[11:21] Now, if you listen to this show, then<br>[11:23] presumably you're interested in ideas<br>[11:25] about taking control of your mind to<br>[11:28] produce deep results in a distracted<br>[11:29] world. But there can be a difference<br>[11:31] sometimes between scattered advice like<br>[11:33] I'm giving over a bunch of different<br>[11:35] podcast episodes and a carefully<br>[11:37] produced class. This is why I recently<br>[11:40] recorded my very own masterclass course.<br>[11:44] It's called Rebuild Your Focus and<br>[11:46] Reclaim Your Time. And it's a<br>[11:48] comprehensive look at the types of<br>[11:50] things we talk about here on this show.<br>[11:53] Now, I was excited to record this class,<br>[11:56] not just because I wanted to get my<br>[11:57] ideas out there, but because uh I'm a<br>[11:59] masterclass fan myself, just to name a<br>[12:01] few examples among many, I've eagerly<br>[12:03] devoured Malcolm Gladwell's, Aaron<br>[12:05] Sorcin, and Ron Howard's Masterclass<br>[12:08] courses, and I've enjoyed every one.<br>[12:10] Now, here's the relevant details.<br>[12:12] Masterclass offers more than 200 classes<br>[12:14] across 14 categories taught by the<br>[12:16] world's best instructors, including<br>[12:19] yours truly. You can watch the classes,<br>[12:22] but you can also listen to them in audio<br>[12:24] mode on your phone, meaning you can<br>[12:26] learn while working out or commuting or<br>[12:28] doing the dishes. And it's affordable<br>[12:29] with plans starting at just $10 a month<br>[12:31] when you choose the bill annually.<br>[12:34] MasterClass keeps adding new classes, so<br>[12:36] there's never been a better time to get<br>[12:38] in. Right now, as a listener of this<br>[12:40] show, you can get at least 15% off any<br>[12:44] annual membership at<br>[12:46] masterclass.com/deep.<br>[12:49] That's 15% off atmasterclass.com/deep.<br>[12:54] Head to masterclass.com/deep<br>[12:57] to see the latest offer. I also want to<br>[13:01] talk about our friends at Lariden.<br>[13:02] Here's something I've learned as someone<br>[13:04] who writes about technology. Sometimes<br>[13:07] figuring out how best to use a new tool<br>[13:09] can be just as hard as innovating the<br>[13:10] tool in the first place. This certainly<br>[13:13] seems to be the case with AI right now<br>[13:15] where you have teams rushing to deploy<br>[13:16] dozens of different tools with no clean<br>[13:18] way of figuring out which ones actually<br>[13:20] help. Sometimes this will make things<br>[13:22] worse rather than better. Which is all<br>[13:24] to say the real challenge at the moment<br>[13:26] isn't just adopting AI, it's<br>[13:28] understanding how it's being used and<br>[13:30] how to maximize the value you're getting<br>[13:31] from it. This is exactly what Laridin<br>[13:34] focuses on. Laridan gives a clear view<br>[13:36] of AI tool adoption and how teams are<br>[13:38] using them daily. No more guesswork. It<br>[13:41] tracks real usage data and outcomes so<br>[13:43] you can connect AI activity to actual<br>[13:45] business results. It can even help you<br>[13:48] enforce internal policies and manage<br>[13:50] risks which is critical as AI usage<br>[13:52] grows. So if AI is already a part of<br>[13:55] your organization, now is the moment to<br>[13:57] get control of it. Head to laridin.com<br>[14:00] today and book a demo to start<br>[14:01] maximizing impact from AI. That's<br>[14:03] lariden lr<br>[14:06] i d i n.com.<br>[14:09] All right, let's get back to the show.<br>[14:11] All right, so what can you as an<br>[14:14] individual do<br>[14:16] to try to escape the worst effects of<br>[14:20] this coming busyness singularity?<br>[14:22] Well, I have five suggestions that I I'm<br>[14:25] going to offer. I'll go through these uh<br>[14:28] one by one and we will discuss. All<br>[14:31] right, the first suggestion,<br>[14:34] plan weekly. All right, let me talk<br>[14:37] about that. Here's what I want you to do<br>[14:39] and then I'll explain why. On Monday<br>[14:41] morning, I want you to look at the week<br>[14:42] ahead. I want you to ask what important<br>[14:46] things, things that create non-ambiguous<br>[14:48] value for your organization.<br>[14:50] Do you want to make progress on that<br>[14:52] week? That I want you to find and<br>[14:54] protect time for it on your calendar<br>[14:56] like you were scheduling a meeting or an<br>[14:58] appointment. This might mean cancelling<br>[15:00] or rescheduling less important things<br>[15:02] that are already on your calendar to<br>[15:04] open up bigger swats of time to make<br>[15:06] progress on the things that are actually<br>[15:08] important. Now, why do I want you to do<br>[15:10] this? Because when you zoom into the<br>[15:12] moment of a given day, it's easy to get<br>[15:15] lost in pseudo productive busyiness.<br>[15:17] There's always more emails to send or<br>[15:18] slide decks to create or transcriptions<br>[15:20] to mess around, things that look like<br>[15:22] you're on it and you're busy.<br>[15:25] And so, if you're just saying, "What do<br>[15:26] I want to work on next?" the obvious<br>[15:28] answer will almost always be something<br>[15:29] pseudo productive. So if you want to<br>[15:31] make uh open up some space between you<br>[15:33] and pseudo productivity and actually<br>[15:35] start producing value, you got to plan<br>[15:37] in advance and the weekly scale is a<br>[15:39] very good way of doing that. All right,<br>[15:43] what's my second tip? Let's go back to<br>[15:44] our big list here.<br>[15:47] Number two,<br>[15:49] maintain a portfolio.<br>[15:52] All right. So, what I mean by this<br>[15:56] is uh you actually want to keep<br>[16:00] somewhere like in the document like a<br>[16:02] professor would with their CV a growing<br>[16:05] list of the important initiatives,<br>[16:07] projects or accomplishments that you are<br>[16:09] responsible for. So, if tip number one<br>[16:11] was about finding more time to do<br>[16:13] valuable activities, tip number two is<br>[16:15] about keeping a record of the valuable<br>[16:17] things you actually did.<br>[16:20] You want an alternative to just let my<br>[16:23] visible busyness<br>[16:25] be how you judge me. You want an<br>[16:27] alternative to that that's actually<br>[16:28] grounded in actual value producing<br>[16:30] accomplishment activities and<br>[16:32] initiatives. So actually keep track of<br>[16:33] it. Here's what I did this month. Here's<br>[16:35] what I did this quarter. I took on this<br>[16:38] project. We did this. It had this<br>[16:40] positive consequence. I did this with<br>[16:42] this product. We made these changes.<br>[16:44] Here's the hardest part about it. Here's<br>[16:45] where I brought my expertise. It had<br>[16:46] these positive consequences. You're<br>[16:48] going through and creating a portfolio<br>[16:51] of things you did that actually brought<br>[16:54] value. Now, you actually want to share<br>[16:56] this. This could be something that you<br>[16:58] bring into your quarterly reviews. It<br>[16:59] could be something that you show to your<br>[17:01] bosses. It can say, "Here's what I was<br>[17:03] did last quarter. What should I focus on<br>[17:06] for the quarter ahead?"<br>[17:08] What you're trying to do here is rewrite<br>[17:10] their understanding of you and your<br>[17:11] value away from pseudo productivity and<br>[17:13] towards the actual pursuit of things<br>[17:15] that are valuable. try to free you from<br>[17:18] this trap of just trying to<br>[17:20] automatically generate busyiness.<br>[17:24] All right, I have a third idea here.<br>[17:27] Bring up my my big list.<br>[17:31] Avoid what AI can do. Well, if you read<br>[17:35] my 2016 book, Deep Work, I have this<br>[17:38] suggestion in there where I say, "Hey,<br>[17:40] when thinking about what activities to<br>[17:42] spend your time on in a professional<br>[17:44] context, ask yourself the question, is<br>[17:45] this something that a smart 22-year-old<br>[17:48] recent college graduate could do on my<br>[17:50] behalf with just like a little bit of<br>[17:52] training?" And if the answer is yes, I<br>[17:55] wrote that's an indication that this is<br>[17:58] not a an activity that's really making<br>[18:00] use of hard one skills. And so it's a<br>[18:02] lower value producing activity and it's<br>[18:04] something that you shouldn't spend as<br>[18:05] much time on. You want to find<br>[18:06] activities that a smart 22-year-old<br>[18:08] without your particular skills and<br>[18:09] training could do. Well, we have a<br>[18:11] better version of this test today which<br>[18:13] I think is this something that I could<br>[18:15] have, you know, claude co-work do? Is<br>[18:17] this something that I could like largely<br>[18:19] automate with chat GPT queries? And if<br>[18:22] the answer is yes, you say then I want<br>[18:24] to avoid that activity to the extent<br>[18:25] possible. I want to move my work away<br>[18:28] from things that AI can do and towards<br>[18:31] things that it cannot. If most of what<br>[18:34] you're doing is just automated by AI or<br>[18:36] soon will be, then you are vulnerable.<br>[18:39] You're kind of bringing this on<br>[18:40] yourself. If you say, "Yeah, I I go to<br>[18:43] the meetings, I get the transcripts, I<br>[18:44] create slide decks, I write a summary of<br>[18:46] the points with AI, all this in AI, I<br>[18:48] have an AI agent send this out to<br>[18:49] everybody." You might feel like you're<br>[18:52] doing a lot of things, but these efforts<br>[18:54] the AI is doing or could do. So, you're<br>[18:56] producing very little value yourself.<br>[18:57] You're more vulnerable. So, just do the<br>[18:59] AI test. Is this something that like an<br>[19:02] AI agent or chatbot could do or do most<br>[19:05] of? Then I want to move away towards<br>[19:06] something else. If the answer is no, I<br>[19:08] wouldn't even know how to use AI to<br>[19:10] really help this except for like at the<br>[19:12] edges, then good. I want to spend more<br>[19:14] time doing that. So, you need to move<br>[19:16] away from activities where it's obvious<br>[19:17] that AI can do them. You're not being<br>[19:19] productive if you're letting AI automate<br>[19:21] your work. You're working on things that<br>[19:23] is not very valuable.<br>[19:25] All right, my fourth piece of advice,<br>[19:28] let's do the big reveal.<br>[19:32] Pursue upskill<br>[19:35] projects.<br>[19:36] So, what you should be doing is always<br>[19:38] have some sort of new skill that's<br>[19:40] valuable and relevant to your job that<br>[19:42] you're working on. Something that will<br>[19:43] make you more rare and valuable in your<br>[19:45] field. if possible to find a way to<br>[19:48] connect this skill to a project you're<br>[19:49] doing for your job, right? So like I I<br>[19:51] hey, I will take on this responsibility<br>[19:53] boss that in order to do this project, I<br>[19:55] have to learn a new skill. So at least<br>[19:56] you can get credit for doing it. But if<br>[19:58] you can't do that, then just take a half<br>[20:00] hour every day to be making slow and<br>[20:01] steady progress on learning something<br>[20:03] new that is going to be valuable for<br>[20:04] your job. It's a the harder your skill,<br>[20:07] the more rare and valuable the skill,<br>[20:09] the more you can escape the trap of AI<br>[20:12] accelerated pseudo productivity because<br>[20:14] you're now playing the game of hard one<br>[20:16] value that you can point to and say, "I<br>[20:18] did this and it's valuable." You can the<br>[20:21] better you are at things, the more<br>[20:22] valuable things you can do, the less you<br>[20:24] have to play the game of using visible<br>[20:26] business as a proxy for useful effort.<br>[20:30] All right, the final tip I am going to<br>[20:32] suggest<br>[20:35] Write well.<br>[20:38] Differentiate yourself by from the AIS<br>[20:40] by writing well, taking the time to<br>[20:43] write well. Make your emails, your<br>[20:46] reports, anytime you're putting down<br>[20:48] professional text, make it super clear,<br>[20:50] make it super concise, make it succinct,<br>[20:52] make it well crafted. Make it clear it's<br>[20:55] from a human. Well, everyone else is<br>[20:57] going to be sending out these long<br>[20:59] reports with bullet point lists with<br>[21:01] emojis next to the list for some reasons<br>[21:03] and all sorts of sort of convoluted<br>[21:05] language or you're like, "This this<br>[21:07] seems like it's smart, but when I look<br>[21:08] closer, I have no idea what it's<br>[21:10] actually saying." Coming succinct,<br>[21:12] coming clear.<br>[21:14] This is the issue.<br>[21:16] We can do it. This is a trap. This is<br>[21:18] the right way forward. Here's what we<br>[21:20] should do. We can make this happen.<br>[21:22] Right? Clear, succinct, and smart. Care<br>[21:24] about your writing. So when more people<br>[21:26] are trying to automate their writing,<br>[21:28] you should spend longer on your writing<br>[21:30] than you were before. It's a huge<br>[21:31] differentiator from you and what's going<br>[21:34] on with AI. It means that people value<br>[21:37] the things you send more than other<br>[21:40] things. So if you're sending less<br>[21:41] because you're avoiding the pseudoity<br>[21:43] trap, that's okay because everything<br>[21:44] else is going to seem sort of sloppy and<br>[21:46] your things might be more rare, but it's<br>[21:48] to the point when you send it. you're<br>[21:50] trying to uh set yourself up as this<br>[21:52] sort of alternative to what's going on<br>[21:55] with some of this AI autogen. So, let's<br>[21:57] look at these five things again. I think<br>[21:58] this is what you can do right now to<br>[22:00] help escape the busyiness singularity.<br>[22:02] Use weekly plans to make sure you're<br>[22:03] making time for what values. Maintain a<br>[22:05] portfolio so you can point to other<br>[22:07] people. Here's the stuff I'm doing<br>[22:09] that's actually valuable that's<br>[22:10] unrelated to how busy I am. Avoid what<br>[22:12] AI can do. Tasks that could be easily or<br>[22:15] substantially automated by AI or tasks<br>[22:16] you need to spend less time on. Always<br>[22:19] be pursuing upskill projects. You want<br>[22:21] to be better, better, better, better<br>[22:23] better. You have to rely on skills, not<br>[22:24] busyness. If you're going to survive<br>[22:26] this moment without going insane and<br>[22:28] value your writing, be succinct, clear,<br>[22:30] and valuable when you write so you don't<br>[22:32] have to write as much and yet still get<br>[22:35] a lot of value or a claim for what you<br>[22:36] do produce in your professional in the<br>[22:39] professional context. All right, so this<br>[22:42] is what you know, it's an idea I've been<br>[22:44] developing. If you're and look, computer<br>[22:46] programmers have their own issues. You<br>[22:48] should listen to a couple weeks ago I<br>[22:50] did a whole AI reality check episode on<br>[22:52] what's really happening with computer<br>[22:53] programming. There's all sorts of issues<br>[22:54] with AI in the fields. Last week I did<br>[22:56] something on what's happening in<br>[22:57] mathematics with AI. These are the<br>[22:59] fields where AI is best suited to play.<br>[23:03] But when it comes to like normal<br>[23:04] knowledge work jobs, you're not a<br>[23:05] professional mathematician or computer<br>[23:07] scientist. You're not a programmer. This<br>[23:09] is what I'm worried about. The busyiness<br>[23:10] singularity pseudo productivity being<br>[23:12] pushed reduct absurdum. And these are<br>[23:15] the type of things. This is what you<br>[23:16] have to be doing now is you have to<br>[23:18] leave the pseudo productivity trap. This<br>[23:20] is the time to start leaving pseudo<br>[23:21] productivity and moving towards depth.<br>[23:24] It's the time to stop relying on visible<br>[23:26] activity as your main marker of value in<br>[23:28] the workplace and instead relying on<br>[23:30] actual hard one things you did and can<br>[23:32] point to. Now it might seem scary at<br>[23:34] first because there's a certain<br>[23:35] predictable comfort to just sitting<br>[23:37] there and sending emails and having AI<br>[23:38] make that even easier. But that is a<br>[23:40] trap. That's not sustainable. It's going<br>[23:42] to become increasingly exhausting and<br>[23:44] you will become increasingly vulnerable.<br>[23:46] Do the hard work of actually doing hard<br>[23:48] work. That is the key to differentiating<br>[23:50] yourself in our current technological<br>[23:53] moment. All right. So, there we go.<br>[23:55] Jesse, I got all the tape off this time.<br>[23:58] >> Yeah,<br>[23:58] >> that's the that's my my protest against<br>[24:01] technology is using painters tape and a<br>[24:03] notebook as like our main graphical<br>[24:05] element on this show.<br>[24:07] >> Do you have new terms in your new book<br>[24:09] that you've developed like pseudo<br>[24:11] productivity? Um, yes. I always have new<br>[24:13] terms.<br>[24:14] >> Yeah, you always have good great new<br>[24:15] terms.<br>[24:15] >> Yeah. So, so for the Deep Life book I'm<br>[24:17] working on, uh, which I'm the final<br>[24:20] edits for the pre-cop like just the main<br>[24:23] edits, the final edits are being done,<br>[24:25] you know, as you hear this episode by<br>[24:27] the end of the week you're hearing this<br>[24:28] episode in theory, I will have submitted<br>[24:31] the the sort of polished version of that<br>[24:33] book. Yeah. that if lifestyle and you've<br>[24:34] heard these on the show before,<br>[24:35] lifestyle ccentric planning, the phase<br>[24:37] shift model of the deep life is being<br>[24:39] worse than the lifestyle ccentric<br>[24:41] approach to to the deep life. Um I I get<br>[24:44] into lifestyle visions, lifestyle<br>[24:46] properties,<br>[24:47] uh keystone habits, things like uh<br>[24:50] property scraping, residence isolation.<br>[24:53] I got a lot of terms in that book. It's<br>[24:54] a very practical book, which is which is<br>[24:56] the way I'm trying to write it. And then<br>[24:57] the new book idea I have, if I end up<br>[24:58] writing it about thinking, is all going<br>[25:00] to be about cognitive fitness, which is<br>[25:02] a term that I'm also really trying to<br>[25:03] promote.<br>[25:04] >> I was I was actually brought that that<br>[25:06] idea is kind of making the rounds.<br>[25:07] There's an Atlantic piece last week<br>[25:09] where the president of Amherst, I think,<br>[25:10] was basically reacting to my idea of<br>[25:12] cognitive fitness. He thought it sounded<br>[25:14] too grim and that college would be more<br>[25:16] fun. But I've actually written tons of<br>[25:18] stuff about how to make the intellectual<br>[25:19] life of college fun. Go back and see<br>[25:21] like five years of my writing from the<br>[25:23] the late 2000s. Um, so we're actually<br>[25:25] more on the same page on that than he<br>[25:27] might realize. But the key thing here is<br>[25:28] the idea is out there. It's being<br>[25:30] reacted to. So, you know, the more I can<br>[25:33] change the vocabulary,<br>[25:35] the happier I am, for whatever that's<br>[25:36] worth. All right, I want to take another<br>[25:38] quick break to hear from our sponsors.<br>[25:41] Look, starting a new business is hard. I<br>[25:43] remember what it was like starting up<br>[25:44] the media company that produces this<br>[25:46] podcast. Here's what I learned. Don't<br>[25:49] reinvent the wheel. Trust existing<br>[25:51] industry leaders where you can. And this<br>[25:53] is where Shopify enters the scene. If<br>[25:55] you need to sell something, you need<br>[25:57] Shopify. Shopify is the commerce<br>[26:00] platform behind millions of businesses<br>[26:02] around the world and 10% of all<br>[26:04] e-commerce in the US. From big names<br>[26:06] like Allirds and Mattel to new brands<br>[26:08] just getting started. Want to sell<br>[26:10] online? Get started with your own design<br>[26:12] studio. With hundreds of readytouse<br>[26:14] templates, Shopify helps you build a<br>[26:16] beautiful online store that matches your<br>[26:17] brand style. Need help spreading the<br>[26:19] word? Shopify can help you easily create<br>[26:22] email and social media campaigns<br>[26:23] wherever your customers are scrolling or<br>[26:26] strolling. If we ever start selling<br>[26:28] products related to this show, I know<br>[26:30] exactly what platform we'll use.<br>[26:32] Shopify. So, it's time to turn those<br>[26:34] whatifs into with Shopify today. Sign up<br>[26:39] for your $1 per month trial today at<br>[26:41] shopify.com/deep.<br>[26:42] Go to shopify.com/deep.<br>[26:45] That's shopify.com/deep.<br>[26:48] Hey, going online without ExpressVPN<br>[26:51] is like forgetting to mute yourself on a<br>[26:53] Zoom meeting. Sometimes it might end up<br>[26:56] okay, but eventually your colleagues are<br>[26:57] going to hear you talking trash about<br>[26:58] them to someone in the next room. All<br>[27:01] right, let me get into the weeds a<br>[27:03] little bit about what I mean by that.<br>[27:04] When you go online, you request the<br>[27:06] websites and services are included in<br>[27:08] little bundles that are called packets.<br>[27:10] Now, the contents of these packets might<br>[27:12] be encoded, but the address of where<br>[27:14] those packets are being sent is not. And<br>[27:17] this means that your internet service<br>[27:18] provider knows exactly what sites and<br>[27:20] services you are using. And in the US,<br>[27:24] they are legally allowed to collect and<br>[27:26] sell that information to advertisers.<br>[27:28] A VPN helps you reclaim your privacy. It<br>[27:31] works by encoding your entire packet and<br>[27:35] then sending it to a VPN server that<br>[27:36] then decodes it and talks to the site<br>[27:38] and service on your behalf. Then it<br>[27:40] encodes the answer and sends that back<br>[27:42] to you. So, all your internet service<br>[27:44] provider learns is that you're<br>[27:45] communicating with a VPN server, not<br>[27:47] what specific sites and services you're<br>[27:49] actually talking to. Your actual traffic<br>[27:51] is hidden. Now, if you're going to use a<br>[27:53] VPN, I recommend ExpressVPN.<br>[27:57] Why? Here are three things I personally<br>[27:59] find compelling about this service.<br>[28:01] Number one, it's affordable with plans<br>[28:04] starting at just $349 a month. Number<br>[28:06] two, it's easy to use. You just click a<br>[28:09] button to launch the app and you're<br>[28:11] protected. You can now just use your<br>[28:12] apps and browsers as you normally would.<br>[28:14] And three, it works on all of your<br>[28:16] devices from phones to laptops to<br>[28:18] tablets and more. So you can get privacy<br>[28:21] however you're accessing the internet.<br>[28:23] So protect your online privacy today by<br>[28:26] visiting expressvpn.com/deep.<br>[28:28] That's exvvpn.com/deep<br>[28:32] to find out how you can get up to four<br>[28:34] extra months. ExpressVPN.com/deep.<br>[28:38] All right, let's get back to the show.<br>[28:41] All right. Well, that's enough about my<br>[28:43] thoughts. Now, it's time to hear what<br>[28:45] you have to say. As is our tradition on<br>[28:47] Mondays.<br>[28:48] We like to open the show's inbox to read<br>[28:50] some of your messages. Remember, if you<br>[28:52] have a question, comment, or interesting<br>[28:53] article, or idea to share, you can reach<br>[28:55] us at
[email protected].<br>[28:59] All right, Jesse, where are we going to<br>[29:00] start this week?<br>[29:03] We received a bunch of notes and<br>[29:04] comments in reaction to your newsletter<br>[29:06] from last week about LLMs and the<br>[29:08] sacredness of speech.<br>[29:10] >> Yeah, we did. People were into this one.<br>[29:12] All right, so let me just load up the<br>[29:14] essay real quick on the screen. It was<br>[29:15] called on gods and LLMs. Um, it opens,<br>[29:20] you know, I talk about Genesis. I talk<br>[29:22] about the identification of humans as<br>[29:25] speaking beings. Uh, I'll just read one<br>[29:28] quote from the Rabbi Shai held.<br>[29:30] According to the medieval commentary<br>[29:31] Rashi, speech is thus not only central<br>[29:33] to who we are as human beings, it is<br>[29:34] also key to our uniqueness alone among<br>[29:36] God's creations. Jewish tradition<br>[29:38] affirms human beings are capable of<br>[29:40] speech. The essay goes on to say,<br>[29:42] "There's something sacred about the<br>[29:44] production of ideas, whether it's<br>[29:46] vocalized or written. It's a telepathy.<br>[29:49] It's a mind state from one human being<br>[29:51] recreated in another human's mind. It's<br>[29:54] the foundation on which we democratize<br>[29:57] holiness and from that all the ideas we<br>[29:59] enjoy today about things like human<br>[30:01] rights and justice that speech<br>[30:04] is at the core of the human experience<br>[30:07] and then the point of the article is<br>[30:08] asking the question the ethical question<br>[30:11] so is there something profane then about<br>[30:13] letting a machine produce speech as well<br>[30:16] is this like unique to humans something<br>[30:18] we should cherish or something like<br>[30:19] machines can do this as well we'll just<br>[30:21] automate it around so I I I asked that<br>[30:23] question. This generated a lot of<br>[30:25] feedback. I'll read a few of these<br>[30:26] pieces of feedback here. Uh Yeshua said,<br>[30:30] "Great peace. I'm an Orthodox Jew and I<br>[30:33] had not had I not known otherwise, your<br>[30:35] piece could have come straight out of a<br>[30:37] rabbis Shabbat sermon." Well, this does<br>[30:41] seem I don't know, Jesse, like a good<br>[30:43] place for a blasphemous Cal Network<br>[30:45] joke. Here's the one I came up with. Cal<br>[30:49] Network doesn't give sermons about God.<br>[30:51] God gives sermons about Cal Network.<br>[30:55] Something I'm gonna go to hell for. Um,<br>[30:58] all right. Let's see what else we have<br>[30:59] here. Thomas wrote and said, "I consider<br>[31:01] LLMs to be practice for communicating in<br>[31:04] real life, not a substitute. What I do<br>[31:06] is similar to what Ben and David of<br>[31:08] Acquired do. They use Claude that train<br>[31:09] themselves on their spiel and test the<br>[31:11] coherence of their ideas and then they<br>[31:12] hit the recording booth and talk to each<br>[31:14] other." I think that's the model. I<br>[31:16] mean, I get that, Thomas. I know people<br>[31:17] do that. They they test out ideas. The<br>[31:19] back and forth. It's like a It's a way<br>[31:22] of thinking that lowers the energy<br>[31:24] required to think because you get all<br>[31:25] these mental breaks while you're waiting<br>[31:26] for the chatbot to say things and to do<br>[31:28] some thinking on your behalf. I get it,<br>[31:31] but it also still makes me<br>[31:32] uncomfortable. It still makes me<br>[31:34] uncomfortable the sort of interacting<br>[31:36] using something as uniquely human and<br>[31:38] sacred as speech with a machine. There's<br>[31:40] a sort of emotional spiritual fraud<br>[31:41] there where a mind even though part of<br>[31:43] our mind knows this is a matrix being<br>[31:46] multiplied a bunch of times to create<br>[31:48] tokens autogressively. A deeper part of<br>[31:50] our mind thinks it's talking to another<br>[31:52] being and treating as such and it's not.<br>[31:54] And there's just something there that<br>[31:55] makes me uncomfortable, but I can't<br>[31:56] quite articulate what to do about it. Uh<br>[31:58] France writes in to say it's hubris to<br>[32:00] think that because other species do not<br>[32:01] use our speech, they have no speech with<br>[32:04] which to communicate. Well, I'm sure all<br>[32:06] species or many species have different<br>[32:08] ways of communicating. But I think the<br>[32:09] point here of Jewish tradition is that<br>[32:12] speech as we know it, that is the the<br>[32:14] ability to transmit arbitrary mental<br>[32:17] states from one individual to another,<br>[32:19] this deeply human thing is core to the<br>[32:21] human experience and therefore should be<br>[32:23] treated uh with care. Alex says, "You<br>[32:27] nailed it. I couldn't put my finger on<br>[32:28] why AI generated emails and messages<br>[32:30] just feel inhuman like we can now see<br>[32:33] through it and know that it did not come<br>[32:34] from a human. So we just feel jaded when<br>[32:36] we read AI generated communication. I<br>[32:38] will be crediting crediting you when I<br>[32:40] say the sacredness of speech. Yeah. I<br>[32:42] mean I'm there Alex. There's something<br>[32:44] we should think about this. It's an<br>[32:45] ethical question like like here's how I<br>[32:47] end I'm going to read the final<br>[32:48] paragraph of my my essay here. Um, I<br>[32:51] said this is all to say before we<br>[32:54] blindly embrace whatever AI product Sam<br>[32:56] Altman or Dario Amade declares to be<br>[32:59] inevitable, we still have a lot of work<br>[33:00] to do in figuring out what we're willing<br>[33:02] to accept. We have to be asking these<br>[33:05] questions.<br>[33:07] This is my philosophy of<br>[33:08] technoslectionism.<br>[33:09] We don't just have to take whatever<br>[33:11] technology comes our way and just try to<br>[33:13] survive the waves. We have agency here<br>[33:16] and we can ask hard questions. We can<br>[33:18] make hard decisions. We can change our<br>[33:20] usage patterns. We could push back. We<br>[33:22] can change our mind after we adopt a<br>[33:24] technology and cut back on how we use<br>[33:25] it. We have control. And this is the<br>[33:28] case with LLMs as well. All right, let's<br>[33:31] move on from AI. Jesse, what other what<br>[33:33] other messages do we have here?<br>[33:35] >> Kevin has a question about slow<br>[33:37] productivity for managers.<br>[33:39] >> All right, this is well connected to<br>[33:41] today's deep dive. All right, Kevin<br>[33:43] says, "I have gone down the Cal Network<br>[33:45] rabbit hole and am sold on your<br>[33:47] productivity ideas. I recently was<br>[33:50] promoted manager of a small team of two<br>[33:53] other employees in my knowledge work<br>[33:54] job. How can I ensure I'm encouraging<br>[33:56] the slow productivity principles for my<br>[33:58] teams?" All right, interesting side<br>[34:00] note. Um, Cal Network doesn't go down<br>[34:02] rabbit holes. The rabbits come out of<br>[34:03] the rabbit holes when he wants them. Not<br>[34:06] going to go down a hole. They're going<br>[34:07] to come out. All right, here's some<br>[34:09] notes. You're you're you want to take my<br>[34:11] ideas of slow productivity. Feel like I<br>[34:13] should show the book again. Hold on.<br>[34:16] Tada.<br>[34:18] There we go. Um, and you want to make<br>[34:20] sure that you're implementing them in<br>[34:22] your workplace. All right. Couple things<br>[34:24] I want to I'll tell you right off the<br>[34:25] bat. Make workloads transparent. Who is<br>[34:29] working on what? Do not let that exist<br>[34:31] implicitly implied by a bunch of<br>[34:33] messages and static, you know, stack<br>[34:36] Slack channel transcripts. Here is a<br>[34:39] central place where we keep track of who<br>[34:41] is working on what task. The central<br>[34:43] place needs a holding pin for things<br>[34:44] that need to be done eventually, but<br>[34:45] that no one is working on. Do not play<br>[34:47] the game of all potential work has to be<br>[34:50] distributed among people. And now you<br>[34:51] have each individual with these huge<br>[34:54] workloads that are unworkable at any<br>[34:56] moment. And they have to kind of figure<br>[34:57] out how to juggle all these things and<br>[34:59] try to make progress on some but not<br>[35:00] others. Keep the workload transparent<br>[35:02] and have a place for uh things that need<br>[35:05] to be worked on but no individual is<br>[35:07] working on in the moment. Have clear<br>[35:09] work in progress limits for how much any<br>[35:11] one individual should be doing. Two, you<br>[35:13] need docket clearing meetings at least<br>[35:14] twice a week. These are meetings where<br>[35:16] your team gets together and you review a<br>[35:18] shared document where when anything new<br>[35:20] pops up on any team member's plate as<br>[35:23] something that needs to be discussed or<br>[35:24] potentially done, an issue to be handled<br>[35:26] that has to pursue, there's a shared<br>[35:28] document called the docket where you put<br>[35:29] it so it's off your mind. You don't<br>[35:30] email it out. You don't jump on a Slack<br>[35:33] channel. You don't call an impromptu<br>[35:34] meeting right there. You put it in the<br>[35:37] docket. It's a shared Google doc. Two or<br>[35:39] three times a week, your team gets<br>[35:40] together and goes through that Google<br>[35:42] doc thing by thing. And what are we<br>[35:43] going to do for each of these? We don't<br>[35:45] need to do this. This we need to work on<br>[35:47] now. So, let's add this to the workload<br>[35:49] for you in our transparent workload<br>[35:51] document. This is something we need to<br>[35:52] do, but not now. So, we're going to add<br>[35:53] it to our transparent workload<br>[35:55] management system in the list of things<br>[35:57] that need to be done but no individuals<br>[35:58] doing. Oh, this we could do right now as<br>[36:00] a team. Let's just handle it right here.<br>[36:02] And you go through and you clear out<br>[36:03] that docket. Doing this two or three<br>[36:05] times a week, 30 minutes at a pop, saves<br>[36:07] so many context switches of just<br>[36:08] ambiguous back and forth messages as you<br>[36:10] try to sort of toss these things around.<br>[36:13] Three, insist that your team holds daily<br>[36:15] office hours at posted times. As much as<br>[36:17] possible, move any discussion that<br>[36:19] requires more than a single message to<br>[36:20] answer to the office hours. Come by my<br>[36:22] office hours. Come by my office hours.<br>[36:24] If you have an issue that you need<br>[36:25] feedback from multiple people on, do a<br>[36:27] reverse meeting. You go to each of their<br>[36:29] office hours one by one instead of<br>[36:30] making all of them come to you. Office<br>[36:33] hours can make a huge difference. And<br>[36:35] finally, borrowing uh one of the pieces<br>[36:37] of advice that I talked about in the<br>[36:38] deep dive of today's episode, have your<br>[36:40] employees maintain a portfolio of highv<br>[36:42] value accomplishments, right? So that<br>[36:44] you can cut through pseudo productivity<br>[36:46] and really be monitoring who is doing<br>[36:48] what that's valuable. If someone is not<br>[36:50] growing that log, you say what we have<br>[36:52] to change it so that you're being more<br>[36:53] valuable to us. This cuts through pseudo<br>[36:54] productivity.<br>[36:56] We no longer care about<br>[36:59] visible busyness. We care about this<br>[37:01] list growing. And when you have<br>[37:02] transparent workloads, this also becomes<br>[37:04] clear because you're like, I know<br>[37:05] exactly what you're supposed to work on.<br>[37:07] Why is this not done? Right? So, it's<br>[37:09] it's a really all these things work<br>[37:11] together to create a system that is<br>[37:12] based off of actual value producing<br>[37:15] uh accomplishment and not on just<br>[37:17] visible signs of busyiness, which again<br>[37:18] in an AI world is just going to collapse<br>[37:20] into a busyness singularity. Um, we<br>[37:23] could do one more. What else do we have<br>[37:24] here? Jesse<br>[37:25] >> Evan reports on his efforts to improve<br>[37:27] his cognitive fitness. All right. So,<br>[37:30] Evan says, "I started the deep work<br>[37:32] process again and feel so much better in<br>[37:34] my entire life because I have my focus<br>[37:36] back. The main things I am doing are<br>[37:39] landlining and memorizing the Bible. I<br>[37:42] have completed all the book of James. Is<br>[37:44] there anything else I can use as a mind<br>[37:46] workout that requires my attention so<br>[37:48] deeply like memorizing?"<br>[37:50] Um,<br>[37:51] >> a I like the use of the term<br>[37:52] landlinining which one of our listeners<br>[37:54] I this a few weeks ago, right? So, one<br>[37:56] of our listeners suggested this idea.<br>[37:57] Landlining is the idea of keeping your<br>[37:59] smartphone plugged in in your kitchen<br>[38:01] when you're at home. So you treat it<br>[38:03] like an oldfashioned landline. You have<br>[38:05] the ringer on. You go there if someone<br>[38:06] calls. You go there to check text<br>[38:08] messages. You go there to look things<br>[38:09] up. It's not on your person as you do<br>[38:11] everything else in your house. I think<br>[38:12] it's a great idea. It really helps your<br>[38:13] focus. Memorizing as a way to get more<br>[38:16] cognitive fitness is an interesting idea<br>[38:18] because I talk about it in my book deep<br>[38:21] work. I actually talked about a<br>[38:24] particular it's a cool story. It was a<br>[38:25] student in Australia who was struggling<br>[38:28] academically. It's a university student<br>[38:31] struggling academically. He gets<br>[38:33] involved in competitive memorizing. So<br>[38:36] there's competitions you can go to where<br>[38:40] you uh you memorize like you memorize a<br>[38:42] deck of cards. It's stuff like this.<br>[38:43] It's memory competitions.<br>[38:45] The techniques he learned. So he's doing<br>[38:47] this in this memory competition.<br>[38:49] This helps him, right? this helps his<br>[38:52] general ability to focus and sustain<br>[38:55] concentration. And what happens to his<br>[38:56] schoolwork? All his grades go up. And he<br>[38:59] when I, you know, when I talked to him,<br>[39:01] he was on his way to like a prestigious<br>[39:02] Australian graduate program. And so I<br>[39:05] used it as an example of like, hey, you<br>[39:06] can train your brain to be better at<br>[39:07] focusing and get all sorts of general<br>[39:09] benefits. And memorizing is like the<br>[39:11] type of thing you can do uh to in<br>[39:13] general make your brain stronger, to get<br>[39:15] more cognitive fitness. So that's that's<br>[39:16] interesting what you're doing there,<br>[39:17] Evan. Um, other things you can do to<br>[39:20] actively strengthen your concentration<br>[39:21] muscles. The three things I talk about a<br>[39:23] lot on this show is uh read, write,<br>[39:26] self-reflect. Right? Reading has a<br>[39:29] unique value to your brain because it's<br>[39:31] not just practicing using your brain. It<br>[39:33] actually rewires your brain in a way<br>[39:34] that you can uh make more areas of your<br>[39:37] brain work together to produce smarter<br>[39:39] thoughts. So reading literally makes you<br>[39:40] smarter, not just from the content, but<br>[39:42] the way it rewires your brain. Writing<br>[39:44] is where you reverse those circuits and<br>[39:45] actually produce original thoughts using<br>[39:47] them. And you get better at actually<br>[39:48] focusing these circuits to producing new<br>[39:50] things of value in the world. So care<br>[39:51] about writing. Don't automate it with<br>[39:53] AI. Hard is not bad. Strain is not bad.<br>[39:56] It's like lifting a weight. You want the<br>[39:58] burn. You want to feel the burn of a<br>[39:59] blank page. And self-reflection is going<br>[40:01] for a walk and thinking about something<br>[40:02] in your head without a phone. Can I<br>[40:04] maintain my mind's eye on an internal<br>[40:06] subject like myself, some problem I'm<br>[40:08] having, something I'm trying to figure<br>[40:09] out, and make progress on it with just<br>[40:12] internal dialogue? Those three things,<br>[40:14] reading, writing, self-reflections, I<br>[40:16] think are the primary activities to<br>[40:18] strengthen your cognitive fitness,<br>[40:19] right? It's like what what would be in<br>[40:22] the athletic context like doing cardio<br>[40:24] and strength training and stretching. I<br>[40:26] think it's roughly that equivalent. All<br>[40:28] right, that's all we have from our inbox<br>[40:30] for this week. Uh, also on Mondays, we<br>[40:32] like to finish with an update about what<br>[40:34] I am up to. Uh, I finished last week my<br>[40:38] fifth book of the month, Jesse. I reread<br>[40:40] In Defense of Food by Michael Pollen<br>[40:43] because again my rough idea for a new<br>[40:45] book, which I'm not sure if I'm doing<br>[40:46] yet or not, but I have this idea for a<br>[40:49] book tenatively titled In Defense of<br>[40:50] Thinking. And I want to go back and read<br>[40:52] Paul's manifesto about eating to see<br>[40:54] what did he do there that might be<br>[40:56] relevant for how I think about<br>[40:57] structuring this book about thinking.<br>[40:59] And so it was interesting to go back. It<br>[41:01] was kind of nostalgic. I remembered when<br>[41:02] this was 2006, this book came out. All<br>[41:04] these ideas were big back then. It's so<br>[41:07] nonsurprising today. like the ideas in<br>[41:09] that book have been so because he was<br>[41:10] successful have been so well uh<br>[41:12] inculcated to our culture that like it<br>[41:14] didn't I I remember the freshest that<br>[41:16] book has which it you know doesn't have<br>[41:18] anymore because like he was successful<br>[41:20] in changing the way we thought about<br>[41:21] thinking so but it was good to go back<br>[41:22] and reread that<br>[41:23] >> is it like no processed food and<br>[41:25] >> well he his three pieces of advice is uh<br>[41:28] eat food mostly plants not too much<br>[41:31] >> but it's a three-part book part one kind<br>[41:33] of lays out the problem of nutritionism<br>[41:36] which is like focusing on individual<br>[41:38] macro and micronutrients when you're<br>[41:39] thinking about health as opposed to like<br>[41:41] thinking about food as you know a whole<br>[41:44] and then he talks about<br>[41:47] getting beyond nutritionism and then the<br>[41:49] third part is like he goes into those<br>[41:51] specific pieces of advice and actually<br>[41:53] like gives a lot of advice so you know<br>[41:54] it's a it's a very good book if you<br>[41:55] haven't uh read it before a lot more<br>[41:57] science reportery than I remembered<br>[41:59] >> it's deep it's a lot of like science<br>[42:01] reporting on like this study came out<br>[42:03] and this legislation happened like very<br>[42:05] much it's very more reperatorial than<br>[42:08] the book that inspired it was his<br>[42:10] previous book, The Omnivore's Dilemma,<br>[42:12] which is based around four setpiece<br>[42:14] stories and is also I reread that not<br>[42:16] long ago as well. And that's also a good<br>[42:17] book. Um, in terms of what I'm up to,<br>[42:19] again, I as I mentioned, I'm in the line<br>[42:21] edits of my my the book that's coming<br>[42:22] out next, coming out next spring is<br>[42:24] called The Deep Life, a one-off book<br>[42:25] about cultivating a deep life. Takes all<br>[42:27] the ideas from the show, puts into a<br>[42:29] system, step by step. Boom. Now you have<br>[42:32] it. This is the source guide for making<br>[42:34] your life so interesting that your phone<br>[42:35] will seem less exciting.<br>[42:37] I mean the final line edits. So that's<br>[42:39] like we've you go back and forth a lot<br>[42:41] with writing. You you you kind of as you<br>[42:43] write you go back and forth with your<br>[42:44] editor until you get something that kind<br>[42:46] of works. And then there's like sort of<br>[42:47] higher level notes of like work on that<br>[42:50] here. Like chapter by chapter we need<br>[42:52] something here. This doesn't make sense.<br>[42:54] Maybe cut this. And then you get to sort<br>[42:55] of the line edit piece of the first<br>[42:57] round of editing where your editor will<br>[42:59] actually go through and you know make<br>[43:01] particular let's cut this and this. This<br>[43:03] isn't clear to me. You know those type<br>[43:04] of things. And that's where you do your<br>[43:05] final like out loud read of sections two<br>[43:07] to really try to get the language<br>[43:09] working. You hope that's what leads to<br>[43:11] what's then called the manuscript<br>[43:12] acceptance. Like okay, now we have a<br>[43:14] manuscript. It works. There's still a<br>[43:16] lot of editing that happens after this<br>[43:17] because you still go on the copy editing<br>[43:19] where you you have like professional<br>[43:20] copy editors getting into like the<br>[43:22] precise grammar and languages and word<br>[43:24] repetitions and factchecking and uh we<br>[43:26] have a professional footnote editor to<br>[43:28] come in and get all the innotes in the<br>[43:29] right format. So there's a lot more<br>[43:30] editing to come but it becomes much more<br>[43:32] lower level and production focused. So<br>[43:34] anyways,<br>[43:35] I'm hoping to be done with that by the<br>[43:36] end of the week this comes out. When<br>[43:39] this airs, I'll actually be on my way to<br>[43:40] Asheville where I'm going to hang out<br>[43:43] with friend of the show Brad Stolberg<br>[43:45] and I'm going to edit in the morning.<br>[43:47] I'm staying in some mountain lodge up<br>[43:48] there in Asheville. I'm going to edit in<br>[43:50] the morning. In the afternoon, we're<br>[43:51] going to uh we share a trainer, so we're<br>[43:53] going to train and then think big<br>[43:54] thoughts about the world of writing. So<br>[43:55] that's going to be a cool trip. So, as<br>[43:57] you hear this, I'm on my way to finish<br>[43:58] my edits among the the crisp mountain<br>[44:01] air of Asheville, North Carolina.<br>[44:03] >> Is editing easier than writing?<br>[44:06] >> Um, yeah. I think writing's hard. Uh,<br>[44:10] like today I was struggling with<br>[44:13] because it's the type of thing I<br>[44:14] struggle with, you know, chapter one,<br>[44:17] right? Chapter one of the book. uh here<br>[44:20] is the you what is our approach here's<br>[44:23] what the deep life is I'm going to kind<br>[44:24] of get to in the intro but I'm like<br>[44:25] let's give the formal definition of the<br>[44:27] deep life what is the approach we're<br>[44:29] going to pursue in this book and I set<br>[44:30] up two contrasting approaches<br>[44:33] there's what I say is like the most<br>[44:34] common model that people think when they<br>[44:36] think about the deep life is something I<br>[44:38] call the phase shift model which is like<br>[44:39] a singular event so either a radical<br>[44:42] change or really impressive<br>[44:44] accomplishment will deliver me a deep<br>[44:47] life so I need to like move to an island<br>[44:50] or you know win this major award and<br>[44:53] then and then I will have a deep life<br>[44:54] right and I argue that doesn't work<br>[44:56] right no singular achievement is<br>[44:58] actually it doesn't last you're you're<br>[45:01] that's not going to work a lot of<br>[45:03] examples they said the the alternative<br>[45:05] notion is the lifestyle ccentric<br>[45:06] approach that obviously is going to be<br>[45:07] the right approach because I talk about<br>[45:09] all the time on the show where you say<br>[45:10] no no no actually the what generates<br>[45:12] your subjective experience of your life<br>[45:14] is like all the aspects of your like<br>[45:15] what is your daily life like all the<br>[45:18] aspects of your life. And so what you<br>[45:20] really need to do is engineer your<br>[45:22] lifestyle so that it uh every single day<br>[45:26] is making you know producing depth. It's<br>[45:28] it's your daily lifestyle, not any<br>[45:30] singular event that really determines<br>[45:31] what your life is like. So you need to<br>[45:32] think about re-engineering all the<br>[45:34] aspects of your lifestyle, not just<br>[45:36] pursuing a single sort of like major<br>[45:38] change or accomplishment.<br>[45:40] But there's these subtleties because the<br>[45:42] way my brain works is like the<br>[45:44] definition of the deep life is too much<br>[45:46] overlapping the definition of the<br>[45:49] lifestyle ccentric approach to the deep<br>[45:51] life and I need good separation. This is<br>[45:53] the deep life. These are two potential<br>[45:55] ways to pursue it. This is the better<br>[45:57] way. But the definition of the deep life<br>[46:00] I was using and I was using like an old<br>[46:01] definition I you know written about 5<br>[46:03] years ago was a little processoriented<br>[46:06] itself. you know, amplify this, reduce<br>[46:08] that. And so it anyway, so that's like<br>[46:09] the type of thing, this is the type of<br>[46:11] thing I really care about is these<br>[46:13] little details about how the pieces fit<br>[46:14] together. You get that just right, it's<br>[46:17] implicitly felt in the reader's mind of<br>[46:20] like a pleasing sensation of things are<br>[46:22] clicking together and their mind gets it<br>[46:24] and you can make progress. If they don't<br>[46:25] quite fit, they won't be able to<br>[46:27] articulate what's making them<br>[46:28] uncomfortable, but the book will, you<br>[46:31] know, that doesn't quite match with that<br>[46:32] and and just gives you a a sensation.<br>[46:35] It's like the key to my books, part of<br>[46:36] the sensation my books create is all the<br>[46:39] pieces are uh gears that mesh.<br>[46:41] >> Yeah, 100%.<br>[46:42] >> And it's supposed to be you're like all<br>[46:44] of this is and then your brain is like<br>[46:45] this makes sense. It can gro the whole<br>[46:47] thing. And so anyways, that's what I'm<br>[46:50] working on.<br>[46:50] >> I think I noticed that a lot during your<br>[46:52] promotion of your last book cuz people<br>[46:54] would ask you a million different<br>[46:54] questions, but you'd always bring it<br>[46:56] back to like a core set of fundamentals<br>[46:57] and I was like<br>[46:58] >> that's what works, right? That's what<br>[47:00] works is like it has to people's minds<br>[47:03] are uncomfortable. I've been doing this<br>[47:04] for 20 years now. People's minds are<br>[47:06] uncomfortable when the pieces don't fit.<br>[47:08] And I think too many pragmatic<br>[47:09] non-fiction writers come into it like, I<br>[47:11] just have a bunch of good ideas and and<br>[47:13] they're thinking about how they present<br>[47:14] each idea and they want to zigg here and<br>[47:16] zap and yeah, and capitalism this and<br>[47:19] that and d and they want to have like<br>[47:21] these moments of these sort of<br>[47:23] rhetorical moments where you're like<br>[47:24] boom, oh yeah, I'm on board with that or<br>[47:26] oh that's funny or yeah, yeah, yeah, I'm<br>[47:28] fired up or whatever. What they miss is<br>[47:30] if the pieces, the big level pieces<br>[47:33] don't click together beautifully, the<br>[47:35] whole thing is going to be make the<br>[47:36] reader uncomfortable. They're like, "Ah,<br>[47:38] these like ideas and this kind of fit,<br>[47:40] but doesn't this push back on that and<br>[47:41] what are you trying to say here?" Idea<br>[47:43] first. All the pieces have to click and<br>[47:46] then you got to deploy craft to when you<br>[47:48] explain things or explain things well<br>[47:50] and clear and that's that's all fine<br>[47:51] too. You need craft as well, but the<br>[47:53] ideas the ideas have to the ideas have<br>[47:55] to click. Mhm.<br>[47:56] >> And so, yeah, I'm I'm obsessive about<br>[47:58] it, but that's what I do. All right. Uh,<br>[48:02] that's all the time we have for this<br>[48:04] week. Um, I'll be back next Monday with<br>[48:07] another advice episode. We usually on<br>[48:09] Thursdays have AI reality checks. I have<br>[48:11] to, you know, I'm going to be on the<br>[48:12] road, so maybe we'll see. So, don't be<br>[48:14] surprised if there's not one this week,<br>[48:16] but we'll be back with an advice episode<br>[48:18] uh next Monday. Um, hey, sign up for my<br>[48:21] newsletter, kel nupart.com if you want<br>[48:23] my dispatches from this fight for depth<br>[48:26] versus distraction. It, you know, it's<br>[48:27] my thoughts on the fly of things I'm<br>[48:31] thinking about. So, if you really want<br>[48:32] the most up-to-date view of like new<br>[48:34] thoughts I'm having about this fight for<br>[48:36] depth and distractions, kelpart.com for<br>[48:37] that newsletter. Uh, buy slow<br>[48:40] productivity was the star of today's<br>[48:42] show. If you haven't read this book, you<br>[48:43] need to because I talk about all the<br>[48:44] time. It's the source. So, you need to<br>[48:45] buy that book if you haven't. All right,<br>[48:46] that's it. See you next week and as<br>[48:48] always stay deep.
<!-- deep-read:sections end -->
## Highlights
- When you set up a work environment in which visible activity is rewarded then you give everyone a machine that can automate those efforts making them essentially free. Well, what's going to happen is work will become a mad performative dash of button mashing.
- Note: 📚 Pseudo-productivity creates vulnerability to AI acceleration · - Core mechanism explaining how AI amplifies existing workplace dysfunction - Demonstrates why fixing measurement systems is prerequisite to beneficial AI integration · #atom/literature/h1
- Digital technology, computers to networks to mobile computing played poorly with pseudo productivity. And in the 90s into the 2000s, these jobs got increasingly frantic and busy and all-encompassing.
- Note: 📚 Digital technology progression amplified pseudo-productivity systematically · - Historical analysis showing current AI problems have deep roots - Each technological wave (computers, networks, mobile) increased busyness density · #atom/literature/h2
- You actually want to keep somewhere like in the document like a professor would with their CV a growing list of the important initiatives, projects or accomplishments that you are responsible for.
- Note: 📚 Portfolio maintenance replaces activity-based evaluation with value demonstration · - Practical strategy for escaping pseudo-productivity evaluation - Creates alternative narrative to visible busyness for career advancement · #atom/literature/h3
- Measurement systems drive behavior more than technology itself
- Note: [[Goodhart's Law]] — because extends the principle that measured metrics lose value as targets · - [[Goodhart's Law]] — because extends the principle that measured metrics lose value as targets · #atom/zettel/z1
- Research historical precedents for measurement system changes in knowledge work — how have organizations successfully transitioned from activity-based to value-based evaluation? #fleeting #research
- Note: ✏️ Fleeting capture #atom/fleeting/f1
- Investigate whether "cognitive fitness" programs show measurable workplace benefits — potential validation for Newport's underlying assumptions about human capability development #fleeting #validation
- Note: ✏️ Fleeting capture #atom/fleeting/f2