Skip to content
Demo prep

Proof beats polish.

The best workshop presentation is the artifact itself: a page, repo, workflow, document, prototype, generated output, or before-and-after comparison. Slides and NotebookLM can help tell the story, but they should not replace what the pod built.

Default Rule

Show the artifact first. Explain after.

Website or page

Use when the output can be inspected visually: a landing page, sponsor page, resource guide, prototype, or local business mockup.

Repo or workflow

Use when the pod built code, a local tool, an automation, a script, or a system people need to see working.

Document or output

Use when the pod built a strategy, research packet, prompt system, playbook, policy, or client-facing draft.

Three-Minute Story

Use the same story for every pod.

Problem

Who has the problem, and why does it matter?

Build

What did the pod make during the workshop?

Proof

Show the website, repo, workflow, document, output, or before-and-after result.

Next step

What would make this useful after the room leaves?

Tool Choice

Pick the presentation format by what the pod built.

Use a website when

  • The audience can inspect the result visually.
  • The pod built a page, resource, prototype, or mockup.
  • The main action can be walked through in the browser.

Use a repo when

  • The pod built code, a local tool, or an automation.
  • The README or project summary explains the work.
  • The demo can run or show output from the tool.

Use a document when

  • The output is research, strategy, policy, or a playbook.
  • The decision supported by the document matters more than a live tool.
  • The next step is review, adoption, or implementation.

Use a deck only when

  • The artifact is hard to inspect live.
  • The output is mostly research or strategy.
  • The audience needs a short shareable summary after the event.
NotebookLM

Use NotebookLM to help the story, not replace the build.

NotebookLM is useful when a pod has notes, docs, or repo summaries and needs a short spoken explanation, study guide, deck outline, or Q&A source. Do not use it if the pod still lacks an artifact.

Turn this project summary into a three-minute presentation.

Use this structure:
1. Problem
2. What we built
3. Live demo plan
4. What AI helped with
5. What we would do next

Keep it practical. Do not make it sound like a pitch deck unless the project actually needs one.
Decision Tree

Use this when pods are unsure.

Can the audience inspect the artifact directly?

Yes: present the artifact. No: continue.

Is the output mostly written strategy or research?

Yes: present the document. No: continue.

Does the presenter need help turning notes into a story?

Yes: use NotebookLM for a talk track. No: continue.

Is the output difficult to show live?

Yes: make a five-slide deck. No: present the artifact with a short verbal explanation.

The final rule: show what changed, explain why it matters, and name the next step.