Logs & journals

How to build a reading list you'll actually finish

Most reading lists are aspirations arranged in a column. A list you finish starts from a question, stays short, and plans for the book that stalls.

A collection tile showing six books under the title Understanding how cities work
A list built around a question is a project; a list built around a canon is homework.

The short answer

A reading list you finish has five properties. It starts from a question you actually have ("how do cities work?", "what is the best of this author?") rather than from a canon. It is short — twelve books is a year at one a month. It alternates demanding and easy so a tired week has an option. It mixes lengths, because six 600-page books is not a list, it is a sentence. And it decides in advance what happens when a book stalls: swap, not stop. Review it every quarter and expect to change a third.

  • Question first. The list is the reading you would do to answer it.
  • Twelve books, or fewer. Longer lists are TBRs in disguise.
  • Hard, easy, hard, easy. Order for the bad week.
  • A stalled book gets swapped after 50 pages, and the swap is written down.
In this article
  1. Why do most reading lists fail?
  2. Start from a question, not a canon
  3. Build it in an hour
  4. How long should a reading list be?
  5. What do I do when a book on the list stalls?
  6. How do I keep track of a reading list?
  7. Common questions

Why do most reading lists fail?

Three ways. They are too long — a list of fifty is a wish, and progress on a wish is invisible. They are built from other people's lists — "100 books to read before you die" — so every book is an obligation rather than a curiosity. And they have no plan for the stall: the fourth book is slow, the list stops, and the whole thing acquires the smell of unfinished homework.

Start from a question, not a canon

The lists people finish are projects. "Everything by one author, in order." "Enough to understand the Roman Republic." "Twelve novels from countries I have never read." "The five books my grandmother kept mentioning." A question gives each book a job and gives the list a finish line; a canon gives you a column of titles and a vague feeling of inadequacy.

Build it in an hour

1 Write the question at the top One sentence. If you cannot write it, you have a TBR, not a list. 2 Gather twenty candidates Recommendations, bibliographies, a bookshop table, your own Someday shelf. 3 Cut to twelve Drop anything you are including because you feel you should. 4 Alternate hard and easy, mix lengths The second and fourth book should be ones you could read tired. 5 Order the first three The rest stay unordered; you will know more after three books. 6 Write the swap rule Fifty pages and stalling means swap in a candidate you cut, and note why.
An hour, once. The list changes as you read it, and that is the list working.

How long should a reading list be?

Reading list length and what it suits
LengthTime to finish at a book a fortnightWorks for
5 booksAbout 10 weeksA single question; a season; a first list
12 booksAbout 6 monthsMost projects; a year at a book a month
25 booksA yearA serious project or a full author
50+Not a listThis is a TBR; sort it into someday, soon and next

What do I do when a book on the list stalls?

Swap it. Fifty pages is a fair trial; if you are rereading paragraphs and avoiding the book, it goes back to the candidates and one of the books you cut comes in. Write the swap down — "stalled at p.52, too slow for August" — because the note is what stops you buying it again in a year. The list is a tool for reading, not a contract, and a list that cannot change is a list that stops.

How do I keep track of a reading list?

Where your reading already lives. A collection in your tracker with the question as its name, the twelve books in it, and the ones you have finished falling off the shelf as you go. The pleasure of a good list is watching the collection thin out; a spreadsheet gives you that too, at the cost of opening a spreadsheet.

In Pensovo Make a Collection named after the question and add the twelve books — any book, including ones no catalogue lists. Starting a book moves it from Want to read to Reading; finishing moves it to the shelf. The collection shows what is left.

Common questions

How many books should be on a reading list?

Twelve or fewer. Five for a season, twelve for a year at one a month, twenty-five for a serious project. Anything longer is a TBR and needs sorting instead.

Should my reading list be in order?

Order the first three and leave the rest. You will know more after three books than you do now, and a fully ordered list breaks the first time a book stalls.

What if I don't finish a book on the list?

Swap it after fifty pages and write down why. The list is for reading, not for finishing every entry.

How do I choose books for a reading list?

Start from a question you have, gather twenty candidates from bibliographies, recommendations and your own long list, and cut to twelve — dropping anything you are including out of obligation.

Should I mix fiction and non-fiction?

If the question allows it, yes. Alternating a demanding book with an easier one — whatever the genre — is what keeps a list moving through a bad week.

What is the difference between a reading list and a TBR?

A TBR is everything you might read; a reading list is a short, ordered set built to answer a question or finish a project. Keep both, and keep them separate.

Amol B

Builds Pensovo, a free reading tracker for people who read real books. Writes here about keeping a reading habit and remembering what you read.

Keep every book you read in one place

Tracking, streaks, collections, notes and highlights — free on iOS and Android, no trial and no card.

Free account · no card · iOS and Android