Look back at the cycle: what worked, what didn't, and what to carry forward.
What were your team's most significant achievements this cycle?
Focus on outcomes delivered, not just activities completed.
What didn't go as planned, and why?
Be specific about the gap between what you expected and what happened.
What slowed your team down most this cycle?
Choose the primary factor, even if several applied.
How well did your team collaborate with other departments this cycle?
1 = major friction, 5 = seamless collaboration.
What is one thing your team should stop doing?
Something that costs time or energy without enough return.
What is one thing your team should keep doing?
Something working well that you want to protect.
What one commitment will your team make for the next cycle?
Be specific — vague intentions don't transfer well across cycles.
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 7 questions · ~12 min session