무료

수료증 무료 발급 — 2027년 3월 31일까지.

PT702E Church Administration and Leadership

Lecture 10-1: Mission and Vision Are Not the Same Document

카드로 보기 (3분)
목차 53
PT702E Church Administration and Leadership
제 0 장 · Introduction: Administration Is the Body of Ministry, Not Its Shadow
  1. Introduction: Administration Is the Body of Ministry, Not Its Shadow
제 1 장 · Chapter 1: Why Administration — A Theology of Order and Stewardship
  1. Lecture 1-1: Order Is God's Own Concern
  2. Lecture 1-2: The Household Manager — Administration as Stewardship
  3. Lecture 1-3: Administration as a Spiritual Gift
  4. Lecture 1-4: What to Take from Secular Management Theory, and What to Leave
제 2 장 · Chapter 2: Biblical Models of Organization
  1. Lecture 2-1: Jethro's Advice to Moses — Delegation, Capacity, and Choosing Leaders
  2. Lecture 2-2: The Wilderness Camp — Order Around a Theological Center
  3. Lecture 2-3: Temple Staffing and Levitical Organization — Building for the Long Term
  4. Lecture 2-4: Acts 6 — A Complaint, a Diagnosis, and a Change in Role
  5. Lecture 2-5: The Jerusalem Council — Deliberation, Evidence, and a Communicated Decision
제 3 장 · Chapter 3: Church Polity and the Theology of Office
  1. Lecture 3-1: The Office of Elder
  2. Lecture 3-2: The Office of Deacon
  3. Lecture 3-3: The Three Polity Families
  4. Lecture 3-4: Convergence and Divergence in Practice
제 4 장 · Chapter 4: Governance Structures in Practice
  1. Lecture 4-1: The Governing Board — Purpose, Composition, and Limits
  2. Lecture 4-2: Bylaws and the Function of Writing Things Down in Advance
  3. Lecture 4-3: Legal Incorporation and Denominational Structure — The Basics
  4. Lecture 4-4: Committees and Delegated Authority
제 5 장 · Chapter 5: Meetings and Decision-Making
  1. Lecture 5-1: What Makes a Meeting Effective
  2. Lecture 5-2: Parliamentary Procedure
  3. Lecture 5-3: Consensus-Based Decision-Making
  4. Lecture 5-4: Discernment-Based Decision-Making
제 6 장 · Chapter 6: Financial Stewardship
  1. Lecture 6-1: A Theology of Giving: Cheerful, Proportionate, and Voluntary
  2. Lecture 6-2: Budgeting as a Theological and Practical Discipline
  3. Lecture 6-3: Internal Financial Controls: Protecting Money and Integrity Together
  4. Lecture 6-4: Financial Transparency and Its Limits
  5. Lecture 6-5: Compensation and Conflicts of Interest
제 7 장 · Chapter 7: Staffing and Volunteer Leadership
  1. Lecture 7-1: Hiring and Job Descriptions
  2. Lecture 7-2: Supervision and Staff Development
  3. Lecture 7-3: Volunteer Recruitment, Training, and Retention
  4. Lecture 7-4: Burnout in Staff and Volunteers
제 8 장 · Chapter 8: Facilities, Risk, and Safety
  1. Lecture 8-1: Facilities as Stewardship
  2. Lecture 8-2: Child Protection Policy
  3. Lecture 8-3: Risk Management and Insurance Basics
  4. Lecture 8-4: Emergency Preparedness
제 9 장 · Chapter 9: Conflict Management and Church Discipline
  1. Lecture 9-1: Matthew 18 and the Shape of a Fair Process
  2. Lecture 9-2: 1 Corinthians 6 and the Question of Litigation
  3. Lecture 9-3: Mediating a Dispute as an Administrative Leader
  4. Lecture 9-4: Formal Church Discipline
  5. Lecture 9-5: When and How to Involve Outside Help
제 10 장 · Chapter 10: Strategic Planning and Vision
  1. Lecture 10-1: Mission and Vision Are Not the Same Document
  2. Lecture 10-2: A Planning Cycle, and What Secular Frameworks Can and Cannot Do
  3. Lecture 10-3: What Gets Measured Is What Gets Pursued
  4. Lecture 10-4: Building a Plan a Congregation Will Actually Own
제 11 장 · Chapter 11: Leading Change and Organizational Culture
  1. Lecture 11-1: Leading Change: Two Models and What Each Misses
  2. Lecture 11-2: Managing Resistance Without Dismissing It
  3. Lecture 11-3: Organizational Culture: What Actually Forms It
  4. Lecture 11-4: Succession: Planning the Handoff Before It Is Forced
제 12 장 · Chapter 12: Legal, Ethical, and Cross-Cultural Administration
  1. Lecture 12-1: Legal Compliance, in General Terms Only
  2. Lecture 12-2: The Ethics of Institutional Power
  3. Lecture 12-3: Cross-Cultural Administration
  4. Lecture 12-4: Whistleblowing and Institutional Self-Correction
  5. Lecture 12-5: Sustainability, and a Personal Philosophy of Administration

핵심만 먼저 보기 ↓

13분

Ask a room of church leaders to state their congregation's mission and vision, and a common result is that they produce the same sentence twice in different words, or one of the two documents does not exist in any form anyone can recite. This lecture treats mission and vision as genuinely different tools that answer different questions, and argues that most of the value either document could provide is lost the moment it is written vaguely enough to make everyone comfortable.

A mission statement answers: why does this congregation exist, in words that would still be true in twenty years? A vision statement answers a narrower and more exposed question: what will faithfulness to that mission actually look like here, by a stated point in time? The first is a claim about identity and does not change often. The second is a claim about a specific, contestable future, and a leader who writes one honestly has said something that could turn out to be wrong — which is exactly why so many vision statements are written to avoid saying anything specific at all.

이 13분으로 얻는 것

  • State the difference between a mission statement and a vision statement in terms of what question each one answers, not merely in terms of length or tone.
  • Identify the specific features that make a mission or vision statement too vague to guide a real decision, and name a concrete way to make each feature testable.
  • Explain why a vision statement, properly written, is a form of exposure rather than a form of inspiration alone.
  • Apply Habakkuk 2:2-3's instruction about writing a vision "plain" to evaluate whether a real vision statement could actually be run with by someone who did not write it.

Yahweh answered me, "Write the vision, and make it plain on tablets, that he who runs may read it.

For the vision is yet for the appointed time, and it hurries toward the end, and won't prove false. Though it takes time, wait for it; because it will surely come. It won't delay.

Habakkuk 2:2 (World English Bible)

Habakkuk 2:3 (WEB)

1. Two questions, not one

Habakkuk had asked God a hard question — why does injustice go unanswered — and received an answer he could not immediately act on, because it described a coming reckoning through the rise of Babylon that would unfold over years, not days. God's instruction to the prophet is not "trust me and wait quietly." It is a command to write the vision down, plainly, on tablets, precisely because the fulfillment was distant enough that Habakkuk and his hearers needed something durable and legible to hold on to in the meantime — something a person moving quickly, a runner, could read at a glance and still grasp correctly (v. 2). The vision was specific enough to be written, specific enough to be misread if written poorly, and distant enough in its fulfillment that clarity mattered more, not less, because of the wait (v. 3).

This lecture borrows Habakkuk's standard — a vision plain enough for a runner to read — as the test for a congregation's own mission and vision statements, while being careful about what is and is not being borrowed. Habakkuk's vision was a specific prophetic word about God's own coming action in history; nothing said here claims a congregation's five-year plan carries that kind of authority. What transfers is narrower and more modest: the standard of plainness, of language a hearer can act on without having to guess what the writer really meant.

Mission answers a question that should be true for the whole life of the institution: why does this congregation exist? A workable mission statement names a purpose specific enough to exclude some things a church could otherwise do. "To glorify God and make disciples" is not wrong, but it is so broad that it could sit above almost any congregation's letterhead unchanged, which means it does not yet help this particular congregation decide anything a different congregation with a different mission statement would decide differently. A more useful mission statement adds enough specificity to the general call — this congregation, in this place, has taken up disciple-making in a way that shows up in what it actually prioritizes — while still describing something durable rather than a five-year initiative.

Vision answers a narrower, time-bound question: what will faithfulness to that mission look like here, by a stated point? A vision statement that says "a thriving, Christ-centered community" fails Habakkuk's test — a runner reading it could not tell whether it had been achieved or not, could not build a budget against it, and could not use it to say no to a proposal that conflicted with it. A vision statement that says something closer to "within five years, every member is meaningfully connected to a small group, and the congregation has planted or substantially supported one new congregation in an unreached part of the city" fails less badly: it is falsifiable, checkable at the stated date, and specific enough that a leadership team could actually use it to choose between two competing proposals for how to spend next year's discretionary budget.

2. Why vagueness is not a neutral failure

It is worth being honest about why vision statements drift toward vagueness, because the drift is not usually laziness. A specific vision statement can be wrong. A congregation that commits to a specific five-year outcome and falls short of it has to account for that publicly, in a way a congregation that committed only to "thriving" never has to. Vagueness protects the writer from being provably mistaken. This is precisely the cost Habakkuk's instruction refuses to let the vision-writer avoid: God commands the vision be written plain, not vague, even though a plain vision is a vision that can be checked against what actually happens. A leader drafting a vision statement is choosing, in effect, between the discomfort of being checkable and the safety of being unfalsifiable — and only the first is actually useful to the people who have to plan around the statement.

None of this means a vision statement should predict outcomes the leader does not actually control — see Lecture 10-2 on Proverbs 16:9 for the necessary caveat that a plan is a proposal, not a guarantee. The claim here is only that a vision statement should be specific enough that its own author, and everyone who reads it, could later agree on whether it happened.

3. A common failure in the other direction

The reverse failure is also real and worth naming: a mission statement that is not actually enduring but is instead a five-year strategy dressed up in "why we exist" language. A congregation whose mission statement names a particular program, a particular building project, or a particular numeric attendance target has written a vision statement in the wrong document. When that program ends or that target is met or missed, the congregation is left without a mission statement at all, because what it called its mission was actually a plan. Keeping the two documents doing two different jobs — one naming a purpose durable enough to survive any single plan's success or failure, the other naming a specific, checkable picture of a stated future — is what lets a congregation revise its vision without having to also rewrite its reason for existing.

Two documents, two questions Habakkuk 2:2's standard: plain enough for a runner to read Mission Question: why do we exist? Timeframe: enduring Test: specific enough to rule some things out — not "glorify God," which fits every congregation alike Vision Question: what will faithfulness look like here, by when? Timeframe: stated and bounded Test: checkable — a runner could tell, at the stated date, whether it happened or not The trap: writing either document vaguely feels safer because a vague claim can never be shown to have failed — but it also can never actually guide a decision.

핵심 요약

  • A mission statement answers why the congregation exists, in words true for decades. A vision statement answers what faithfulness will look like here by a stated time.
  • Habakkuk 2:2-3 commands that the vision be written plain, so a runner can read it. The lecture borrows only that standard of plainness, not the prophet's authority.
  • A mission such as "glorify God and make disciples" fits any church and rules nothing out. A useful one is specific enough to exclude some options.
  • A vision like "thriving, Christ-centered community" cannot be checked. A vision with a date and measurable outcomes can guide a budget decision.
  • Vagueness feels safe because it can never be proven wrong, but it cannot guide decisions. Plain vision accepts being checkable.
  • Do not put a program, building project or attendance target in the mission. That is a vision written in the wrong document.

Topic: This lecture argues that mission and vision are two different documents answering two different questions, and that both should be plain enough to guide decisions.

Remember: Mission is the enduring reason for existing. Vision is a specific, checkable picture of a stated future.

Caution: The lecture does not claim a congregation's plan carries prophetic authority, and a vision should not promise outcomes the leader does not control. It only asks that the vision be specific enough to check.

One line to carry into ministry: Write a vision that you and everyone else could later agree did or did not happen.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.

묵상 및 토론

  • Take a mission statement you know well (your own congregation's, or one you have seen elsewhere). Apply the test in this lecture: does it exclude anything a church could otherwise do, or would it fit almost any congregation unchanged?
  • Habakkuk was told to write the vision "plain" specifically because its fulfillment was distant and the wait would be hard. Why might distance and difficulty make plainness more important, rather than less, for a congregation's own multi-year vision?
  • This lecture claims vagueness in a vision statement is often a way of avoiding the discomfort of being provably wrong. Do you find that explanation persuasive, or can you think of a better reason a leadership team might genuinely prefer a vague statement?
  • Think of a real decision your congregation or organization faced in the last year. Would a specific, checkable vision statement (had one existed) have actually changed how that decision was made, or only how it was described afterward?

로그인하시면 여기에 답을 적고 보관하실 수 있습니다

다음 단계

여기까지가 강의입니다. 아래는 읽은 사람들이 남긴 글입니다.