Category 066 skills
Systems & Strategy
The skills that change the job, not just the copy: a clear picture of what you actually own, a shared way to decide what's urgent, a working system for taking in requests, and a week you plan instead of just survive.
scope-mapper
Scope Mapper
Ch. 1 · Own / Influence / Support✓
Turns “I guess I'm in charge of everything” into a clear, written list of what you actually own, plus the exact words to say when you talk to leadership about it.
Input — Emily’s brain-dump (12 items, excerpt)
Website · weekly email · socials · Sunday slides · kids ministry flyers (“every Thursday, somehow”) · pastor’s letters (“clean it up a bit”) · new-ministry launch assets · event photography · bulletin · ProPresenter uploads…
Output — labeled map (excerpt) + scripts
| Item | Domain | Label |
| Weekly email, website, socials | Digital Channels | Own |
| Pastor’s letters | Messaging | Influence — he owns voice & content; you bring clarity |
| Kids ministry flyers | Visual Identity | Support — template + review, not production |
| Sunday slides | Sunday Experience | Own (content) / Influence (service flow, with worship) |
Mismatches flagged: 1) Thursday flyers are being treated as Own — four hours/week that a template system returns to you. 2) New-ministry launches arrive as Support-priced requests but are Create-scale work — needs the lead-time conversation.
Conversation opener (word-for-word from the book): “Can we spend thirty minutes mapping what communications actually owns versus what we help with? I think we’ve got some work to do.”
What to noticeThe output treats every boundary as a way to serve well, not defend turf, and it schedules its own 90-day check-in, since the labels will need updating.
level-sorter
Level Sorter
Ch. 3 · The three levels✓
“What level is this?”: the five-question sort that turns visibility debates into shared decisions, plus the coaching language.
Input — three live requests
1) Easter services promotion. 2) Women’s mentoring program launch. 3) Tech team training huddle (“can we get it announced Sunday?”).
Output — sorted, with reasoning
Easter → Level 1 Churchwide. For basically everyone, including the community. Full channel support; the loudest channels serve the broadest audience.
Women’s mentoring → Level 2 People Group. Large demographic, real momentum — featured email placement, dedicated social, targeted follow-up. Not stage-by-default: “this is about fit, not importance.”
Tech huddle → Level 3 Ministry. Q4 settles it: the audience is already reachable (the team’s own channel). Coaching reply included: “Love that you’re investing in the team — a Sunday announcement would mostly reach people it isn’t for. Let’s send it straight to your team roster and I’ll give you a template that takes five minutes.”
What to noticeEach answer shows its work, and a “no” always shows up as a better plan instead. (The skill also generated a second output: a one-page guide to the three levels with Grace-specific examples, tested and working.)
request-system-builder
Request System Builder
Ch. 5–7 · The Saturday Morning system✓
Takes the book’s Saturday Morning story and turns it into a real system you can use: an intake form, timelines, a simple way to score requests, ready-to-send replies, and a guide explaining what the team can realistically handle, all in one run.
Input — the situation
“Solo coordinator, ~600 people. Requests arrive by text, email, and hallway conversation after second service. No form, no stated lead times. I need a real intake system I can roll out at staff meeting.”
Output — the system (excerpt)
Form (9 fields): ministry & contact · what’s happening, plainly · who it’s for, really · the one next step · event date / date needed · Communication Level (best guess is fine) · support type — Create / Collaborate / Consult (“not sure? leave blank & we’ll figure it out together”) · content status · anything already designed.
Lead times, printed on the form: Create 6–8 weeks · Collaborate 3–4 weeks · Consult days.
Response template — the not-yet (1 of 4): “I love this, and I want it to land well — which it won’t on this week’s calendar next to the series launch. Here’s what I can offer: featured email slot on the 22nd and the social template today. Can we aim the bigger push there?”
Full output also includes a simple 5-point scoring guide, ready-made replies for “yes,” “yes, with changes,” and “not this time,” and a one-page guide for ministry partners on what to expect.
What to noticeBuilt to fit a team of one: the skill kept the system simple on purpose, since a complicated system nobody keeps up with is worse than no system at all, and every reply sounds warm enough to send as-is.
request-triage
Request Triage
Ch. 3, 4, 7 · The Monday pass✓
The weekly workhorse: everything else in this pack, run together against a real Monday inbox: sorting by level and category, checking timelines, deciding what's urgent, and drafting the replies.
Input — Monday’s five requests, exactly as they came in
- “New ministry launch in 6 days — need logo, landing page, 3 emails, social. Not a big deal!”
- “Flyer for kids parent meeting next week, nothing fancy”
- “Sermon series assets — launches in 7 weeks”
- “Announcement for Marge H.’s memorial service”
- “Social post for men’s breakfast?”
Output — triage table + replies (excerpt)
| Request | Level / Category | Verdict |
| Ministry launch, 6 days | L2 / Create-scale | Timeline fails — honest-conversation reply drafted |
| Kids flyer | L3 / Consult | Template + 10-min review; this week |
| Series assets | L1 / Create | Right runway — schedule kickoff now |
| Memorial service | Set aside for a person to handle | “This one needs a conversation, not a template” |
| Men’s breakfast post | L2 / Consult | Template today |
Drafted reply (the 6-day launch): “I’m genuinely excited about this ministry — and I want its first impression to be great, which six days can’t deliver at full scale. Here’s what six days can do well: a clean announcement, an email to the people most likely to care, and a simple sign-up. Then let’s plan the full launch package for [date] — logo, landing page, the works. Can we grab 20 minutes?”
Pattern noticed: “Two of five requests arrived under lead time — the capacity guide from request-system-builder should go out at this month’s staff meeting.”
What to noticeHandled correctly The memorial announcement wasn’t drafted at all: it was sent straight to a real conversation with pastoral leadership instead, exactly what the pack promises to do with sensitive moments like this.
weekly-comms-planner
Weekly Comms Planner
Ch. 2–4 · The week, planned✓Continues test 22
Turns the sorted-out week into a day-by-day plan built around the one big churchwide focus: a week you run instead of a week that just happens to you.
Input — this week
Approved items from Monday’s triage · churchwide focus: Everyday Faith launch Sunday · email sends Wednesday 10 AM · capacity: ~12 production hours.
Output — the weekly plan (excerpt)
| Day | Email | Social | Stage / screens |
| Tue | — | Takeaway: series teaser | slides finalized |
| Wed | Newsletter (series on top) | — | — |
| Fri | — | Friday Story: group member | — |
| Sun | — | launch-day photo post | 2 announcements · 3 slides |
Production checklist: series slides (done) · kids flyer template pass (Tue, 30 min) · breakfast social template (Tue, 15 min) · series kickoff meeting booked (Thu).
Flags: Story slot preserved (Friday) — the week isn’t all promotion. Youth car wash bumped to next week’s email: “nothing this week should compete with the launch.”
What to noticeOne churchwide focus, protected: the plan pushed a good idea to next week rather than let it compete with the main thing, and it still kept a slot for a real story. This is the book’s advice to protect one focus per week, applied to an actual week.
ai-policy-drafter
AI Policy Drafter
Ch. 5 · A Theology of the Tool✓
Drafts the AI guidelines the book assigns as homework: built on four simple questions about using AI responsibly, sized to fit how cautious or open the church wants to be.
Input — the situation
“Church of 600. Elder board is cautious but open. Staff and two volunteers already use Claude and Canva AI informally. I need a one-pager the elders can adopt — practical, not a theology paper.”
Output — the policy (excerpt)
Preamble: “Like the printing press and the livestream before it, AI expands what’s possible for good and for harm. Our response is neither blanket rejection nor uncritical embrace, but wise stewardship. These guidelines are how we practice it.”
The four rules, in plain terms: 1) Mission — okay to use for drafting, editing, brainstorming, summarizing, and internal systems. 2) Dignity — no personal, pastoral, or identifiable information about anyone in the congregation ever goes into an AI tool. 3) Stewardship — AI should free up time for the work only a person can do, not replace it. 4) Verification — a human reads and approves every AI draft before it goes out. The tool drafts; we decide.
Always human: pastoral care · decisions about people · anything presented as someone’s own words · crisis and grief communication. Never: manufactured testimonials · impersonated voices · AI-generated content passed off as human where it matters.
Delivered with a three-bullet staff-meeting summary and an annual review cadence. Flagged for elder review before adoption — “the draft informs their judgment; it doesn’t replace it.”
What to noticeThe policy the pack ships with is the same ethic the pack runs on: the “always human” list is why there are no crisis or pastoral-messaging skills in this product at all.