HOW TO READ · 2026-09-10
The day's guides
Method
Follow the Word "Therefore"
Paul's letters are arguments, not essays — and every argument has hinges you can find and name.
Paul did not write devotionals. He wrote arguments — tight, sequential, building one claim on the last. The trouble is that most of us read his letters the way we read Psalms, drifting from verse to verse for a phrase that lands, and in doing that we miss the thing that makes them work: the hinges. Romans 12 opens with therefore, and that one word is doing enormous labor, reaching back across eleven chapters of theology to say: because of everything just said, here is what your body does now. Skip the therefore and you get ethics with no foundation. Read it and the whole letter clicks into a single structure.
The method is almost embarrassingly simple. Take one chapter — Ephesians 2, Romans 8, Philippians 2 — on paper you're allowed to write on. Go through slowly and circle every therefore, but, for, since, and so that you find. These are not filler words. They are the joints of the sentence, and each one is making a specific move: therefore draws a conclusion, but reverses direction, for gives a reason, so that states a purpose. A page that looked like flowing prose starts to look like a structure with load-bearing beams.
Now ask, out loud if it helps, what each joint is connecting. Ephesians 2:8 says "for it is by grace you have been saved" — for what? Trace it backward: for this is why God, being rich in mercy, made us alive. The for is explaining a claim two verses earlier. Write a small arrow in the margin pointing back to what it explains. Do this for every conjunction in the chapter and you'll end up with something that looks less like commentary and more like a wiring diagram.
This is where most readers stop, but the payoff is in the second pass. Reread the chapter and follow only the arrows, skipping everything else — read just the therefores and buts and fors in sequence, ignoring the sentences between them. What you get is the argument's skeleton, stripped of illustration and detail. It usually takes four or five lines. That skeleton is what the author actually wants you to walk away holding.
It changes how you read Paul specifically, because he is the New Testament's most argumentative writer, but it works anywhere prose reasons its way somewhere — a psalm's wisdom sayings, a prophet's oracle, even a Gospel discourse. You start to notice when a writer is building toward something rather than simply describing it, and you stop treating a chapter as a bag of verses you can pull out at random. It also catches you when you've misread a favorite verse in isolation — half the misquoted lines in Scripture are missing their therefore.
None of this requires Greek or a commentary. It requires a pen, a printed page, and the patience to read slower than feels natural at first. The conjunctions were always there. Most of us just read past them.
- Print or photocopy a single chapter you can mark up
- Circle every therefore, but, for, and so that
- Ask what each word is doing to the sentence before it
- Sketch the flow as a short arrow chain in the margin
- Reread the chapter following only the arrows
7 MIN
Practice
Read With an Eye for Echoes
The Gospel writers had the Old Testament memorized, and their scenes are built to remind you of it.
When John opens his Gospel with "in the beginning," he is not being poetic for its own sake. He is telling you, in the first three words, to have Genesis 1 open in your mind at the same time you read his page. This is how the Gospel writers work throughout — not by footnoting their sources but by using images so specific that a reader who knew the Hebrew Scriptures by heart, which most of their first audience did, couldn't help but hear the older story underneath the new one.
The habit worth building is simple: when a Gospel scene has a strong physical image — water, bread, a mountain, a shepherd, a lamb, a wilderness, forty of anything — stop and ask where else in the Bible that image carries weight. Jesus feeds a crowd bread in a wilderness; Israel ate bread in a wilderness. Jesus is led up a mountain to deliver teaching; Moses was led up a mountain to receive it. Jesus is called the Lamb before he's called almost anything else; there was a lamb at the first Passover, and its blood meant a household lived. These aren't coincidences the Gospel writers hoped you'd notice — they built the scenes to be noticed.
The important step is the one people skip: go read the earlier story in full, not just the single verse that seems to match. Don't just note that Exodus has manna — read the whole chapter, the grumbling that preceded it, the instructions about gathering only enough for the day, the omer kept as a memorial. Context is where the echo gets its meaning. A single matching word can mislead you; a whole matching story rarely does.
Then put the two scenes side by side, literally if it helps — two columns, two open pages. List what's identical and what's different. Israel needed a place to gather bread every day and grumbled about it; the crowd Jesus feeds needs one meal and is satisfied. Moses climbed the mountain to receive law from God; Jesus sits down on the mountain and speaks the law himself. The differences are not errors in the pattern — they're the point of it. Every echo in Scripture is making an argument through comparison, usually the argument that what came before was real but partial, and what's happening now completes it.
This kind of reading takes longer than reading for information, and it will feel unfamiliar if you've mostly read the Bible in isolated daily chunks. But it rewards rereading more than almost any other habit, because the Bible was written by authors in constant conversation with everything written before them. Once you start looking for the echoes, you stop being able to not see them — and passages you thought you already knew fully open up a second layer underneath the first.
Getting started
Bring Three Questions, Not Answers
A Bible study works better as a room full of honest questions than a room full of people trying to sound like they already have it figured out.
Most people dread Bible studies for the same reason: someone shows up having already decided what the passage means, and the hour becomes them explaining it to everyone else. It's not malicious — it usually comes from nerves, from not wanting to look unprepared. But it turns a room of people into an audience, and it means nobody in the room, including the person leading, is actually reading anymore. They're performing a reading they already finished at home.
The fix is a small discipline: come with questions instead of conclusions. Read the passage alone beforehand, and instead of writing down what you think it means, write down three things you genuinely don't understand. Not softball questions you already know the answer to and are asking rhetorically — real ones. Why does this genealogy matter here. Why does Jesus say this and not something kinder. Why does this psalm end on a complaint instead of a resolution. If you can't find three honest questions, you haven't read closely enough yet.
Bring those three questions to the group instead of a lesson. This does something structural to the room: it makes you a participant instead of a teacher, and it gives everyone else permission to admit what they don't understand either, because you went first. Groups loosen up remarkably fast once the person who usually has answers shows up with questions instead.
When you ask your question, let someone else answer first — even if you have a guess, even if their guess is wrong or incomplete. The instinct to jump in and correct or finish someone else's thought is the same instinct that turns a study into a lecture. Silence after a question is not a problem to be solved. It's usually just people actually thinking, which is the entire point of showing up.
At the end, instead of writing down a summary of what was said, write down what changed your mind — a reading you hadn't considered, an objection someone raised that you couldn't answer, a question that's still open. This is a different kind of note than "what we agreed on," and it's the one worth keeping, because agreement is easy to remember and rarely useful, while the thing that actually moved you is worth finding again later.
None of this requires a curriculum or a trained leader. It requires people willing to read the passage before they arrive and admit, out loud, what they don't yet understand about it. That's a lower bar than most groups set for themselves, and a much more honest one.
Back to today's paper →