Blog/Bible Study6 min read

From Then to Now

From Then to Now illustration for Protos Bible study guide

Application goes wrong in two opposite directions. Collapsing the gap treats us as the original audience and turns Deuteronomy 22:8 into a rule about balcony railings. Jumping the gap skips the setting entirely and builds on a phrase that merely sounds meaningful. The bridge is three steps: what the text meant first, the principle behind it, then application.

A cell group leader once told her group that Deuteronomy 22:8 was God's instruction to put railings on their balconies. She wasn't wrong that the principle had something to do with safety. But she wasn't quite right either. She had taken a command written to farmers living in flat-roofed houses where people gathered in the evenings, and turned it into a building code for modern apartments. Close, but the gap between then and now had done some damage in the crossing.

Every passage of Scripture involves a gap, the distance between the world it was written into and the world we read it in. How we cross that gap shapes everything. Cross it carelessly and we misapply the text. Skip it entirely and we lose the text's weight. The work of faithful application is learning to cross it well.

The first error: collapsing the gap

Collapsing the gap means treating ourselves as the original audience. We read a command, feel its moral force, and apply it directly, as though two thousand years and a completely different culture don't stand between us and the page. Deuteronomy 22:8 is a clean example. "When you build a new house, you shall make a parapet for your roof, that you may not bring the guilt of blood upon your house, if anyone should fall from it" (Deut 22:8, ESV). A reader who collapses the gap starts wondering whether their roof deck has adequate safety rails.

The roof here was a flat work surface, a social space, part of daily life for an ancient Israelite household. The command was never about roof architecture for its own sake. It was about responsibility toward neighbors. If someone is hurt on your property because of your negligence, that blood is on your hands. Lift the principle out of the ancient rooftop, and you find something that speaks directly to workplace safety, car maintenance, the condition of your staircase. The command is not weaker for being translated. It is stronger, because you've found what it was always actually saying.

The second error: jumping the gap

Jumping the gap is the opposite problem. Here, the reader skips the original context entirely, grabs a phrase that sounds meaningful, and builds application on top of it without ever asking what the author intended. The result is often true in a thin sense but hollow at the root.

Take Philippians 4:4: "Rejoice in the Lord always; again I will say, Rejoice" (Phil 4:4, ESV). Lifted clean from its context, this becomes a slogan about staying positive. A motivational poster. But Paul wrote those words from prison, into a culture saturated with Stoic philosophy that prized emotional self-control as its own reward. His readers would have heard the echo of that framework and recognized that Paul was doing something different. He was not prescribing a mood. He was naming a source. The joy he commands is "in the Lord," grounded in a person and a finished work, not in willpower or circumstance. A group that understands that does not tell a grieving member to cheer up. They sit with him, and they point him back to Christ.

The bridge: principle before application

Between collapsing and jumping is the real work. The method has three steps. First, establish what the text meant to its original audience. Second, name the theological principle the original command or teaching was expressing. Third, apply that principle into your own context. The principle is the bridge. Without it, you are either in the ancient world pretending it is your world, or in your world pretending the ancient world does not matter.

First Corinthians 11:2-16 is one of the most consistently mishandled passages in this regard. Paul's instructions about head coverings in worship have attracted two centuries of misreading. Collapse the gap, and you get a dress code: women must cover their heads in church. Jump the gap, and you get a vague principle about honoring God in worship, with the text doing no real work at all.

Bridge it carefully, and something more interesting emerges. Paul is addressing a specific situation in Corinth where certain practices in gathered worship were obscuring the relationships and order the gospel itself had established. The head covering was a culturally legible signal about those relationships in that setting. The theological principle is not "women must wear hats." It is something closer to this: worship practices should honor the relationships and order the gospel addresses, not erase them or perform against them. Evangelicals read the underlying principle differently. Some emphasize creation-order distinction between men and women. Others emphasize mutual honor without specifying a hierarchy. Either way, the principle lands very differently in different cultures, and asking how it lands in yours is exactly the right question.

How to find the principle

When you read a passage, ask two questions before reaching for application. First, what was the specific problem or situation this text was addressing? Second, what does the author's response to that situation reveal about God, humanity, or the shape of the Christian life? The answer to the second question is usually the transferable principle. It will sit above the specific cultural detail but below pure abstraction. "Be responsible for the safety of those in your care" is the right altitude for Deuteronomy 22:8. "Joy is grounded in Christ, not in conditions" is the right altitude for Philippians 4:4.

Good commentaries help here, not because they do the application for you, but because they do the historical work that makes the original situation legible. The more clearly you see the ancient world, the more confidently you can name what was culturally specific and what was theologically load-bearing. This is also why genre matters. A law code, a letter, and a proverb all carry principles differently, and reading each as if it were the other produces confusion. If you want to go further on that, Reading by Genre works through those differences in detail.

Faithful application is not optional

Some readers treat application as the lesser half of Bible study, the practical follow-up to the real theological work. But faithful application is itself a theological act. It says: this Word was given by a God who meant it to reach us, not just the first audience. The gap is real. The bridge is real. The arrival matters.

The opposite of sloppy application is not no application. It is careful application: slow, contextually informed, theologically grounded. A group that does this well does not produce thin moralism or arbitrary proof-texting. It produces people who know why they believe what they believe, and who can explain it to someone else. That is what Why Context Matters has always been pointing toward. The original context is not an end in itself. It is the foundation that makes trustworthy application possible.

This week, take one passage from your group's study text, write down the original situation in one sentence, the theological principle in one sentence, and then the specific application for your group in one sentence. Share all three with your group before you open the discussion.

#hamartiology#lay-leadership

Terms in this article

Every passage each one appears in, with the definition attributed to its source.

Keep reading

Read it in context

Read the passage with the background already on it.

Tap any name, place, or word you do not recognize and the background opens on the verse you are reading. No second tab, no search, no losing your place.

The Protos reader open on Genesis 1 with the How to Read Genesis background sheet raised over it
"People don't give up on the Bible for lack of discipline. They give up because they don't understand what they read. So they skim past it and jump straight to what it means for them, before they have listened to what God is saying through the words, the story, and the voice of the writer. It happens so often that theology has a name for it: eisegesis."
Fabio Jonathan ArifinFabio JonathanFounder of Protos · Portland Bible College graduate

Protos is the answer to that. Every explanation you read was written by a scholar and published in a reference work, credited right on the page.

★★★★★4.7 from 107 App Store ratings

The streak feature actually got people in my congregation excited to read, especially the youth. We've started comparing notes after service.
★★★★★
PPhilPastor, Ohio
between work + kids i barely get time to breathe lol. but protos somehow helps making deep studies doable. i've been reading during lunch breaks again for the first time in years.
★★★★★
CCalebA dad
been using protos for like 2 weeks now. It helps me prep for our small group without getting overwhelmed. The context snippets show up right where I need them.
★★★★★
CChloe ChuaSmall group leader, Singapore

Start understanding the Bible better.

Download on the App StoreGet it on Google Play

Android is in review with Google Play. Tap the Play badge and we will email you the day it lands.