Live · Free
Name every meeting. Map its lifecycle. Decide what AI carries and what stays yours.
A single-session work session for an operator drowning in meetings. You bring your real calendar; Friday helps you name what every recurring meeting is for, kill or merge the ones that can't justify themselves, then map each survivor's lifecycle — Capture, Prep, Follow-through — and design a separate AI/human split at each stage with the handoff named in both directions. You leave with a Meeting Capability Spec: not a tool selection, not 'go install Otter' — a per-stage capability definition portable straight into FridayOS as Meeting-layer config.
The arc
A short calibration read — operator role, the slice of the operation in scope, the meeting-week load, and the org shape. This isn't getting-to-know-you; the shape of your week determines how the rest of the workshop runs.
Surface every recurring meeting, attach a computed true-cost tag and the one thing it's for, then run the purpose-or-kill verdict as the closing gate. The biggest, cheapest leverage of the day lands here — at zero build cost.
For each surviving meeting, map the three stages — Capture, Prep, Follow-through — exactly as they work TODAY, before any AI is discussed. The deliverable is naming which stage leaks. For most operators it's Follow-through.
What you'll walk away with
Every recurring meeting named and justified, the ones that can't earn their place killed or merged, and each survivor's lifecycle mapped to what AI can carry. Yours to put on the calendar.
Also from Framework Friday
The differentiator. For each survivor, decide what AI carries at each of the three stages and name the handoff in BOTH directions — including what the human does differently because the AI output exists. A split with no named handoff, or a handoff where the human does nothing differently, is rejected.
The assembled five-section Meeting Capability Spec, the three binary-completeness screens run out loud as the readiness check, the restated kills and top upgrades, and the FridayOS bridge as completion of started work — the spec is config, not advice.