What does it mean that graceful degradation?

Design your systems to fail partially rather than completely.

Example: You run a weekly review every Sunday that covers five domains: health, work, relationships, finances, and personal projects. One Sunday, a family emergency consumes your entire afternoon. A brittle system collapses — you skip the review entirely, then skip the next one because you already 'fell behind,' and within a month the practice is dead. A gracefully degrading system has fallback modes: if you cannot do the full review, you do a three-minute version that covers only the top two domains. If you cannot do even that, you open the template and write one sentence about the single most important thing that happened this week. The system loses fidelity, but it never loses continuity. And continuity — not perfection — is what compounds.

Try this: Identify one system in your life that has collapsed completely at least once in the past year — a habit, a routine, a process. Write down the full version of that system. Now design two degraded modes: a 'reduced' version that takes half the time and covers the most critical elements, and a 'minimal' version that takes under two minutes and preserves only continuity. Write all three versions on a single card or document. The next time conditions prevent the full version, execute the reduced version instead. You have just built graceful degradation into a system that previously had only two states: working and broken.