Signing in

You will be sent to MillerKnoll sign-in.

For teams

Workshops

The best way to learn this is in the room, with your hands on the keyboard.

Self-serve paths build familiarity. In-person workshops build habits you can repeat Monday — verification, iteration, and team norms, coached on real work.

Why in the room

Async learning gets you started. Hands-on practice makes it stick.

You can read about prompting, watch a demo, and still freeze when it is your email thread, your spreadsheet, your client deck. That gap closes fastest when someone can redirect a bad prompt in real time, when the room tries the same skill on different tasks, and when verification becomes a reflex before anything leaves with your name on it.

We run workshops in person because judgment is physical — you feel when an output is too confident, when a source is missing, when a teammate's use case needs a different guardrail. The toolkit stays open after; the workshop is where the habit forms.

Formats we run

Pick the depth that matches your team's schedule. Every format is in-person and hands-on — laptops open, real tasks on the table.

  • Spark

    ~1 hour

    One skill, one win.

    Best for A first Copilot prompt that survives review, a team kickoff, or a lunch-and-learn on a single technique.

  • Working session

    ~2 hours

    Two skills plus practice on your own task.

    Best for Teams that want depth on prompting and verification without losing an afternoon — bring a live brief or thread.

  • Half day

    ~4 hours

    Foundations plus one application track.

    Best for Excel analysis, client decks in PowerPoint, or your first agent — enough time to set up, practice, and debrief.

  • Full day

    6–7 hours

    Orientation, policy, and team breakouts.

    Best for Cross-functional groups: morning on tool choice and shared norms; afternoon breakouts each leave with a concrete next step.

Tailored to your function

We start from the work your team actually does. Here is the shape a session takes for a few functions — yours is built the same way, from a short pre-work survey and your real files.

  • Workshops for sales

    Client-ready output that survives scrutiny — decks, research, and follow-up, coached on live accounts.

    Often covers PowerPoint on the MK template, pre-meeting research with citations, weekly status and follow-up drafting.

  • Workshops for manufacturing

    Faster reads on the spreadsheets your plant already runs — without pretending Copilot replaces the system of record.

    Often covers Excel analysis on machine and inventory data, weekly status drafting, order-change triage with clear IT boundaries.

  • Workshops for product development

    Judgment for early, ambiguous work — research synthesis, drafting, and structured experimentation.

    Often covers Multimodal review, spec and brief drafting, structured experiments, and documentation that keeps pace.

Not listed here? Sales, operations, design, product, finance, HR — every agenda is shaped from your team's workflows. Tell us the function and the task you want to improve, and we build the room around it.

Topics we cover

Application tracks with live Copilot practice, plus the core readiness paths every session assumes. We mix and match based on who is in the room.

Core readiness 8 paths

Judgment and fluency — the habits every path assumes.

How to book

Bring your team's real work.

Request a team session or house call through the AI program support hub. Tell us your group size, format preference, and one workflow you want to improve — we'll propose an agenda shaped to it.

AI program support →

Review before you send, especially when the output sounds confident.

The room is where the habit forms.

AI program support →

MillerKnoll AI · 2026