Name the meeting outcome
Write one sentence that says what must be understood, decided, or assigned by the end. If the outcome is unclear, AI will produce polished background instead of useful preparation.
Join Free
AI for meetings
A practical guide to using AI before, during, and after meetings without handing it confidential material or your judgment.
Use AI to prepare the decision, questions, risks, and follow-up before you ask it to summarize anything. Give it a cleaned brief, request a specific artifact, and keep a human responsible for the decision.
Use this guide when you need to
The method
Start with a small, real task. Keep the source material and review path visible.
Write one sentence that says what must be understood, decided, or assigned by the end. If the outcome is unclear, AI will produce polished background instead of useful preparation.
Use only the facts, constraints, participants, prior decisions, and open questions the tool needs. Remove personal data, confidential details, and any material your employer does not permit you to share.
Request a brief with the decision, options, tradeoffs, missing information, three questions, and a proposed next step. A named artifact is easier to inspect than a broad request for help.
Check names, numbers, source facts, and assumptions. Mark what came from the record and what the model inferred. You remain responsible for the meeting and the decision.
Start here
Each note gives you a small move, an example, and an artifact you can keep.
Turn safe context into a compact pre-meeting brief.
Read the Shift →Pull the actual choice out of a crowded thread.
Read the Shift →Fix the vague input that produces bland preparation.
Read the Shift →Create a durable record people can use later.
Read the Shift →Inspect the follow-up before it reaches the room.
Read the Shift →Define the meeting artifact before adding context.
Read the Shift →Turn rough notes into a reviewable decision record.
Build a decision receipt →Common questions
The best prompt names the outcome, safe context, audience, constraints, and exact artifact. Ask for decisions, tradeoffs, missing information, and questions instead of a generic agenda.
No. Recording depends on consent, employer policy, client commitments, and local law. A cleaned written brief is often enough for useful preparation.
Require owners, dates, decisions, unresolved questions, and the next message. If a note has no downstream action or reference value, do not create it.
Editorial note: This page organizes original ThinkShift field notes. It was reviewed on 2026-09-02. Changing product, policy, legal, or security claims require current primary sources and qualified review. See our editorial standards.
One useful shift at a time
Two or three short issues each week. Every issue names a real work moment and leaves you with something you can use.