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.
Experiential learning is the most powerful developmental tool in higher education. It is also the most consistently under-realized. Students complete six-month placements, semester abroad programs, clinical rotations, and trades apprenticeships and return with highlight reels rather than developed judgment — not because the experiences lacked developmental potential, but because nobody built the infrastructure to convert that potential into practical wisdom.
The infrastructure gap has a structural cause: a single co-op coordinator cannot carry 200 students' developmental arcs simultaneously. AI closes that gap. But only if it is the right kind of AI, deployed in the right relationship. Every tool being marketed to experiential learning programs right now was designed for a classroom. A student in a co-op does not need a teacher. They need a Sherpa.
The three phases
Before the experience begins. Developmental taxonomy, experience map, and the focused question the student carries in — the question that makes them pay attention to the right things when they get there.
Throughout the experience. A living journal structured by the MVAL protocol. An AI companion that reads the journal, recognizes developmental patterns, and asks the questions that move the student from description to reflection — without ever providing the answers.
After the experience ends. Ricoeur's refiguration phase: not a summary of what happened, but a coherent narrative of what changed and why — a story the student can tell and build from.
Who this book is for
This book is for experiential learning professionals who already know that some students extract enormous developmental value from placements while others complete the same experience and learn almost nothing — and who have always suspected the difference is not about the student.
What this book assumes
You know Kolb's four-stage cycle. You have reflection frameworks and debrief protocols. You know your institution's placement infrastructure and constraints. You have encountered the Excel modeling student — by different name, in different domain — and recognized the design failure underneath her answer.
What this book does not assume
Any familiarity with AI systems. Any technical background. The book treats AI tools as infrastructure — the same way you treat a learning management system. The Sherpa is configured in conversation; no code, no platform expertise required.
What this book actively dismantles
The assumption that the same experience works for every student who wants it. The assumption that AI gives every student the same generic response. The assumption that the advisor role shrinks when AI takes on the scaffolding. It does not shrink. It becomes more powerful — freed from the repetitive scaffolding work the Sherpa carries, the advisor can focus entirely on the interpretive and strategic conversations only a human who knows the student can have.
What you will leave with
- A complete Sherpa infrastructure deployable in your program — developmental taxonomy, experience map, living journal structure, MVAL protocol, Sherpa configuration for before and during, refiguration protocol for after.
- A redesigned advising practice: the advisor conversation that opens not with "what did you learn?" but with "the Sherpa flagged three recurring patterns — the one I want to talk about is this one." The conversation that is possible only when the scaffolding has already happened.
- A field guide written for your specific deployment context — co-op, study abroad, clinical placement, trades apprenticeship, or corporate early career program — with domain-specific failure modes, stakeholder conflicts, and an implementation checklist that gets the system running.
The MVAL protocol
The argument, stated directly
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. Because AI carries the reflection infrastructure that no single human advisor could carry for 200 students simultaneously, freeing the advisor to do the irreducibly human work: the strategic conversation, the developmental challenge, the relationship that makes refiguration possible.
How the book is structured
The book runs in three acts plus a set of fully self-contained field guides — one for each deployment context.
Act One establishes the design failure and gives the diagnostic framework. Theory earns its place through recognition, not instruction.
The Gap: Why Having an Experience Is Not the Same as Learning from One
The Boston co-op student. Six months, well-evaluated, Excel skills instead of judgment. The 200-student structural constraint that no single advisor has ever been able to solve alone. And the central diagnostic: classroom AI tools arrive at the wrong address when deployed in experiential learning contexts, because the relationship they are built for is teaching, and the relationship experiential learning requires is something categorically different.
The Framework: Ricoeur, Kolb, and the Three Movements of Experiential Learning
The nursing student who said "I just knew what to do" after a code and could not articulate the knowing that saved the patient. Prefiguration, configuration, refiguration — named through her story before the terms appear. Kolb's four-stage cycle mapped against where most program infrastructure actually breaks down. The Act One transition condition stated explicitly: before turning to Chapter 3, the practitioner holds three commitments — the developmental gap is a design failure, AI's role is a Sherpa relationship, and they are willing to challenge a student's placement preference on developmental grounds.
Act Two builds the complete Sherpa system piece by piece — from developmental taxonomy through the Sherpa During deployment.
The Taxonomy: Profiling What a Student Needs to Develop
Two students, same major, same GPA, same expressed interest. An interest inventory produces identical recommendations. The developmental taxonomy produces a profile that reveals they are not the same. The seven-tier taxonomy applied to a specific student — naming current strengths and the capacity gaps that no standard assessment surfaces. This chapter's final exercise produces a working developmental profile. Chapter 4 opens by using one.
The Experience Map: Matching Developmental Need to Placement Type
The London case: a US student whose developmental profile indicates London but who wants Boston. The advisor has the experience map. Does the advisor have the language? The experience map translates a developmental profile into a specific placement recommendation with reasoning the student can understand and the advisor can defend — including the argument for a placement the student would not have chosen for themselves.
Pre-Experience Preparation: The Question to Carry In
Two students, same London employer, different preparation. One leaves with a checklist. One leaves with a question. Six months later, different journals. The pre-experience preparation protocol that translates the developmental profile into one or two focused developmental questions — and configures the Sherpa before the experience begins. The distinction between orientation and developmental preparation, and why conflating them is one of the most common design failures in experiential programs.
The Living Journal: What It Is and Why Visual Matters
A study abroad student's text journal versus 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. The living journal as a fundamentally different document from current portfolio or reflection formats. The developmental function of visual documentation — not decorative but primary, especially in embodied domains.
The MVAL Protocol: Structuring Reflection for Practical Wisdom
Same client meeting, two journal entries. The unstructured entry produces a note to self. The MVAL entry produces the question the student will still be thinking about next week. How to teach the protocol to students in a way that produces internalization rather than mechanical compliance. The corporate analyst whose "environment" field consistently describes the room rather than the organizational dynamics: that is the diagnostic the MVAL makes visible.
Failure as First-Class Artifact: Documenting What Went Wrong
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. Failure documentation is not the medicine you take when things go wrong. It is the practice that determines whether consequential experience produces wisdom.
The Sherpa Before: Profile, Map, and Focused Attention
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. The Sherpa Before translates the developmental profile and experience map into Sherpa parameters before the experience begins: what patterns to watch for, when to escalate to the human advisor. The minimum viable deployment note: the two-page entry point for practitioners who need to get something running before they finish the book.
The Sherpa During: Companion, Not Coach
Same journal entry, two Sherpa responses. Response A gives advice. Response B asks "What did you start to say?" One produces strategy. One produces the judgment the student withheld. The London student's Week 3 entry — the team meeting where she went invisible — and the Sherpa's one-sentence response. Week 3 Entry 8, written two days later, is a different kind of document. The three core Sherpa prompts, the pattern recognition that deploys them, and the escalation threshold that brings the human advisor back in.
Act Three addresses the hardest moments: the refiguration protocol, the boundary that makes development possible, and the redesigned advising conversation the full infrastructure makes possible.
The Sherpa After: Refiguration and the Capstone Narrative
Ricoeur's third phase, designed rather than hoped for. How do you design the conditions that make refiguration happen reliably, rather than waiting to see if it happens on its own? The post-experience Sherpa sequence that guides a student from raw journal material to a coherent narrative of what changed. The capstone criteria: specific journal evidence, self-revision, forward projection, unresolved questions. The difference between a capstone that integrates and one that summarizes.
What the Sherpa Cannot Do: The Boundary That Makes Development Possible
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. The boundary between guidance and doing is not a limitation of the tool — it is the condition that makes the developmental process work. Five dependency patterns, the diagnostic for each, and the redesign that converts a Sherpa producing dependency into one producing development.
The Advisor Shift: From Gap-Filling to Strategy
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." The advisor role, freed from scaffolding work the Sherpa now carries, becomes more powerful — not smaller. The redesigned advising conversation protocol and caseload management system for a Sherpa-supported context.
Each field guide is fully self-contained. Enter at your chapter. A Construct Quick Reference provides the operational definitions you need to begin immediately. No need to read the preceding chapters first.
The Co-op Coordinator's Field Guide
Full system deployment for six-month university co-op placements — multi-cycle developmental arcs, employer partner relationships, the Northeastern model as the flagship case. Domain-specific failure modes: employer-visibility suppression of failure documentation; multi-cycle profile drift when each advisor starts from scratch; the return-offer trap where a strong performance review conceals a developmental plateau. Explicit stakeholder conflict: employer evaluation interest versus student journal privacy — designed and resolved.
The Study Abroad Advisor's Field Guide
Full system deployment for international placements — with specific configuration for cross-cultural disorientation as a developmental resource, not a logistical problem, and re-entry as a designed protocol rather than an afterthought. Domain-specific failure modes: disorientation managed rather than developed; the tourist journal rich with observation and empty of perspective-taking; re-entry without integration — refiguration abandoned at the airport.
The Clinical Placement Director's Field Guide
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. Nursing, medicine, allied health, social work, law. The specific challenge: clinical errors are simultaneously the most important developmental artifacts and the most likely to be suppressed or documented defensively. Mandatory reporting boundary language reviewed for institutional compliance before publication.
The Workforce Development Coordinator's Field Guide
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. The text-only journal is inadequate here — the visual dimension is the primary documentation mode, not an enhancement. The trades apprenticeship is the oldest Sherpa relationship in human history; this chapter builds the infrastructure that relationship has always deserved.
The Corporate Early Career Program Manager's Field Guide
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. The specific challenge: organizational culture navigation is the primary developmental variable and the thing most likely to be documented around rather than through. The tension between employee developmental ownership and program talent development data — named honestly, not resolved by document design.