When you’re preaching, you’re not an island.
You’re connected to the congregation.
You’re connected to those in the wider church whom you’ve read and listened to in preparation.
Importantly, if those present were attending last Sunday, you’re connected to the person who preached the previous week.
So, if you reference the previous speaker, what should you say?
To begin with, it all depends what you thought of the sermon last Sunday?
Did you agree with what they said? Is there a natural connection to what you are currently saying?
Frankly, I think that the majority of the time, you won’t reference who spoke seven days prior. You just won’t need to.
They will have done a perfectly faithful, adequate, job. They used the text well. They shared the message of Jesus. They applied their points so they would impact beyond the few hours on a Sunday morning or evening.
But, what if you have something to add?
While there’s nothing wrong with chipping in to the sermon last week, I’d hope you have enough to say about the passage before you currently to forego the addition.
Furthermore, if you intend to correct something said the week prior (unless it is a simple factual mistake that can be addressed within 30 seconds) then the majority of criticisms are better touched on in person with the preacher, not flaunted at the pulpit without the ability for a response.
Let’s face it, it would be foolish to start an ongoing theological debate cross-crossing a number of weeks.
The pulpit should primarily be for the edification of the congregation, not a place for academic arm-wrestling or chest-puffing.
The best thing you could do, if you’re pointing people back to the previous week, is to say that you agree with what you heard. Declare that you genuinely agreed. Say where you saw God move as a consequence. Share how the message inspired you. Better yet, tell the congregation how this previous message helped shape your current sermon.
These are the best ways, if you have to at all, to share the spotlight with the preacher the week before.
No comments:
Post a Comment