Just posted a new article on PDYMCommunity.com – a reflection on leaving a ministry and transitioning from one church to another. Here’s a clip from Life in Transition:
1. Be honest!
Before we left for our 2nd visit I felt that I needed to be honest with my senior pastor. We had been through a lot together. I respected his leadership and valued his friendship. We had seen God do some amazing things together and the last thing I wanted was for this to come across as a form of betrayal.
As we talked, he let me know that he would be sad to see us go, but he wanted us to be where God wanted us to be. After talking and praying, I left his office feeling that I wasn’t hiding anything from him and I felt like I could really focus on where and how God was leading.
2. Let God take control!
Upon landing from our 2nd visit I learned quickly that the news of our visit to another church had been told to other staff members, including our student staff. This was shocking and very hurtful. It made the hard conversations that I planned even harder.
With each conversation, I caught myself trying to fix things. This was exhausting! I had lost control. No matter what I said, or how many times I tried to explain the situation and the process, people were hurt that they didn’t hear the news from me first. This made our first day back very difficult and I knew the next two days were going to be just as hard as I told all of our volunteers and then finally our students.
Also, noticed a classic Rand post about what he values (and possibly others do, too) in a resume. Worth the read if you’re in a “what’s next?” mode. Here’s an excerpt:
Never include a cover letter. I don’t read them. Recruiters don’t pass them on. Make sure the key points of your cover letter are living in your career objective and your job history.
Embrace honest buzzword compliance. Remember, I’m not the only who is going to read your resume. I’m likely the most qualified to make a call whether you’re a fit for my job, but before your resume gets to me, its going to be passed through a couple of different recruiters and these folks are just as busy as I am.
The lifeblood of the recruiter is the keyword. Java, C++, Objective-C. The more specific relevant keywords and buzzwords you can shove into your resume, there more likely you’re going to make it past the initial cut.
As I said above, I skip the Skills section because most folks already know that recruiters are just searching for specific words when they’re sourcing candidates, so they shove every possible buzzword into their resume. Know this, if you claim to Strong Java Background in your resume, I’m going to be compelled to figure out how strong your skills actually are. Don’t include any keyword or buzzword that you aren’t comfortable talking about at length.
Differentiate, don’t annoy. You’re likely going to start developing your resume from a template. Maybe you’ll use a friend’s resume that you like as a starting point. Excellent. How are you going to make it yours?
JG