“Think it Faster” worksheet

[Raemon]

This is a succinct worksheet version of the “Think It Faster” Exercise. ^[1]

You can use this worksheet either for purposeful practice, after completing some kind of challenging/​confusing intellectual exercise (such as Thinking Physics or Baba is You). Or, if in your real life work you find something took a noticeably long time to figure out, or you were surprised about something you might have been able to notice.

The goal is to identify:

• skills you can train

• principles you can apply

• actions you can take (either physical or mental)

…that move you to correct solutions to problems as quickly as possible.

I recommend setting the standard of “what would have been necessary for me to have figured this out with like 15 minutes of effort?”. (This won’t always usually be possible, but I find this frame helpful for noticing how high the skill ceiling here is. Imagine 10x programmers or senior UI developers who intuitively move towards the right solution – what properties do they have, that you don’t yet?)

Overview

Part 1

“How could you have Thought it Faster?”

• What was the solution to your problem?

• List the steps you actually took to solve the problem.

• List the minimum steps a magical superintelligence could possibly take (or, a “maximally epistemically lucky^[2] person” would take).

• Add steps to the magical-shortlist until it doesn’t feel magical.

• Identify obvious wasted motion in your original steps.

• List each moment where you could have steered more towards some kind of more productive thought, but didn’t. (i.e. clues you almost noticed, ugh fields you considered leaning into but didn’t, etc)

• Identify skills or principles that would have helped you solve it quickly.

Part 2

“What did you learn, which’ll let you Think It Faster The First Time, later?

• List past moments you could have benefited from those skills or principles

• List future moments might benefit from those skills or principles

• In the next week, what is…

  • …something you need to do that feels confusing?

  • …a cognitive task you expect to take a lot of time?

• Pick a specific problem you expect to face, and ask:
  “What life-lessons can I generalize from this puzzle, to help approach that problem in a way that is less confused, less long, so I can Think It Faster the First Time?

Rather than go through each step exhaustively, in sequence, I recommend cycling through them: jot down a few quick ideas for each prompt, circling back to the first one, with each pass giving you a sense of how all the pieces fit together.

Part I: Thinking it Faster

What was the solution?

What were the most important details? What concepts

Steps you actually took

In chronological order (as best you remember) what happened?

Magical superintelligence steps

If you were a waaaay smarter version yourself, or if you imagine some other waaaay (unrealistically) smarter genius, what is the shortest number of steps you can possibly imagine this taking?

(Right now, it’s okay for this to feel like cheating)

Iterate on those lists

Identify steps in the first list you could straightforwardly remove, or simplify. And, identify steps to add to the second list until it no longer feels like unrealistic cheating. (i.e. if you’re not overfitting. The plan doesn’t imply you should spend tons of cognitive overhead all the time on minor, unimportant clues)

Try these prompts to help you:

What skills, if you’d trained for 20 or 100 hours, would have helped you find the answer intuitively?

What principles, if you internalized and they came easily to mind, would have allowed you to make some of those leaps ~instantly, or at least much faster?

What jumps-between-steps feel magical or unrealistic, in “magical short list”?

For the “original steps you took”, what steps could you have skipped? What would have been necessary to skip them?

Overall, what takeaways do you want to remember for later?

What’s the broadest generalization that feels reasonable to draw?

Part II: Thinking It Faster The First Time

That was the easy part. The hard part is noticing when you’re about to think something Too Slowly, and… do something else instead.

Some suggested triggers:

• Things feel confusing or muddled. You’re not sure the right next step to take.

Generalizing from this exercise

First, consolidate your list of skills and principles

List past situations you could have benefited from those skills or principles

List future situations where you suspect might benefit from those skills or principles.

In the next week, what’s 1-3 tasks you’re doing that might benefit from those skills or principles?

Anticipating Future Life Lessons

The flipside of “how can this exercise generalize to real life?” is “what real life situations are likely to benefit from some kind of exercise?”.

So an alternate set of prompts are:

In the next couple days, what’s something you’re planning to do that you expect to take a long time?

...what’s something you’re confused about, or where you’re not sure how to do it?

...what’s something you expect to solve via tinkering/​iteration without much of a plan, that you expect to take awhile?

These might be situations that don’t naturally lend themselves to the most obvious life lessons from the exercise you just did. But, they might give you clues about additional life-lessons to be on the lookout for. Or, might give you clues about which sorts of toy exercises are useful to apply this practice to.

Getting Detailed, and TAPs

After you’ve soaked in some basic ideas for takeways, and some practical places to apply them, you want to get a lot more detailed. Form explicit intentions about when to remind yourself of some advice, and see if it’s helpful.

For one of the past moments, think in detail about how principles/​skills would apply.

(Imagine doing this whole doc again, for that past moment, and how you wish you’d thought-it-faster then. Don’t do the whole-ass version of the doc, but briefly think about the key moments)

For the future moments, how would the skills or principles apply? What would you hope you do, in the moment, to avoid taking longer or making mistakes? (When you imagine failing to remember in the moment, why was that? What steps could you take to avoid forgetting?)

Write down 3 tactical plans for remembering and applying lessons from this exercise during the next week. (They can be bad plans, and they can be short/​rough. Ideally, they should include some actions you take right now, and some actions you’ll take later)

Pick any of the plans that seem worthwhile. Make an explicit prediction about whether it’ll work. (If it doesn’t feel that likely to work, ask “how can I improve this plan?” until you’d be surprised if it failed.)

Take whatever actions you can take right now.

Part III: The Five Minute Version

Doing all of this thoroughly takes a long time. I recommend doing it thoroughly the first couple times, to build a complete model of how everything fits together.

But, ultimately, to practice a skill, you need to get a lot of reps in. You can’t get a lot of reps in if you have to dedicate an hour each time.

So, what’s the five minute version of this? When you look at everything you just thought about, what were the single most important thoughts you had? What prompts would have helped direct you to those important thoughts?

I recommend thinking about this quickly rather than slowly/​deliberately, to help practice the art of “just actually think the most important thoughts, don’t overthink it”, which is it’s own skill.

The next time you naturally stumble into a situation you could have Thought Faster, apply the 5 minute version of this exercise.

You can probably find at least 1-3 moments per week that would benefit from Thinking It Faster.

1. ^

   I’m not actually sure what makes for a good LessWrong post version of an exercise, and curious whether people would have preferred to read this first or the longer version first.

2. ^

   i.e. at each step in the thought-chain, their brain happened to stumble upon a branch that was along the shortest route towards the correct answer.

[Towards_Keeperhood]

I created an obsidian Templater template for the 5-minute version of this skill. It inserts the following list:

• how could I have thought that faster?

  • recall—what are key takeaways/​insights?

  • trace—what substeps did I do?

  • review—how could one have done it (much) faster?

    • what parts were good?

    • where did i have wasted motions? what mistakes did i make?

  • generalize lesson—how act in future?

    • what are example cases where this might be relevant?

Here’s the full template so it inserts this at the right level of indentation. (You can set a shortcut for inserting this template. I use “Alt+h”.)

<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length) + “—how could I have thought that faster?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 1) + “—recall—what are key takeaways/​insights?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “- ” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 1) + “—trace—what substeps did I do?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “- ” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 1) + “—review—how could one have done it (much) faster?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “- ” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “—what parts were good?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “—where did i have wasted motions? what mistakes did i make?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 1) + “—generalize lesson—how act in future?” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “- ” %>
<% “\t”.repeat(tp.file.content.split(“\n”)[app.workspace.activeLeaf?.view?.editor.getCursor().line].match(/​^\t*/​)[0].length + 2) + “—what are example cases where this might be relevant?” %>

[keltan]

Haha! I did the exact same thing. I have a Claude project that makes templates for me draft one up. It’s a much longer version of yours. I think I’ll probably steal the one you made instead. But, I’ll post this here in case anyone wants a longer version.

---

type: think-faster created: <% tp.date.now(“YYYY-MM-DD HH:mm”) %> tags: [think-faster, reflection] aliases: [“TF-<% tp.date.now(“YYYYMMDD-HHmm”) %>”] situation: “” duration: 5 # minutes spent on reflection difficulty: 3 # 1-5 scale

Think it Faster—Quick Reflection

[!info] Situation What happened? Brief description of the situation or problem that took longer than ideal to solve.

Part 1: Analysis

[!note] Actual Steps Taken

[!tip] Optimal Path What would be the minimum necessary steps to solve this?

Key Insights

1. Wasted Motion: What steps could have been skipped?

2. Missed Opportunities: What clues or approaches did I overlook?

3. Required Skills: What capabilities would have helped?

Part 2: Future Application

[!question] Pattern Recognition Where else might this lesson apply?

• Past:

• Future:

• Next Week:

Action Plan

1. Immediate Action: What can I do right now?

2. Trigger Setup: When should I remember this lesson?

   • When I feel [emotion/​situation]

   • During [activity/​context]

   • Before starting [task type]

3. Success Prediction: How confident am I this will help? (/10)

   • Confidence:

   • Why:

Quick Wins

[!important] Key Takeaway The single most important insight from this reflection:

---

Review Prompts

• [ ] Did I identify the true bottleneck?

• [ ] Is my action plan specific enough?

• [ ] Have I set clear triggers for future application?

• [ ] Could this insight generalize to other areas?

[!note] Related Notes Previous similar situations: [[]] Related principles: [[]] Skills to develop: [[]]

[Raemon]

Curious how this takes you typically?

[keltan]

Not sure yet. I haven’t had the opportunity to try it out. I expect it’ll be cut down as I use it, for friction avoiding purposes. I’ll update in a week if I’ve found anything interesting.

[CstineSublime]

Or, if in your real life work you find something took a noticeably long time to figure out, or you were surprised about something you might have been able to notice.

Can you detail what kinds of problems “in your real life” you find might be better served or less appropriate to this exercise? Just off the top of my head, would forgetting who was the star of a movie you’d expect to remember and having the name on the tip of your tongue for an hour not be suitable? But what general code debugging, say of a fragment shader where you finally realize by flipping the x,y coordinates it starts to “look right”—is that more appropriate?

[Raemon]

I feel less optimistic about the “forgetting something on the tip of your tongue”, and pretty optimistic about the code debugging.

[Towards_Keeperhood]

As of a couple of days ago, I have a file where I save lessons from such review exercises for reviewing them periodically.

Some are in weekly review category and some in monthly review. Every day when I do my daily recall I now also check through the lessons in the corresponding weekday and monthday tag.

Here’s how my file currently looks like:
(I use some short codes for typing faster like “W=what”, “h=how”, “t=to”, “w=with” and maybe some more.)

- Mon
- [[lesson—clarify Gs on concrete examples]]
- [[lesson—delegate whenever you can (including if possible large scale responsibilities where you need to find someone competent and get funding)]]
- [[lesson—notice when i search for facts (e.g. w GPT) (as opposed to searching for understanding) and then perhaps delegate if possible]]
- Tue
- [[lesson—do not waste time on designing details that i might want to change later]]
- [[periodic reminder—stop and review what you’d do if you had pretty unlimited funding → if it could speed you up, then perhaps try to find some]]
- Wed
- [[lesson—try to find edge cases where your current model does not work well]]
- notice when sth worked well (you made good progress) → see h you did that (-> generalize W t do right next time)
- Thu
- it’s probably useless/​counterproductive to apply effort for thinking. rather try to calmly focus your attention.
- perhaps train to energize the thing you want to think about like a swing through resonance. (?)
- Fri
- [[lesson—first ask W you want t use a proposal for rather than directly h you want proposal t look like]]
- Sat
- [[lesson—start w simple plan and try and rv and replan, rather than overoptimize t get great plan directly]]
- Sun
- group
- plan for particular (S)G h t achieve it rather than find good general methodology for a large class of Gs
- [[lesson—when possible t get concrete example (or observations) then get them first before forming models or plans on vague ideas of h it might look like]]
- 1
- don’t dive too deep into math if you don’t want to get really good understanding (-> either get shallow or very deep model, not half-deep)
- 2
- [[lesson—take care not to get sidetracked by math]]
- 3
- [[lesson—when writing an important message or making a presentation, imagine what the other person will likely think]]
- 4
- [[lesson—read (problem statements) precisely]]
- 5
- perhaps more often ask myself “Y do i blv W i blv?” (e.g. after rc W i think are good insights/​plans)
- 6
- sometimes imagine W keepers would want you to do
- 7
- group
- beware conceptual limitations you set yourself
- sometimes imagine you were smarter
- 8
- possible tht patts t add
- if PG not clear → CPG
- if G not clear → CG
- if not sure h continue → P
- if say sth abstract → TBW
- if say sth general → E (example)
- 9
- ,rc methodology i want t use (and Y)
- Keltham methodology.
- loop: pr → gather obs → carve into subprs → attack a subpr
- 10
- reminder of insights:
- hyp that any model i have needs t be able t be applied on examples (?)
- disentangle habitual execution from model building (??)
- don’t think too abstractly. see underlying structure to be able t carve reality better. don’t be blinded by words. TBW.
- don’t ask e.g. W concepts are, but just look at observations and carve useful concepts anew.
- form models of concrete cases and generalize later.
- 11
- always do introspection/​rationality-training and review practices. (except maybe in some sprints.)
- 12
- Wr down questions towards the end of a session. Wr down questions after having formed some takeaway. (from Abram)
- 13
- write out insights more in math (from Abram)
- 14
- periodically write out my big picture of my research (from Abram)
- 15
- Hoops. first clarify observations. note confusions. understand the problem.
- 16
- have multiple hypotheses. including for plans as hypotheses of what’s the best course of action.
- 17
- actually fucking backchain. W are your LT Gs.
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- read https://​​www.lesswrong.com/​​posts/​​f2NX4mNbB4esdinRs/​​towards_keeperhood-s-shortform?commentId=D66XSCkv6Sxwwyeep

[Towards_Keeperhood]

I now want to always think of concrete examples where a lesson might become relevant in the next week/​month, instead of just reading them.