Staff asked to develop strategy without clear constraints produce work that gets shelved. Here's how to set boundaries that enable real progress.
You ask your team to develop a ministry philosophy or departmental strategy. Months pass. They deliver work. You review it and realize it doesn't fit. It gets filed away. Your team member feels frustrated. You feel like the time was wasted. This cycle repeats.
What's actually happening is this: you've asked staff to build something without telling them where the walls are. They're guessing at your vision while you're guessing at theirs. The work fails not because they're incapable, but because the sandbox was never defined.
This is one of the most common failures I see in strategic planning conversations with church leaders. The fix is simple, but it requires you to do your work first.
Here's where language breaks down: when you say "develop a philosophy," different people hear different things.
Organizational philosophy is what the whole church believes and practices. It's the non-negotiables. It's the water everyone swims in. When you say "our discipleship philosophy is formation through small groups," that's a church-wide conviction that shapes everything.
Departmental philosophy is how a specific team lives out that larger conviction. When your small groups leader develops a groups philosophy, they're not inventing something new. They're translating the church philosophy into their lane.
I worked with an executive pastor who asked his children's ministry director to "develop a philosophy for how we approach kids' spiritual formation." She spent weeks on it. When she presented it, the lead pastor said, "This doesn't match what we're doing in the rest of the church." The director had created something original when she was supposed to be applying something existing.
The problem wasn't her work. The problem was the assignment. No one had said, "Here's what the church believes about spiritual formation. Now, how do you live that out in kids' ministry?"
The key is clarity about what sits at the SLT level and what sits at the staff level. SLT owns organizational philosophy and vision. Staff applies it within their domain.
When staff don't know what the leadership team has already decided, they either guess or start from scratch. Both paths lead to rework.
No spam. Unsubscribe anytime.
I coached a pastor through this exact situation. His worship leader and small groups director were both asked to "develop strategies for engagement." The worship leader created something that required significant budget changes. The small groups director created something that contradicted the discipleship approach the SLT had already committed to.
Neither was wrong. Both were working in a vacuum.
Here's what changed: the SLT spent two hours clarifying three things:
What we've already decided. The leadership team named the non-negotiables. The discipleship approach. The budget constraints. The timeline. The vision direction for the next two years.
What we're asking you to develop. Not "create a strategy from nothing." Instead: "Given these constraints and this direction, what's your plan to execute it?"
What success looks like. Not vague approval. Specific measurables. Alignment with the broader vision. Realistic timelines.
Once staff understood the sandbox, the work accelerated. The strategies they developed fit. They didn't need major revisions. They moved forward.
What most leaders miss is that staff don't need more freedom to think creatively. They need clearer boundaries so their creativity lands in the right place.
This is non-negotiable: constraints and expectations must be documented before staff begin developing strategy.
Not after. Not verbally. In writing.
Why? Because memory is unreliable. Verbal conversations get interpreted differently. When someone spends weeks on work and then hears "that's not what we meant," they're rightfully frustrated.
Here's what I recommend documenting:
One executive pastor I worked with created a one-page brief for each staff member. It took her ninety minutes. It saved her team months of rework and frustration.
The brief included: "Here's the vision direction for your area. Here's what we've already decided. Here's what we need from you. Here's the timeline. Here's how we'll know it's good." Nothing fancy. Just clarity.
Staff came back with work that fit. Not because they were suddenly more competent, but because they knew what they were building toward.
If this is happening in your church, here's the move:
Step 1: Clarify what your SLT owns. Before you ask anyone to develop anything, your leadership team needs to be clear on what you've decided. Vision direction. Core values. Discipleship approach. Budget parameters. Non-negotiables. Write it down.
Step 2: Identify what needs staff input. What strategies, plans, or implementations do you actually need from your team? Be specific. Not "develop a strategy." Instead: "Develop a seasonal plan to execute the small groups vision we've committed to."
Step 3: Create a brief for each assignment. One page. Includes the vision context, the constraints, the specific deliverable, the timeline, and the approval process. Give it to staff before they start.
Step 4: Check in midway. Don't wait until they're done. At the halfway point, review what they're building. Catch misalignment early. Adjust the brief if needed. This prevents the "we spent weeks on this and it doesn't fit" conversation.
Step 5: Approve and communicate. When staff deliver, approve it or give specific feedback. Don't file it away. Use it. Tell the team what you're doing with their work. This builds trust and momentum.
This is not micromanagement. This is clarity. Staff actually prefer it. They know what they're building toward. They can move with confidence.
In my work with church teams, I've seen this shift change everything. Not because the staff got smarter, but because the leaders got clearer about what they actually needed.
When you ask staff to develop strategy without guardrails, you're not saving time. You're spending it twice.
First, staff spend time developing something. Then, you spend time reviewing work that doesn't fit. Then, either they revise it (more time) or it gets shelved (wasted time and discouraged staff).
The cost isn't just hours. It's trust. Staff feel like they did something wrong when really the assignment was unclear. Leaders feel frustrated because the work didn't land. Both sides blame each other.
Clarity breaks that cycle.
Your next move: look at what you're currently asking staff to develop. Is it clear what the sandbox is? Is it documented? If not, spend an hour clarifying it. Write it down. Share it. Then watch what happens.
Your team will move faster. Your work will fit better. And your staff will feel like they're building something that actually matters.
