Keep this life skill for later
Sign in to save
← All life skills

Learning & thinking · a life skill

Advanced Curiosity Lists

a ledger, not a wish list

A long curiosity list turns into a guilt pile, and an open chase turns into a lost evening. The fix is a ledger. Make a call on each question, give each chase a budget, and score it before and after. Once a month, the gap between what you expected and what you got says where your curiosity pays.

  • Challenging to start
  • Life-Changing impact
  • Learn it in 30 days
  • Scored before and after
one week of the ledger, and the month it adds to
A curiosity ledger: a call and a budget for each question, curiosity before, satisfaction after, the gap, the questions parked mid-chase, and a month's average gap by tag The week's ledger: bee navigation (nature), chase, 30 min, curiosity 5, satisfaction 6, gap +1; Roman cement (history), chase, 30 min, curiosity 4, satisfaction 6, gap +2; flat sourdough (cooking), chase, evening, curiosity 6, satisfaction 4, gap −2; Fourier transform (maths), chase, evening, curiosity 5, satisfaction 5, gap 0; who wrote Desiderata (history), know; why cats knead (nature), skip; heat pumps (home), chase, 5 min, curiosity 3, satisfaction 5, gap +2. Parked during chases rather than followed: Why did Roman concrete outlast ours? (from Roman cement); Do bees sleep? (from bee navigation). Over the month, 14 chases averaged by tag: history +1.8, home +1.5, nature +0.7, maths −0.5, cooking −1.3. History keeps beating its rating, so it gets more time; cooking keeps falling short, so its questions need sharpening. The ledger, this week question tag call budget before after gap bee navigation nature chase 30 min 5 6 +1 Roman cement history chase 30 min 4 6 +2 flat sourdough cooking chase evening 6 4 −2 Fourier transform maths chase evening 5 5 0 who wrote Desiderata history know — why cats knead nature skip — heat pumps home chase 5 min 3 5 +2 Parked, not chased Why did Roman concrete outlast ours? from the Roman cement chase Do bees sleep? from the bee navigation chase turned up mid-chase, saved for later The month: average gap by tag 14 chases 0 fell short beat it history +1.8 home +1.5 nature +0.7 maths −0.5 cooking −1.3 History beats its rating: give it the evenings. Cooking falls short: ask sharper questions there. 1 2 3 4 5

One month's ledger. A gap above zero means the answer was better than the curiosity promised.

The system

Try it now.

For readers whose list already runs long. The ledger is one table: a row per question, filled in as you go.

  1. Make a call, and set a budget

    Each question is know, skip or chase. A chase gets five minutes, thirty, or an evening, decided before you start.

    Marked "know"? Once a week, answer one of them out loud before you check it. A wrong "know" is a hidden chase.
  2. Score curiosity before you start

    1 to 7, the moment you open the chase. It's your forecast of how good the answer will be.

  3. Score satisfaction when you stop

    1 to 7 again, when the budget runs out or the answer lands. Write after minus before in the gap column.

  4. Park what turns up, don't follow it

    A new question that appears mid-chase goes on the list with where it came from. The budget ends the chase, not the last link.

  5. Once a month, read the gap by tag

    Topics that keep beating their rating earn longer budgets. Topics that keep falling short need sharper questions or less time. A question skipped three times comes off the list.

When to break the rule: if a question blocks real work, such as a bug, a form or a decision due today, chase it now and past its budget. The ledger is for curiosity, not for the things you have to know.

Keep the ledger

Call it, budget it, score it twice.

Each row is one question. The panel adds up the week's budgets, averages the gap by tag, and lists the housekeeping: questions to drop, one "know" to spot-check, and what you've parked.

Ledger

    This week's budget

    Gap by tag

    Housekeeping

      Nothing you type is saved or sent anywhere. It's gone when you leave the page, so copy the ledger into your own notes.

      Why score twice

      Answers that beat their curiosity were more likely to be remembered.

      Caroline Marvin and Daphna Shohamy at Columbia gave 81 people 69 trivia questions. For each, they chose know, skip or wait, where waiting meant sitting through 10 to 30 seconds for the answer. Afterwards they rated how curious each question had made them and how satisfied they were with its answer, both 1 to 7. Sixty-six came back about a week later and typed the answers they remembered.

      The more curious people were, the more often they waited, and the more they remembered. The study's own measure was the gap: satisfaction minus curiosity, which it called an information prediction error.

      curious 4→satisfied 6=gap +2

      With curiosity taken into account, a bigger positive gap still went with a better chance of remembering. That is the column this ledger keeps.

      The honest limits: these were trivia questions, mostly students, and one week. Curiosity and satisfaction were rated after the task, from memory. The study shows that the gap goes with memory, not that tracking your own gap improves it.

      ×½ ×1 ×2 ×5 Waiting for the answer one point more curious ×4.93 a longer wait ×0.88 a pleasant topic ×1.31 Remembered a week later one point more curious ×1.79 a pleasant topic ×1.36 With the gap added one point more curious ×1.26 one point more gap ×1.19
      How each thing changed the odds, on a log scale. "A pleasant topic" compares questions a separate group rated pleasant with neutral ones. Right of the line, more likely; left, less. Marvin & Shohamy (2016), "Curiosity and reward: valence predicts choice and information prediction errors enhance learning", Journal of Experimental Psychology: General 145(3).

      The idea

      Why it works.

      Curiosity is a forecast: it's how good you expect an answer to be. Forecasts get better when you check them against what happened. The before-and-after scores do that, question by question, and the monthly average shows which topics you misjudge and in which direction.

      The calls and budgets handle the other failure. An open list grows faster than anyone can clear it, and an open chase never ends on its own. A call closes the question you won't chase, and a budget closes the one you will.

      When it goes wrong

      Habits that help.

      • Score before, not after. Curiosity rated once you have the answer drifts toward how the answer felt, and the gap shrinks to nothing.
      • Read a tag, not a row. One disappointing chase means little. A tag that falls short month after month is telling you something.
      • Keep dread off the list. Questions that only feed worry, like symptoms at midnight or the news, aren't curiosity. Give them their own time or let them go.
      • Let parked questions wait a day. Most of them look smaller the next morning. The ones that don't are your next chases.

      Practise this in HourLife.

      In Someday: Ideas that show their age. A parking lot for ideas you're not ready to act on. Review it monthly and turn the ones that last into goals, tasks, or desires.