LANDMARK · 7 MIN · USE
Meetings and summaries
After this landmark, you can direct AI to produce notes that hold the load-bearing parts of a meeting instead of flattening them into pleasant prose.
↗
This concept is shared, but the Everyday lens is less central here.
You can still explore it. We’re showing the shared explanation and a related practical view without hiding the knowledge.
A summary optimises for reading well, which quietly rewards leaving things out. The parts of a meeting that matter later are the awkward ones: what was decided, who owns it, and what’s still unresolved. A model asked to “summarise” will happily smooth those into a tidy narrative that loses exactly the detail you’ll need. If you want the useful version, you have to ask for that structure by name.
This is the canonical concept. It stays the same across learner lenses so personalization never changes the underlying facts.
◌ EVERYDAY LENS
What this looks like for you
Instead of “summarise this call,” ask for decisions, action items with owners, and open questions as separate lists. The shape forces the content to survive.
MAKE A DECISION
AI produces clean minutes from your team call. The action items look tidy, but two tasks have no owner named. What’s the right move?
CARRY THISFor your next meeting, ask AI for three lists — decisions, owners, open questions — and personally verify the open-questions list is complete.