Good Goals vs. Bad Goals: Five Real Examples From Churches

I love setting goals.

Always have. I've got annual goals for my family, quarterly goals for our company, and a sticky note on my monitor that I look at most mornings. When I was a pastor, I set goals for our church and helped every staff member set goals for their ministry.

So when I tell you that most church goals don't work, you should know I'm not against goal setting. I'm against the version of goal setting that takes up an entire planning retreat and then gets forgotten by March.

Here's what I keep noticing.

Most church goals look fine on paper. The sentences are coherent. The priorities are reasonable. A pastor reading the list at a staff meeting would feel good about saying the words out loud. And almost none of those goals actually drive the work between January and December.

The reason is almost always the same. The goals are missing pieces.

What Makes a Goal a Goal

Before we get to the examples, let's get clear on what we're aiming for.

A goal is a commitment that shapes how your staff spends their time between today and a deadline. If it doesn't do that, it's something else. A wish, maybe. A priority. A direction. Those are fine. They are just not goals.

A real goal has five pieces.

• A starting number. Where you are right now.
• A target number. Where you need to be.
• A deadline. A real date. Not "this year." Not "by summer."
• A reason. What gets better when you hit it.
• One owner. A single name responsible for moving it forward.

At Alignify, we use a formula that holds all five together. From X to Y by When and Why.

That's the whole formula. We've covered the full system in the Goal Setting Guide for Churches, but the fastest way to internalize it isn't to read about it. It's to study broken goals and see what's missing.

So let's do that.

What follows are five goals pulled from real church planning documents. The goals are exactly as they were written down. For each one, I'll tell you what I'd say if I were sitting at the table when it got written. Then I'll show you the rewrite.

Goal #1: "Finalize the discipleship pathway."

I love this one because it sounds so reasonable. Verb, noun, presumably an outcome. A pastor reading it would nod along.

Here's the problem.

Ask three staff members what "finalized" means and you'll get three answers.

• The discipleship pastor thinks it means written down somewhere on the shared drive.
• The kids pastor thinks it means integrated into the children's ministry curriculum.
• The connections director thinks it shows up in the first-time guest email sequence.

I've been in that meeting. I've written that goal. And six months later I've watched the team realize at a staff retreat that we couldn't agree on whether the pathway was actually finalized, because we never defined what "done" looked like.

The rewrite: Publish the discipleship pathway by August 31 with four named stages, a one-page visual, and at least one next step defined per stage, so any staff member can answer "what should I do next?" for any member in under 10 seconds.

Look at what changed.

There's a real deadline. There are specific outputs. There's a test that tells you whether the work actually worked. When August 31 comes around, any staff member can pull up the one-page visual, get asked a question by a real person, and see in real time whether the goal is done.

That's a great example of a great goal.

Goal #2: "Consulting about the 200 growth barrier."

This is a note to self masquerading as a goal.

I do this too. I write something on my list that's really just a thought I want to come back to, but I put it in the goals column because it feels too important to lose.

"Consulting about the 200 growth barrier" could mean almost anything.

• Reading a book by a church-growth consultant.
• Listening to a Carey Nieuwhof episode.
• Asking a friend who pastors a 400-person church to grab coffee.
• Hiring an actual firm to come in and do an analysis.

There's no decision point and no output, which means the goal can stay "in progress" forever without ever actually moving. If you put this on a weekly check-in agenda, the owner will say "still thinking about it" every single week, and they won't be lying.

The rewrite: Engage a church growth consultant by April 30 and complete a 90-day diagnostic on the 200 attendance barrier, so we have a written plan with three specific changes to implement by the end of Q3.

Now there's a decision (hire someone), a scope (90-day diagnostic), and a deliverable (a written plan with three changes). The pastor knows what week the work starts. The team knows what they'll be looking at in Q3.

What's interesting is that the original goal and the rewrite are pointed at the same priority. The pastor wasn't wrong about what mattered. He just hadn't written it down in a way the team could act on.

Goal #3: "Scale team alignment through monthly manager check-ins."

This is what happens when church leaders read too many business books.

The language sounds strategic. "Scale alignment." "Manager check-ins." A board member would feel like they had heard a real plan.

What this goal actually describes is a meeting format, not an outcome. Even if every manager runs every monthly check-in for the entire year and not a single one gets skipped, the church won't know whether team alignment got better. They'll only know that the meetings happened.

I've watched churches mistake activity for outcome more times than I can count. It's one of the most expensive mistakes in ministry leadership, because you can put in a full year of effort on the activity and have nothing to show for it at the end.

Activity is not outcome. Effort is not impact.

The rewrite: Roll out monthly 1:1s between every manager and direct report by April 15 using a shared agenda covering wins, blockers, and goal progress, so every team member receives consistent coaching and we can measure alignment in the quarterly staff survey.

The 1:1s are still there. The mechanism didn't change. What changed is the goal now measures whether the mechanism is producing alignment. The staff survey gives you a signal at the end of the quarter. Without that, you're running meetings and hoping.

Goal #4: "Equip 25 of our members to share their faith."

The number is the trap on this one.

"25" feels specific. The team feels like they wrote a measurable goal. By December, they'll know whether they hit it.

But what does "equipped" mean?

• A handout passed out at a Sunday service?
• A sermon series on evangelism?
• A six-week class with worksheets?
• A semester-long training with role-play and accountability partners?

All four produce a count of 25 "equipped" members. All four produce wildly different outcomes for the church, for the members, and for the people they're trying to reach.

When I was pastoring, we used to count classes finished without measuring whether anything changed because of them. It's one of the easier traps to fall into, because counting feels like accountability even when nothing actually got accomplished.

The rewrite: Graduate 25 members through a six-week evangelism course by November 15, with each participant completing three logged real-world conversations, so we are measuring application rather than attendance.

The rewrite changes "equipped" into a specific completion event and adds a behavioral test. You're no longer measuring whether 25 people sat through something. You're measuring whether 25 people did something different because of what they sat through.

That's the goal you actually wanted in the first place.

Goal #5: "Get staff and leaders aligned and organized."

This is the most common first-time leadership goal I see.

Two abstract verbs. No outcome. No timeline. Almost every pastor I've worked with has written something like this at some point. I have written it.

The problem with "aligned and organized" is that those are conditions, not outcomes. They have no finish line. You can always be more aligned. You can always be more organized.

A goal you can never finish is not a goal. It's an aspiration.

The rewrite: Implement a weekly staff meeting, a quarterly leader retreat, and a single project tracker used by every staff member by May 31, so I can see in under five minutes what every team is working on.

The rewrite turns the conditions into structures you can verify.

• The weekly meeting is happening or it isn't.
• The retreat is on the calendar or it isn't.
• Every staff member is using the project tracker or they aren't.

And the test at the end ("under five minutes") gives you a way to know whether the structures are doing the work they were supposed to do.

The Pattern Across All Five

Read those five back to back and the same failures keep showing up.

• Activity treated as outcome
• Vague verbs that mean whatever the reader wants them to mean
• Missing numbers, missing deadlines, or both
• No reason that tells the team why this one matters now

Every rewrite puts those pieces back in. From X. To Y. By When. And Why. Five pieces, every time.

One Last Thing

Here's what I want you to take from this.

The pastors who wrote these original goals were not lazy or strategically impaired. They were trying. They were doing the work. They got to the part of the planning retreat where someone said, "Okay, what are our goals for the year?" and they wrote down the priorities that came to mind.

That part was right.

What got missed was the discipline of turning those priorities into commitments their team could act on. That's not a character flaw. It's a skill, and it's one most pastors never got trained on.

The good news is you can learn it. The formula is short enough to memorize. And the difference it makes in your team's energy, focus, and follow-through is significant.

So here's what I want you to do this week.

Pull out your most recent planning document. Find the goal that bothers you most — the one you wrote and haven't looked at since. Run it through the formula. From X to Y by When and Why. Assign one owner.

Then do the next one.

A clear goal is not the whole job. But it is the place where the work starts.

Alignify was built to help church staff teams write goals like the rewrites above, then keep them alive through weekly check-ins and focused meetings. If you want to see how it works for a team like yours, book a demo and I'll walk you through it personally.