← LibraryBlog · Philosophy

Questions

Patrick Collison
✓ Source-grounded

The world is defined by systemic patterns—cost explosions, institutional decay, and technological ossification—that require deep inquiry to solve.

Read the original

In one sentence

We must identify the underlying dynamics of why certain systems (infrastructure, education, software) become inefficient or stale while others remain high-performing.

Why read this (and who it's for)

This material is for the thinker who is frustrated by the "status quo"—the person who notices that things are getting more expensive, slower, and less malleable without a clear explanation. It solves the problem of surface-level observation by providing a framework for systemic inquiry. After engaging with these questions, you will be able to look at any failing system (a city, a software tool, an educational model) and ask: What is the underlying dynamic here? Is this a matter of cost, decay, or a loss of malleability?

The big idea

Collison argues that our current reality is defined by a series of systemic anomalies. We see dramatic declines in costs in some areas while others (healthcare, education, infrastructure) exhibit steep increases that significantly outpace inflation. He suggests these aren't isolated incidents but symptoms of deeper issues: how we manage institutional replacement, how we design physical and digital environments, and how we measure the progress of science.

The logic is that if we can identify the "why" behind these patterns—such as why a BART extension takes seven years while the Empire State Building took 410 days—we can begin to engineer better outcomes. The goal is to move from observing symptoms to understanding the dynamics of progress and decay.

Key ideas

The Cost Explosion

Institutional Decay vs. Replacement

The Two Sigma Problem

Bicycle vs. Monorail Computing

Execution Capital

Frameworks & tools

The Malleability Audit

Use this to evaluate any software or tool you use daily:

  1. Identify the "Glass": Is the application logic hidden behind a UI that prevents you from making small tweaks?
  2. Check for Scripting: Can you write a quick script (like VBA) to automate a simple task?
  3. Assess the "Bicycle" Factor: If the tool doesn't do exactly what you want, is it easy to augment? Or are you forced to use a separate package for every new application?

The Institutional Replacement Audit

Use this to diagnose why a system (a department, a city project, a company) feels stale:

  1. Identify Survival Instincts: Is the system working hard to survive even though it is less effective?
  2. Check for Natural Extinction: Does this system have a natural way to die (like bankruptcy)?
  3. Determine Replacement Rate: If not, what mechanism exists to destroy the old structure and create a new one?

Memorable examples & stories

Key quotes

How to apply it

This week

Ongoing

Common pitfalls

Connects to

If you remember only three things

Internalize it

Fidelity note

I have a high confidence in this summary as it is based strictly on the provided list of questions and responses. I am certain about the specific examples (Empire State Building, Japan/Switzerland) and the "bicycle vs monorail" framework. The reader should verify the specific numbers for cost growth (e.g., 9X for healthcare) against the original source to ensure accuracy in specific contexts.

Keep going — related reads

More from Patrick Collison