13:30 · Cowork · build and iterate

Build and iterate

Build the smallest useful version from the approved Build Brief. Run it once. Look at the evidence. Change one thing.

The challenge

Each pair carries forward one Build Brief. Build the smallest solution that moves the pain.

Work in pairs, in your own approved AI environment. Non-sensitive material only. The Pain Card defines the need; the Build Brief defines what you are testing.

Before you build · Open the Build MapDecide what kind of build this is, and how good it has to be, before you open a tool.

Three steps

  1. 01Bring your approved Build Brief, build pattern and delivery bar.
  2. 02Build the smallest reusable helper, and run it once for real.
  3. 03Inspect the evidence, change one thing, run it again.

The prompt

Here is my Pain Card, approved Build Brief, build pattern and delivery bar. First confirm whether an approved tool or agent already solves enough. Then propose the smallest version that proves value today and wait for my go-ahead. Build it, run it once on this real example, show the evidence, and recommend one improvement. Stop before any external action or high-impact decision.

Need a nudge?
  • What triggers it?
  • What evidence did the first run actually produce?
  • What is still unresolved?

If Cowork is not switched on · Use Microsoft 365 Copilot Cowork where it is switched on for you. If it is not, build the same helper as an agent or as a saved, reusable instruction — the design is portable even when the surface is not.

Submit your cowork card

Six short fields. Keep the pain and the helper distinct. Non-sensitive only. JJ releases it before it appears in the gallery.

connecting…

Loading…

What we leave with

Working helpers. Evidence from a real run, not promises.