Lecture 10-2: Trust as Covenant, Not Transaction
Contents 59
- Lecture 1-1: Secular Leadership Theory and the Question It Does Not Ask
- Lecture 1-2: The Image of God and the Dominion Mandate
- Lecture 1-3: What Biblical Leadership Is — Delegated Authority Under a Higher Authority
- Lecture 1-4: The Purpose of Leadership — Kingdom and Next Generation, Not Legacy
- Lecture 2-1: "It Shall Not Be So Among You" — Mark 10:42-45
- Lecture 2-2: Footwashing and Status Anxiety — John 13
- Lecture 2-3: The Kenosis Hymn — Philippians 2:5-11
- Lecture 2-4: What Servant Leadership Is Not
- Lecture 3-1: Leadership as One Gift Among Many
- Lecture 3-2: Spirit-Empowered Authority Versus Natural Charisma
- Lecture 3-3: The Fruit of the Spirit as Leadership Character
- Lecture 3-4: Case Studies — Stephen and Barnabas
- Lecture 4-1: Moses' Call — Resistance and an Unwilling Leader
- Lecture 4-2: Jethro's Counsel — The Theology of Delegation
- Lecture 4-3: Moses' Failure at Meribah — Private Frustration, Public Sin
- Lecture 4-4: Joshua's Succession — Transition as a Theological Event
- Lecture 4-5: Two Case Studies — David's Fall and Restoration, and Nehemiah's Crisis Leadership
- Lecture 5-1: Jesus' Method — Calling, Presence, Sending, and Correction
- Lecture 5-2: Peter's Denial and Restoration — Formation Through Foreknown Failure
- Lecture 5-3: Peter at Pentecost — What Changed and What Did Not
- Lecture 5-4: Paul — Called, Vouched For, and Built to Be Left
- Lecture 6-1: The Qualifications — Cataloging Character and Competence in 1 Timothy 3 and Titus 1
- Lecture 6-2: Gift Is Not Readiness — 1 Corinthians 12-13
- Lecture 6-3: The Leader's Shadow Side — Saul and David Under the Same Kind of Pressure
- Lecture 6-4: Warning Signs and the Danger of Standing Confidently
- Lecture 7-1: The Leader's Own Source: Solitude, Prayer, and Scripture
- Lecture 7-2: Calling: Inward Conviction and Outward Confirmation
- Lecture 7-3: Accountability Structures for Leaders
- Lecture 7-4: Burnout, Sabbath, and the Theology of Rest for Leaders
- Lecture 8-1: Vision as Received, Not Invented
- Lecture 8-2: The Hidden Process: Nehemiah's Grief, Prayer, and Assessment
- Lecture 8-3: Communicating Vision: Repetition, Symbol, and Story
- Lecture 8-4: The Ethics of Persuasion, and Vision That Fades
- Lecture 9-1: Emotional Intelligence and the Wisdom of Proverbs
- Lecture 9-2: Empathic Listening: What Job's Friends Got Right, and Then Wrong
- Lecture 9-3: Self-Regulation Under Pressure: Moses at Meribah Revisited
- Lecture 9-4: Relational Capital Across a Power Gap: David and Jonathan
- Lecture 10-1: How Teams Actually Form
- Lecture 10-2: Trust as Covenant, Not Transaction
- Lecture 10-3: Building a Team of Different People, on Purpose
- Lecture 10-4: Delegation Is a Spectrum, Not a Switch
- Lecture 11-1: Conflict as an Opportunity for Reconciliation
- Lecture 11-2: Matthew 18 and the Discipline of Confrontation
- Lecture 11-3: What a Leader Owes People Who Are Afraid
- Lecture 11-4: Can the Church Use a Corporate Change Model?
- Lecture 11-5: Crisis Leadership — Composure and Communication
- Lecture 12-1: The Four-Generation Standard
- Lecture 12-2: Designing Formation That Reproduces Leaders
- Lecture 12-3: Modeling — Teaching by Being Watched
- Lecture 12-4: Three Mentoring Pairs Compared
- Lecture 12-5: Coaching Through Questions
- Lecture 13-1: A Reusable Leadership Pipeline
- Lecture 13-2: Leading Across Generations
- Lecture 13-3: Women in Church Leadership — Two Positions, Fairly Stated
- Lecture 13-4: Leadership Across Cultural, Marketplace, and Digital Boundaries
Chapter 9 introduced David and Jonathan's relationship as a case study in relational trust across an asymmetry of power — Jonathan the king's son, David the popular rising rival who by every political logic should have been Jonathan's enemy. That lecture asked what made trust possible between two people in that situation. This lecture does not re-tell that story. It asks a different question of the same evidence: what kind of trust was this, structurally, and what does that structure require of a leader trying to build trust inside a team today, long after the particular history between David and Jonathan is no longer available as a template.
The argument of this lecture is that Scripture's account of trust in relationships like this one is covenantal rather than merely transactional, and that the difference is not a matter of degree but of kind. A transactional account of trust treats it as an accumulating balance: each kept promise, each instance of reliability, adds credit, and each failure withdraws it, so that trust is fundamentally a running tally of performance. A covenantal account treats trust as a commitment made and kept regardless of the other party's ongoing performance — closer to a vow than a ledger. Both accounts are real and both matter in team life, but a team led on transactional trust alone will be only as strong as its members' least reliable day, while a team with covenantal trust underneath it can survive a member's failure without collapsing.
What these 12 minutes give you
- Distinguish transactional trust from covenantal trust and explain what each account predicts about how a relationship responds to a single failure.
- Explain, without re-narrating the story from Chapter 9, what 1 Samuel 18's covenant language specifically adds to an account of trust between David and Jonathan.
- Identify at least two concrete practices a leader can use to build covenantal, not merely transactional, trust within a team.
- Explain a limitation of the covenant framework: why covenantal trust does not mean trust without any accountability or boundaries.
1 Samuel 18:1, 3 (World English Bible): "When he had made an end of speaking to Saul, the soul of Jonathan was knit with the soul of David, and Jonathan loved him as his own soul. ... Then Jonathan and David made a , because he loved him as his own soul."
1. What Chapter 9 already covered, and what this lecture adds
Chapter 9's treatment (9-4) used this same text to ask how trust becomes possible between people whose positions put them in tension — a king's heir and a rising, popularly acclaimed rival with a credible claim to succeed Saul instead of Jonathan. That lecture's answer centered on what each man risked and chose not to protect: Jonathan surrendering the succession itself, David refusing to exploit the access Jonathan's friendship gave him. This lecture takes that history as established and asks a narrower, more structural question: what does the text's specific word choice — covenant (Hebrew berith), not merely friendship or affection — add to the picture, and what does a covenantal frame require of a leader building trust in an ordinary team today, where no comparable history of shared risk yet exists to draw on.
2. Covenant versus transaction
The text is precise about the sequence: the soul-bond ("the soul of Jonathan was knit with the soul of David... Jonathan loved him as his own soul," v. 1) is reported first, and the covenant (v. 3) follows it — the covenant formalizes and commits to something that was already true relationally, rather than manufacturing the relationship out of a formal agreement. That order matters for a leader's expectations: a covenant does not create trust out of nothing; it commits publicly to sustain a trust that already has some real basis, and in doing so makes that trust more durable than feeling alone would make it.
A transactional account of trust is not wrong so much as it is partial. It is true, and important, that trust is built through a pattern of kept commitments over time — a leader who says one thing and does another will not be trusted regardless of any covenant language used, and this course is not arguing that covenantal language substitutes for reliability. But a purely transactional account has a structural weakness: because it is a running tally, a single serious failure can zero it out, and because it is a tally, each party is implicitly still keeping score. A covenantal account adds something a tally cannot: a decision, made in advance and independent of any single data point, to remain committed to the relationship's good even through a failure that a transactional ledger would count against the balance. 1 Samuel 20 (just past this lecture's anchor text) shows this exact durability: Jonathan continues to protect David even as Saul's hostility toward David escalates and even though protecting David plainly damages Jonathan's own political position — the covenant, not a fresh calculation of David's reliability that week, is what holds.
3. What covenantal trust asks of a leader building a team
Three practices follow from taking the covenant frame seriously rather than treating it as an interesting fact about an ancient friendship.
First, a leader who wants covenantal trust on a team has to name the commitment explicitly rather than assume it will accumulate silently through good behavior. Jonathan and David's covenant was spoken and, per verse 4, sealed with a visible sign (Jonathan's robe and weapons given to David). A team whose trust is never named — never stated in terms of what members owe each other regardless of performance — will default to the transactional mode by default, because that is the mode people fall back into without a deliberate alternative.
Second, covenantal trust requires the leader to model absorbing cost for the relationship's sake before asking team members to do the same. Jonathan moved first, and moved at real cost to his own position; a leader who wants a team to extend covenantal trust to one another, and to the leader, but is never seen absorbing any cost themselves is asking for something they have not modeled.
Third, covenantal trust has to be distinguished from indiscriminate trust — trust extended without regard to a person's actual conduct or character. The covenant between David and Jonathan was made between two people of demonstrated integrity toward one another; it was not made in the absence of that evidence, and this course's earlier treatment (Chapter 6) of character as prior to competence in scriptural leadership qualifications applies here as well. A leader building covenantal trust into a team is not thereby exempted from the ordinary work of assessing character, and a covenant is not a substitute for the accountability structures Chapter 7 already argued no leader should be without.
4. A caution
It would overreach the text to claim that every team relationship should be a formal covenant in the specific, near-liturgical sense David and Jonathan's was — the text does not present their arrangement as a normative structure to be replicated procedurally, and turning "covenant" into a required team ritual would risk exactly the kind of self-conscious formality that undercuts the trust it is meant to express. The transferable claim is narrower: that trust built to last is trust committed to in advance, named rather than assumed, and modeled by the leader first — not trust that merely accumulates and can therefore just as easily be spent down to zero.
In short
- Transactional trust is a running tally of reliability, so one serious failure can zero it out. Covenantal trust is a commitment made in advance and kept through a failure.
- In 1 Samuel 18:1 the bond of love comes first and the covenant follows. The covenant commits to sustain trust that already has a real basis.
- Jonathan kept protecting David even at cost to his own position (1 Samuel 20). The covenant held, not a fresh calculation.
- Three practices: name the commitment, model absorbing cost first as the leader, and do not confuse covenant with indiscriminate trust.
- The lecture does not claim every team relationship must be a formal covenant.
Topic: The lecture asks what kind of trust David and Jonathan had, and what a covenant frame asks of a leader building a team.
Remember: Trust built to last is committed to in advance, named rather than assumed, and modeled by the leader first.
Caution: Covenantal trust is not trust without accountability or character checks. Kept promises still matter, and a covenant does not replace reliability.
One line to carry into ministry: Say aloud what team members owe one another, and be first to bear the cost.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Where in a team you have led or served on has trust functioned mostly as a transactional balance? What happened the first time someone made a serious mistake?
- What would it look like, concretely, to "name the commitment" of trust within a real ministry team without turning it into an empty ritual?
- The lecture argues covenantal trust is not indiscriminate trust. How would you tell the difference in practice between extending covenantal trust to a team member and ignoring a real, character-level concern about that person?
- Jonathan moved first and at real cost. What would it cost a leader today to model that kind of first move toward a team?