One Spin Rule

Pick the worst spin episode from last week. One. Diagnose it. Write a single sentence you could put on a sticky note.

A sentence you can pin.

Good rules are operational: “If the goal is not written, I do not start a Copilot loop.” “If I retry twice with no new instruction, I stop and rewrite the brief.” “Decks get built in PowerPoint, not in Chat.”

Apply it for a week. Then, if you want a ranked list of new use cases instead of fixing old ones, open Where to Next.

Core principles

  1. One rule. If you need a paragraph, it will not change Tuesday.
  2. The rule should have prevented your named spin episode.
  3. Confidence: say what you measured vs what you inferred from memory.
  4. Revisit the inventory in two weeks. Shapes change when rules stick.

Next: The Taste Test — route the option to the job

Check yourself

What makes a spin rule worth pinning?

Do this in Copilot

Pin your spin rule where you will see it when you open Copilot. Optional: share the report card with no one, or with one colleague.

Keep the spin rule. The rest of the report card is for you.

Write the report card

Produce a personal Copilot usage report card from my notes. Sections: (1) Usage shape, (2) Shipped vs spin with examples, (3) Three routing fixes, (4) One spin rule — a single sentence I can pin, (5) Confidence — measured vs inferred. Notes: [PASTE INVENTORY + SCORES + FIXES]. Tone: honest athlete readout, not a performance review.

Techniques: Role + task + format

  • Example rules: “No Copilot loop without a done-when line.” “Two retries, then rewrite the brief.” “File work in the file’s app.”
Open Copilot

Did you run this in Copilot? Mark complete when you have tried it.

AI

Part of the MillerKnoll collective

Studio · 2026