Fifteen minutes before each meeting, attendees get a Slack DM with relevant notes, pull requests, and tickets.
It branches. Every path runs; all paths must finish before it continues; runs once per each meeting attendee.
Pattern: Parallel Split (2) · Synchronisation (3) · Multiple Instances with a priori Design-Time Knowledge (13)
Walking into a meeting without the context from last time, or without knowing what's already in progress, wastes everyone's time. Digging through Notion, GitHub, and Jira right before a call to catch up is a scramble nobody enjoys.
Engineering managers, product managers, and team leads who run recurring status or planning meetings.
Fifteen minutes before each meeting, every attendee gets a Slack message with relevant notes, pull requests, and tickets pulled together for them.
The hard question is not how to build it. It is whether this is the right thing to build first.
That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.
Let's Talk Strategy