AI note
Adaptive leadership and AI adoption: stress-test for Movemental’s thesis (internal synthesis)
Executive summary
Ronald Heifetz’s distinction between technical problems (knowable, delegable to expertise) and adaptive challenges (requiring learning, value conflict, and distributed responsibility) remains a justified and legible lens for how generative AI lands in mission-shaped organizations. It is not, however, a sufficient exclusive lens. Contemporary research and standards discourse frame enterprise and institutional AI as sociotechnical: irreducibly about data, models, procurement, security, and law as well as culture and courage.
Recommendation: Treat adaptive leadership as a co-primary sensemaking frame alongside sociotechnical governance — not as a replacement for technical strategy. For Movemental’s audiences, that pairing is both more honest and more pastorally credible than “anthropological, not technological” taken literally.
For maturity models, the field already offers four- and five-stage enterprise schemas (e.g., MIT CISR four-stage enterprise AI maturity; Gartner five-level framings). Movemental’s five-stage narrative is competitive with industry habit but not uniquely validated as a scientific stage theory. Credibility in sales and product copy requires humility: present stages as a working heuristic tied to observable behaviors and governance milestones, and avoid implying empirical developmental psychology without measurement.
On Dunning–Kruger, recent experimental work complicates a simple morality tale. Fernandes et al. (Computers in Human Behavior, 2026, DOI 10.1016/j.chb.2025.108779) find that with ChatGPT-class tools on demanding reasoning tasks, participants gained performance yet lost calibration — overestimating how well they did; the classic DK pattern was disrupted, and higher AI literacy was associated with greater overconfidence in the publicized interpretation. Movemental should not claim “DK exactly as in the textbooks” for AI; it should warn that fluency and optimism can outrun judgment — including for sophisticated users.
1. Is Heifetz the right primary lens?
What Heifetz actually contributes. In Leadership Without Easy Answers (1994) and The Practice of Adaptive Leadership (Heifetz, Grashow, Linsky, 2009), adaptive work is the learning required when values, roles, or identities must change — not merely when a new tool ships. That maps cleanly onto generative AI in churches and movements: questions of truthfulness, attribution, pastoral presence, speed vs. depth, and who is displaced are not resolved by a sharper IT roadmap alone.
Where the lens strains. AI adoption in real institutions is simultaneously:
- Technical: data quality, integration, evaluation of outputs, incident response, cybersecurity.
- Legal / ethical: copyright, privacy, discrimination risk, record-keeping.
- Economic: vendor contracts, lock-in, total cost of ownership.
Standards such as ISO/IEC 42001 and policy frameworks (e.g., NIST AI RMF, EU regulatory conversation) presuppose competence and documentation — not “vibes.” If Movemental’s message implies leaders can delegate all technical discernment, it collides with accountable oversight norms.
Verdict: Heifetz is a strong primary lens for the anxiety, conflict, and identity work AI provokes — and a secondary lens is mandatory for the sociotechnical remainder. Public language should read: “primarily adaptive in how it changes us; unavoidably technical in how it runs.”
2. Maturity models: differentiation without overclaiming
Established models. MIT CISR’s enterprise AI maturity work (Weill, Woerner, Sebastian; see MIT Sloan and CISR publications) organizes progress across a four-stage trajectory grounded in large surveys and interviews. Gartner popularizes five-level maturity language for AI portfolios. McKinsey’s recurring “State of AI” reporting emphasizes adoption breadth, value capture, and rewiring more than a single canonical ladder in every edition.
Movemental’s five-stage model (C-F10). Five stages sit in the industry-recognizable band (especially vs. Gartner). Differentiation should not rest on “we discovered the true stages of AI.” It should rest on:
- Audience fit: formation-rich language for movement leaders vs. generic CIO stages.
- Ethical and public leadership milestones: e.g., when an org is safe to speak externally about AI use, not only when it deploys copilots.
- Honest epistemology: stages as scaffolding for coaching, not validated developmental psychology.
Overclaiming risk. Stage theories in Kohlberg, Fowler, and Kegan traditions are contested as predictive instruments for adults. Slapping a “stage 3” label on a small nonprofit may feel evaluative rather than formative. Product and marketing should prefer capabilities unlocked language over identity ranking.
What would empirical validation require? Longitudinal evidence that users progress in order, rarely regress, and that stage assignments predict responsible behaviors (verification habits, governance artifacts, incident reporting). Without that, say “model” or “map”, not “science.”
3. “Anthropological, not technological”: rhetorical power vs. literal truth
The headline book-003 is rhetorically powerful for audiences tired of being shamed for not keeping up with Silicon Valley. It names a real phenomenon: AI reorders attention, trust, craft, and vocation.
Taken literally, the phrase is too strong. Movemental itself will presumably counsel on data stewardship, vendor risk, and truthful representation — all technological or techno-legal competencies. A disciplined public version:
- Anthropological first for why this hurts and why we resist.
- Technological enough for what we must never be naive about.
That split preserves moral seriousness without inviting critics to accuse Movemental of anti-intellectualism or consultant mystique.
4. Experimentation vs. discernment (book-005, book-043)
What research rewards. Innovation and design-thinking literatures strongly support cheap experiments under uncertainty — consistent with “experimentation as prerequisite to discernment” when discernment means discovering faithfulness in fog, not avoiding accountability.
What traditions rightly slow down. Prudence, authority of office, and communal discernment exist partly to prevent individualistic trial-and-error on matters that touch vulnerable people (pastoral care, counseling, public teaching). “Permission to stay at experimentation level” book-043 is pastorally necessary if it means relief from shame and premature public posturing — and dangerous if it becomes permission to skip oversight where harm is asymmetric.
Synthesis line for copy: Experimentation should be structured — hypothesis, scope, review, rollback — not impulsive play. That bridges lean learning with ecclesial seriousness.
5. “Leaders don’t need technical expertise” (articles-027)
Strongest true version: Leaders do not need to train transformers or write Python to lead.
False version: Leaders need no technical literacy to govern.
Responsible leadership requires enough literacy to commission the right questions: data provenance, evaluation of failure modes, human-in-the-loop expectations, and when to refuse automation. Movemental should keep the encouragement for non-engineer leaders but qualify it with minimum viable literacy for their context tier.
6. Speed, hype, and “Dunning–Kruger” (research-005)
Do not lean on a pop-psych DK caricature for AI without nuance. The Fernandes et al. program suggests metacognitive risk is widespread, including among those who think they understand AI. That actually raises the stakes for Movemental’s formation positioning: the enemy is not only incompetence but miscalibrated confidence across skill levels.
7. Trade-offs of leaning hard into adaptive framing
| Upside | Downside |
|---|---|
| Dignifies slow, moral reasoning | Can moralize resistance unfairly |
| Explains why tool-first rollouts fail | Can slow adoption paths that Movemental as a vendor needs |
| Fits conflicted congregations | May under-specify procurement and engineering realities |
| Differentiates from hype merchants | Risks sounding like another leadership seminar |
Business lens (business-034): Position adaptive leadership as why Movemental sells coaching and formation, not as a denial that platforms must be engineered well.
8. Argument index — keep, qualify, or drop
| ID | Guidance |
|---|---|
book-003 | Keep as ordered priority (“first anthropological”) ; qualify literal “not technological.” |
business-034 | Keep with sociotechnical pairing; name procurement/governance explicitly in deeper tiers. |
C-F10 | Keep as heuristic map; qualify vs. MIT/Gartner; avoid empire-building claims about uniqueness. |
book-005 | Keep; bind to accountable experimentation language. |
book-043 | Keep as anti-shame; qualify with non-negotiables for high-risk contexts. |
articles-027 | Qualify sharply; add governance floor. |
research-005 | Rewrite to track metacognitive miscalibration evidence; drop naive DK shorthand. |
9. Strong counter-arguments and the defensible thesis
Counter-arguments to own:
- AI is infrastructure, not only culture — scale, latency, and liability follow technical facts.
- “Adaptive” is consultant-coded — audiences may glaze unless tied to concrete practices.
- Elite frameworks (Harvard Kennedy School lineage) may feel distant from volunteer-led churches unless translated.
Strongest defensible thesis the evidence allows:
Generative AI is a sociotechnical shock that presents as a tools conversation but forces adaptive work on communities of truth and care. Movemental’s value is to hold the adaptive conversation honestly while refusing two reductions: neither tech solutionism nor anti-tech romanticism.
Relation to adjacent prompts (internal scope)
This synthesis intentionally does not merge adaptive leadership with market-timing or “historical moment” claims (Prompt 16) or with assessment science (Prompt 17), except where stage theories overlap: any borrowing from developmental psychology for product narrative should be flagged for separate validation. Likewise, communitas and embodied trust (Prompt 18) sit underneath adaptive work in congregations; tools land differently where liminal solidarity is high vs. where institutional suspicion already dominates. Keeping those boundaries clean prevents the book manuscript from sounding as if one leadership theory explains credibility economics, community formation, and AI governance in a single breath.
Next steps (internal)
- Cross-read
/article-corpusfor Alan’s existing language on formation, discernment, and change so Movemental’s voice stays distinct from generic Heifetz recycling. - If
C-F10appears elsewhere with a different meaning in the argument database, reconcile IDs to avoid editorial collisions. - For any public maturity claims, attach one external benchmark citation (e.g., MIT CISR or Gartner) in footnotes — not to borrow authority, but to show good-faith comparison.