Practitioner Handbook · TIC TOC · Bear Brown & Company

The AI Sherpa: full table of contents and chapter specifications

A practitioner's guide for experiential learning

Bear Brown & Company / Kindle Direct Publishing, 2026  ·  18 chapters across 5 parts
Version 1.0  ·  2026-03-21  ·  Reviewed by Dev the Dev

Contents

Section 1

Book Concept and Thesis

Thesis
"AI deployed in experiential learning contexts is categorically different from AI deployed in classroom contexts — it is a Sherpa, not a teacher — which means that every design principle imported from AI-in-education literature into experiential learning programs produces the wrong tool for the wrong relationship, and this matters because the cost is not just inefficiency but the active undermining of the developmental process that makes consequential experience educative in the first place."

Concept: This book teaches experiential learning professionals to use AI as a structured developmental companion — before, during, and after the experience — filling the gap left by Kolb (theoretical framework, no AI infrastructure), Schön (reflection model, no scalable tool), and every institutional assessment rubric that produces a form instead of a living document.

Success condition: The reader can design and deploy an AI-assisted reflection infrastructure — experience map, living journal, and AI Sherpa — that develops practical wisdom in students at a scale and depth no single advisor could achieve alone.

The payoff: When the Sherpa relationship is correctly understood and correctly designed, the developmental potential of experiential learning — practical wisdom, narrative identity, judgment under real stakes — can be realized at scale for the first time. Not because AI replaces the human advisor, but because AI carries the reflection infrastructure that no single human advisor could carry for 200 students simultaneously, freeing the advisor to do the interpretive and strategic work that only a human who knows the student as a person can do.

The Pebble — the book's founding case

A student completes a six-month co-op at a Boston financial services firm. Well-evaluated. Offered a return position. Her co-op coordinator asks what she learned. She says: "I got really good at Excel modeling." Three years later she is struggling with exactly the judgment problems — organizational navigation, advocacy for her own analysis, responding to being wrong in public — that the co-op had six months to develop. It did not. This is not a student failure. It is a design failure. The book is built on that sentence.

Section 2

Learner Profile

Primary reader

An experiential learning professional at a university, professional school, or corporate early career program — co-op coordinator, study abroad advisor, clinical placement director, apprenticeship program manager, experiential learning faculty lead, career development professional.

What they already knowWhat they do not know
Kolb's four-stage cycle by reflex; reflection frameworks and debrief protocols; their institution's placement infrastructure and constraints; that some students extract enormous developmental value from placements while others complete the same experience and learn almost nothing.What AI can actually do in a non-classroom context; that AI can hold longitudinal context across a student's journal; that the placement decision itself can be made analytically against a developmental profile; that their advisor role changes — does not disappear — when a Sherpa handles the scaffolding at scale.

Prior misconceptions to dismantle

Motivation type: Professional with a mission. Will tolerate theory only if immediately connected to practice.

Secondary reader

Graduate students in higher education administration, student affairs, and instructional design who encounter this book in a course. The book works for this reader but is not designed for them.

Section 3

Three-Act Learning Arc

Arc statement: This book takes the practitioner from the recognition that most students' experiential learning potential is lost to a design failure — by first naming the failure and diagnosing why the wrong tools make it worse, then building the three-part infrastructure that constitutes the right tool, then demonstrating the judgment the system requires at its hardest moments: the end of the experience, the boundary the Sherpa must not cross, and the advisor conversation that the system makes possible.
ActChaptersWhat it does
Act One — The Problem1–2Establishes the design failure; names the wrong model; introduces the framework
Act Two — The Infrastructure3–10Builds the complete Sherpa system: taxonomy, experience map, living journal, MVAL, failure documentation, Sherpa Before and During
Act Three — The Synthesis11–13Refiguration protocol; the thesis boundary; the advisor shift
Outside arc — Demonstration14–18Five domain field guides; the arc running under domain-specific constraints

Transition conditions

Act One → Act Two

The practitioner holds three commitments: the developmental gap is a design failure (not a student failure), AI's role is categorically a Sherpa relationship (not a teaching relationship), and they are willing to challenge a student's placement preference on developmental grounds. Without these three, the Act Two tools are misused.

Act Two → Act Three

The practitioner can produce a developmental profile, design a living journal calibrated to that profile, configure and deploy Sherpa Before and During, and distinguish a Sherpa response that supports reflection from one that substitutes for it. Without these, Chapter 12 (the thesis chapter) lands as a warning, not an argument.

Navigation note for readers: Chapters 1–13 build the complete foundational argument and the full Sherpa infrastructure — read in sequence for professional development, staff onboarding, or graduate coursework. Chapters 14–18 are fully self-contained domain field guides — enter at the chapter written for your role. A Construct Quick Reference at the opening of each field guide provides the operational definitions you need to begin immediately.
Section 4

Chapter-by-Chapter Specifications

Part One · Chapters 1–2

Foundations: The Argument

Sequential read. Two chapters. Makes the case and gives the diagnostic framework.

Chapter 1 The Gap: Why Having an Experience Is Not the Same as Learning from One Act One · Practitioner-facing
The practitioner diagnoses the design failure that converts developmental potential into resume lines — and names the 200-student structural constraint that no single advisor has ever been able to solve alone.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-1.1AnalyzeDistinguish between an experience that produces a resume line and one that produces practical wisdom — by naming the specific infrastructure conditions that determine which outcome occurs.Yes
LO-1.2AnalyzeDiagnose the reflection gap in their own program — identify where the infrastructure breaks down and what students are losing.Yes
LO-1.3UnderstandArticulate why classroom AI tools are the wrong model for experiential learning, in terms specific enough for a conversation with a dean.Yes
LO-1.4ApplyName the 200-student problem and connect it to a specific failure they have observed in their own practice.Yes
Opening Case

The Boston co-op student — six months, well-evaluated, Excel skills instead of judgment. The recognition case. Thirty end-of-semester reflections, two that are different, one advisor who recognizes the difference and cannot produce more of it.

Worked Example Domain

University co-op, engineering discipline.

Bridge to Ch. 2 "Naming the failure is not enough. To build the solution, we need a framework precise enough to design against..."
Chapter 2 The Framework: Ricoeur, Kolb, and the Three Movements of Experiential Learning Act One · Practitioner-facing Spiral — introduces Ricoeur
The practitioner maps a student's experience arc onto Ricoeur's three phases and identifies where in Kolb's cycle their program infrastructure is strongest and where it breaks down.
Author briefing — dropout risk chapter. Student narrative precedes framework name. Theory earns its place through recognition, not instruction. Act One transition condition must be drafted with care before editorial review (OQ-004).
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-2.1ApplyMap a specific student's experience arc onto Ricoeur's three phases.Yes
LO-2.2AnalyzeIdentify where in Kolb's four-stage cycle their program infrastructure breaks down.Yes
LO-2.3ApplyExplain the refiguration concept to a student in motivating language — without using Ricoeur's terminology.Yes
LO-2.4CreateDesign a reflection prompt for each of Ricoeur's three phases.Yes
Opening Case

A nursing student who said "I just knew what to do" after a code — and could not articulate the knowing that saved a patient's life. Prefiguration / configuration / refiguration named through her story before the terms appear.

Worked Example Domain

Study abroad, liberal arts college — reflection essays rich with description, thin on analysis; director reframes "not developmentally ready" as "asked the wrong question."

Practitioner test (OQ-014): Nursing student narrative to be tested with 3 practitioners before editorial review — all must say "I know this student."
Bridge / Act One → Act Two transition Act One transition condition stated explicitly before the reader turns to Chapter 3.
Part Two · Chapters 3–5

The Experience Map

Sequential in professional development context; re-enterable by task.

Chapter 3 The Taxonomy: Profiling What a Student Needs to Develop Act Two · Practitioner-facing
The practitioner applies the seven-tier taxonomy to produce a developmental profile — the information no interest inventory provides and no placement decision should be made without.
Most load-bearing chapter in the book. Its absence degrades the entire system. Chapter 3's final exercise must produce a working developmental profile — Chapter 4 opens by using one.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-3.1ApplyApply the seven-tier taxonomy to profile a specific student — naming current strengths and capacity gaps.Yes
LO-3.2AnalyzeIdentify what a standard interest inventory reveals and what it conceals about developmental needs.Yes
LO-3.3AnalyzeDistinguish between a student who is underdeveloped in a capacity and one who has never been exposed to the conditions that develop it.Yes
LO-3.4CreateDesign a profiling conversation that surfaces developmental gaps a student would not self-report on a form.Yes
Opening Case

Two students, same major, same GPA, same expressed interest — interest inventory produces identical recommendations; the taxonomy produces a profile that reveals why they are not the same.

Worked Example Domain

University co-op, business discipline — second-cycle student whose performance review said "excellent" and whose developmental profile said "half-formed."

Bridge to Ch. 4 "The developmental profile names what the student needs to build. The next question is: which experience builds it?"
Chapter 4 The Experience Map: Matching Developmental Need to Placement Type Act Two · Hybrid (practitioner designs; student receives)
The practitioner builds a structured placement recommendation — an experience map — that translates a developmental profile into a specific placement choice with reasoning the student can understand and the advisor can defend.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-4.1CreateBuild an experience map for a specific student.Yes
LO-4.2ApplyMake the case to a student for a placement they would not have chosen for themselves — using their developmental profile as the argument.Yes
LO-4.3EvaluateEvaluate two placement options against a student's developmental profile with explicit trade-off analysis.Yes
LO-4.4AnalyzeIdentify placement recommendation patterns driven by availability rather than developmental fit — and name the cost.Yes
Opening Case

The London case — US student whose developmental profile indicates London but who wants Boston. The advisor has the experience map. Does the advisor have the language?

Worked Example Domain

Study abroad program — the London case documented as the experience map in action.

Bridge to Ch. 5 "The experience map tells the student where to go and why. But arriving at the right place is not enough. What the student pays attention to when they get there determines what they bring back."
Chapter 5 Pre-Experience Preparation: The Question to Carry In Act Two · Pivot chapter · Hybrid
The practitioner designs a pre-experience preparation protocol that translates the developmental profile into one or two focused developmental questions — and configures the Sherpa for the work before the experience begins.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-5.1CreateDesign a pre-experience preparation protocol that translates the developmental profile into focused developmental questions.Yes
LO-5.2AnalyzeDistinguish between orientation and developmental preparation.Yes
LO-5.3ApplyBrief a student on what the Sherpa will be watching for — in a way that increases attentiveness without producing performance anxiety.Yes
LO-5.4ApplyConfigure the Sherpa for a specific student's pre-experience profile.Yes
Opening Case

Two students, same London employer, different preparation — one leaves with a checklist, one leaves with a question. Six months later, different journals.

Worked Example Domain

Clinical placement, social work — second-year student whose focused question is "Where do I notice that I am managing my own distress rather than being present to the client's?"

Bridge to Part Three "The preparation is complete... What is not yet running is the companion that reads the journal, recognizes the patterns, and asks the questions that turn documentation into development."
Part Three · Chapters 6–8

The Living Journal

Sequential in professional development context; re-enterable as implementation reference.

Chapter 6 The Living Journal: What It Is and Why Visual Matters Act Two · Student-facing infrastructure
The practitioner designs a living journal structure that captures the texture of lived experience — visual, integrated, honest — and understands why the visual dimension is developmental, not decorative.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-6.1AnalyzeDistinguish a living journal from current documentation formats — naming what it captures that current formats do not.Yes
LO-6.2ApplyExplain the developmental function of visual documentation to a student who has never kept a visual journal.Yes
LO-6.3CreateDesign a living journal structure for a specific deployment context.Yes
LO-6.4EvaluateEvaluate a sample student journal against the living journal criteria.Yes
Opening Case

A study abroad student's text journal vs. the photograph she took in the Makola market — and the analytical precision the image held that the text did not produce until she was asked about it.

Worked Example Domain

Electrical trades apprenticeship — the panel sketch with the error circled, the question about the journeyman's hands.

Bridge to Ch. 7 "Documentation without structure produces narrative, not analysis. The next chapter introduces the MVAL protocol..."
Chapter 7 The MVAL Protocol: Structuring Reflection for Practical Wisdom Act Two · Both-facing
The practitioner applies the MVAL protocol to structure student journal entries into analysis — and teaches the protocol to students in a way that produces internalization rather than mechanical compliance.
Author briefing (OQ-009): Must position MVAL as an adaptation of a broader class of structured reflection protocols — not as a Boyle System advertisement. This framing must be established before contributor assignment.
MVAL Fields

What happened  /  Why it mattered  /  How you responded  /  Environment  /  Results  /  Questions

Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-7.1ApplyApply the MVAL protocol to a specific student entry — producing an analysis of developmental progress and Sherpa probe direction.Yes
LO-7.2ApplyTeach the MVAL protocol to a student in a way that produces internalization.Yes
LO-7.3AnalyzeDiagnose what is missing from a student's MVAL entry and design a Sherpa prompt that addresses the gap without naming it prescriptively.Yes
LO-7.4CreateAdapt the MVAL protocol for a specific deployment domain.Yes
Opening Case

The client meeting — same event, unstructured entry vs. MVAL-structured entry. The unstructured entry produces a note to self. The MVAL entry produces the question the student will still be thinking about next week.

Worked Example Domain

Corporate early career rotational program — first-year analyst whose "environment" field consistently describes the room rather than the organizational dynamics.

Bridge to Ch. 8 "MVAL gives the student a structure for documenting what happened and why it mattered. But there is one category of event that MVAL alone cannot address — not because the protocol fails, but because the student's instinct is to omit the event entirely."
Chapter 8 Failure as First-Class Artifact: Documenting What Went Wrong Act Two · Both-facing Author briefing
The practitioner designs a failure documentation protocol that creates structural safety for honest reflection — because failures are the primary raw material for the learning that only consequential experience can produce.
Author briefing: This chapter is affirmative, not remedial. Failure documentation is not the medicine you take when things go wrong. It is the practice that determines whether consequential experience produces wisdom.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-8.1CreateDesign a failure documentation protocol with genuine structural safety.Yes
LO-8.2AnalyzeDistinguish a failure entry that produces developmental reflection from one that produces self-criticism without analysis — and design Sherpa prompts that move students from the latter to the former.Yes
LO-8.3EvaluateIdentify program design features that discourage failure documentation and propose one structural change.Yes
LO-8.4AnalyzeUse a student's failure documentation to identify a developmental pattern not visible from success entries alone.Yes
Opening Case — Primary documented failure case

A senior co-op student with two journals — the official one (the highlight reel) and the personal notebook (the developmental record). He kept two because the official one was not safe for the honest material. That is not a student failure. That is a program design failure.

Worked Example Domain

Clinical placement, nursing — the medication error documented procedurally in the official journal, developmentally in the private section.

Bridge to Part Four "The infrastructure is built... What is not yet running is the companion that reads the journal, recognizes the patterns, and asks the questions that turn documentation into development."
Part Four · Chapters 9–13

The AI Sherpa in Practice

Sequential in professional development context; re-enterable as deployment reference. Five chapters covering Act Two deployment (9–10) and Act Three synthesis (11–13).

Chapter 9 The Sherpa Before: Profile, Map, and Focused Attention Act Two · Practitioner-facing First deployment chapter
The practitioner configures the Sherpa for a specific student's pre-experience profile — translating the developmental map into Sherpa parameters before the experience begins.
⚑ OQ-013 (Urgent): "Getting Started" minimum viable deployment note must be present in this chapter — two pages, required for the publisher proposal. This is the acquisitions editor's primary question. Lead author writes before Chapter 9 first draft.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-9.1ApplyConfigure a Sherpa for a specific student's pre-experience profile — translating the experience map into Sherpa parameters.Yes
LO-9.2CreateDesign the pre-experience Sherpa conversation sequence for a student entering a high-stakes placement.Yes
LO-9.3AnalyzeDistinguish between a Sherpa that prepares a student for an experience and one that reduces the experience's developmental challenge.Yes
Opening Case

The practitioner who configured the same generic Sherpa for 200 students and found it producing the same three prompts for everyone — and the specific configuration that changes that.

Worked Example Domain

Northeastern co-op, business analytics — second-cycle student, Tier 5 and Tier 6 focus, pattern recognition flags for attribution patterns.

Bridge to Ch. 10 "The Sherpa is configured. The experience has begun... The question now is: what does the Sherpa do when a journal entry arrives that tells it something important is happening?"
Chapter 10 The Sherpa During: Companion, Not Coach Act Two → Act Three threshold · Both-facing Author briefing
The practitioner deploys the Sherpa's core during-experience function — pattern recognition and Socratic question — and masters the distinction between a Sherpa response that supports reflection and one that substitutes for it.
Author briefing: The worked example is load-bearing. The London student's Week 3 entry and the Sherpa's single-sentence response is the moment the "question not answer" principle becomes operational. If this example is generic, the principle stays theoretical.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-10.1CreateDesign a Sherpa prompt sequence for a student whose journal entries suggest avoidance of a developmental challenge.Yes
LO-10.2AnalyzeDistinguish between a Sherpa response that supports reflection and one that substitutes for it.Yes
LO-10.3ApplyApply the three core Sherpa prompts — What surprised you? What did you commit to? What would you do differently? — to a specific student entry.Yes
LO-10.4EvaluateIdentify the point in a student's experience arc where the Sherpa should escalate to a human advisor.Yes
Opening Case

Same journal entry, two Sherpa responses. Response A gives advice (three sentences). Response B asks "What did you start to say?" One produces strategy. One produces the judgment the student withheld.

Worked Example Domain — Load-bearing

Study abroad, the London student — Week 3, the team meeting where she went invisible, the Sherpa's one-sentence prompt, and Week 3 Entry 8 written two days later.

Bridge / Act Two → Act Three transition "The experience is ending... Most of the time that reflection will produce a summary. Occasionally — in programs with the right infrastructure — it will produce something different."
Chapter 11 The Sherpa After: Refiguration and the Capstone Narrative Act Three · Both-facing Ricoeur spiral return
The practitioner designs the post-experience Sherpa sequence that guides a student through Ricoeur's third phase — from the raw material of the journal to a coherent narrative of what changed and why.
Domain note (OQ-008): Chapter 11 opening must use a corporate early career domain — clinical domain is at its three-case cap. Character Thread D (the business junior) is the primary longitudinal case.
Spiral opening required: "Chapter 2 introduced Ricoeur's three phases as a framework for understanding what is happening when an experience becomes formative. This chapter asks a harder question: how do you design the conditions that make refiguration happen reliably, rather than waiting to see if it happens on its own?"
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-11.1CreateDesign a post-experience Sherpa sequence that guides a student through Ricoeur's refiguration phase.Yes
LO-11.2EvaluateEvaluate a student's capstone reflection against the refiguration criteria — distinguishing integration from summary.Yes
LO-11.3CreateDesign a capstone reflection protocol for their specific deployment context.Yes
Opening Case — Character Thread D

Corporate early career domain. "I spent the first two months of this placement reporting what happened in rooms. In the third month I started reporting what I did in rooms."

Capstone Criteria

Specific journal evidence  /  Self-revision  /  Forward projection  /  Unresolved questions

Bridge to Ch. 12 "The student has refigured... And somewhere in that process — in the before, the during, or the after — there were moments where the Sherpa could have done something it shouldn't have."
Chapter 12 What the Sherpa Cannot Do: The Boundary That Makes Development Possible Act Three · Both-facing Thesis chapter
The practitioner identifies and corrects Sherpa dependency — and understands why the boundary between guidance and doing is not a limitation of the tool but the condition that makes the developmental process work.
Author briefing (fourth and final): This chapter is written as argument, not disclaimer. The boundary is not a risk to manage. It is the design principle that makes the system work. Every sentence defends that claim. Written by the lead author, not a contributor. First chapter reviewed by the editor after drafting.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-12.1AnalyzeIdentify Sherpa dependency — recognize journal entry patterns and student behaviors signaling avoidance of judgment rather than development of it.Yes
LO-12.2ApplyRedesign a Sherpa prompt that is producing dependency — transform a response that answers into a question that requires the student to answer.Yes
LO-12.3ApplyArticulate the boundary to a student who is frustrated by the Sherpa's refusal to give answers.Yes
LO-12.4EvaluateEvaluate their deployed Sherpa configuration against the dependency risk criteria.Yes
Opening Case — Primary documented failure case

The clinical rotation student whose entries became shorter and more question-shaped until she was writing to get an answer rather than to do analysis. "The Sherpa keeps asking me questions instead of helping me." Her frustration is honest. Her misunderstanding is architectural.

Five Dependency Patterns

Entry length decreasing  /  Entries question-shaped  /  MVAL "questions" field dominant  /  Emotional escalation at Sherpa questions  /  Waiting rather than deciding

Bridge to Ch. 13 "The Sherpa is doing what it was designed to do... What remains is the practitioner's own role in this system — not the Sherpa's role, but the human advisor's."
Chapter 13 The Advisor Shift: From Gap-Filling to Strategy Act Three — Arc resolution · Practitioner-facing
The practitioner redesigns their advising protocol for a Sherpa-supported context — and discovers that the advisor role, freed from scaffolding work the Sherpa now carries, becomes more powerful, not smaller.
Closing note: Chapter 13 is the arc resolution. The liberation reframe must be structural, not inspirational — demonstrated through the redesigned conversation protocol and the caseload management system, not through aspirational language.
Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-13.1CreateRedesign their advising conversation protocol for a Sherpa-supported context.Yes
LO-13.2AnalyzeDistinguish between a gap-filling advising conversation and a strategic one.Yes
LO-13.3ApplyUse the Sherpa's journal pattern summary as the opening document for an advising conversation.Yes
LO-13.4CreateDesign a caseload management protocol for a Sherpa-supported advising context.Yes
Opening Case

The same co-op coordinator with the same student across two cycles. First cycle: "what happened, what did you learn." Second cycle with the Sherpa: "the Sherpa flagged three recurring patterns. The one I want to talk about is this one. Tell me what you think it means for where you go next."

Worked Example Domain

Co-op program — Character Thread D's second cycle debrief, using the Sherpa's pattern summary as the opening document.

Bridge to Part Five "The argument is complete... What remains is the demonstration — not the proof, which is already made, but the showing: what the full system looks like when it is running in five different domains."
Part Five · Chapters 14–18

The Field Guides

Outside the arc. Domain demonstration. Fully self-contained. Enter at your chapter.

Shared structure — all five field guide chapters
  • "If you are starting here" navigation note
  • Construct Quick Reference (six constructs, one page, identical closing line)
  • Domain context (2–3 pages — specific enough for practitioner recognition in paragraph 1)
  • Full system deployment guide (pre-experience / during / after)
  • Domain-specific failure modes (3–5)
  • Stakeholder section (includes at least one stakeholder conflict)
  • Implementation checklist (12–18 items, binary completion criteria)
  • Three domain-specific assessable exercises
  • Further resources (5–8 annotated sources)
⚑ OQ-005 (Open): Construct Quick Reference closing line must be identical across all five Part Five chapters — must be finalized before Part Five drafting begins.
Chapter 14 The Co-op Coordinator's Field Guide Field Guide · Self-contained
Full system deployment for six-month university co-op placements — including multi-cycle developmental arcs, employer partner relationships, and the Northeastern model as the flagship case.
Domain Context

Six-month placements, multi-cycle structure, employer evaluation integration, Northeastern model as benchmark. The specific challenge: employer is a stakeholder in performance evaluation; journal privacy must be designed, not assumed.

Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-14.1ApplyDeploy the full Sherpa infrastructure for a six-month co-op placement.Yes
LO-14.2CreateDesign a multi-cycle developmental arc across two or three placements.Yes
LO-14.3ApplyAdapt the Sherpa configuration for employer relationship complexity.Yes
LO-14.4EvaluateEvaluate developmental outcomes of a co-op cohort using journal pattern data.Yes
LO-14.5ApplyMake the case to an employer partner for the living journal and Sherpa infrastructure.Yes
Flagship Case — Character Thread D

Three-cycle arc, Northeastern co-op model, first cycle abroad through senior-year strategy placement.

Domain-Specific Failure Modes
  • Employer-visibility suppression of failure documentation
  • Multi-cycle profile drift (each advisor starts from scratch)
  • The return-offer trap (strong performance review concealing developmental plateau)
Stakeholder conflict: Employer's evaluation interest vs. student journal privacy — explicitly designed and resolved.
Chapter 15 The Study Abroad Advisor's Field Guide Field Guide · Self-contained
Full system deployment for international placements — with specific configuration for cross-cultural disorientation as a developmental resource and re-entry as a designed protocol, not an afterthought.
Domain Context

Highest density of Tier 3 developmental opportunity; highest rate of unrealized potential. The specific challenge: disorientation is a developmental resource, not a logistical problem. Re-entry is the most underdesigned phase.

Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-15.1ApplyDeploy the full Sherpa infrastructure for a study abroad placement with cross-cultural disorientation configuration.Yes
LO-15.2CreateDesign an experience map that makes the developmental case for a specific international placement.Yes
LO-15.3ApplyConfigure Sherpa prompts for the disorientation phase.Yes
LO-15.4CreateDesign a re-entry protocol that prevents developmental gains from dissipating in the transition home.Yes
LO-15.5EvaluateEvaluate a study abroad student's journal for evidence of cross-cultural capacity development — distinguishing observation of cultural difference from genuine perspective-taking.Yes
Flagship Case — Character Thread C

The London student, full arc from experience map through refiguration.

Domain-Specific Failure Modes
  • Disorientation managed as logistical problem rather than developmental resource
  • Re-entry without designed integration (refiguration abandoned at the airport)
  • The tourist journal (rich description, zero perspective-taking)
Chapter 16 The Clinical Placement Director's Field Guide Field Guide · Self-contained
Full system deployment in the highest-stakes experiential learning context — with specific design for failure documentation under liability constraints, clinical error processing, and professional identity formation under evaluation pressure.
⚑ OQ-006 (Critical): Mandatory reporting boundary language requires institutional legal review before publication. Privacy boundary template must not be released before legal review is complete. Long lead time — initiate now.
Domain Context

Nursing, medicine, allied health, social work, law. Errors have real consequences. Failure documentation carries liability. Student is being evaluated for professional licensure. The specific challenge: clinical errors are simultaneously the most important developmental artifacts and the most likely to be suppressed or documented defensively.

Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-16.1ApplyDeploy the full Sherpa infrastructure in a clinical placement context with failure documentation safety design.Yes
LO-16.2CreateDesign a failure documentation protocol for a clinical context that satisfies reflection and does not conflict with mandatory reporting.Yes
LO-16.3ApplyConfigure Sherpa prompts for a student processing a clinical error or near-miss.Yes
LO-16.4AnalyzeDistinguish between a student developing clinical judgment and one developing clinical compliance — using journal entries as evidence.Yes
LO-16.5CreateAdapt the capstone reflection protocol for clinical professional identity formation.Yes
Flagship Longitudinal Case — Character Thread B

The nursing student from Chapter 2, full clinical arc through professional identity formation.

Domain-Specific Failure Modes
  • Mandatory reporting conflict with private documentation
  • Clinical error suppression under evaluation pressure
  • The compliance-not-judgment development pattern
Chapter 17 The Workforce Development Coordinator's Field Guide Field Guide · Self-contained
Full system deployment in trades and apprenticeship contexts — with specific adaptations for embodied skill development, the master-apprentice relationship, and the living journal as a visual document of physical learning.
Author briefing: The trades chapter is not simplified content for less-educated learners. Trades apprentices develop expert judgment in domains requiring both physical precision and conceptual mastery. The adaptation is translation, not simplification.
Domain Context

Electricians, plumbers, HVAC, welding, construction. The primary learning is in the hands. The master-apprentice relationship is the oldest Sherpa relationship in human history. The specific challenge: a text-only journal is inadequate for capturing embodied skill development — the visual dimension is the primary documentation mode, not an enhancement.

Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-17.1ApplyDeploy the full Sherpa infrastructure in a trades apprenticeship context with embodied skill adaptations.Yes
LO-17.2CreateDesign a living journal format appropriate for embodied skill development.Yes
LO-17.3ApplyConfigure Sherpa prompts for the master-apprentice relationship.Yes
LO-17.4ApplyMake the case for Sherpa infrastructure to a trades program administrator skeptical of documentation approaches.Yes
LO-17.5CreateAdapt the experience map for workforce development contexts.Yes
Flagship Case — Character Thread E

The electrical apprentice, full deployment from taxonomy profile through multi-year apprenticeship arc.

Theoretical connection: The Pirsig tradition (Zen and the Art of Motorcycle Maintenance) and the AI and the Art of Motorcycle Maintenance companion volume — quality as a relationship between the craftsperson and the work.
Chapter 18 The Corporate Early Career Program Manager's Field Guide Field Guide · Self-contained
Full system deployment for rotational programs and first assignments — with specific adaptations for organizational culture navigation, the student-to-professional transition, and the dual-use refiguration document.
⚑ OQ-007 (Critical): Dual-use refiguration document requires explicit program policy and consent framework design before production begins. The tension between employee ownership and program data interest must be named honestly — not resolved by clever document design.
Domain Context

Structured rotational programs, first assignments, transition from student to professional. The specific challenge: organizational culture navigation is the primary developmental variable and the thing most likely to be documented around rather than through.

Learning Outcomes
IDBloom'sLearning outcomeAssessable
LO-18.1ApplyDeploy the full Sherpa infrastructure in a corporate early career context with organizational culture navigation configuration.Yes
LO-18.2CreateDesign an experience map for a corporate rotational program.Yes
LO-18.3ApplyConfigure the Sherpa for organizational culture navigation without producing political risk.Yes
LO-18.4CreateAdapt the refiguration protocol for a dual-use corporate context.Yes
LO-18.5EvaluateEvaluate developmental outcomes of an early career cohort using journal pattern data and produce a program-level recommendation.Yes
Flagship Case

Corporate rotational analyst — organizational culture as the developmental variable that no case study could have taught.

Domain-Specific Failure Modes
  • Culture navigation documented around rather than through
  • Dual-use document eroding employee developmental ownership
  • Rotation sequence optimized for organizational exposure rather than developmental arc
Section 5

Out of Scope

ItemReasonAcknowledged in
Grading and assessment of reflective journalsUndermines the thesisPreface
Equity and access in experiential learningDifferent book — companion volumePreface
Disability-inclusive designOutside author expertise for this editionPreface
Multilingual and international student contextsTechnology-dependent exclusionCh. 15 sidebar
AI ethics frameworkHandled through design, not standaloneCh. 1 or preface
Classroom AI tools and content deliveryExplicitly rejectedPreface redirect
Platform-specific implementation guidesPlatform-agnostic by designOQ-010 audit
Research methodology for studying Sherpa effectivenessDifferent readerResearch gap acknowledgment
Student-facing instruction in using the SherpaDifferent bookCompanion guide opportunity
Longitudinal outcome researchDoes not yet exist at scaleContested claims acknowledgment
Generative AI as student writing toolDifferent domainCh. 12 dependency section
Institutional policy and compliance frameworksChanging too rapidlyPreface + OQ-010
Two visible second books: a research and evidence base companion monograph (3–5 years post-publication) and an equity, access, and inclusive design extension volume (higher priority — companion volume in development, noted in preface).
Section 6

Market Positioning

Primary positioning: The only practitioner handbook at the intersection of experiential learning and AI — not AI for classroom delivery, but AI as a developmental companion for students in consequential real-world experiences.

Comparable textWhat it doesWhy this book instead
KolbDescribes the cycleThis book builds the infrastructure to make it reliable
SchönDescribes what experts doThis book develops that capacity in students at scale
KuhProves experiential learning worksThis book addresses why it sometimes doesn't
Eyler & GilesIdentifies reflection quality as the mediating variableThis book produces it
MollickAddresses classroom AIThis book addresses the application Mollick does not reach

Primary adoption channel

Institutional staff development budget — an experiential learning director deploying this as a professional development curriculum for their team.

Secondary channels

Individual practitioner purchase through conference sales; graduate course adoption; corporate talent development programs.

Section 7

Supplementary Materials

FeaturePriorityStatus
Two-anatomy chapter structure enforcedEssentialSpecified
Five Part Five field guidesEssentialDocumented
Construct Quick Reference (Part Five)EssentialTemplate specified — OQ-005 open
Facilitator guides (13 Type A chapters)EssentialTemplate specified
Implementation checklists (5 Part Five chapters)EssentialTemplate specified
MVAL reference card (downloadable)ImportantReady for design post-manuscript
Experience map template (downloadable)ImportantReady for design post-manuscript
Sherpa configuration template (downloadable)ImportantReady for design post-manuscript
Capstone reflection protocol (downloadable)ImportantReady for design post-manuscript
Compiled instructor manualValuableWithin 90 days of publication
Slide decks (reduced set, 5 slides/session)ValuableWithin 6 months of publication
Failure documentation templateValuableBlocked — OQ-006 legal review
Section 8

Open Questions Log

Priority action items before anything else: OQ-013 (write the "Getting Started" note — two pages, required for the publisher proposal) · OQ-012 (create character continuity sheets for B, C, D, E — required before contributor recruitment) · OQ-006 (initiate legal review for Chapter 16 mandatory reporting language — long lead time, start now).
OQ-006CriticalChapter 16 mandatory reporting language — legal review required
Legal liability risk. Chapter 16 mandatory reporting boundary template cannot ship before institutional legal review. Owner: Author + publisher legal. Failure documentation template for supplementary materials is blocked pending this review.
OQ-007CriticalChapter 18 dual-use refiguration document — employee consent framework required
Employee consent and ownership framework required before production begins. The tension between employee developmental ownership and program talent development data must be named honestly — not resolved by clever document design. Owner: Author.
OQ-012UrgentCharacter continuity sheets for B, C, D, E — required before contributor recruitment
Characters B–E appear across multiple chapters and contributors. Continuity sheets must be created by the lead author (not volunteer) before first contributor assignment. Without this, character consistency across chapters cannot be guaranteed.
OQ-013Urgent"Getting Started" minimum viable deployment note — required for publisher proposal
Two pages. This is the acquisitions editor's primary question. Must be written by the lead author before Chapter 9 first draft. Practitioners cannot identify a deployment path after Chapter 9 without it.
OQ-003OpenAct Two bridge language — [Author to refine] drafts
Chapter bridges are draft placeholders. Must be refined before editorial review. Owner: Author.
OQ-004OpenChapter 2 closing transition condition — load-bearing for Act Two
Must be drafted with care before Chapter 2 editorial review. Owner: Author.
OQ-005OpenConstruct Quick Reference closing line — must be identical across all five Part Five chapters
Must be finalized before Part Five drafting begins. Owner: Author.
OQ-008OpenChapter 11 domain substitution — clinical domain at three-case cap
Substitute corporate early career domain for Chapter 11 opening. Character Thread D is the designated primary longitudinal case. Owner: Author.
OQ-009OpenChapter 7 MVAL framing — not a Boyle System advertisement
Must position MVAL as an adaptation of a broader class of structured reflection protocols before contributor assignment. Owner: Author.
OQ-010OpenPlatform-agnostic language audit — named AI products tie shelf life to vendors
Named AI products in main text tie shelf life to vendor release cycles. Audit required before final manuscript submission. Owner: Author + editor.
OQ-011OpenEquity acknowledgment language — preface requires practitioner input
Preface must acknowledge equity gap with input from community college practitioner. Owner: Author + community college practitioner.
OQ-014OpenChapter 2 narrative practitioner test
Nursing student narrative to be tested with 3 practitioners before editorial review — all must say "I know this student." Owner: Author.
OQ-015OpenSecond edition rapid cycle plan for AI capability claims
Negotiate rapid edition cycle rights before contract signing. Owner: Author + editor.
OQ-001ResolvedPart Four chapter count — five chapters confirmed
Resolved at /l3.
OQ-002ResolvedChapter 12 author briefing — incorporated four times
Incorporated across /l1, /l2, /c1, /g1.
The AI Sherpa: A Practitioner's Guide for Experiential Learning — TIC TOC v1.0 · 2026-03-21
18 chapters across 5 parts. 13 open questions active. 2 critical (OQ-006, OQ-007). 2 urgent (OQ-012, OQ-013). Pending /g2 audit and author review before production begins.