The Knowledge Adventure Club Graph

The Knowledge Adventure Club didn’t come from a single idea. It came from a lot of people - books, collaborators, and experiments that all pointed in the same direction: the best learning structures are small groups working through hard material together, guided by a facilitator who plays Dungeon Master rather than teacher.

These aren’t hypotheticals. Every one of these threads is something we ran at egghead between 2019-2024 with real learners, real money, and real outcomes.

The Foundation: Kathy Sierra’s Badass Framework

Everything starts with Kathy Sierra’s Badass: Making Users Awesome. The core insight: you don’t make a better product, you make a better user.

Sierra’s framework centers on the “compelling context” - the bigger thing the user is trying to be badass at. A camera company isn’t selling cameras, it’s making photographers. The book maps this as a curve: users move from “suck” to “not suck” to “badass” within a compelling context, and your job is to help them make that journey. The key mechanisms are deliberate practice, perceptual exposure to the right examples, and reducing cognitive leaks that drain willpower.

“Kathy Sierra talks about this idea that you’re learning at a higher resolution as you gain expertise. You start at the 35,000 foot view. What you’re actually doing is increasing your resolution as you spiral in on a topic.”

“The Badass approach is having Acquisition and Retention be reframed to not only focus on having people pay us, but to help them make progress in things relevant to them.”

Badass was the first book in the egghead book club. It framed everything that came after: value paths, portfolio clubs, the entire learner-centric strategy.

Value Paths: Samuel Hulick’s Architecture

Samuel Hulick was the primary collaborator on translating Kathy Sierra’s framework into something operational. This was the strategic spine.

“Currently totally obsessed with badass developer portfolio club and how we can leverage the work with Samuel Hulick and value paths into a core strategy for egghead.”

“Confirmed with Samuel Hulick the value paths consulting for Q1 2020 and feeling super fuckin stoked about what we are about to do as a team around badass developer portfolio north star.”

“Samuel Hulick is leading the value paths execution.”

“The biggest takeaway from the call is that value paths and badass developer portfolio club inform one another.”

“Courses are outcome-focused. People don’t wake up excited to watch a course. Egghead videos are valuable but there are no value paths. Frame guardrails that put students into a path. Customize the outcome.”

Hulick brought rigor. He was “less prone to assumption” and wanted to “prove the value and the process as an effective tool.” Maggie Appleton worked with Hulick on Miro boards mapping the value paths visually. The sorting hat surveys fed data into path design.

Value paths gave the system its directional structure - learners aren’t browsing content, they’re moving toward outcomes.

Understanding by Design: The Curriculum Engine

Wiggins and McTighe’s Understanding by Design was the system underneath everything. The book’s central argument: “Nowhere does the backward design process depart more from conventional practice than at Stage 2. Instead of moving from target to teaching, we ask, What would count as evidence of successful learning? Before planning our instructional activities.” Most curriculum design starts with activities. UbD starts with what understanding looks like, then designs assessment, then plans instruction.

Three stages, applied to every course, every club, every portfolio project:

Stage 1: Define big ideas, essential questions, goals, knowledge, and skills. Work backwards from the desired understanding.

Stage 2: Design performance tasks using the GRASPS framework (Goal, Role, Audience, Situation, Product, Standards). Assessment as authentic work, not tests.

Stage 3: Plan the learning experiences - the actual lesson sequence.

“At egghead we use Understanding by Design as a system for developing curriculum. This curriculum is composed of three distinct stages.”

“Designing a club is an Understanding by Design exercise at the core.”

“The developer portfolio project club is designed using the principles from Understanding by Design.”

“We’ve got the in house design skills needed to make this a reality very early in 2021. The first step is instructional design and applying Understanding by Design to craft a badass developer portfolio club.”

Applied to the Badass Developer Portfolio Club, the three stages looked like this:

Stage 1 (goals): What does standing out actually look like? A developer who researched their target companies, understood the problems those companies are trying to solve, and shipped a project that demonstrates it. That’s the understanding we’re building toward.

Stage 2 (assessment): The portfolio project brief, written with GRASPS. Goal: land a job at a company building with modern e-commerce tech. Role: developer. Audience: engineering team at a Series A startup. Situation: you have six weeks and a cohort of peers. Product: a shipped project with a published case study. The performance task is the assessment — not a quiz, not a rubric, a real thing you built.

Stage 3 (instruction): The six-week sprint. Sales Safari research → company targeting → technology identification → scoped project design → build → ship → case study write-up.

The GRASPS framework for Stage 2 was particularly powerful - it structured portfolio projects as situated performances, not abstract exercises:

“We write the Portfolio Project prompt using the GRASPS framework, but do not use that term when presenting it to the learner.”

UbD’s essential questions concept became central to how egghead framed not just courses but entire podcast seasons and workshop series.

Amy Hoy & 30x500: Backwards Planning

Amy Hoy and Alex Hillman brought the backwards planning methodology and Sales Safari research technique.

“We are not providing full designs. We are providing assets. How do we combine shape up? 30x500, JBTD, Value Paths… This separates tutorial works from actual projects.”

“For example, we ran a 30x500 club and it was great.”

“30x500 is a portfolio project club. We have permission to do Sales Safari for developers.”

“Backwards planning a cabin is the same as backward planning a book. If you can plan a dinner party, you can ship a product.”

The 30x500 methodology mapped perfectly onto UbD’s backward design - start with the desired outcome, work backward to the activities. Amy Hoy’s backwards planning was the entrepreneurial version of what Wiggins and McTighe formalized in education.

The egghead team ran Sales Safari to identify learner pains, then used backwards planning to design interventions. The portfolio club was the embodiment: research ideal companies → identify technologies → build a scoped project that solves a business problem → present as portfolio piece.

The Badass Developer Portfolio Club

This was the operational manifestation of all the above threads. A facilitated cohort experience designed with UbD, powered by value paths, aimed at the “Stand Out & Get Hired” outcome.

“At the same time Lauro, Zac, and Taylor are working on our first learning designs for badass developer portfolio clubs which will provide a small group of curated/invited developers - a mix of staff, egghead learner advocates, and egghead instructors - to spend ~6 weeks working on a portfolio project centered on a technical theme (ecommerce store, etc).”

“Running portfolio clubs that take 12-14 people through the process of researching their ideal companies, what technologies those companies use, and designing a small scoped project that solves one specific business problem.”

“The lessons learned from the badass developer portfolio club are applied to the learning design that will be published as a badass developer portfolio project.”

“Systems design of the portfolio clubs is the thing we could really use help with. We’re great at the technical curriculum curriculum design bit (watch this lesson, read this article, build with these tools). But how to map out a service design map of all the touch points of that experience, what automation systems would need to be involved, what the experience looks and feels like for people going through it.”

The clubs ran multiple cohorts. Application copy was written. Pre-meeting interviews conducted. Journey maps built in Miro with Taylor. Email sequences designed. Facilitators assigned - Taylor, Will Johnson, Lauro, Zac, Ian Jones.

Structure: curated group of 12-14 → 6-week sprint → technical theme → portfolio piece as output → case study published on egghead.

The Book Clubs

Before portfolio clubs, there were book clubs - the simpler form of the same pattern:

• Badass - first egghead book club
• Interviewing Users - multiple sessions with Steve Portigal’s book
• JIT PM - Just in Time Project Management study group
• UbD Book Club Pilot - Notion-hosted, Joel ran v2
• 30x500 Club - Amy Hoy’s methodology as group study
• Hacktivist Content Plan - study group around Shedrack Akintayo’s content planning

“As far as I know, the Book Clubs and Portfolio projects went really well.”

“Community Projects? Book Clubs? Running through courses as a group?”

These were Kerievsky’s Knowledge Hydrant patterns in action - small groups studying great literature together. Kerievsky writes that “without a moderator, dialogues may wander aimlessly, arguments may erupt, people may talk on top of each another, and a group may fail to ever explore an author’s deeper meanings.” His Motivated Moderator pattern solved this: a facilitator who keeps the group productive without dominating the conversation.

The Opening Question pattern was equally important: “Asking an opening question at the commencement of a dialogue comes from an age-old tradition that is still practiced at schools like Oxford University and St. John’s College.” The right question at the start of a session sets the entire trajectory.

The evolution to portfolio clubs added the performance task layer (UbD Stage 2) and the value path direction.

The Facilitators: Dungeon Masters, Not Teachers

A critical thread - the role of the person running the experience:

“The club should give learners a great collaborative experience with a skilled facilitator and a distinct goal at the end of the adventure.”

“Dungeon Master/Tummeling, not Teaching.”

“It’s a workshop. A book club. A D&D campaign.”

“Taylor facilitated so that Marcy could focus on teaching.”

The facilitator roster at egghead: Taylor Bell, Lauro Silva, Zac Jones, Will Johnson, Ian Jones. Each ran clubs with their own style. The UbD framework gave them structure; the DM role gave them permission to guide without lecturing.

Tummeling comes from Heather Gold - the tummeler is a Yiddish role, the person at a party who makes sure everyone’s having a good time, draws out the quiet people, keeps energy flowing. It’s the Motivated Moderator from Kerievsky’s patterns: someone who “helps produce valuable educational experiences” by directing dialogue without controlling it.

The Adventure Club Pattern

The meta-pattern that ties it all together:

“The Adventure Club Pattern has a lot of interesting potential for an obviously premium offer, but it might also make sense as an entirely different product.”

“Adventure Club Pattern can be considered an active implementation of Understanding by Design and value paths.”

“Code Adventure Club” - the code-specific variant.

This is where the D&D metaphor becomes structural, not decorative:

The Network

People who shaped this thinking:

• Kathy Sierra - Badass framework, resolution-of-expertise model
• Samuel Hulick - Value paths, user onboarding as career navigation
• Amy Hoy & Alex Hillman - 30x500, Sales Safari, backwards planning
• Maggie Appleton - Visual design of value paths, illustration
• Joshua Kerievsky - Knowledge Hydrant pattern language
• Wiggins & McTighe - Understanding by Design, backward design, GRASPS
• Christopher Alexander - Pattern languages (meta-influence on everything)
• Mortimer Adler - How to Read a Book, Great Books seminars
• David Bohm - On Dialogue, non-competitive learning
• Jared Pereira - Hyperlink Academy, neighborhood-scale software
• Heather Gold - Tummeling concept
• Taylor Bell, Lauro Silva, Zac Jones, Will Johnson, Ian Jones - The facilitators who ran it

The Lineage

Kathy Sierra (Badass) → "Make the user awesome, not the product"
    ↓
Samuel Hulick (Value Paths) → Directional learner outcomes
    ↓
Amy Hoy (30x500) → Backwards planning from outcome to activity
    ↓
Wiggins & McTighe (UbD) → Three-stage curriculum design
    ↓
Christopher Alexander → Pattern languages as design tool
    ↓
Joshua Kerievsky (Knowledge Hydrant) → Study group patterns
    ↓
Knowledge Adventure Club → "It's a workshop. A book club. A D&D campaign."

The framework exists. It was tested with real cohorts at egghead. The missing piece was always the platform - the thing that makes the facilitator role scalable. An agent that can play Motivated Moderator, track individual learner progress through the value path, and serve up the right Opening Question at the right time.

Source: Research notes, 2019-2024. 1,400+ relevant blocks across value paths, UbD, portfolio clubs, book clubs, and the adventure pattern.