Homiletics 2

Sermon Preparation & Preaching

New Page

The Shorter Sermon

1. The Secondary Loop Vulnerability

A new context introduced that must be explained like a separate,independant story line and or scriptural text introduces a secondary loop that must be opened, processed, and closed so as to return to the primary loop.

The Problem: You need to establish a critical truth (e.g., "The ruler was sincere"), but instead of mining the data already inside the text, you open a secondary narrative loop (e.g., The Lawyer in Luke 10) to create a contrast.

The Cost: Every secondary loop requires setup, execution, and closure. This is where the clock evaporates.

The Fix: "Mine the Metadata First." Look for high-density, low-word-count data points inside the primary scene (like the ruler running or kneeling) before you reach for an external cross-reference. Prove your point using the immediate architecture.

2. The Abstracted Interface Principle

The Problem: You have done deep infrastructure work in your study (lexicons, historical timelines, 517 verses of towb). You feel a responsibility to show the listener the "source code" so they know your interpretation is stable and authoritative.

The Cost: You spend 10 minutes teaching a mini-seminary class on Greek linguistics or Ancient Near Eastern history before hitting the actual message.

The Systemic Fix: "Deliver the Output, Not the Process." Trust your own study. The listener needs the high-level user interface, not the database schema. If the lexicon study proves God is an uncaused source of active generosity, don't teach the dictionary entry—just deliver the Waterfall. Your authority comes from the accuracy of the metaphor, not the recitation of the notes.

The Abstracted Interface Principle <== this one is personally difficult as it is a dense concern for me. It is both practically heavily waited for me and ethically. I feel a moral responsibility to not make claims without demonstrating warrant. I notice I "spend" alot of time due to this kind of tension of "to show the listener the "source code". My philosopy of preaching informs me that intention of preaching is to persuade and therefore by extension is unethical to persuade someone without ensuring they are properly INFORMED.

If the goal of preaching is persuasion toward eternal truth, then bypassing the "warrant" (the evidence, the source code) to get a quick emotional or practical response can feel dangerously close to manipulation.

You aren't trying to sell a product with a slick user interface; you are trying to form a mind. If you don't show the text's infrastructure, you aren't training the listener how to read their Bible responsibly—you're just asking them to take your word for it.

The reason you hit 42 minutes is that your notes treated the "Informing" stage and the "Persuading" stage as separate, sequential batches

I clearly have imperfectly solved this tension. I think part of my challenge is how I know my mind compartmentalizes information and speaking extemporaneously well requires me to remember a primary structure. I naturally gravitate to "lay the foundation" , "build on the foundation" as sequential steps where I move on from "lay the foundation" once in real time it feels like the audience has be properly primed.

---- 2. THE FOUNDATION: The Source Code of Good [MAX: 4 MINUTES]

Ethical Warrant: Ground the word "Good" in the Creator, not human effort.

[== HARD STOP: DO NOT PASS THIS LINE WITHOUT SWITCHING TO THE RULER ==]

If you try to hedge against every possible misinterpretation or speak to every demographic disposition simultaneously, the architecture collapses under its own protective weight. You end up preaching a sermon about preventing misunderstandings rather than preaching the text itself.

To keep your pillars from expanding when you face an unknown audience disposition, you have to shift from a strategy of Defensive Hedging to a strategy of Controlled Sampling. Here are three tactical ways to handle this out loud:

  1. The "Brackets of Awareness" Technique
  2. Establish a "Target User Persona" Beforehand
  3. The "API Rate Limit" for Real-Time Caveats

3. The Topologically Dense Error

The Problem: On a flat piece of paper, a bulleted list looks short and linear. Point 1 flows to Point 2 flows to Point 3.

The Cost: In real time, Point 2 ("God is the uncaused creator") turns out to be a massive, infinite theological cavern. You realize mid-sermon that you cannot jump from the dirt road of Matthew 19 into the cosmic genesis of the universe without building a massive linguistic bridge, which grinds the momentum to a halt.

The Systemic Fix: "Match the Topological Footprint." If your sermon starts in a narrative sandbox, stay in the narrative sandbox. If you must introduce grand systematic theology, do not build a new sandbox for it. Force that theology to serve as a flashlight illuminating the characters already on the stage (e.g., freezing the frame on Jesus' words in Mark 10:18 to unpack towb right there).

4. The Pre-Run Warmup Expansion

When you stood up, your brain registered a high emotional distance between the audience and a 2,000-year-old story about a wealthy provincial ruler. Your pastoral instinct correctly diagnosed a connection problem: “If they don’t care about the theme of 'not being good enough' on a raw, human level, the upcoming exposition will just feel like an academic lecture.”

So, you fired up an ad-hoc personal story to bridge the empathy gap. It worked—it hooked them—but it cost you 4 minutes before you even opened the book.

The Concept of "Subversive Usurping" Your story about the young lady misinterpreting your general lack of interest as a personal rejection ("I'm not good enough") is a perfect narrative match for the Rich Young Ruler. It establishes the exact psychological phenomenon you wanted to preach: taking a structural truth and internalizing it as a personal performance failure.

The young man in Matthew 19 did the exact same thing. Jesus was presenting a structural truth about the nature of God's uncaused goodness, but the ruler internalized it as a personal checklist challenge: "What good thing must I do?"

The problem wasn't the story; the problem was redundancy.

Your personal story and the young ruler's story are structurally identical. By telling both, you ran two completely separate instances of the exact same narrative code. The personal story usurped the primary text's job, turning the actual reading of scripture into a repetitive second step.

"...she took my general boundary and internalized it as: 'I'm not good enough.' We do this all the time. We take massive realities and shrink them down into a scoreboard for our own worth.

And that is exactly what is happening on this dirt road in Matthew 19. A young man comes running up to Jesus with the exact same haunting insecurity..."

By stitching the personal story directly into the neck of the passage, the 4-minute investment pays for itself. You read the text, bypass the historical context and the lawyer contrast entirely, and move immediately to Jesus’ response in verse 18.

The Redundancy Test: If a personal illustration perfectly captures the emotional heartbeat of the sermon's tension, it cannot be an addition to the scriptural story. It must become the lens through which the scriptural story is immediately read.

You either use the text's internal metadata to hook the room (the ruler running and kneeling), or you use your personal story to hook the room and then aggressively strip the text down to its bare structural components. You cannot run both pipelines to full capacity in 20 minutes.

The Memory Anchor

A short, powerful sermon is not about compressing a 40-minute document; it is about restricting the environment.

If you keep the camera locked on one narrative landscape and mine its internal metadata, the sermon remains incredibly deep ("rich furrows in a small field") rather than shallowly covering the whole globe in 20 minutes.