Chapter 6
[ Chapter Six ]
Sermon Preparation
A good friend of ours—a coffee snob if ever there was one—once said that when he goes into Starbucks, he orders a "triple grande, two-pump, low-foam, extra hot, low-fat, regular-syrup, vanilla latte." No kidding, that's his drink. Those who know him will not be surprised! Truth in advertising, mine's not much better. It's a "Grande Tazo Chai tea, unsweetened, with a little steamed milk on top." Mark's is . . . "milk. What do you mean what kind of milk? Just milk."
God bless him.
Giving preachers advice on how to prepare sermons is a little like telling them what "their drink" should be at Starbucks. It's deeply personal! So is sermon preparation in many ways, and every preacher does it somewhat differently. For example, I learned most everything I know about preaching from Mark, but you'll notice in this chapter that we don't do everything exactly the same way. We don't even think about some parts of sermon preparation in exactly the same way. That's inevitable, really, and probably a good thing. God calls a lot of different kinds of men to be preachers, and that creates a magnificent richness in the life of His church around the world.
We also hope you'll realize that entire books have been written and seminars taught on the mechanics of sermon preparation. Many of those books and seminars are exceedingly good, and we doubt there's much we can do in a chapter like this to match all of that. So we're not going to try. This chapter, therefore, should not be understood as a comprehensive guide to sermon preparation. Nor is it a comprehensive guide to biblical exegesis or to hermeneutics or to biblical theology.
On the other hand, we are also convinced that sermon preparation is a hard, time-consuming process, and that many preachers do not give themselves as fully as they should to that work. In this chapter, therefore, we want to show you a little of what we do in preparation for preaching, and perhaps even give you some ideas that will make your times of preparation more fruitful. You'll notice that we don't do everything in exactly the same way, but what we are both aiming for—most fundamentally—is to understand the text and then explain it and apply it to our people's lives.
Understand the Text
That's the first step. If you're going to expose God's Word to your people, naturally you have to start with understanding what your text says and what it means. If you mess that up—if the meaning of the text is muddled in your mind or if you're convinced of a wrong understanding of the text—your sermon will misfire badly. For that reason the most important part of sermon preparation is to make sure your understanding of the biblical text is deep, solid, and as comprehensive as possible.
Read It
Start with reading it. Both of us read the text we're going to preach multiple times in the previous week. Mark even uses the text as a part of his daily devotional time, reading it and meditating on it alongside any other readings he is doing. That's not to say that you have to be reading the text with the same intensity you will when you really start preparing for the sermon. Probably, in fact, you shouldn't read it with that kind of intensity. Just read it devotionally, and let it affect your heart; see what the Lord does with it in your own life. That could be wonderfully helpful to you as you prepare to present the text to your congregation.
One practice we both have found helpful in understanding the text is reading it in multiple translations. Whether it's by having an assistant sit and read the text to me in one translation while I stare at it in another (Mark), or just doing it myself (Greg), it's helpful to see how other Christians have translated the underlying Greek or Hebrew. Sometimes, of course, they get it wrong, and therefore you have to be careful before you make a particularly colorful translation the main point of your teaching! But on the whole it's helpful. Sometimes ideas are rendered more clearly by one translation than by another. Sometimes just the repetition of the same ideas in different words can jar your mind into new thoughts and new insights. The point, however, is simply to spend a good deal of time letting the text roll around in your mind, and reading it in different translations is a good way to keep the roll going!
Diagram It
Once you begin preparing in earnest, you should turn your full attention to understanding every detail of the text. That doesn't mean simply the meaning of every word and preposition and the archaeological background of every town name. Perhaps even more important is to understand the flow of the text. Why does this sentence follow that sentence? Why on earth does Jesus start talking about that right after He's been talking about this? How does this paragraph set that paragraph up, and where is Paul going with this whole train of thought?
One thing we find helpful in this process of understanding the flow of a text is diagramming it. There are many different methods of diagramming, and even the two of us do it slightly differently. Some prefer to do it in the original languages; others in English. Some like to mark the part of speech of each word, and others don't. I (Mark) generally type the text into a word-processing document. I don't copy and paste it; the act of typing it is helpful in flagging for my mind phrases and relationships between phrases that the eye can miss when I'm just reading. Once it's typed, I print the document out and then use colored markers to highlight various themes in the text. So every time I see Peter talking about perseverance, for example, I might mark it in green. Or when I see him mentioning something about atonement, I mark it in red. That color-coding system, which changes with every text, helps me see the tenor of the text. I can see at a glance how it flows from one idea to another, and that can help me as I'm working toward an outline.
My (Greg's) diagramming process is somewhat different. I don't type the text into a document but rather copy it with pen into a notebook. In the process I divide the text phrase by phrase, using lines to show how the various phrases connect to one another. As I move through the diagram, I find that I can get a clear picture of the "shape" of the text. Paul's writings, for example, are made up many times of one dependent clause after another. Diagramming helps me identify the main clause and then see more clearly how all the dependent ones relate to it. It can also help me see things that aren't obvious when I'm just looking at the text in paragraph form—when two clauses are parallel to each other, for example, or when even entire paragraphs hang on a single idea from a previous paragraph. I have found many times already in my preaching that a text will click into shape almost immediately when I diagram it, even if it looked really difficult the first time I read it.
Use the Original Languages
What about the original languages? Again, different preachers use the original languages to different degrees. Some guys actually take the originals into the pulpit and preach from them! Neither of us does that. We do use the original languages, but precisely how much varies from sermon to sermon. Both of us, for example, find ourselves using Greek more than Hebrew. Why? Neither of us is sure. Maybe it's that we both tend to preach longer passages out of the Old Testament than we do from the New Testament, so it's simply harder to spend as much time with a long passage of Hebrew as with a short passage of Greek. Even in the New Testament, though, our work with the originals varies from text to text. Some weeks I (Greg) read my whole text in Greek several times. Other weeks I find myself turning to the Greek only when I've run into some snag and need to look more deeply at it. Sometimes that clears up problems nicely; other times, frankly, it just translates the problem into Greek!
Ultimately, hardly a week goes by that we don't find ourselves in the original languages for at least part of our sermon preparation. The fact is, our English translations are for the most part very good, and it's rare to find them all wrong at the same time on something that I will be able to figure out on my own from the original language. And yet there's something wonderfully clarifying and insight generating about looking at a familiar text in a thoroughly unfamiliar way. One of the preacher's greatest enemies is familiarity: He thinks he understands a particular text because he has known its meaning all his life, and because of that he winds up missing its point when he preaches it. Looking at a text in the original languages helps minimize that kind of mistake.
Both Greek and Hebrew, for instance, tend to front-load their most important ideas, so the phrases that come at the end of our English sentences will often show up first in a Greek or Hebrew sentence. That's helpful if you've memorized a text in a certain way in English; when you read it in the original, it strikes your mind at a different and helpful angle. Not only that, but there are some texts that are the subject of raucous controversy, and many times that controversy turns on some point of Greek or Hebrew syntax or definition. You can certainly follow the arguments without knowing or engaging in any original language study, but the only way to get to the nub of the argument, formulate an opinion of your own, and then present your conclusion to your congregation is to have some facility with Greek and Hebrew. You don't have to know the languages fluently. I (Greg) have only what I call a "Bible-working" knowledge of both—just enough to use the software program BibleWorks! But as long as I remain humble about what I do and don't know—as long as I remember that there is a point at which you know just enough Greek to make a fool of yourself—it's helpful to me as a preacher to have that knowledge. It gives my understanding of the texts, and therefore my preaching (I hope), a depth and texture they would not otherwise have.
Use Commentaries . . . Eventually
Many preachers, we are convinced, retreat to commentaries on a text way too quickly. Sometimes even before they open the passage and read through it for themselves, they look at commentaries to find out what they should be seeing in the text when they finally read it. We think that's backwards. Part of the reason your congregation called you to preach to them is because they recognized in you an ability to read and understand the Bible, not just other people's opinions about the Bible.
We would encourage preachers, therefore, to spend a huge amount of time staring at the text for themselves, trying to discern the structure and the main idea on their own. Through reading it repeatedly, diagramming it, color-coding it, and meditating on it, you'll be able to understand its main contours and come to a good idea of how you want to teach it and apply it to your church.
So, when should you turn to commentaries? Essentially, we've found that there are two very good times to use commentaries. The first is when you run into a problem you just can't seem to break through. You've tried looking the phrase up in other parts of the Bible, turning it over in your mind to see if any new ideas come to light, even rethinking your diagram of the text to see if it clicks a different way; and it still doesn't make sense. That's a good time to go to the commentaries for help, and many times you'll find an insight there that will help smooth out the problem. Other times you'll just confirm that everyone else is as flummoxed as you about this particular problem, which is helpful in its own way! The second time commentaries are helpful is when you've come to a point where you think you have a good grasp of the text's meaning and you're getting ready to move toward a sermon outline. At that point we both find that it's a good idea to read a commentary or two just to make sure we haven't missed anything. So, for example, is there an Old Testament allusion you didn't notice or a logical connection between sentences you missed? Is there some important background information you weren't aware of, or have you been misunderstanding something? A good commentary on a text can help you discern all that before you move on to developing a sermon outline.
Move toward an Outline
Before you start thinking hard about application, you'll probably want to move toward an outline of the sermon. That will give you something to hang your application on, and it will also help you focus your application on the main points of the text.
The outline is a hugely important part of the sermon. It's what gives your congregation "handles" to grasp as you're preaching, and it helps them track along with you as you speak. Without a solid, clear outline, a sermon can easily become just a smooth, undifferentiated mass of words; and your listeners, not having any handles to hold to, will tune out until you're done. Not only that, but a good outline can serve to focus a sermon like a laser. Every point builds on and reinforces the last, until the whole sermon comes together powerfully to drive home one or two simple points. If you've done your outline well, your congregation should be able to write down only your main points and come away with a really good idea of what your sermon was about.
The Exegetical Outline
Both of us work our way toward a preaching outline through an exegetical outline. In other words, the first step of our outlining process is to put down on paper, in the plainest possible language, the main ideas of our text in the order they appear. That doesn't have to be complicated. Sometimes it's just a few sentences that give a snapshot of what's going on in the text. Here, for example, is the exegetical outline I (Greg) used recently in preparing a sermon on Matthew 12:1–21.
Jesus Lord of the Sabbath
Man with Withered Hand
Fulfillment of Isaiah Passage
You can see that in terms of wordage there's not much to it—even embarrassingly little, perhaps! Yes, there's a boatload of study behind those few phrases, and that outline obviously doesn't say everything I wound up preaching in nearly an hour-long sermon. But the point of that exercise wasn't to put every detail on paper. It was simply to give me a good snapshot of the main exegetical thrust of the passage. Your exegetical outlines may be more detailed than that; they may be less detailed. Just remember that your goal in an exegetical outline is not necessarily to include everything. It's to capture the shape and point and thrust of the text you're about to preach so you can move toward a preaching outline.
The Preaching Outline
Once you've nailed down an exegetical outline, you should move next toward a preaching outline—the actual points you'll articulate to your congregation when you preach the sermon. Sometimes you'll follow the progression of your exegetical outline almost exactly. Sometimes you'll deviate from it for one reason or another. Either way, now you are moving from a bare statement of what the text says and means to a more pointed "firing" of that text into the hearts and minds of your congregation.
One practice I (Greg) and my congregation have found particularly helpful is for me to work toward crafting a single sentence or two that will serve as the Main Idea for the sermon. Of course, because I intend to preach expositionally, that Main Idea of my sermon should also be what I think is the Main Idea of the text. Sometimes it's a statement and other times a question. But the purpose of it is really twofold. For one thing, it helps me in my preparation by focusing my thoughts and leading me to make sure I'm not putting anything extraneous in the sermon. Moreover, it gives my congregation one sentence that will call back to their minds the main thing we considered together. In a similar way, Mark will often conclude his pastoral prayer, which he prays just before the sermon, by praying through the points of the sermon (though he doesn't tell the congregation that's what he's doing). That, too, helps to orient people's minds to what is about to be preached from God's Word.
Ideally, a Main Idea sentence will have some rhetorical punch to it, and not be something flat and relatively boring. So, for example, instead of saying something like, "Jesus says spiritual life comes through Him, rather than through the Jewish ritual law," I'll present the Main Idea to my congregation like this: "Religion will kill your spiritual life. If you want spiritual life, you get it through Jesus, not through religion—and those two things are NOT the same!" Better, isn't it? Here's a list of some of the Main Ideas I used through my most recent series in Matthew:
Some of those are better than others, but they all achieve the goal of stating the text in a provocative way, arresting the congregation's attention, and giving them something that will help them recall the main point of the sermon and therefore (if I've preached well) of the text.
Whether you use a Main Idea sentence or not, the next step is to decide on the points you'll use in the sermon itself. Sometimes those points will line up perfectly with your exegetical outline; sometimes they won't. Sometimes the best way to present a text to your congregation, for example, will be straight through the logical progression of the text. Other times the author weaves a number of themes and points together, bringing them up over and over again, and the best way to preach that text will be for your preaching outline to be more thematic. Either way, there are a few things that will help make your outlines more attention grabbing and memorable to your congregation.
I (Greg) had a preaching class in seminary in which the professor said that we should always try to make the points of our sermon "applicational." What he meant was that the points of our sermons should be in the form of imperatives because that will most engage the minds of our hearers and help them realize the relevance to their lives of what we're saying. That's probably good advice sometimes. There are plenty of times, though, when I wind up thinking that imperatives actually don't communicate the text in the best way, and it's better to use strong indicatives. The principle behind what my professor said, though, is certainly right: even if you don't use imperatives every time, you should strive to make the points of your sermon arresting in their own right. Imagine a sermon on Matthew 3:1–4:11, for example. You could certainly title the points of your sermon something like
And that would be accurate. But you could also take it a step further and title them something more like
That's the same text under consideration, of course, but those points are more interesting and more arresting. They also point your listener to the main point of each of those stories instead of just identifying them, and they push the listener into thinking a little bit, too. "What? What does God demand? Who is Jesus? And what does He win? Tell me!!" Your goal ought to be to arrest attention from the moment you say the points. Create interest, raise questions, increase tension. Make people sit forward in their seats, anticipating how you're going to resolve all this.
Of course you have to be careful with the outline. You want it to be arresting, but in the process of getting there, you don't want to lose sight of the meaning of the text. Sometimes a dead-set determination to deal deftly in a dexterous display of alliteration will distract from the divine document more than it will duly declare its drift. Sophistication, style, and symmetry are swell in a series of sermon subjects (OK, OK—enough!), but the trouble is that sometimes your desire to find a word that starts with P will overshadow your desire to find a word that communicates the meaning of the text. The same is true of parallelism in sermon points. Sometimes it works. I think the "what, who, what" progression is pretty good in the example above. But sometimes it doesn't work at all. You just can't make it fit. When that happens, it's much better to go with what the text says and means than force the text into an outline that sounds good but is fifteen degrees off the actual meaning.
It's always a great feeling to get to the point of having a preaching outline. After you've done the work of exegesis, after you've understood the text and worked out the problems, and after you've brought it all down to a preachable outline, a huge part of the work of sermon preparation is done. Now you get to move on to the next huge part—application.
Meditate on Application
The first thing we should say about application is that you cannot do it until you have understood the text accurately. If you do, your sermon will leave people scratching their heads because the application will be off.
I (Greg) was driving to Chicago some time ago and caught a sermon by a radio preacher on my way. He was preaching on Isaac's blessing of Jacob and Esau in Genesis, and the point he was trying to draw from it—with great passion—was that parents should be effusive in their affection and praise for their children. One of his points was that parents should speak kind words to their children, just like Isaac did for his boys. Another was that it is important for parents to physically touch their children frequently, perhaps especially when they are speaking kind words to them.
Now all that may well be true. I try to do both those things for all my kids. But let's just be straight—that is not the point Genesis is trying to get across. Isaac's blessing has far more to do with God's promises to Israel and the chosen line from which the Messiah would come than it does any parenting principles. And sure enough, there was one thing in the text that threw this particular preacher off his stride, one thing he couldn't quite fit into his understanding of the text. It was that Isaac waited so long to speak like that to his sons. He should have done it earlier, the preacher said, when they were still children. Well, yes. Perhaps. And perhaps that oddity should have alerted him to the possibility that maybe parenting principles weren't really the main issue here.
I hope you can see my point. Trying to apply a text you haven't understood well is like hitting a nail at an angle. You can put all the raw strength behind it that you want, but it's never going to go in clean. You're going to leave people wondering where it came from.
Once you have the meaning of the text nailed, it's time to move on to application. It's time to meditate on why this text matters to your congregation, how it challenges their thinking and their behavior, how it undermines false gods they're clinging to, how it sets their eyes on Jesus and teaches them to rely on Him in the gritty details of their lives, how it uncovers and indicts sin and unbelief in their lives. If we really do preach for effect as we considered earlier, then application is a crucial part of our preaching. It is our job as proclaimers of God's Word not just to tell them what the truth is but also to tell them why the truth matters to them, and what the truth demands from them. You, as a preacher, do not just inform. You "reprove, rebuke, and exhort, with complete patience and teaching" (2 Tim. 4:2). In short, you apply.
Each of us has different ways of meditating on how a text applies to our churches. I (Mark) use a tool I call an "Application Grid." Once I've settled on a sermon outline, I create a grid with those points down the side and a number of categories across the top. Those categories ask various questions:
Then I spend a good deal of time thinking, praying, and filling in the grid. Not every point of application I consider will make it into the sermon, but many of them do; and this grid helps me not to fall into the rut of preaching only to the individual Christian, which, in my experience of listening to preaching, is where most preachers tend. It forces me to think about how my text applies to other groups of people as well, not least to my particular local church.
I've also found that talking through application with a member of my church is helpful in stimulating thought. I've made it a practice over the last fifteen years to take a few members of my church to lunch on Saturdays and think with them through the application grid. Those are sweet times of fellowship, and they're also enormously productive. More times than I can count, the men with whom I'm having lunch have asked a question I hadn't considered, made a point I'd overlooked, or had a pastoral insight that hadn't occurred to me. Then, later, after I've written the sermon, I'll read it to a few friends in my study on Saturday night, and often there are women present who give me some of the best comments I receive.
My (Greg's) process of thinking about application is a bit different. I don't use an Application Grid, at least not one that's on paper. My way of thinking about application is to take a long "sermon walk." Most Saturday afternoons I go for a two-, even three-hour walk around my neighborhood if the weather's good or at the local mall when it's not. I take my iPhone with a Bible on it, a notebook with my outline written in it, and a pen. I walk, think, and pray. I've always hoped somebody would stop me and ask kindly, "What are you doing, young man? Oh? Preparing a sermon? Tell me about it." That's never happened, but I did have a guy once run out of his house yelling at me and demanding to know why I wrote his license plate number down. I tried to explain, but he seemed to be more relieved and slightly embarrassed than interested.
On that sermon walk, I think through the text I'm preaching and ask similar questions to the ones we mentioned above on the application grid. What is the burden of this text? Why does it matter for my church? What keeps people from thinking this way? What are the obstacles to doing this or to living this way? Why does this text or doctrine or truth matter for Robert? There's an important point: I almost always try to think of specific individuals in my congregation and think about why this text should matter to those people in particular. That practice helps remind me that I'm not preaching to the Internet but to a specific congregation, and it helps me, I think, to make applications that are more personal and trenchant. In the two or three hours I'm walking, I probably preach the sermon to myself in a hundred different ways. I chase rabbits in my head, I walk around in my own mind and heart, and I try to uncover my own motivations and fears and sins that are challenged by the text. And all the while I make notes in my notebook. By the time that walk is done, I have a good idea of where I want to go with the sermon, and I'm ready to put it on paper.
One last point on application for now: we encourage you to work toward having multiple "levels" of application in your sermons. Some applications will be long and involved because they will tap into the main thrust of the text and be among the one, two, or three main points you're hoping to get across in the sermon. Other times your applications will be shorter, one- or two-sentence exhortations that you fire into your listeners' hearts. Maybe it's because those applications are coming from a relatively peripheral point in the text; maybe it's because you have other applications to give. Either way, don't be afraid of those. Sometimes the most commented-on points in our sermons are those one-off, sentence-long applications.
Preach the Gospel
One crucial thing you should keep in mind through all your preparation—from understanding to outlining to meditating on application—is that your task as a preacher is ultimately and fundamentally to preach God's Word. "Yes, yes, you say, of course! That's what you've been saying through this whole book!" True, but we're making a more specific point here, and it is that one of our convictions as Christians is that every text of the Bible points finally and ultimately to Jesus Christ and His gospel. Every Old Testament text, as Jesus told us time and again, points forward to Him, and every New Testament text points either backward or forward to Him. Jesus is the beginning, the center, and the end of every text in the Bible.
Because of that, your sermons should never be forty-five-minute morality lessons or best practices for living a better life. They should drive forward to the good news that King Jesus saves sinners through His life, death, and resurrection from the grave. In fact, we think that in every sermon you preach, you should include at some point a clear and concise presentation of the gospel. Tell people how they may be saved! I never want someone to come to my church, not just for a length of time but even for one single service, and be able to say they didn't hear the gospel of Jesus Christ. Brothers, you are not Jewish rabbis. You are not called to give sermons that merely tell people how to live rightly or better. Is teaching people to live rightly part of preaching the whole counsel of God? Yes, absolutely, depending on the text! Is that ever all there is to it? Absolutely not! One way or another, every text in the Bible points to Jesus, and you should follow where it points.
That doesn't mean you should simply tack the gospel onto the end of your sermons. We've all heard that—a sermon on marriage that really says nothing about Jesus until the last two minutes of the sermon, and then the gospel is just sort of duct-taped onto the end. That's not what we mean. What we mean is that the gospel should flow naturally and forcefully out of the themes and stories that make up the text you're preaching. It's vitally important that you let every text speak for itself; if you're preaching from the Old Testament, present that text with its own voice, and let it speak to your congregation with all its original force. But you also want to let those texts speak with their full voices, and that includes letting them say what they want to say about Jesus! In other words, you should not just preach each text in its immediate context, but you should also preach it in its context with reference to the entire Bible.
But how do you do that without it sounding contrived and forced? It has helped me in my preaching to know there are two different roads to the gospel from every text in the Bible, roads we should be on the lookout for in every sermon we prepare. One is the road of biblical theology, and the other is the road of systematic theology. Let me give you an example from a most unlikely text: I (Greg) recently preached a series on the book of Judges, easily one of the darkest, most hopeless books in the Old Testament, and probably further away from the gospel, salvation-historically, than any other book. I mean, how, for example, do you get to Jesus in a sermon about Ehud? When the text you're preaching is about a tricky, left-handed sneak who stabs a fat king and gets away because the guards are deterred by the smell, how exactly do you turn from that to the glories of Jesus? Or how do you do it from the story of the Levite and his concubine or the civil war in Israel? It's not obvious sometimes, but it can and should be done. And it can be done by following the roads of biblical theology and systematic theology.
Biblical theology has to do with the whole grand story line of the Bible. From Genesis to Revelation, the Bible tells a story, and from any given text you can always step into that narrative river and be swept pretty quickly toward the cross. Even in Judges you can get to Jesus easily by seeing how the book fits into the whole story. After all, the main point of Judges is the refrain, "In those days there was no king in Israel" (Judg. 17:6; 18:1; 19:1, for example). The book is an apologetic for godly kingship, even kingship rooted in the tribe of Judah. Follow that unfolding story line, and you quickly find yourself at King David and ultimately at King Jesus, "the Lion of the tribe of Judah, the Root of David" (Rev. 5:5).
Of course, you can't make that the main point of every sermon in the series. Even if you mention that story line in every sermon to be sure your people understand it, sometimes you need another road to the gospel. That's where systematic theology comes in. Throughout the Bible, there are certain themes that are easy to find. Sin, grace, sacrifice, and salvation, just to name a few, underlie every story in the Bible; and all of those themes find their highest expression in Jesus' death and resurrection. So when you're preaching from the Old Testament, find one or more of those themes and then turn strongly to the cross. In Judges, for example, human sin, broken covenant, God's grace and love, God's wrath, and His deliverance of His sinful people are all strong theological themes, and any one of them is a great way to turn your listeners' minds to Jesus and His work of salvation for His people.
It's easy to preach the Bible, especially the Old Testament, as if it were a book of fables—a series of stories that do little more than instruct us morally. But if we believe Jesus, we know those stories are doing much more than that; they are pointing us to Him. So whether we do it by following the story line or pointing out the themes, our job is to show our congregations how to see Jesus, even from the story of Ehud.
Write It Down
Once you have a good grasp of the text, the applications that flow from it, and the way it points to the gospel of Jesus, all that's left is to write it down. That's always the hard part for both of us, but it's also the crucible in which language takes shape. Mark Twain once said that "the difference between the almost-right word and the right word is really a large matter—it's the difference between lightning and the lightning bug." He's right, and the writing of the sermon is where the hard work of getting the right words is done.
The English language is a remarkable tool for communicating. There are so many words, each with its own shades of meaning that can change the whole tenor of a sentence or even make it strike the heart in a wholly unexpected way. Is there a difference, for example, between warning your congregation that they might fall away from the faith and warning them that they are in danger of drifting away? Perhaps not much, but the latter carries a connotation of neglect resulting in slow, almost imperceptible loss. It's not sudden like a fall, and if you're not careful, you can drift far away before you realize it's happening.
Be careful about the words you use. Work on them. Figure out precisely what you want to say and say it precisely. It's hard to do that on the fly while you're in the pulpit. Much better to do it on paper, beforehand, when you can try one word or way of putting an idea, reject it, and then try another. Your preaching will benefit from that discipline, and so will your congregation.
