Loop — portable pieces, lighter AI

Loop components are portable: a table, a list, a paragraph that can show up in Teams, Outlook, or a Loop page and stay in sync. AI help here is lighter. Use Loop when the unit of work is a shared block, not a research room and not a one-page brief.

A component is not a notebook and not a Page.

Personal Brain already allows a Loop page as a place to save About Me. That is storage. This lesson is when Loop is the right *working* surface.

Core principles

  1. Loop: a living block many people will touch.
  2. Page: a brief or canvas you own, maybe share.
  3. Notebook: a fenced project room for Copilot.
  4. If you do not use Loop at MillerKnoll, skip the product and keep the rule: portable block vs canvas vs fenced room.

Check yourself

When is Loop the right surface?

Do this in Copilot

Name one block on your project that two people edit (agenda, decision log, open questions). That is a Loop candidate. If Loop is unused on your team, put it in a shared OneDrive file instead and write that down.

Paste into Copilot Chat.

Pick Loop vs Page vs Notebook for one block

Project: [FIVE WORDS]. This block of work: [AGENDA / DECISION LOG / OPEN QUESTIONS / OTHER]. Two or more people will edit it: [YES/NO]. I need Copilot to stay inside a closed set of files: [YES/NO]. Recommend Loop, a Copilot Page (or Word), or a Notebook, in one paragraph. If my tenant might not have one of those, give the fallback. Do not recommend all three “just in case.”

Techniques: Goal and context

Open Copilot

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

Next lesson: One project, one room →

AI

Part of the MillerKnoll collective

Studio · 2026