Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Resolve Cycles, published by CFAR!Duncan on July 16, 2022 on LessWrong.
Epistemic status: Anecdotally strong
This technique was largely developed by Kenzi Amodei in the context of after-workshop followups and pair debugging. It has been refined and iterated, and has proven highly useful to our alumni, but all theorizing is post-hoc and untested, and direct research into (e.g.) an underlying theory of mind has yet to be done.
Consider the following scenarios:
You’ve been assigned a task that feels like it’s going to take about ten or fifteen hours of work, and you’ve been given three weeks to get it done (e.g. a document that needs to be written).
You’re facing a problem that you’ve tried solving off and on again for years, a problem that your friends and family never seem to run into (e.g. a struggle with motivation as you try to learn a new skill).
There’s a thing you need to do, but it seems impossibly huge or vague (e.g. to achieve your goals you’d need to found a company, emigrate to India, or cure a disease), and you don’t know where to begin.
You’re pretty sure you know all the steps between you and your goal, but there are about forty thousand of them (e.g. you’re hoping to run an actual marathon).
You’ve got a to-do list that’s long and growing, and you can only ever manage to get to the ones that are urgent (e.g. getting your car’s registration renewed, two months late).
Problems like the ones above can range from trivial to crucial, from simple to complex, and from one-time bugs to persistent, serious drains on your time, attention, and resources. There are a lot of elements in the mix—motivation, creativity, perseverance, prioritization—and a lot of justifiable reasons for thinking that solutions will be hard to come by.
Sometimes, though—despite every bit of common sense and experience telling us otherwise—those solutions aren’t hard to come by. Or rather, they might be hard, but they’re not elusive or mysterious or complicated.
The resolve cycle technique is one we offer up with a sort of shamefaced shrug, because it doesn’t sound like “real” applied rationality. It doesn’t have the rock-solid research underpinnings of TAPs or inner sim, or a carefully considered model like the ones behind turbocharging and double crux. It sometimes comes across like the worst possible advice—the sort of thing people say when they don’t actually want to help you with your problem:
“Have you tried setting a five-minute timer and just, y’know—solving it?”
But it works. Not always, not perfectly, but shockingly often and surprisingly well. And so we recommend that you suspend your disbelief (it’s justified) and put your objections on hold (we were just as incredulous as you are) and give it an actual, honest shot. In the worst case, if it does you absolutely no good, you’ve only wasted five minutes, and you’ve successfully exercised your Try Things muscles.
Post-hoc and half-baked
We’ll provide more detail in later sections, but the core of the technique— set a timer and solve your problem in five minutes or less—is extremely straightforward. The question is, why does this work? What’s going on?
We don’t have a complete answer yet, but we do have some quasi-models that pseudo- explain parts of what might be happening for some subset of hypothetical people (maybe).
If we look at the line above, it’s clear that, within the context of a given problem or project, we’d like to be operating as close to the upper end as possible. This is assuming that the project is genuinely important, that we aren’t in need of a break or a vacation, that we aren’t neglecting something else, etc.
There are situations which naturally bring out the Actually Try, such as deadline mode or emergencies, but ideally, we’d like to be able to access it at will, rather than by having to trick ourselves int...