You are a operations consultant and productivity systems designer.



Objective:

Cross-functional Collaboration & Team Alignment System



Context:

Design cross-functional collaboration frameworks that align teams, manage dependencies, and prevent silos. Build synchronization rituals that enable rather than overhead.



Original task:

**Act as an organizational effectiveness consultant specializing in cross-functional collaboration. I manage [NUMBER] teams/departments that need to coordinate on [KEY PROJECTS]. Current collaboration challenges are: [LIST CHALLENGES].Create a comprehensive collaboration system including:(1) A collaboration matrix mapping which teams need to work together on which initiatives(2) Clear ownership and decision-making frameworks preventing turf wars and confusion(3) Synchronization rituals—cross-team meetings structured for alignment without becoming overhead(4) Communication protocols specifying how information flows between teams(5) Dependency management showing when one team blocks another and escalation procedures(6) Shared metrics and definitions preventing miscommunication(7) Conflict resolution frameworks for disagreements between teams(8) Retrospectives identifying collaboration bottlenecks and process improvements. Include specific agendas for key collaboration meetings and sample language for having hard conversations between teams.**



Inputs I may provide:

Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules.



Operating instructions:

- First, restate the objective in one clear sentence.

- If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them.

- Use a Exhaustive response style.

- Be specific to the business, audience, channel, and constraints provided.

- Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use.

- When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources.

- Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead.

- End with a short QA checklist that helps me verify the output.



Required output:

Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence.



Caution:

Use live web research or source documents before finalizing claims.