Prototype Demo + Feedback

Prototype Demo + Feedback is a learning activity in which participants present a rough, early-stage prototype of their work-in-progress — a draft structure, a mocked-up artifact, a sketch of a plan — and receive structured feedback from peers and the workshop leader before the artifact is milestone-ready or launch-ready. The demo is explicitly for work-in-progress rather than for completed work. The "roughness" is structural, not apologetic — a polished prototype invites polish-level feedback that does not help the participant know what to build next, while a rough prototype invites the kind of early-stage feedback that shapes what the next round of work actually produces. The activity lives at the iteration stage that precedes Project Milestone Review's named-milestone evaluation.

The approach draws on design-thinking practice. Tim Brown's Change by Design (2009) documented rapid prototyping and feedback cycles as the design-thinking mechanism that separates successful iteration from over-polished first drafts. Tom Kelley and David Kelley's Creative Confidence (2013) extended the framing to non-designer audiences and named the specific discipline of demoing roughness rather than hiding it. Michael Schrage's Serious Play: How the World's Best Companies Simulate to Innovate (2000) provides the organizational-learning framing — prototyping as the primary mechanism by which organizations figure out what they are actually building, not just evaluate what they have already built.

Prototype Demo + Feedback closes the action-and-project family. Where Action Learning Set handles live unresolved problems, Work-Cycle Check-In maintains recurring rhythm, and Project Milestone Review evaluates artifacts at named milestones, Prototype Demo + Feedback handles the earlier iterative stage — before milestones, when the artifact is still forming. The family covers the full arc of between-session action from recurring rhythm through deep peer advisory to milestone evaluation, with prototyping at the earliest iterative stage.

What It Is

Four structural components define Prototype Demo + Feedback.

• An early-stage prototype, deliberately rough. The participant brings work-in-progress — a draft, a sketch, a mockup, a rough structure. Polish is explicitly not the goal; in fact, over-polished prototypes undermine the activity because they signal "this is done" and invite polish-level feedback. Rough prototypes signal "this is still forming" and invite shape-level feedback that actually helps the participant decide what to build next. The roughness principle is the activity's load-bearing element.
• A structured demo of the prototype. The participant demos their prototype — walks the cohort through what it is, what it is supposed to do, what they are trying to figure out, and where they know it is weak. Demos are typically 3–7 minutes per participant; longer demos invite over-explanation that substitutes for the prototype's own evidence.
• Feedback focused on shape and direction, not on polish. Peers and the workshop leader give feedback specifically focused on structural questions: does this solve the problem you are trying to solve, what does this assume that might not be true, what would you try differently if you rebuilt this tomorrow, what piece of this would benefit from more roughness or less. Feedback on spelling, formatting, or polish is explicitly deferred — that is downstream work the prototype stage is not trying to address.
• A specific next-iteration commitment. The demoing participant names what they will change or add before the next iteration. The commitment is concrete and targets one or two specific shifts based on the feedback, not a wholesale revision. Next-iteration commitments are typically smaller than Project Milestone Review's next-milestone commitments because the iteration cycle is shorter.

When to Use It

Prototype Demo + Feedback fits workshops where participants are building artifacts that benefit from early shape-level feedback rather than late polish-level feedback. It is especially strong early in a multi-session program's build phase, before milestone reviews become the primary evaluation mechanism, when participants' artifacts are still taking shape and changing shape is cheap.

Good candidates:

• Early-stage artifact work where shape, structure, and direction are still being figured out.
• Programs that include iteration cycles between sessions — the prototype demo produces feedback that shapes the next iteration.
• Cohorts comfortable with showing rough work — participants who cannot bring themselves to demo work-in-progress will over-polish before the demo and lose the activity's value.
• Session segments of 60 to 120 minutes depending on cohort size — demos plus feedback for each participant take real time.

Less suitable:

• Late-stage work where milestone evaluation against specific criteria is what is needed — Project Milestone Review fits that stage.
• Work that has no iterative development phase — some artifacts are built in one pass and evaluated at completion; prototyping does not apply.
• Cohorts that treat rough work as embarrassing — the activity requires a cultural container where roughness is valued, not merely tolerated.
• Single-session workshops where participants have not had time to develop even a rough prototype — the activity requires prior building time.

In-Person and Virtual Delivery

Prototype Demo + Feedback runs in both in-person and virtual delivery. Modality choice depends on artifact type and what "rough prototype" means in that context.

In person. Prototypes are often physical — paper sketches, poster-boarded drafts, printed mockups, hand-drawn diagrams. The physicality reinforces roughness (participants cannot over-polish a paper sketch as easily as a digital document). In-person demo produces strong shape-level feedback because the tactile rough prototype invites shape-level reaction.

Virtual. Prototypes are typically digital — rough slides, draft documents, quick mockups in Figma or Miro, sketch-level Loom videos. Virtual delivery has a risk: digital tools make polish easy, so rough digital prototypes often get accidentally over-polished. Counter-move: explicit instructions to use low-fidelity tools (handwritten notes photographed, sketch-level mockups rather than production-quality ones, outlines rather than drafted content). Virtual delivery's advantage is that digital prototypes can be shared before the session for async review, which produces richer in-session feedback discussions.

Choosing the modality. Match the modality to the prototype's natural form. For digital artifacts, virtual works cleanly with explicit roughness discipline. For physical artifacts or cohorts that benefit from tactile prototyping, in-person is stronger. For mixed-modality cohorts, run virtually with explicit low-fidelity guidance.

How to Run It

Before the Session

1. Frame the prototype expectation clearly (leader design work, pre-session). Communicate to participants what "rough prototype" means for the specific artifact type they are building — a three-slide sketch, a one-page outline, a hand-drawn diagram, a 90-second Loom walkthrough. Set the roughness floor (below this = not enough to demo) and ceiling (above this = over-polished, defeats the purpose). Participants calibrate their preparation to the framing.
2. Communicate the feedback discipline (leader design work). Make explicit that feedback focuses on shape and direction, not on polish. Share the specific questions feedback will target (does this solve the problem, what does it assume, what would you try differently). Participants prepare to give and receive this specific feedback, not general impressions.
3. Each participant builds and brings their rough prototype (pre-session). Every participant arrives with a prototype ready to demo — not a polished draft, not a completed first version, a rough prototype ready for shape-level feedback. Preparation time between sessions is typically 3–7 days for moderately-complex artifacts.

During the Session

1. Open with the roughness framing and feedback discipline reminder (5–8 minutes). Re-emphasize the prototype-not-polish expectation and the shape-level feedback discipline. Especially important in the first few demo sessions before the cohort has internalized the framing.
2. Round-robin demos and feedback (60–90 minutes, scaling with cohort size). Each participant demos for 3–7 minutes, then receives 5–10 minutes of structured feedback. Move through the cohort deliberately. The workshop leader monitors for polish-level feedback creep and redirects peers back to shape-level questions when it drifts.
3. Cross-cohort pattern surfacing (8–12 minutes). The workshop leader names patterns — what structural questions came up across multiple prototypes, where the cohort's shape-level work converges or diverges, what assumptions multiple prototypes share. Pattern-naming helps participants see their own prototype in relation to the cohort's collective shape of work.
4. Next-iteration commitment capture (8–12 minutes). Each participant names what they will change in their next iteration — typically one or two specific shape-level shifts, not a full revision. Commitments are captured for the program's next session or the next prototype demo cycle.

After the Session

1. Participants iterate their prototypes before the next demo or milestone review. The iteration happens between sessions. Each participant applies the feedback-targeted shifts to their artifact. The iteration cycle is typically shorter than milestone-to-milestone revision — days or a week rather than weeks.
2. Bring the iterated version to the next demo or milestone review. Depending on the program's structure, the next event is either another prototype demo (further shape-level work) or a milestone review (evaluation against named criteria). The prototype demo cycle feeds into milestone reviews as the artifact approaches milestone-ready form.

An Example in Practice

A six-week cohort program for eight workshop creators building new workshop activities for their own sessions. The program's week-three session runs as a Prototype Demo + Feedback after participants have had ten days to build a rough version of the activity they are developing.

The workshop leader frames the expectation: bring a rough prototype — a one-page outline, a three-slide sketch, a 2-minute Loom walkthrough of the activity's shape. Not a completed draft. Not a polished version. Something rough enough that you are still deciding what to build. The feedback discipline: questions about shape, not about polish. Does the activity solve the problem you are trying to solve? What does it assume about participants that might not be true? What would you try differently if you rebuilt it tomorrow?

Eight participants each demo for five minutes. One coach demos a rough outline of a new client-onboarding conversation structure — four pages of handwritten notes photographed on her phone. She walks the cohort through the structure: what it covers, what she is trying to produce by the end of the conversation, where she knows it is weak. Feedback follows for seven minutes: peers ask about the assumptions embedded in the structure's opening, about whether one of the middle phases is doing the work she thinks it is, about what she would expect to change if her audience were more senior or more entry-level. The workshop leader adds one question — what is the single most structurally weak move in the current shape, and what does she want to see replace it.

The coach names her next iteration: tighten the middle phase, rewrite the opening based on the assumption-level feedback, try the revised version in a real client conversation before the next demo session. Demos continue through the cohort.

Cross-cohort pattern surfacing takes ten minutes. The workshop leader names a pattern: most of the cohort's prototypes have strong opening and closing shapes but weak middle-phase work, which is common at this stage of activity design and will be the focus of week four's session.

Next-iteration commitments are captured in ten minutes. Each participant names their specific iteration shifts. The session closes; participants go into their week of iteration before the next prototype demo in week five.

Variations

• Structured-Rubric Prototype Demo + Feedback. Feedback is anchored to a specific rubric of shape-level questions (does it solve the problem, what does it assume, where is it weakest, what is missing). Moves toward milestone review's rubric discipline while staying at the prototype stage. Used when the cohort benefits from more structure than open shape-level feedback provides.
• Async Prototype Demo + Feedback. Prototypes are posted (shared documents, Loom videos, Figma boards) between sessions, and feedback is given asynchronously in writing. Used when the cohort is distributed, when the prototype type is digital-native, or when the program cannot accommodate a full live demo session. Produces written feedback persistence; loses the live cohort dynamic.
• Paired Prototype Demo + Feedback. Participants demo to one partner rather than the full cohort, using the same shape-level feedback discipline. Used when the cohort is large enough that full-cohort demos would consume disproportionate time, or when the program values one-on-one depth over cohort-wide breadth in the demo stage.
• Multi-Round Prototype Demo + Feedback. Two or three rounds of demos in the same session, with brief iteration between each round. Participants demo, receive feedback, modify their prototype on the spot, demo the revised version in the next round. Used when the iteration cycle is tight enough that multi-round work produces meaningful capability growth — often the case for simple artifact types.

Which Method It Serves

Prototype Demo + Feedback is primarily a Project-Based Learning activity. The method's iteration discipline — building, demoing, refining, rebuilding — runs on prototype-demo cycles, especially early in a multi-session program before milestone reviews become the primary evaluation mechanism. The activity is how Project-Based Learning produces the rapid iteration that separates strong programs from programs where participants polish a single first draft for too long.

Prototype Demo + Feedback also functions inside other methods. In Problem-Based Learning that produces participant-generated solutions, prototype demos let the cohort see each other's proposed solutions before the solutions are finalized. In Action Learning, prototype demos can be used to show participants' in-progress work between set meetings — a lighter feedback moment that complements the set's deeper hot-seat questioning. In Case-Based Learning where cases are participant-developed, prototype demos evaluate cases as they take shape before they become the cohort's analytical material.

Design Considerations

• The roughness of the prototype determines the value of the activity. Prototype Demo + Feedback is defined by the rough-versus-polished distinction. Over-polished prototypes invite polish-level feedback (spelling, formatting, completeness) that does not help the participant decide what to build next. Rough prototypes invite shape-level feedback (does this work, what does it assume, what is missing) that actually shapes the next iteration. Participants' instinct is to over-polish before showing — the cultural norm in most professional contexts is to present polished work — so the roughness expectation has to be named explicitly and reinforced consistently. Before running Prototype Demo + Feedback, pressure-test the roughness framing: is the expected prototype level specified concretely enough that participants know what to bring (a one-page outline, a three-slide sketch, a 2-minute Loom), and is the feedback discipline tight enough that participants can give and receive shape-level feedback without drifting into polish? If either answer is soft, the activity collapses into early-stage peer review that treats work-in-progress as finished work.
• Protect the feedback's shape-level focus. Peers' instinct is to give feedback on what is visible, which in any prototype includes polish dimensions (formatting, word choice, visual design). Shape-level feedback requires explicit discipline: peers name structural questions about what the prototype is trying to do and whether it is doing that, not about how it looks. The workshop leader redirects peers who slide into polish-level feedback, especially in the first few demo sessions before the cohort has internalized the discipline.
• Keep iterations tight and targeted. Next-iteration commitments should target one or two specific shape-level shifts, not a full revision. A participant who tries to address every piece of feedback in the next iteration over-revises and loses the rough-prototype cycle's tempo. The discipline is choosing the most valuable shifts, not responding to all feedback.
• Establish the roughness-is-valued cultural container. In professional contexts where polished work is the default expectation, rough work can feel unsafe to show. The cultural container for Prototype Demo + Feedback has to name roughness as valued and structurally necessary, not as tolerated weakness. Programs where participants consistently over-polish are missing the container; fix the container before fixing individual participants' prototypes.
• Sequence prototype demos earlier than milestone reviews. Prototype Demo + Feedback handles the shape-level iteration; milestone reviews handle the rubric-level evaluation. The activities fit together — prototype demos happen in the weeks before a milestone; milestone reviews happen at the named milestone. Programs that use only milestone reviews without earlier prototype demos often produce under-iterated artifacts that get their first structural feedback at the milestone, which is late.

Where this goes next: Prototype Demo + Feedback closes the action-and-project family and, with it, the three families that cover the main arc of multi-session workshop work — collaborative interaction, problem-and-inquiry investigation, and action-project iteration. The next family shifts to cross-method activities that serve a narrower function — retrieval, reflection, and memory consolidation — regardless of the program's primary method. See Minute Paper.

Related

Read this next:

• Minute Paper — the first activity in the retrieval-and-reflection family; cross-method activities that serve memory consolidation and reflection regardless of the program's primary method.

Foundations of this activity:

• Project-Based Learning — the primary method served; the activity handles the iterative-prototype stage that precedes milestone evaluation.
• Project Milestone Review — the later-stage counterpart in this family; prototype demos feed into milestone reviews as artifacts approach milestone-ready form.
• Design Challenge — the problem-inquiry activity that produces first-pass designs; prototype demo+feedback handles the iteration cycles that refine those designs.
• The Guiding Principles of Active Learning — the principles activated, especially honest reflection and engaged interest.

Where this leads:

• Which Active Learning Method Fits Your Workshop? — Prototype Demo + Feedback is the strongest sub-activity when early-stage shape-level iteration is a target outcome in a multi-session program.
• Action Learning — the method where prototype demos often appear as complementary lighter-feedback moments between deeper set meetings.

References

Brown, T. (2009). Change by design: How design thinking transforms organizations and inspires innovation. Harper Business.

Kelley, T., & Kelley, D. (2013). Creative confidence: Unleashing the creative potential within us all. Crown Business.

Schrage, M. (2000). Serious play: How the world's best companies simulate to innovate. Harvard Business School Press.