← Operator Hour
Season 1 · Episode 4 · Public recap

Prototypes that show, not tell.

A working thing changes the conversation. We turned fictionalised meeting notes into a clickable prototype, then wrote the handover an engineer would need.

Recap

You know the meeting. The deck makes sense, everyone nods, and the customer asks you to send it over. The idea stayed abstract, so the room had to imagine too much.

We started from a fictional retail scenario based on common constraints. No customer records. The agent read the notes, built a small browser prototype, and kept the boundaries visible on screen.

The shiftA slide asks someone to imagine. A prototype gives them something to react to.

The final prompt wrote a README and infrastructure handover. Demo-grade work stayed demo-grade. Production was left to a repository, review, and an engineering team.

Operator move: choose one conversation that stalled on slides. Build a fictionalised first version in twenty minutes and show it to a colleague before it reaches a customer.

Take it home

Build the first clickable version

Use the synthetic service-desk brief below, or replace it with a fictionalised version of a conversation you are allowed to use.

20 to 30 minutesOne HTML file
Download synthetic prototype brief
  1. Save the sample as brief.md in an empty folder.
  2. Run the prototype prompt and review the plan before approving the build.
  3. Open the HTML file and complete the main task as a user.
  4. Ask for a README that separates working behaviour from mocked behaviour.
Prototype prompt 
Read brief.md and any supporting files in this folder.

First, restate the problem, intended user, and constraints. Flag anything uncertain.

Then build a small single-file HTML prototype that lets someone experience the core idea. Use fictional data only. Label it clearly as a prototype.

Before changing files, show me a short plan and wait for approval.

After the prototype works, write a README that explains what is real, what is mocked, the safety boundaries, and what an engineering team would need for production.
You are done when: someone else can open the file, complete the main task, and tell which parts are mocked without asking you.
Keep it safe: use fictional records. A prototype should never connect to a real customer system or claim production readiness.
Resources
🎞️

Public slide deck

The prototype argument, fictional example, exercise, and handover boundary.

open slides 🎬

Full recording

Microsoft employees can watch the complete prototype build after corporate sign-in.

Microsoft employees 📂

Files as context

Learn the public workflow for turning notes and documents into structured work.

public lesson 🐙

Public build pattern

A reusable example of shipping browser artifacts with validation and clean handover.

public repo

Still not a developer. I can make the idea visible, then hand it to the people who make it real.