A Short History of My Last Six Years

In one sentence

The book is a meta-narrative on the grueling, six-year creative process of tackling a massive societal problem, revealing how the "delusion of a madman" can both fuel and ruin a project.

Why read this (and who it's for)

This is for the "perfectionist" creator, the researcher who gets lost in the weeds of a "too big" topic, and the writer who finds themselves perpetually "almost finished." It solves the problem of scope creep and analysis paralysis. After reading this, you will be able to identify the psychological traps that keep your projects in a state of perpetual "crunch time" and learn how to force a project into completion.

The big idea

Urban argues that when you tackle a massive, complex topic (like "the problems of society"), the sheer scale of the subject can become a trap. Because the topic is so vast, you feel a moral and intellectual obligation to include everything—every news story, every nuance, and every sub-topic. This creates a feedback loop where the project grows faster than your ability to write it.

The core of the problem is a psychological trap: The "Almost Done" Delusion. This is the belief that you are just one more research session, one more chapter, or one more revision away from completion. This belief is dangerous because it allows you to justify putting your entire life on hold for a "crunch time" that never actually ends. To finish, you must eventually stop trying to "capture it all" and instead find a way to "cut the albatross" of your own perfectionism.

Key ideas

The "Almost Done" Delusion

• What it is — The psychological state where a creator believes they are just a few weeks away from finishing a massive project, leading them to sacrifice their work-life balance for a "crunch" that lasts years.
• Why it matters — It creates a "perfect way to ruin your life" because it justifies putting everything else on hold for a deadline that keeps moving.
• In the book — Urban admits he believed he was "finally getting close" every single time someone asked him for an update for six years straight.

The Sunk Cost Fallacy of Knowledge

• What it is — The inability to abandon a project because of the sheer amount of time and mental energy already invested in it.
• Why it matters — It prevents you from making the necessary "hard cuts" to a project's scope, forcing you to keep adding "sub-sub-outlines" rather than simplifying the core message.
• In the book — Urban describes how he had a "Future Posts" folder full of easy topics (like VR) but couldn't bring himself to switch because he had already put so much time into the "Society" folder.

The Albatross of "Full Coverage"

• What it is — The perfectionist urge to tell the "full, full story" by incorporating every single relevant piece of information found in the news or social media.
• Why it matters — It turns a manageable project into an unmanageable "monster" because the more you learn, the more you feel you must include, making the finish line recede further away.
• In the book — Urban notes that as he grew more aware of the world's problems, his "Society" folder grew to include 11,081 documents, making the project nearly impossible to synthesize.

The Necessity of External Deadlines

• What it is — The realization that internal willpower is often insufficient to finish a massive project; you need a "forcing function" that carries real-world consequences.
• Why it matters — It breaks the cycle of "internal" deadlines that you can easily ignore or move.
• In the book — The birth of Urban's child served as the ultimate "forcing function," creating a hard deadline where the book had to be done by a specific date.

Frameworks & tools

The "Scale-Up" Pipeline

Urban describes a three-stage evolution for handling massive topics to avoid being crushed by their scale:

1. The Mini-Post: Write what is "incessantly on your mind" without a plan.
2. The Series: Break the massive topic into 12 (or more) parts to create "adrenaline" and manageable milestones.
3. The Book: When the topic is too large for a web page, move to a format (like a book) that allows for a "complete" story.

The "Hard Cut" Rule (Implicit)

To escape the "Albatross" of a project, you must:

1. Identify the Core: What is the one thing you must say?
2. Identify the Albatross: What are the "nice-to-know" but non-essential details?
3. Cut: Explicitly decide to leave the "nice-to-know" out, even if it feels like a "partial story."

Memorable examples & stories

• The "Society" Folder: Urban describes a folder that grew from a single document to a chaotic mess of 11,081 documents. Lesson: Research is a bottomless pit; you must eventually stop collecting and start synthesizing.
• The "Crunch Time" Lie: For six years, Urban told himself he was in "crunch time" to justify a lack of work-life balance. Lesson: Beware of any "deadline" that doesn't have a fixed, external consequence.
• The Pregnancy Stick: The moment Urban realized he had to finish the book because a baby was coming. Lesson: Sometimes, you need a "life-altering" deadline to break a cycle of perfectionist procrastination.

Key quotes

• "The delusion of a madman... is a perfect way to ruin your life."
• "I was determined to tell the full, full story." (Paraphrased: The danger of wanting to be exhaustive rather than effective.)
• "This baby could not enter a world where this project was still going on." (Paraphrased: The necessity of a hard, external stopping point.)

How to apply it

This week

• Audit your "Society" Folder: Identify one project you have been "working on" for more than 3 months. List every sub-topic you feel "obligated" to include.
• The "Mini-Post" Test: Take one small, specific thought from that project and write 300 words on it today. Do not allow yourself to research anything else.

Ongoing

• The "Hard Cut" Rule: Every time you find a new "relevant" piece of information for a project, ask: "Does this change the core message?" If not, it goes in a "Later" folder, not the current draft.
• Externalize Deadlines: For any project over 3 months in length, find a way to make the deadline "real" (e.g., a public commitment, a paid contract, or a hard-coded calendar date).

Common pitfalls

• Confusing Research with Progress: You can spend years "gathering" (the Society folder) without ever "producing."
• The Perfectionism Trap: Thinking that "more" equals "better." In many cases, a "partial story" that is finished is more valuable than a "full story" that never gets published.
• The "Almost Done" Trap: If you tell yourself you're "almost done" for the third time, you are lying to yourself. You must acknowledge that the project is actually growing because of your own refusal to cut content.

Connects to

• Deep Work (Cal Newport): For the discipline required to focus on these "monstrous" topics.
• The War of Art (Steven Pressfield): For understanding the "resistance" that makes us choose research over actual writing.

If you remember only three things

• The "Almost Done" Delusion is a trap that allows you to sacrifice your life for a project that never ends.
• Perfectionism often manifests as "The Albatross"—the need to include every single detail until the project becomes unmanageable.
• To finish a massive project, you must eventually stop trying to "capture it all" and start making "hard cuts."

Internalize it

• Reflection questions
  • What is the "Cloud" or "Albatross" currently hanging over my most important project?
  • In what ways have I used the "Almost Done" excuse to avoid making a hard decision about my project's scope?
  • What would happen if I committed to a "partial story" today? What would I be able to finish?
• Flashcards
  • Q: What is the "Almost Done" Delusion?
  • A: The belief that a project is just a few weeks from completion, which allows a creator to justify a "crunch" that lasts for years.
  • Q: What is the "Albatross" of a project?
  • A: The perfectionist urge to include every single relevant detail, which causes the project's scope to grow faster than the author can write it.
  • Q: Why did the "Society" folder become so difficult to manage?
  • A: Because the author felt a moral obligation to include every piece of news and every nuance, leading to 11,081 documents.
  • Q: What was the "forcing function" that finally ended the project?
  • A: The birth of a child, which created a non-negotiable, external deadline.

Fidelity note

Confidence is high. This summary is based strictly on the provided text, which is a personal reflection on the creation of a book. The summary captures the author's internal struggle with scope, perfectionism, and the psychological traps of long-form creation. It does not include any information about the content of the resulting book ("What's Our Problem?"), as that was not provided in the source text.