ThinkWithPrompt by SynotticThinkWithPrompt

Find duplicated work and silo thinking across teams

Spots teams doing the same work twice or optimizing for their own goals at the expense of the whole, and suggests fixes.

Projects & OperationsFew-ShotStandardAnalyzeFill-in Template

The prompt

Help me find duplicated work and places where teams optimize for themselves instead of the whole organization. Overall goal or outcome: [WHAT THE TEAMS ARE MEANT TO ACHIEVE TOGETHER] Teams and what each is doing: [PASTE roadmaps, project lists, OKRs, team plans] Each team's targets: [METRICS each team is measured on] Symptoms I've noticed: [e.g. "two teams built similar dashboards", "ops cuts cost but customer complaints rise"] Look for: 1. Duplication: similar projects, tools, reports, data sets, vendor contracts, or analyses in more than one team. 2. Local optimization: a team hitting its target in a way that hurts another team or the shared outcome (e.g. sales closing deals delivery can't serve, procurement saving cost but delaying projects). 3. Conflicting targets that push teams in opposite directions. 4. Work nobody owns because each team assumes another does it. Return: 1. Duplication table: Work item | Teams involved | Overlap (full / partial) | Estimated wasted effort (from my data, or [ESTIMATE]) | Suggested owner. 2. Local optimization table: Team | What they optimize | Effect on others or the whole | Evidence | Fix (shared metric, handoff rule, joint review). 3. The 3 changes with the biggest payoff. 4. Questions to raise with team leads to confirm before acting. Treat duplication as a design problem, not a performance failure. Mark assumptions clearly; some apparent overlap may be deliberate.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Projects & Operations prompts

What to fill in

  • WHAT THE TEAMS ARE MEANT TO ACHIEVE TOGETHER
  • PASTE roadmaps, project lists, OKRs, team plans
  • METRICS each team is measured on
  • ESTIMATE

How this prompt is built

This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.

Related prompts

Find more prompts like this