Question
What does it mean that revolution versus evolution in schemas?
Quick Answer
Sometimes a schema needs a complete replacement not just modification.
Sometimes a schema needs a complete replacement not just modification.
Example: You've been iterating on a productivity system for three years — adding tags, restructuring folders, tweaking templates. Each change makes it slightly better and slightly more complex. One day you realize the system assumes a project-based work model, but your actual work is relational and event-driven. No amount of folder restructuring will fix a category error. You need to scrap the taxonomy and rebuild from a different premise entirely.
Try this: Identify one schema you've been patching for a long time — a belief about your career, a framework for decision-making, a mental model of how your industry works. Write down the three most recent modifications you've made to it. Then ask: am I adjusting details within the same framework, or am I trying to force new evidence into a structure that no longer fits? If the answer is the latter, write down what the replacement schema might look like if you started from scratch.
Learn more in these lessons