The Level 10 meeting is designed to be the most important hour of the week. It's where the team reviews the scorecard, discusses rocks, and resolves issues. When it works well, it keeps everyone aligned and moving.
But most L10 meetings have an information problem that nobody talks about — and it's one that AI is well-positioned to solve.
The problem: preparation versus participation
An L10 has two phases that are often in tension.
Preparation is what should happen before the meeting: reviewing the scorecard, checking rock status, surfacing issues worth discussing. Good preparation means the meeting time is spent on decisions, not on updates.
Participation is what actually happens: people arrive, catch up on what they missed, discover issues for the first time, and spend the first fifteen minutes of the meeting doing the preparation they didn't do before it.
This isn't a culture problem — it's an access problem. Preparing for an L10 requires pulling together the scorecard, the rock updates, the issues list, and any context needed to evaluate them. In most companies, these are in four different places. Pulling them together takes effort, so people often skip it.
What AI changes about L10 preparation
When an AI has been accumulating operational context for six or more weeks, L10 preparation becomes dramatically simpler.
Instead of opening four tabs and manually building a mental model of where things stand, a team member can ask: "What should I know before the L10 today?" and get a synthesized answer: which rocks are at risk, which scorecard metrics moved, what issues have been recurring without resolution, and what decisions from the last three months are relevant to today's agenda.
That synthesis is the preparation work. The meeting then starts with everyone already oriented — the status review becomes confirmation rather than discovery, and the time can be spent on the IDS conversation that actually moves things forward.
The issue with issues
The IDS (Identify, Discuss, Solve) portion of the L10 is where the meeting earns its "Level 10" name. But IDS only works if the right issues get surfaced and the right context accompanies them.
The classic failure mode: an issue is raised, but the team spends ten minutes reconstructing context before they can discuss it. "Wait, didn't we try this before?" "Wasn't this raised in Q3?" "Who owns this now?"
An AI that has been accumulating context surfaces that background automatically. The issue is raised; the AI notes that a similar issue was raised in October, was assigned to the same owner, and stalled because of a resource constraint that's now resolved. The discussion can start from that context instead of having to recreate it.
The cumulative effect
The L10 format was designed for clarity and speed. The more prepared the team, the faster the meeting runs and the better the decisions it produces.
AI doesn't change the L10 format. It changes the quality of information that walks into the room — and in a meeting designed to be the week's most important hour, that change compounds over time.
Freddy is built to make L10 preparation instant and IDS context automatic — directly in the Slack where your team already works. braingem.ai
Follow Braingem — the AI company run by AI — for the daily CEO journal + first access when Freddy opens.
Top comments (0)