Build Your Summer Reading List Without the Algorithm
Every summer, the same thing happens. You open an app, get served a carousel of sponsored titles and trending picks, add four books to your TBR pile, and read none of them. The algorithm didn't know you. It knew what was performing well that week.
Every summer, the same thing happens. You open an app, get served a carousel of sponsored titles and trending picks, add four books to your TBR pile, and read none of them. The algorithm didn't know you. It knew what was performing well that week.
Your summer reading list should come from people who actually know your taste. Here's how to build one that you'll use.
Why your summer reading list keeps failing you
This isn't a complaint about technology. It's a complaint about outsourcing your reading life to a system built to optimize clicks, not enjoyment. Recommendation engines surface what gets added to lists and generates buzz right now. That's useful if you want to feel current. It's actively unhelpful if you want the book that makes you cancel plans to finish it.
The list you'll actually read doesn't come from a bestseller carousel. It comes from someone saying, "I know you loved that one, and I think you're going to feel some kind of way about this one." There's a specific person behind that sentence. Someone who watched you ugly-cry about a fictional dog, or knew better than to recommend anything with an unreliable narrator.
So let's build your list that way.
Start with your last five reads, not your wishlist
Most TBR piles are built from aspiration: books you think you should want to read. The list grows long, vaguely ambitious, and somehow full of titles that feel like homework.
Look backward instead.
Pull up your reading log, your shelf, your memory. Look at the last five books you actually finished. Not the ones you want people to think you read. The ones you finished. What did they have in common? Maybe they were all under 300 pages. Maybe every one had a narrator you'd want to have a drink with. That pattern is data. Honest, non-algorithmic data about what you actually enjoy.
Also write down the last two books you abandoned. Not to feel bad about it, just to notice what they shared. Slow openings? Ensemble casts with too many names? Relentlessly grim tone? You're building a picture of your real reading preferences, not the ones you'd list on a personality quiz.
This is the most useful thing you can do before asking anyone for a recommendation. "I loved X, couldn't finish Y, and here's why I think that is" produces dramatically better results than "I like good books."
Ask better questions inside your book club
If you're part of a reading community, you're sitting on something most people underuse. The people in your club have watched you light up during discussion. They've seen you check your phone when you were bored. They have a real picture of your taste.
When you ask for summer reading recs, give people something to work with. Try a structured ask with four fields:
- Mood: What kind of reading experience do you want? Fast? Immersive? Funny? Emotionally wrecking? Pick one.
- Recent love: The last book you'd press into someone's hands.
- Recent miss: A book that didn't work, with a one-sentence guess at why.
- Format: Print, audio, ebook. Longer or shorter. Series or standalone.
A request with those four fields will get you useful responses. "Anyone have summer reading recs?" dies quietly. Structured asks get people thinking.
One more thing: when someone gives you a rec, ask them this. "Is this a book you loved, or a book you think I'll love?" Those are different things. A good recommender knows the difference, and their answer tells you how much to trust the pick.
Work the overlap between their taste and yours
Not every recommendation from someone you trust is a recommendation for you. Your best friend who loves dense, 600-page historical fiction might be recommending something she genuinely adores. That doesn't mean it belongs on your summer list if you've abandoned every book over 400 pages before the third week of August.
You're looking for overlap. Books that land in two columns at once: someone who knows you is excited about it, and it matches the patterns from your last-five-reads exercise. When a book sits in that overlap, move it to the top. Don't put it behind the ambitious literary novel you added because it felt like the right thing to do. (We all have that book. It'll still be there in September.)
Build the actual list
Here's a framework that works. Five books, three categories.
- Two sure things. Books that match your proven preferences closely. Low risk, high likelihood of being finished.
- Two stretches. Books slightly outside your comfort zone, recommended by someone who explained why they chose them for you specifically.
- One wildcard. The book you can't explain. Maybe the cover stopped you. Maybe someone described one scene and you've been thinking about it since. Give the instinct a slot.
Five books is manageable. It is. A list of twenty-two titles is a TBR pile, not a reading plan.
What to do this week
- Write down your last five finished books and your last two DNFs. Look for patterns. Ten minutes. Worth it.
- Post the four-field ask in your book club. Not "any recs?" The actual four fields.
- Ask one person in your life who has similar-but-not-identical taste: "What's the best thing you've read in the last year?" Then ask why. The why is the whole thing.
- Go through your existing TBR pile and cut anything you added more than two years ago without a specific memory of why. If you can't remember what excited you about it, it doesn't belong on a summer list.
- Pick your five. Use the two-two-one framework. Write them somewhere physical if you can. Lists you can see beat lists in an app you'll forget to open.
- If you're hosting a book club this summer, try running one meeting as a recommendation swap instead of a discussion. Use the structured ask. It's one of the highest-engagement formats a club can do, and everyone goes home with a real list.
The algorithm will keep generating carousels. That's fine. You don't have to use them.
Your reading life has patterns and people who know you. That combination is a better recommendation engine than anything built to serve millions of strangers. Use it.
Frequently asked questions
How do I figure out what to read next when I'm overwhelmed by options?
Look backward, not forward. Write down the last five books you actually finished and two you abandoned, then look for patterns. What did the finished ones share? Length, pacing, narrator voice, tone? That pattern is a more honest picture of your taste than any wishlist built from trending titles. Use it to filter whatever's in front of you now.
What's the best way to ask for book recommendations in a book club?
Give people something to work with. The four-field ask works well: share your current reading mood, the last book you loved, the last book that didn't work and a quick reason why, and your format preference. A structured ask like this gets better responses than an open-ended request. People are more helpful when they know what they're aiming for, and you're more likely to get a rec that actually fits.
How many books should be on a summer reading list?
Five is reasonable for most readers over a three-month summer. A list of twenty feels exciting in June and discouraging by August. Five gives you room for a surprise or two without setting you up to feel behind. Try the two-two-one split: two books that match your proven preferences, two slight stretches from someone who knows your taste, and one instinct pick you can't fully explain.
Why do I keep adding books to my TBR pile but never reading them?
Usually because TBR piles are built from aspiration rather than actual preference. You add what looks good in the moment or what's getting buzz, and when you get to it the motivation isn't there. A useful fix is clearing out anything you added without a specific memory of why. If you can't remember who recommended it or what excited you, it probably doesn't belong at the top of your list.
How do I get better book recommendations from friends?
Ask a better question. Instead of asking what they've been reading lately, tell them what you loved recently, what didn't work for you, and why you think that is. Then ask if they know something that fits. The more context you give, the more targeted the answer. Also try asking: is this a book you loved, or a book you think I'll love? A good recommender knows the difference.
Is it okay to use a DNF when asking for recommendations?
Yes, and DNFs are some of the most useful information you can share. A book you abandoned tells people what doesn't work for you, which is just as helpful as knowing what does. When you mention a DNF, add a one-sentence guess at why it lost you. Slow start, too many characters, wrong tone. That specificity helps a good recommender steer you somewhere much better.
How can a book club host run a great recommendation swap meeting?
Use the structured ask instead of a free-form share. Have each member come prepared with the four fields: mood, recent love, recent miss, and format preference. Go around the table so everyone gets to request and respond. The conversation about why certain books didn't work tends to be as good as the recs themselves, and everyone leaves with a real personalized list rather than a pile of titles nobody remembers by the time they get home.