Synthesize skip-level notes into org-wide systemic themes

Group individual skip-level feedback into root-cause operational themes while protecting team member confidentiality.

Prompt

Prompt
Act as an organizational development advisor for senior executives. Analyze raw notes from multiple skip-level interviews to uncover systemic themes across the department. Rules: Remove all individual employee names or identifying details; categorize feedback into organizational themes rather than isolated complaints; distinguish between process bottlenecks, tooling gaps, and team communication breakdowns; highlight high-impact risks that need executive intervention. Output format: 1. Executive Summary (3 sentences), 2. Recurring Themes Table (Columns: Theme, Signal Description, Impact Level, Suggested Leadership Action), 3. Blocker Prioritization (top 2 urgent items to address first). The raw notes are below:

Example output

Example for: raw notes from 6 skip-level interviews across design and product

1. Executive Summary

Individual contributors report high alignment with company goals but face chronic delivery drag caused by ambiguous decision ownership. Cross-functional friction between design and engineering is increasing cycle times and burning sprint capacity. Addressing review bottlenecks will quickly restore team momentum.

2. Recurring Themes Table
ThemeSignal DescriptionImpact LevelSuggested Leadership Action
Approval BottlenecksWork stalls while waiting for late-stage sign-offs from multiple product directors.HighImplement a documented decision-rights framework (e.g., DACI) for product reviews.
Tooling FragmentationDesign files, specs, and Jira tickets are frequently out of sync across squads.MediumStandardize handoff templates and establish an agreed source of truth for technical specs.
Unclear Career PathsSenior individual contributors report ambiguity on growth tracks past senior level.MediumPartner with HR to publish concrete level competencies before the next review cycle.
3. Blocker Prioritization
  1. Ambiguous sign-off ownership: Directly causing delivery slippage on core Q3 milestones; clear decision rights are needed immediately.
  2. Tooling fragmentation: Causes daily rework; team leads can align on standard documentation rules within two weeks.
Written by AI from this prompt. Your results will vary.

Paste the prompt into ChatGPT, Claude, or Gemini, then paste your raw meeting notes immediately following the last line. Follow up by asking the model to draft an announcement email addressing the top theme to the entire team.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Meetings & Notes
Meetings & Notes

Prepare talking points for a tough meeting

Frame difficult news like budget cuts, project delays, or pivots with clarity and composure. Use it before addressing stakeholders or your team under pressure.