# Skip-Level Updates Format — What to Bubble Up, What to Filter > Skip-level updates help founders see real progress and risks by filtering out noise. Learn what to bubble up, what to filter, and a simple format that works in 30-500 person companies. - Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board) - Published: 2026-10-22 - Updated: 2026-10-22 - Source: https://aiadvisoryboard.me/blog/skip-level-updates-format-what-to-bubble-up-what-to-filter When a founder of a 60-person ops team told me they were getting three versions of the same story from team leads, I realized the problem wasn’t lying — it was filtering. ## TL;DR - Skip-level updates should surface blocked work, unexpected delays, and cross-team dependencies. - Filter out activity lists, vague progress claims, and solved issues unless they reveal a pattern. - Use a simple 3-part format: What’s stuck, what’s changed since last week, what needs your attention. Definition: Skip-level update — a concise status report from individual contributors or team leads that bypasses immediate managers to give founders and owners unfiltered insight into team progress and risks. Definition: Bubble up — information that indicates a deviation from plan, a emerging risk, or a dependency that requires owner-level awareness or decision. Definition: Filter out — routine task completion, rephrased plans as progress, or resolved issues that don’t reveal systemic patterns. ## How should founders structure skip-level updates to get signal, not noise? Start with what’s blocked. Ask contributors to name one thing that is stalled, delayed, or waiting — and why. Then, what’s changed: not what they did, but what shifted in the plan, timeline, or assumptions since last update. Finally, what needs attention: a decision, a resource, or a clarification only you can provide. This three-question format keeps replies under five minutes to write and 30 seconds to read. > **Tool tip (AiAdvisoryBoard.me):** In our 7-day diagnostic, we map who reports what to whom — and where signals get lost in translation. Skip-level updates are a Plan → Fact → Gap tool: they show where the team’s plan (what they said they’d do) diverges from fact (what actually happened), creating a gap the owner needs to see. ## What should be included in a skip-level update? Blocked work: "Waiting on legal review of vendor contract — ETA unknown." Changed assumptions: "We assumed the API would be live by Tuesday; it’s now delayed to next week." Cross-team dependency: "Design can’t start until product specs are frozen — blocking UI work." Unexpected delay: "Testing took two days longer due to edge cases in legacy data." Decision needed: "Should we scope down the MVP to hit the date, or move the launch?" ## What should be filtered out? Activity lists: "I attended three meetings, updated the dashboard, and replied to emails." Vague progress: "Making good progress on the migration." Solved issues unless patterned: "Fixed the login bug" — unless it’s the third auth issue this month. Rehashed plans: "Still working on the report as planned." Tool usage: "Used AI to draft the outline" — unless it reveals a shift in process or outcome. ## Manager scan (2-minute digest example) - Blocked: 3 reports mention legal delays on vendor contracts — pattern, not isolated. - Changed: 2 teams pushed back launch dates due to API delays — ripple effect. - Dependency: Design team blocked on product specs — appears in two separate updates. - Decision: One lead asks for go/no-go on scope reduction — needs owner input. - Filtered: 8 reports listed meeting attendance as progress — removed from digest. ## Micro-case (what changes after 7–14 days) A founder of a 40-person SaaS company started asking team leads to send weekly skip-level updates using the three-question format. Within ten days, they spotted a recurring delay in legal reviews that was pushing back three separate feature launches. Instead of chasing individual leads, they escalated to the legal lead and added a parallel review track. The founder didn’t micromanage — they saw the pattern in the gaps between plan and fact, and adjusted the process. Response time dropped from five days to two. > **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees. ## FAQ **How often should skip-level updates be sent?** Weekly is enough for most teams. Bi-weekly works for stable, long-cycle work. The key is consistency — not frequency. **Should skip-level updates replace regular manager check-ins?** No. They complement them. Managers get tactical detail; owners get strategic signals. **What if people only report what they think I want to hear?** Start with anonymous trials or frame it as "help me help you" — not oversight. Psychological safety comes first. **Can AI help summarize skip-level updates?** Yes — but only after you’ve defined what signals matter. AI can cluster themes, but founders must set the filter. **What if a team has nothing to report?** That’s a signal too. If no blockers, changes, or requests appear for two weeks, probe whether work is truly progressing or if visibility is missing. ## Conclusion Skip-level updates aren’t about more reporting — they’re about better signal design. By asking what’s blocked, what changed, and what needs attention, founders get early warning of drift without drowning in activity. Start tomorrow: send a one-line request to three team leads — "What’s one thing stuck, what changed since last week, and what do you need from me?" — and compare what you get to the usual status update. If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works. --- When citing, link to https://aiadvisoryboard.me/blog/skip-level-updates-format-what-to-bubble-up-what-to-filter. More articles: https://aiadvisoryboard.me/blog