Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/salvagh0/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home4/salvagh0/public_html/wp-includes/script-loader.php on line 333

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/salvagh0/public_html/wp-includes/class-wp.php on line 173
pastoral discoveries – Salvaged Faith

pastoral discoveries

So – my last post kind of cryptically talked about growing and stretching and being challenged and stressed. As I’m wading around in all of that still, I thought it would be good to talk about some of the things that Im learning about what it means to be a pastor in the midst of it.

1) It’s okay to not answer your phone. At our Healthy Ministerial Relations workshop we talked about boundaries and many people shared that they turn their phone off on their sabbath days. I wouldn’t do that simply because my cell phone is also my personal phone – but I did remember that advice when I recieved five phone calls from church folk on Sunday afternoon. I didn’t have my pastor hat on then – I was being a sister and was helping paint my brother-in-laws new house. So I let the calls go to voice mail. And then I listened to see if they were important. And then I let it wait. When I started my day on Monday – I called each one of them back. And while initially I felt kind of guilty about doing so, it was a reminder that I don’t have to be “on” 24-7.

2) Why do pledge drives/stewardship campaigns have to be in November? With how busy our lives are right now it just seems like one more thing on top of every other thing. I think for the most part we like the connection of offering and thanksgiving and consecration all going together, but there is no time left. We are now talking about pushing all of that back to January. We don’t use our pledges to make our budget anyways because we don’t have enough history with them. What difference would it make if as a congregation we commit to support the church at the end of January instead of the end of November? Plus – it gives us the opportunity to really push our small group study and having a “new year, new finances” kind of focus might work out really well!

3) Rookie mistake – don’t talk to reporters. And especially don’t talk to people when you really don’t have time. As I was finishing up the funeral orders – about 15 minutes before the family was scheduled to arrive – I got a phone call that I really didn’t have time to answer. I told him I didn’t have time to talk, and was trying to show that I had no information that could help him, but in my rush to get on with my business, and because I had no idea what he was talking about I said something that was taken out of context in the article. Note to everyone else: just say no comment. (see also #1 – it’s okay not to answer the phone and screen the calls through voicemail)

4) Your support network keeps you sane… or at least helps you let off steam. Without my best friends and facebook, without my brothers/sisters (in-laws too), and without being honest and vulnerable with my congregation, some of this week might have been unbearable. But because we talked (and typed) and prayed and hugged and watched football, we got through it.

5) You have to keep the joys and thanksgivings at the front. I carried around the pictures of my new nephew and showed him to lots of people this week – it gave me a chance to celebrate in the midst of the stress.

6) Sometimes you can get away with swearing during a sermon. At the funeral this week, the family didn’t want to get up and speak, but had some things that they wanted me to include. And so I said them – and it cut to the heart of who this guy was and everyone understood and I didn’t get any snide looks from anyone who thought it was inappropriate.

7) Once you use powerpoint in a sermon, you may never go back.  I preached on the three major atonement theories in worship on Sunday and used visuals/bullet points.  I had so many positive comments that now I’m wondering how we can adapt the technology in our worship space to make it easier to continue doing so.

No Comments

Post a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.