Kidlin's Law states: *"If you can write the problem down clearly and specifically, the matter is half solved."* It captures a deceptively simple but powerful insight — that the act of articulating a problem with precision is itself a major step toward resolving it.
**Why Writing Down Problems Works**:
Most problems feel overwhelming when they live only in your head. In mental space, problems are vague, entangled with emotions, and contaminated by adjacent worries. The moment you force yourself to write a problem down clearly, several things happen simultaneously:
1. **Forced precision**: You can't write clearly about something you don't understand. The attempt to articulate forces you to separate what you actually know from what you're assuming, fearing, or conflating
2. **Decomposition**: A written problem naturally breaks apart. What seemed like one monolithic issue often reveals itself as several distinct sub-problems, some of which may already be solved or irrelevant
3. **Emotional separation**: Externalizing a problem onto paper creates psychological distance. You move from being *inside* the problem to *looking at* the problem
4. **Scope definition**: Writing forces boundaries. You must decide what is and isn't part of the problem, which prevents scope creep in your thinking
5. **Pattern recognition**: Once written, problems often match patterns you've seen before — solutions become visible that were invisible when the problem was a formless worry
**How to Apply Kidlin's Law**:
- **State the problem in one sentence**: If you can't, you don't understand it yet. Keep refining until you can
- **Separate facts from interpretations**: What do you actually know versus what are you inferring or feeling?
- **Define 'solved'**: What would the situation look like if the problem were resolved? This often reveals the path
- **List what you've already tried**: Writing this down prevents circular thinking and reveals new angles
- **Identify the real constraint**: Often the written problem reveals that the obstacle isn't what you thought
**Kidlin's Law in Different Domains**:
**Software engineering**: Bug reports that clearly describe expected vs. actual behavior are famously easier to fix. The discipline of writing a minimal reproduction case often leads the developer to the root cause before anyone else looks at it. Rubber duck debugging works on the same principle — explaining the problem clearly to an inanimate object is often enough to solve it.
**Business**: Clearly written problem statements prevent teams from spending months building solutions to the wrong problem. Amazon's practice of writing six-page memos before meetings forces the clarity that Kidlin's Law describes.
**Personal life**: Journaling about a problem you're ruminating over often produces surprising clarity. The act of writing transforms a swirling anxiety into a concrete challenge with identifiable components.
**Science**: The history of science shows that correctly formulating the question is often the hardest and most important step. Once Darwin clearly articulated the problem of how species diverge, the mechanism of natural selection became much more visible.
**Related Principles**:
Kidlin's Law is part of a family of ideas that share the insight that clarity precedes solutions:
- *"A problem well-stated is a problem half-solved"* — attributed to Charles Kettering
- *"If I had an hour to solve a problem, I'd spend 55 minutes thinking about the problem"* — attributed to Einstein
- *"Writing is thinking"* — the broader principle that writing itself is a cognitive tool, not just a recording device
**Limitations**:
Kidlin's Law works best for problems that are solvable through analysis and clear thinking. Some problems — grief, existential questions, wicked problems with no clear boundaries — may resist clean articulation. But even for these, the attempt to write them down usually reduces suffering by converting vague dread into something more concrete and manageable.