Lecture 7-1: Hiring and Job Descriptions
목차 53
- Lecture 1-1: Order Is God's Own Concern
- Lecture 1-2: The Household Manager — Administration as Stewardship
- Lecture 1-3: Administration as a Spiritual Gift
- Lecture 1-4: What to Take from Secular Management Theory, and What to Leave
- Lecture 2-1: Jethro's Advice to Moses — Delegation, Capacity, and Choosing Leaders
- Lecture 2-2: The Wilderness Camp — Order Around a Theological Center
- Lecture 2-3: Temple Staffing and Levitical Organization — Building for the Long Term
- Lecture 2-4: Acts 6 — A Complaint, a Diagnosis, and a Change in Role
- Lecture 2-5: The Jerusalem Council — Deliberation, Evidence, and a Communicated Decision
- Lecture 3-1: The Office of Elder
- Lecture 3-2: The Office of Deacon
- Lecture 3-3: The Three Polity Families
- Lecture 3-4: Convergence and Divergence in Practice
- Lecture 4-1: The Governing Board — Purpose, Composition, and Limits
- Lecture 4-2: Bylaws and the Function of Writing Things Down in Advance
- Lecture 4-3: Legal Incorporation and Denominational Structure — The Basics
- Lecture 4-4: Committees and Delegated Authority
- Lecture 5-1: What Makes a Meeting Effective
- Lecture 5-2: Parliamentary Procedure
- Lecture 5-3: Consensus-Based Decision-Making
- Lecture 5-4: Discernment-Based Decision-Making
- Lecture 6-1: A Theology of Giving: Cheerful, Proportionate, and Voluntary
- Lecture 6-2: Budgeting as a Theological and Practical Discipline
- Lecture 6-3: Internal Financial Controls: Protecting Money and Integrity Together
- Lecture 6-4: Financial Transparency and Its Limits
- Lecture 6-5: Compensation and Conflicts of Interest
- Lecture 7-1: Hiring and Job Descriptions
- Lecture 7-2: Supervision and Staff Development
- Lecture 7-3: Volunteer Recruitment, Training, and Retention
- Lecture 7-4: Burnout in Staff and Volunteers
- Lecture 8-1: Facilities as Stewardship
- Lecture 8-2: Child Protection Policy
- Lecture 8-3: Risk Management and Insurance Basics
- Lecture 8-4: Emergency Preparedness
- Lecture 9-1: Matthew 18 and the Shape of a Fair Process
- Lecture 9-2: 1 Corinthians 6 and the Question of Litigation
- Lecture 9-3: Mediating a Dispute as an Administrative Leader
- Lecture 9-4: Formal Church Discipline
- Lecture 9-5: When and How to Involve Outside Help
- Lecture 10-1: Mission and Vision Are Not the Same Document
- Lecture 10-2: A Planning Cycle, and What Secular Frameworks Can and Cannot Do
- Lecture 10-3: What Gets Measured Is What Gets Pursued
- Lecture 10-4: Building a Plan a Congregation Will Actually Own
- Lecture 11-1: Leading Change: Two Models and What Each Misses
- Lecture 11-2: Managing Resistance Without Dismissing It
- Lecture 11-3: Organizational Culture: What Actually Forms It
- Lecture 11-4: Succession: Planning the Handoff Before It Is Forced
A congregation rarely disputes a hire on the day it is made. The dispute comes eighteen months later, when a staff member believes a task falls outside what they agreed to do, a supervisor believes it plainly falls inside their duties, and the only document anyone can point to is a one-paragraph posting written quickly to fill a vacancy. This lecture treats the job description not as paperwork attached to hiring but as the primary tool for preventing that later dispute, and treats the hiring process itself as a place where a church's theology of the person — not only its need for labor — has to show up in practice.
Chapter 6 dealt with money moving through an institution; this chapter turns to the people who do the institution's work, paid and unpaid. The chapter's governing claim, stated in the table above, is that staff and volunteers are stewarded people, not simply labor to be deployed efficiently. A hiring process built only to fill a role as fast as possible treats a candidate as a function to be executed. A hiring process built with 1 Timothy 3:10's logic in view treats a candidate as someone whose character is at stake in the decision, and whose eventual scope of responsibility deserves to be stated clearly enough that no one has to guess at it later.
이 14분으로 얻는 것
- Write a job description with enough specificity to prevent a later dispute about scope, including the elements a vague posting typically omits.
- Explain what 1 Timothy 3:10 requires of a candidate for the diaconate, and state carefully what does and does not transfer when the same logic is applied, by extension, to a staff hire who holds no ordained office.
- Distinguish a hiring process that checks competency alone from one that checks both competency and character, and name at least one concrete practice each requires.
- Identify at least one common failure mode in church hiring (rushed hiring under vacancy pressure, hiring on referral alone without independent verification, or a job description written to attract a candidate rather than to describe the actual job) and explain why it recurs.
Let them also first be tested; then let them serve if they are blameless.
1 Timothy 3:10 (World English Bible)
1. Why a job description is a dispute-prevention document, not an advertisement
A job posting and a job description are not the same document, even though many congregations write only the first and never the second. A posting exists to attract a candidate; naturally, it emphasizes what makes the role appealing. A job description exists to govern the working relationship after the candidate accepts, and its job is different: to state, specifically enough that a disagreement eighteen months later has something to be checked against, what the role actually includes.
A job description that will hold up under later disagreement needs several elements a brief posting usually lacks. It needs a reporting line — who supervises this role, and who this role supervises, if anyone — stated plainly enough that an org chart could be drawn from it without asking anyone. It needs a list of core duties specific enough to distinguish this role from an adjacent one; "supports the children's ministry" invites a different set of expectations than "teaches the Sunday second-grade class, recruits and schedules two rotating volunteer assistants, and orders curriculum by the first of each quarter." It needs a statement of decision authority — what this role may decide alone, what it must bring to a supervisor, and what it must bring to a board or committee — because an unstated boundary here is exactly the kind of ambiguity that produces both the paralyzed employee who will not act without permission and the employee who acts far outside what anyone intended. And it needs a stated review cycle, so that the document itself is revisited rather than drifting silently out of date while the actual duties change underneath it.
None of this is decoration. A congregation that treats its staff as stewarded people, not simply labor, owes them a description specific enough that they are not left guessing what is actually expected of them — and owes itself the same clarity, since an institution with no stated scope for a role has no fair basis for later evaluating whether the role was performed well.
2. 1 Timothy 3:10 and testing before entrusting
Paul's instruction concerning deacons — "let them also first be tested; then let them serve if they are blameless" — sits inside a specific passage about qualification for a specific ordained office, and this course has already treated that office's textual basis in Chapter 3. The verse is worth returning to here for a narrower reason: it names a sequence — testing, then service — that is a defensible model for any hire carrying real responsibility over people or resources, ordained or not, even though the text itself is speaking only of deacons.
The extension has to be made carefully, and stated as an extension rather than as if the text directly commanded a hiring procedure for, say, a facilities coordinator. What transfers is the logic, not the specific office: a person is not simply declared qualified because they are willing, available, or well liked. Something is checked first — Paul does not specify exactly what "tested" (Greek dokimazō, to examine and approve) required in practice, and interpreters differ on whether this points to an observation period, a specific examination, or both — and only afterward is responsibility actually handed over. What does not transfer is the assumption that every staff role carries the theological weight of ordained office; a projectionist and a are not qualified by an identical process, and treating every hire as though it required the scrutiny appropriate to spiritual oversight would import a weight the text does not place there. The transferable principle is narrower and more useful: character is checked before responsibility is granted, not assumed from competence or affirmed only after a problem surfaces.
3. Checking competency and character together
A hiring process built on competency alone asks whether a candidate can do the job — the right credentials, relevant experience, a portfolio or reference that demonstrates skill. This is necessary and should not be treated as unimportant; a church that hires a bookkeeper with no financial competence because she is well loved in the congregation has not honored 1 Timothy 3:10's logic, it has ignored a different, equally real qualification.
A process built on character together with competency adds distinct steps that a purely skills-based process often skips: independent reference checks that ask a former supervisor open questions rather than confirming what the candidate already claimed; a defined probationary period in which both the institution and the new hire can discover whether the fit is real, with the terms of that period stated in writing before it begins rather than improvised if a problem arises; and, for roles working with minors or vulnerable adults, the background-check and screening practices this course returns to in Chapter 8. None of these steps guarantees a good hire. Together they represent a hiring process that has actually tested something, rather than one that has simply trusted a first impression, a referral from a respected member, or the relief of finally filling a vacancy that has sat open too long.
4. Where hiring goes wrong
Three failure modes recur often enough to name specifically. The first is hiring under vacancy pressure: a position sits empty, ministry visibly suffers, and the pressure to fill it quickly overwhelms the discipline to test first. The second is hiring on referral alone — a well-regarded member vouches for a candidate, and the vouching substitutes for independent verification rather than supplementing it; a personal recommendation is evidence, not a completed process. The third is a job description written to be attractive rather than accurate — listing duties in their most appealing light, understating a role's less desirable responsibilities, and thereby setting up the very dispute this lecture opened with, since the new hire's reasonable expectation was shaped by a document the institution never intended to be followed literally.
None of these failure modes is a scandal by itself. Each is an ordinary shortcut taken under ordinary pressure. What Chapter 7's governing claim asks a leader to notice is that each shortcut, however understandable, treats the hiring process as an obstacle to be gotten past rather than as the first place a congregation practices its stated belief that the people it employs are stewarded, not simply deployed.
핵심 요약
- A job description is a dispute-prevention document, not an advertisement. It governs the working relationship after the hire.
- It needs a reporting line, specific core duties, a statement of decision authority, and a review cycle.
- 1 Timothy 3:10 ("first be tested") speaks of deacons. Its logic of checking character before granting responsibility is extended to staff hires, but not its weight as ordained office.
- Hiring should check competency and character together: independent reference checks, a written probationary period, and screening for roles with minors or vulnerable adults.
- Three recurring failures: hiring under vacancy pressure, hiring on referral alone, and a job description written to attract rather than describe.
Topic: This lecture treats job descriptions and hiring as places where a church practices its belief that staff are stewarded people, not just labor.
Remember: Test before you entrust. Write a job description specific enough that scope can be checked later.
Caution: 1 Timothy 3:10 is about deacons, and interpreters differ on what "tested" meant. Do not treat every hire as needing the scrutiny of spiritual oversight.
One line to carry into ministry: Write the real duties, reporting line and decision limits before you advertise, and verify references independently.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- 1 Timothy 3:10 speaks specifically of deacons. What, precisely, transfers to a staff hire holding no ordained office, and what does not? How would you defend that line if someone challenged it as reading too much, or too little, into the text?
- Think of a job description you have seen — your own, or one you know of — that was too vague to prevent a later disagreement. What specific element was missing: reporting line, decision authority, scope of duties, or something else?
- Why might a congregation resist a formal, written hiring process for a role that has always been filled informally by asking around? What is actually being protected by the informal approach, and what is being risked?
- This lecture treats a rushed hire under vacancy pressure as an understandable shortcut rather than a scandal. Can you think of a case where the pressure to fill a role quickly is strong enough that skipping part of the sequence is, on balance, the right call? What would make that judgment defensible rather than merely convenient?