Flash Lab vs. Vibecoding: What’s Our Special Sauce?
Context: Josh shared an article by Alex Kotran (aiEDU) about vibecoding workshops — hands-on sessions where participants build functional software using AI tools like Lovable, Replit, and Claude Code. Kotran is running them at SXSW EDU (100+ people), Urban Assembly, GSV Google Fellowship. Others are following. The question: as this becomes commonplace, what is Flash Lab’s defensible position?
For: Josh Weiss (and Reuben’s own strategic thinking) Prepared: March 13, 2026
The Honest Overlap
Flash Lab and vibecoding workshops share more DNA than is comfortable:
- Both put AI tools in people’s hands in a facilitated, time-boxed session
- Both aim for the “I made a thing!” emotional payoff
- Both are constructionist in practice (learning through building)
- Both require no technical prerequisites
- Both produce working prototypes as outputs
- Both are riding the same cultural moment: AI lowered the floor for building
If someone attended both, the Build phase of Flash Lab would feel familiar. That overlap is real.
Where Vibecoding Workshops Win
Being honest about the competition’s advantages:
| Advantage | Why It Matters |
|---|---|
| Simpler pitch | “Build software with AI” is one sentence. Flash Lab’s value prop takes a paragraph. |
| Lower facilitator bar | Anyone who has vibecoded can run a session. Flash Lab needs trained facilitators. |
| Cultural momentum | “Vibecoding” is viral. Conferences, media, social posts. Flash Lab doesn’t have a movement. |
| Legible artifact | Participants leave with a working app URL. Flash Lab prototypes are more varied/conceptual. |
| Faster to stand up | Can design and deliver in days vs. Flash Lab’s toolkit investment. |
The Six Real Differentiators
1. Problem-First, Not Tool-First
Vibecoding: “Here’s Lovable. What do you want to build?” — the tool’s capabilities shape what gets built. You end up solving problems the tool is good at, not necessarily problems that matter. The what and the why are implicit — inherited from the tool rather than chosen deliberately.
Flash Lab: “What’s the problem you’re trying to solve?” — the Design phase forces participants to articulate the problem, decide the approach, and evaluate whether AI even belongs here before the tool enters the picture. The decisions are explicit and yours.
Vibecoding produces tool proficiency. Flash Lab produces design judgment.
2. AI Boosts vs. Human Boosts — The When-to-Use-AI Question
Flash Lab explicitly asks participants to choose: does AI add value here, or does human collaboration? No vibecoding workshop asks this question because the answer is assumed.
This builds the meta-skill that matters most for educators: knowing when AI helps and when it doesn’t. For someone who has to make integration decisions for a classroom, department, or school — this is the skill.
3. “Achieve Failure” — Discovering Limits Is a Valid Outcome
Vibecoding workshops are optimized for success. A participant who struggles has had a bad experience.
Flash Lab is designed so that “AI can’t do this” is a valuable finding. From the capacity building model: “Confidently articulating what doesn’t work (so far) is an output, not a failure.”
In a cultural moment where every workshop promises “you’ll build something amazing,” Flash Lab is one of the few formats that says: “You might discover something amazing doesn’t work — and that’s the point.”
This connects directly to the Broken Proxy problem: if we only celebrate AI successes, we reinforce the gap between what a product looks like and what the builder actually understands. The Broken Proxy essay argues that AI severed the link between the quality of the product and the quality of the process that produced it — and that the right response is making the process visible, not banning the tool. Flash Lab’s “Achieve Failure” philosophy is that response in workshop form.
4. The Advocate Phase — From “I Built This” to “Here’s Why It Matters”
Vibecoding workshops end when the thing is built. Flash Lab adds a third act: make the case for your solution. This forces metacognition — What did I actually build? What problem does it solve? Why should anyone care?
Vibecoding’s viral moment: “one person builds, shows a colleague, colleague starts building.” Flash Lab’s viral moment: “one person builds, argues for why it matters, and the audience evaluates whether the case holds.”
This develops the leadership capacity participants need to champion AI integration back in their own contexts — not just use the tools, but argue for them (or against them) with evidence.
5. Context-Agnostic Architecture
Vibecoding workshops are locked to one output: software. Flash Lab’s three-phase structure works for:
- K-12 educators — lesson redesign
- Researchers — study design (Anna-Lena renamed “Build” to “Research Design” in Paris; 6 research projects emerged)
- International conferences — Oman teaching profession conference (Feb 2026)
- District-level PD — Christine Bywater’s 5-session series, Lake Forest visit
- On-campus makerspace — Tinkery Flash Lab (March 30)
The structure travels because it’s about problems and prototypes, not about any particular tool.
6. Front Door, Not Standalone Event
Flash Lab routes people somewhere afterward. The Three Personas framework (from Feb 24 AS:DE discussion):
| Persona | Driving Question | Pathway |
|---|---|---|
| Instructional Practices | “How do I use AI without shortcutting the learning process?” | CSET/PLEX, ISTE PD |
| Contextual Curiosity | “How could AI specifically help (or hurt) me in my situation?” | Tinkery, custom consultation |
| Identity | “How do I rediscover my value in the age of AI?” | TBD — emerging need |
Every session is diagnostic: participants discover which question drives them. An organization that runs Flash Lab gets a map of what their people need next. An organization that runs a vibecoding workshop gets excited builders.
The Special Sauce (One Line)
Vibecoding workshops teach people to build with AI. Flash Lab teaches people to think, build, and advocate — including knowing when AI is the wrong tool.
The unifying thread across all six differentiators: Flash Lab is human-centered; vibecoding is tool-centered by default. Every differentiator is about keeping humans in the driver’s seat — choosing the problem, choosing whether AI helps, discovering limits, making the case for why it matters. Vibecoding lets the tool shape the decisions. Flash Lab makes the human shape them explicitly.
Flash Lab develops AI judgment, not just AI skills. It’s the difference between “I can use this tool” and “I know when to use this tool, when not to, and I can make the case for my decision.”
Vibecoding fits inside Flash Lab’s Build hat — but it’s one possible build, not the whole experience.
The Naming Question
Don’t position against vibecoding. It cedes the frame and creates a false binary. Instead, position Flash Lab as what wraps around the build.
Vibecoding is phase 2 of Flash Lab. Flash Lab is the full cycle: think, build, advocate.
More precisely: vibecoding could fit under Flash Lab’s Build hat, but the Build hat is flexible enough that it doesn’t have to be vibecoding. The Build phase might be designing a research study (Anna-Lena), drafting a lesson plan, or prototyping a policy proposal (Oman). The hat is tool- and output-agnostic.
Many participants will come into Flash Lab expecting to vibecode. That’s actually useful: they get what they expect during Build, but they also get the Design and Advocate phases they didn’t know they needed. The expectation mismatch is a feature.
This framing is:
- Honest — the Build phase can include vibecoding
- Generous — doesn’t dismiss vibecoding
- Differentiating — makes clear Flash Lab wraps richer learning around the build
If a rename happens, it should communicate the three-phase arc (problem, build, advocate), not just differentiate from vibecoding. “Flash Lab” is fine — it communicates speed and experimentation. But if the team wants a name that better signals the full experience, focus on the problem-first + critical judgment elements.
Strategic Moves
1. Claim the “around the build” territory
Write the narrative that connects vibecoding to Flash Lab. Vibecoding is the appetizer; Flash Lab is the full meal. Reframe vibecoding workshops as proof of demand, not competition.
Use Kotran’s own observation: “enthusiasm hits walls (databases, APIs, auth).” Flash Lab’s Design and Advocate phases are how you help people know what to do before and after they hit those walls.
2. Use the Broken Proxy framing internally when explaining Flash Lab’s design philosophy
The Broken Proxy essay (published Feb 2026) articulates why making the learning process visible matters. “Achieve Failure” is Flash Lab’s practical answer to that problem.
Use this framing in conversations with partners, in the toolkit, and when pitching Flash Lab to institutional buyers — it’s a powerful way to explain why the Design and Advocate phases exist. The blog stands on its own; the connection lives in how we talk about Flash Lab.
3. Make the Three Personas framework external-facing
An org that runs a vibecoding workshop gets excited builders. An org that runs Flash Lab gets a diagnostic map of what their people need next.
This is the compelling pitch for institutional buyers (ISTE, LAUSD, districts, ministries) who care about sustained development, not a single event. ISTE’s audience is likely heaviest in Persona 1 (Instructional Practices) — districts buying PD on teaching with AI. The Three Personas framework turns Flash Lab from a one-off event into the front door of a pathway.
4. Build the Activation Stage with a vibecoding moment
Already proposed for ISTE (Feb 25 meeting). Make the 20-30 minute Activation Stage explicitly include a vibecoding-like build moment (10 min), but sandwich it:
- Before: Framing question (“What problem are you trying to solve?”)
- During: Quick build with AI tool (the vibecoding-like moment)
- After: Reflection (“What did you learn about what AI can and can’t do?”)
Rides vibecoding’s cultural momentum while demonstrating Flash Lab’s additional value. A taste of the full 3-hour experience.
5. Close the evidence gap first
Kotran claims constructionism but has zero evidence that vibecoding changes practice. Flash Lab has the same gap — but with ISTE’s Community of Practice, evaluation instruments already in use, and the partnership infrastructure to track outcomes, Flash Lab is positioned to close it first.
The organization that can say “we have evidence this changes teaching practice, not just builds confidence” wins the institutional buyer.
This maps to the SMART goal finalized March 12: two publishable case studies by end of Q2. Those case studies are the beginning of the evidence advantage.
Summary Matrix
| Dimension | Vibecoding | Flash Lab | Who Wins |
|---|---|---|---|
| Entry pitch | “Build software with AI” | “Explore AI through design thinking” | Vibecoding |
| Facilitator bar | Low — anyone who’s vibecoded | Trained facilitators needed | Vibecoding |
| Cultural momentum | Viral term, conference buzz | Stanford brand + partnerships | Vibecoding |
| Artifact legibility | Working app with URL | Variable (prototype, design, plan) | Vibecoding |
| Problem-first design | No | Yes — Design before Build | Flash Lab |
| Critical judgment | No — optimized for success | Yes — “Achieve Failure” | Flash Lab |
| Audience adaptability | Software builders only | K-12, research, international, policy | Flash Lab |
| Post-workshop pathway | None | Three Personas + ecosystem routing | Flash Lab |
| Train-the-trainer | Organic replication | Designed pipeline (scripts, observation, debrief) | Flash Lab |
| Evidence trajectory | Testimonials only | Testimonials + evaluation + case studies in progress | Flash Lab |
| Revenue model | Generally free/grant-funded | $5K-$25K validated; ISTE rev-share on $7,500/day CLS | Flash Lab |
The Bottom Line
Vibecoding workshops will win the volume game — they’re simpler, faster, and riding a cultural wave.
Flash Lab will win the institutional buyer game — it’s deeper, more adaptable, and designed for sustained impact. These are not the same market.
The strategic error would be competing on vibecoding’s terms instead of making Flash Lab’s terms the ones that matter to the buyers who count.
Next Steps
- Review with Josh at March 19 1:1
- Test the framing: “vibecoding is phase 2 of Flash Lab” — does Josh agree?
- Connect to rename conversation: if the name changes, it should signal the three-phase arc, not react to vibecoding
- Publish Broken Proxy essay — makes the “Achieve Failure” differentiator visible externally
Prepared: March 13, 2026 References: capacity-building-model.md, personal-logic-model.md, prep/2026-02-19-iste-strategy.md, drafts/the-broken-proxy.md, projects/briefings/ai-flash-lab.md
prep/2026-03-19-flash-lab-special-sauce.md