Capture what happened at the seams of a shared project — where friction emerged, what each team assumed, and what to carry forward.
What initiative or project are we debriefing, and which team are you representing?
Name the project, your team or function, and your role in it.
Where did collaboration across teams work well on this initiative?
Specific moments, decisions, or handoffs that went smoothly — and why.
Where did cross-team friction slow things down or cause problems?
Misaligned expectations, unclear ownership, communication gaps, or conflicting priorities.
What did you assume about another team's work that turned out to be wrong?
Assumptions about timelines, capabilities, priorities, or how decisions were being made.
What should have been decided earlier that caused downstream problems?
Ownership, scope, tooling, process — anything where ambiguity created rework.
What would you change about how cross-team collaboration is structured for the next initiative?
Meeting cadence, decision rights, shared documentation, escalation paths — anything structural.
After each completed session, Mayetik generates a structured AI summary. Here's an example of the output format — the actual content reflects each respondent's answers.
The respondent's answers highlighted three recurring themes — each supported by specific examples drawn from their experience. The summary captures what was said, not what was expected.
Two responses stood out as unusually detailed and pointed to an area worth following up on. The full text of each answer is preserved below the summary.
Based on the patterns in this session, the AI identified three concrete actions for the project team to consider. These are drawn directly from the respondent's own suggestions.
Generated from 6 questions · ~3 min session