When stuck, write about the stuckness — resolution often comes by paragraph three
When stuck on a problem, write about being stuck by describing the problem, what you've tried, what you expected versus what happened, as the narrative structure itself often produces resolution by the third paragraph.
Why This Is a Rule
This is the rubber duck debugging principle, generalized beyond code. When you're stuck, the problem feels like a fog — you can't see the edges, you don't know what's wrong, and continued thinking produces the same loop of confusion. Writing about the stuckness forces structure onto the fog.
Paragraph one describes the problem: what are you trying to do? This sounds trivial, but forcing yourself to state the problem precisely often reveals that you're solving the wrong problem, or that the problem is actually two problems conflated into one.
Paragraph two describes what you've tried and what happened: not what you think happened, but what actually happened. The gap between expectation and reality, forced into explicit language, frequently exposes the false assumption you've been operating on.
Paragraph three is where resolution typically lives — not because three paragraphs is magic, but because paragraphs one and two forced enough structure onto the problem to make the solution visible. Pennebaker's research confirms that imposing narrative structure on confusion is itself a path to resolution.
When This Fires
- You've been stuck on a problem for more than 20 minutes with no progress
- You've tried the same approaches multiple times without success
- You're about to ask someone for help (write about the stuckness first — you'll often solve it)
- Any situation where confusion persists despite active effort
Common Failure Mode
Writing about the problem at a high level without being specific. "I'm stuck on the authentication flow" doesn't force enough structure. "I expected the token refresh to return a new access token, but instead it returns a 401 with the message 'session expired,' even though the refresh token hasn't expired according to the timestamp" — that level of specificity is where the writing produces insight.
The Protocol
When stuck: (1) Write paragraph one: "The problem is [precise description]." (2) Write paragraph two: "I've tried [specific approaches]. I expected [X] but got [Y]." (3) Write paragraph three: "The gap between my expectation and reality might be because..." (4) If you solve it during writing — most people do by paragraph three — you've just experienced writing-as-thinking. If you don't, you now have a precisely structured problem description that makes asking for help dramatically more effective.