Lecture 1-2: Exegesis, Hermeneutics, and Homiletics — A Dependency Chain
Contents 43
- Lecture 1-1: Hermeneutics — A Discipline, Not a Byproduct
- Lecture 1-2: Exegesis, Hermeneutics, and Homiletics — A Dependency Chain
- Lecture 1-3: The Hermeneutical Spiral — Text and Reader in Dialogue
- Lecture 2-1: Inspiration — What the Claim Is, and Is Not
- Lecture 2-2: Dual Authorship, and How Strictly to State Inerrancy
- Lecture 2-3: Clarity and Its Limits — Who Has the Final Word?
- Lecture 3-1: Observation — What Is Actually on the Page
- Lecture 3-2: Interpretation — Turning Observations into Answered Questions
- Lecture 3-3: Application — From Meaning to Life Without Moralizing
- Lecture 4-1: Jewish Interpretive Tradition — Peshat, Derash, and Early Midrash
- Lecture 4-2: Patristic Interpretation — Alexandria, Antioch, and the Fourfold Sense
- Lecture 4-3: The Reformation, the Enlightenment, and the Twentieth Century's Turns
- Lecture 5-1: Copies, Not Autographs — Why Textual Criticism Exists
- Lecture 5-2: Manuscript Families — the Masoretic Text, the Dead Sea Scrolls, and the New Testament's Text-Type Debate
- Lecture 5-3: How the Canon Took Shape — and What That Process Does and Does Not Establish
- Lecture 6-1: Tools for Readers Without Hebrew or Greek
- Lecture 6-2: The Root Fallacy and Other Classic Word-Study Errors
- Lecture 6-3: Semantic Range, Context, and the Trap of the "Secret Meaning"
- Lecture 7-1: Grammar Carries an Argument's Logic
- Lecture 7-2: What Greek Tense and Voice Can — and Cannot — Establish
- Lecture 7-3: From Grammatical Analysis to a Sermon That Keeps Its Logic
- Lecture 8-1: Context Is King
- Lecture 8-2: Near Context — The Paragraph's Argument
- Lecture 8-3: Canonical Context and Two Case Studies
- Lecture 9-1: Why Background Study Matters, and What It Serves
- Lecture 9-2: Ancient Near Eastern Backgrounds and Second Temple Judaism
- Lecture 9-3: The Greco-Roman World and the Limits of Background Study
- Lecture 10-1: Narrative as Literary Art
- Lecture 10-2: The Exemplary-Only Trap
- Lecture 10-3: Acts and the Descriptive/Prescriptive Distinction
- Lecture 11-1: Reading Old Testament Law Today
- Lecture 11-2: The Threefold Division of the Law
- Lecture 11-3: Wisdom Literature's Genre — Proverbs, Job, and Ecclesiastes
- Lecture 12-1: Psalm Genres and the Problem of the Imprecatory Psalms
- Lecture 12-2: Prophetic Literature and the Conditionality of Prophecy
- Lecture 12-3: Apocalyptic Symbolism and How to Read Revelation
- Lecture 13-1: What Kind of Book Is a Gospel?
- Lecture 13-2: Parables — How Far Do the Details Go?
- Lecture 13-3: Epistles — Reading an Argument Across Nineteen Centuries
Three words get used loosely as near-synonyms in ordinary church conversation — exegesis, hermeneutics, homiletics — and the looseness costs something. This lecture separates them, not as a pedantic exercise in vocabulary, but because each names a genuinely different task, and the three stand in a strict dependency order: homiletics builds on exegesis, and exegesis is only as sound as the hermeneutics governing it. A sermon can be moving, well delivered, and completely disconnected from what a text actually says, and when that happens, the failure almost never began in the pulpit. It began earlier in the chain, usually in a hermeneutical assumption nobody examined.
This matters for a reason beyond definitions. Once the three tasks are seen as dependent rather than interchangeable, a listener gains a genuinely useful diagnostic: when a sermon or a Bible study conclusion feels wrong, the question "which link in the chain broke?" is more productive than simply disagreeing with the conclusion. Sometimes the exegesis was careless — a detail in the text was missed. More often, once a course has spent time on the discipline, the deeper problem is hermeneutical: an unexamined assumption about how to move from ancient text to present meaning, quietly steering the exegesis before it even started.
What these 14 minutes give you
- Define exegesis, hermeneutics, and homiletics, and state accurately what each one does.
- Explain why the three stand in a dependency order rather than functioning as three independent skills.
- Give an example of a sermon conclusion that could be homiletically polished while resting on faulty exegesis, and identify where the chain likely broke.
- Explain, using Nehemiah 8:8, why "reading" and "giving the sense" were already treated as two distinct acts long before the word "hermeneutics" existed.
They read in the book, in the law of God, distinctly; and they gave the sense, so that they understood the reading. — Nehemiah 8:8
World English Bible
1. Three tasks, three different questions
comes from the Greek exēgeomai, "to lead out" or "to draw out" — the discipline of drawing meaning out of a text rather than reading a meaning into it (the opposite move, reading a prior conclusion back into a text, has its own name: , "leading in," and it is the failure mode exegesis exists to prevent). Exegesis asks a narrow question about one specific passage: what does this text, in its own language, grammar, and historical setting, actually say? It is close, patient, text-level work — the kind of work chapter 3's inductive method will train directly.
, as lecture 1-1 defined it, is not the close reading of one passage but the theory governing how that close reading should be done at all — the set of principles that tells an interpreter which questions to ask of a text, how much weight the original audience's situation carries, and how a passage's meaning legitimately becomes relevant to a reader who was never part of that audience. If exegesis is the doing, hermeneutics is the theory of how to do it correctly — every exegetical decision, whether the interpreter names it or not, rests on hermeneutical assumptions about what kind of thing a biblical text is and how meaning is supposed to be found in it.
is furthest downstream: the discipline of building a sermon — structure, illustration, application, delivery — from what exegesis, disciplined by sound hermeneutics, has already established. Homiletics does not investigate what a text says; it takes that as settled and asks how to communicate it faithfully and compellingly to a particular congregation.
2. A dependency chain, not three parallel skills
The three are often taught as though they were three separate competencies a minister happens to need — as if a preacher could be weak in exegesis but strong in homiletics, the way someone might be a poor cook but a fine host. Robert Plummer's 40 Questions About Interpreting the Bible resists exactly this picture by devoting sustained attention to how interpretation and application relate, treating faithful preaching as something that stands or falls on the exegetical and hermeneutical work beneath it, not as a separately rescuable skill. Bernard Ramm's Protestant Biblical Interpretation, one of the standard treatments of Protestant hermeneutical method, makes the ordering explicit: hermeneutics is the science whose rules exegesis applies to specific texts, and it is only once that application has produced a sound reading that homiletics has sound material to work with.
The dependency runs one direction. A preacher can have flawless delivery, a compelling illustration, and a genuinely moving structure, and still preach a sermon that misrepresents the text — because homiletical skill operates on whatever exegetical conclusion it is handed, and it has no way of checking that conclusion's accuracy. Homiletics is not equipped to catch an exegetical error, any more than excellent packaging can fix a flawed product inside the box. And exegesis, in turn, is only as reliable as the hermeneutical assumptions steering it: an interpreter who assumes every Old Testament narrative detail is a moral example to imitate (a hermeneutical assumption, examined directly in chapter 10) will do careful, honest-feeling exegetical work and still arrive somewhere the text never intended, because the assumption steering the search was faulty before the search began.
3. Where the chain actually breaks
This gives a working diagnostic worth practicing now, because the rest of the course will keep using it. When a sermon or a Bible-study conclusion feels off, three questions, asked in order, usually locate the break:
First — is this a homiletical problem? Sometimes the exegesis and hermeneutics are entirely sound and the sermon is simply poorly organized, or the illustration does not fit, or the delivery undercuts the point. This is a real problem, but not the kind this course addresses.
Second — is this an exegetical problem? Did the preacher miss a detail actually present in the text — an overlooked connective, an ignored parallel passage, a mistranslated phrase? This is a failure at the "drawing out" level, and chapter 3's inductive method and chapter 7's grammatical method exist to reduce exactly this kind of error.
Third, and hardest to see because it is invisible in the sermon itself — is this a hermeneutical problem? Did an unexamined assumption about how to read Scripture govern the exegesis before the exegesis began? This is usually the deepest break, and the one most likely to be repeated across many sermons and many texts, because the same faulty assumption is doing the same damage every time it is applied. A congregation that hears the same kind of misreading across many different passages is very often hearing the downstream effect of one uncorrected hermeneutical assumption, not a string of unrelated exegetical mistakes.
4. An old distinction, not a modern invention
Nehemiah 8:8 shows this distinction is not a modern academic import onto an ancient practice. "They read in the book... distinctly; and they gave the sense, so that they understood the reading" names two separate acts: correct public reading, and a further act of explanation that made the reading understood. The text does not treat these as the same accomplishment achieved twice. Reading distinctly — getting the words right — is closer to what this lecture calls the raw material exegesis works on; giving the sense so the people understood is closer to what hermeneutics governs and homiletics eventually delivers. The postexilic community, generations before any Greek term for "interpretation" existed, already knew that correct reading and given understanding were two different achievements, and that the second did not automatically follow from the first.
5. What this changes about how you read — and preach
The practical upshot for this course, and for any later ministry, is a habit of checking the chain in order rather than jumping to conclusions about where a problem lies. Before revising a sermon's illustrations, ask whether the exegesis underneath is actually sound. Before trusting a compelling exegetical conclusion, ask what hermeneutical assumption made that reading seem obvious — and whether that assumption would survive being stated out loud. A discipline that checks its own foundations, rather than only its finished product, is what keeps "properly handling the Word of Truth" (2 Timothy 2:15, cited in the previous lecture) from becoming a phrase reserved for polish rather than accuracy.
In short
- Exegesis ("to lead out," from exēgeomai) is close, text-level work drawing meaning out of a passage; its failure mode, reading a prior conclusion back in, is called eisegesis.
- Hermeneutics is not the close reading itself but the theory governing how that reading should be done — the assumptions about what a biblical text is and how meaning is legitimately found in it.
- Homiletics builds a sermon from what exegesis, governed by sound hermeneutics, has already established, and has no way to catch or repair an exegetical error underneath it.
- Bernard Ramm's Protestant Biblical Interpretation makes the ordering explicit: hermeneutics is the science whose rules exegesis applies, and only then does homiletics have sound material to work with; Robert Plummer's 40 Questions About Interpreting the Bible likewise treats faithful preaching as standing or falling on that exegetical and hermeneutical work.
- Nehemiah 8:8 names two distinct acts — reading the law distinctly, and giving the sense so the people understood — showing the distinction between correct reading and given understanding predates any Greek term for "interpretation."
If you remember nothing else from this lecture: Exegesis, hermeneutics, and homiletics are not three interchangeable skills but a dependency chain — hermeneutics is the theory of how to read rightly, exegesis applies that theory to one passage, and homiletics builds a sermon from what exegesis has already settled, with no power to fix a flawed exegesis underneath. A polished, moving sermon can still misrepresent a text, because homiletical skill cannot check the accuracy of the conclusion it is handed — like fine packaging that cannot repair a flawed product inside the box. When a sermon feels "off," the three-question diagnostic (homiletical? exegetical? hermeneutical?) usually finds the break, and the hermeneutical break is the deepest, because it repeats the same error across every text it touches. Nehemiah 8:8 shows this was already understood long before anyone had a word for "hermeneutics": reading the words correctly and giving the sense so people understood were always two different achievements.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Think of a sermon or Bible study you have heard that felt "off" even though the delivery was strong. Using the three-question diagnostic in section 3, where in the chain do you now think the actual break was?
- Ramm treats hermeneutics as the "science" whose rules exegesis applies. Why might calling it a science, rather than an art or a gift, matter for how seriously a preacher takes it?
- Nehemiah 8:8 distinguishes reading distinctly from giving the sense. Can you think of a place — in your own church, or your own reading — where the first happens without the second?
- This lecture claims homiletical skill cannot rescue faulty exegesis. Is there a limit to that claim — can a genuinely gifted communicator ever compensate for a shaky exegetical foundation, or does the compensation only ever hide the problem rather than fix it?