Key Takeaways

  • Corporate leaders use AI displacement as public relations cover for over-hiring, blaming algorithms instead of admitting management errors.
  • Delegating to AI creates psychological friction because workers feel asked to train a replacement that is ten times faster rather than delegating to grow.
  • Standing still in a legacy workflow feels safe, but holding onto static knowledge is the quickest path to professional obsolescence.
  • Journalism survived decades of digital transformation by evolving its distribution and tools rather than disappearing, providing a blueprint for modern tech roles.
  • Adopting The Six-Year Reinvention Mindset allows knowledge workers to lead role transitions instead of defensively hoarding skills.

The Six-Year Reinvention Mindset

Corporate narratives around artificial intelligence often present a toxic bargain to employees. As Graham observes: “The narrative right now is literally like okay we hired this new employee. This new employee is the smartest employee that you have ever met. This employee is like 10 times smarter than you and I want you to pour every single thing that you know into this employee and then they're going to take your job in six months. Like who wants to do that?”

At the same time, Graham rejects the claim that mass job cuts stem directly from automation: “I have a lot of beef to pick with all the AI branded layoffs out there because they are not about AI. They are about badly run companies slapping an AI label and getting some share points from that versus saying, 'Whoops, we hired too many people.'”

Instead of panic, Graham points to journalism's multi-decade digital evolution. Newsrooms did not vanish; their tools, publishing rhythms, and business models altered completely. Surviving disruption requires treating your skill set as a dynamic system through three explicit components:

  • Core Premise: Operate under the assumption that your core profession will not disappear, but its tools, workflows, and deliverables will transform completely every six years.
  • Action: Instead of protecting legacy workflows or hoarding specialized technical knowledge, actively participate in designing the next iteration of your role.
  • Mindset Shift: Shift from 'How do I protect what I know?' to 'What could this profession look like next, and how can I lead that transition?'

As Graham puts it, “What would you do if you believed your job was always going to exist? It was just going to look completely different every six years.” Defending existing habits creates false comfort. “Standing still feels safe. It feels like hold on to what you know, because that at least is not scary and unknown. But actually standing still is the least safe thing you can do. What you can learn by tomorrow matters way more than what you know today.”

When This Works (and When It Doesn't)

This framework works best in fast-moving knowledge professions like software engineering, product management, design, and editorial work. In these domains, defending manual tasks or gatekeeping technical arcana guarantees that newer, faster peers will replace you. Leaning into the technology expands your leverage.

It breaks down when an organization faces structural margin collapse rather than workflow evolution. If a business unit is mathematically unsustainable regardless of tooling, reimagining your individual daily workflow will not protect you from a plant shutdown or complete department dissolution. In those cases, the right move is company-level exit, not internal workflow redesign.

What to Do With This

Take your weekly calendar and identify the single technical workflow you guard most fiercely, such as manual sprint backlog grooming, writing initial draft specs, or generating raw copy.

Tomorrow morning, spend two hours setting up an automated AI workflow that executes that exact task in five minutes. Document the prompts and share the template directly with your engineering or product team in Slack. If you show your team how to automate the work you used to protect, you force yourself to take on the higher-order problem of orchestrating the system.