Your sprint wrapped. The retrospective happened. You've got a list of what went well, what didn't, and three action items nobody will remember by next Monday. The problem: those insights are stuck in a document. They won't move the needle with stakeholders or stick with the team unless you show them, not tell them.
That's where retrospective infographics come in. A well-designed visual takes the messy conversation from your retro and converts it into something people actually look at, understand, and act on. But designing that visual from scratch takes time you don't have. ChatGPT can help. The right prompts can extract patterns from your retro notes, suggest design layouts, and even generate copy for your infographics.
Below are seven prompts, each designed for a specific stage of turning retrospective data into impactful visuals. Start with planning, move through execution and analysis, then use the communication and iteration prompts to refine your approach over time.
Identify Key Themes for Visual Storytelling
Use this prompt after your retrospective when you have raw notes but haven't yet decided what story the data should tell. A Scrum Master with a 6-person team and 14-day sprints will find this especially useful for distilling 30+ discussion points into 4-5 visual themes.
You are an experienced Scrum Master with 12 years facilitating retrospectives across teams of 3 to 50 people. Your strength is pattern recognition: you can spot recurring themes in messy team feedback and translate them into clear, actionable narratives.
Context: I just finished a sprint retrospective with a [team size]-person team working in [sprint length]-week sprints. We use [primary tools or tech stack]. The team's maturity level is [early-stage/established/high-performing].
Task: Extract the 4–5 most important themes from these retro notes and suggest a visual angle for each one.
Constraints:
- Themes must be recurring or high-impact (mentioned by multiple people or affecting velocity/quality).
- Avoid generic themes like "communication is important." Be specific: "Slack notifications during focus time fragment work."
- Surface one theme that surprised you or contradicted team assumptions.
- Rank themes by impact on next sprint, not by frequency alone.
- Output format: numbered list with theme name (bold), 1-sentence description, and one suggested visual format (e.g., "stacked bar chart," "comparison timeline," "fishbone diagram").
- Do not suggest pie charts. They obscure data.
- Do not recommend more than 5 themes; prioritize ruthlessly.
Input: [Paste your retrospective notes here]
Output:
Variables to fill in
[team size]— number of people in your team, typically 3–9 for Scrum[sprint length]— your sprint duration in weeks, typically 1 or 2[primary tools or tech stack]— the platforms your team uses (e.g., "Jira, Slack, React") or leave blank if not relevant[early-stage/established/high-performing]— how long the team has worked together and how mature their processes are
What to expect
You'll get 4–5 themes with specific language (not jargon), a one-sentence rationale for each, and a visual recommendation. The output will flag one counterintuitive insight that's worth highlighting in your infographic.
When to skip it
Skip this if your retrospective was very small (under 3 people) or if you already know exactly which 2–3 data points you want to visualize. This prompt shines when you have rich notes and need help deciding what matters most.
Design a Retrospective Infographic Layout
Once you know your themes, use this prompt to sketch a visual layout before you open design software. This saves time and ensures your infographic tells a coherent story, not just dumps data on a page.
You are a UX-savvy Scrum Master and information designer. You understand how teams absorb visual information and you design infographics that work on a 1-page printout, a Slack message, and a monitor.
Context: I'm creating an infographic to communicate retrospective insights to a [audience: team/leadership/cross-functional stakeholders]. The infographic will be shared via [channels: email/Slack/printed/presentation]. The audience's familiarity with Agile is [low/medium/high].
Task: Suggest a layout structure for an infographic that tells this story: [your 4–5 themes from Prompt 1].
Constraints:
- The layout must fit on a single page or screen (no scrolling required).
- Prioritize the top 2 themes visually; the remaining themes should be supporting details.
- Include one section for "what we're doing about it" (action items) so the infographic isn't just diagnostic.
- Use a hierarchy: headline, 2–3 key insights, supporting data, action items.
- Avoid clutter. Whitespace is your friend.
- Suggest a color palette (e.g., 2–3 brand colors plus neutral) and font pairing if you have brand guidelines; otherwise, suggest readable defaults.
- Output format: ASCII sketch or detailed text description of sections from top to bottom, with recommended dimensions and color assignments.
- Do not suggest animations or interactive elements; this is static.
Input: [Describe your themes and the story you want to tell]
Variables to fill in
[audience: team/leadership/cross-functional stakeholders]— who will see this infographic[channels: email/Slack/printed/presentation]— where the infographic will be shared[low/medium/high]— how familiar your audience is with Agile concepts and sprint retrospectives[your 4–5 themes from Prompt 1]— paste the themes you extracted in Prompt 1
What to expect
You'll receive a layout blueprint with section recommendations, a suggested color scheme, and rationale for the visual hierarchy. If you share brand guidelines, ChatGPT will incorporate them.
When to skip it
Skip this if you already have a template or design tool you're comfortable with, or if your organization mandates a specific infographic format. This prompt is most valuable when you're starting from scratch.
Extract Quantitative Insights From Retro Data
Retros are mostly qualitative. But numbers stick. This prompt helps you surface or calculate metrics from your retro conversation that can anchor your infographic and make the story more credible.
You are a data-minded Scrum Master. You know how to extract meaningful metrics from retrospective discussions without cherry-picking data to support a predetermined conclusion.
Context: Our team is [team size] people. We've run [number] sprints in the past [timeframe]. Our primary metric for success is [velocity/quality/predictability/team satisfaction]. We're currently [struggling with/optimizing/maintaining] [specific challenge].
Task: Identify 3–5 quantifiable metrics or data points I can extract or calculate from my retrospective notes and historical sprint data to support the themes I want to visualize.
Constraints:
- Metrics must be traceable to actual retro feedback or sprint data (not speculation).
- Avoid vanity metrics (e.g., "lines of code"). Focus on outcomes and team health.
- Include at least one metric about team perception or satisfaction, not just velocity.
- For each metric, explain how to measure it going forward so it becomes a leading indicator, not a lagging one.
- Output format: bulleted list with metric name (bold), current value or trend, why it matters, and how to track it next sprint.
- Do not invent metrics that require tools you don't have access to.
Input: [Paste your retrospective notes and any sprint velocity or quality data you have]
Variables to fill in
[team size]— number of people on the team[number]— how many sprints you've completed[timeframe]— time period (e.g., "past 6 weeks" or "past quarter")[velocity/quality/predictability/team satisfaction]— what your team optimizes for[struggling with/optimizing/maintaining]— your current focus area[specific challenge]— the challenge you named above (e.g., "unplanned interruptions")
What to expect
You'll get 3–5 metrics with current baselines, a one-sentence explanation of why each matters, and a suggestion for how to track it in future sprints. Some metrics may require you to ask the team or dig into your sprint tool.
When to skip it
Skip this if your retrospective was focused entirely on process or interpersonal dynamics and didn't touch on delivery metrics. This prompt is most useful when you want to quantify team health or sprint performance.
Craft Copy and Captions for Your Infographic
A beautiful chart with no context confuses people. This prompt generates clear, concise captions and callout text that guide the reader through your visual story without overwhelming them.
You are a technical writer who specializes in making Agile concepts accessible to mixed audiences. You write captions that are clear, specific, and jargon-light.
Context: I'm creating an infographic for [audience] about a sprint retrospective. The team is [team size] people, and we work in [sprint length]-week sprints. The infographic will be shared via [channel]. The audience's Agile literacy is [low/medium/high].
Task: Write a headline, subheading, 3–5 section captions, and a closing call-to-action for an infographic that visualizes these themes: [your themes].
Constraints:
- Headline must be under 10 words and immediately answer "Why should I care?"
- Captions must be under 2 sentences each; one sentence is better.
- Use active voice. Avoid passive constructions like "It was found that."
- Define any Agile terms (e.g., "sprint," "backlog") for low-literacy audiences; skip definitions for high-literacy ones.
- Tone: professional but conversational. No corporate jargon or buzzwords.
- Output format: labeled sections (Headline, Subheading, Section 1 Caption, Section 2 Caption, etc., Call-to-Action) with the text for each.
- Do not use exclamation marks. Do not use ALL CAPS for emphasis.
- The call-to-action should direct the audience to a next step (e.g., "Join us in sprint planning on Thursday" or "Read the full retro summary here").
Input: [Describe the themes, metrics, and story your infographic tells]
Variables to fill in
[audience]— who will read this (team, leadership, stakeholders)[team size]— number of people on the team[sprint length]— sprint duration in weeks[channel]— where it will be shared (email, Slack, printed, presentation)[low/medium/high]— Agile literacy level of the audience[your themes]— the 4–5 themes you identified earlier
What to expect
You'll receive a complete set of copy: a punchy headline, a clarifying subheading, section-by-section captions that guide the eye through your visual, and a concrete call-to-action. All language will be clear and specific.
When to skip it
Skip this if you're creating an internal team infographic that doesn't need formal copy, or if you have a communications team handling all text. This prompt is most valuable for stakeholder-facing retrospective summaries.
Suggest Visual Formats for Different Data Types
Not all data looks good in the same format. A timeline works for sequencing problems; a comparison chart works for before-and-after; a fishbone works for root causes. This prompt matches your data to the right visual format and explains why.
You are an information designer with deep experience in Agile retrospectives. You know which visual formats work for which types of retro data and why some combinations confuse rather than clarify.
Context: I'm visualizing retro insights for a [audience]. The team's technical literacy is [low/medium/high], and they're used to seeing data presented as [typical format: dashboards/reports/slides/infographics].
Task: Recommend the best visual format for each of these data points, and explain why it works better than alternatives: [your themes and metrics].
Constraints:
- Recommend formats that work in static media (no animations or interactivity).
- For each format, suggest one alternative and explain why you didn't pick it.
- Avoid pie charts, 3D charts, and dual-axis charts; they confuse more than they clarify.
- If a data point is qualitative (e.g., "team morale"), suggest a visual metaphor or icon-based approach instead of a traditional chart.
- Output format: for each data point, list the recommended format (bold), a 1-sentence rationale, one alternative, and why the alternative is weaker.
- Consider color-blind accessibility; recommend formats that don't rely solely on color to distinguish categories.
Input: [List your themes and metrics with brief descriptions of the data in each]
Variables to fill in
[audience]— who will see this (team, leadership, stakeholders)[low/medium/high]— technical literacy of the audience[typical format: dashboards/reports/slides/infographics]— what format your audience is accustomed to[your themes and metrics]— the data points you want to visualize
What to expect
You'll receive a format recommendation for each data point with a clear rationale. ChatGPT will flag formats that look nice but don't work well for your specific data or audience.
When to skip it
Skip this if you already have a design tool and you're comfortable choosing formats yourself, or if your organization has a standard template. This prompt is most useful when you're unsure whether a bar chart or a timeline makes more sense.
Generate Actionable Insights From Patterns
An infographic that just reports what happened isn't enough. This prompt helps you surface patterns and generate specific, trackable action items that your team can commit to and your infographic can highlight.
You are an experienced Scrum Master who specializes in turning retrospective observations into concrete, measurable action items that teams actually complete.
Context: Our team is [team size] people working in [sprint length]-week sprints. We've identified these themes from our retrospective: [your themes]. Our team's typical capacity for new initiatives is [low/medium/high], and we're currently [well-resourced/stretched/overwhelmed].
Task: For each theme, identify the underlying pattern and suggest 1–2 specific, measurable action items the team can commit to in the next [sprint length] sprints.
Constraints:
- Action items must be completable within [sprint length] sprints, not vague aspirations.
- Each action item must have a single owner and a clear success metric.
- Avoid action items that require organizational change or new tools; focus on team-level changes first.
- If a theme points to a systemic problem (e.g., "too many interruptions"), suggest a team-level workaround and a longer-term escalation point.
- Output format: for each theme, list the pattern (bold), 1–2 action items with owner and success metric, and a confidence level (high/medium/low) that the team will complete it.
- Rank action items by impact and feasibility; put the "quick win" first.
- Do not include action items that are just "communicate better" or "be more proactive."
Input: [Paste your retrospective notes and themes]
Variables to fill in
[team size]— number of people on the team[sprint length]— sprint duration in weeks[your themes]— the themes you identified in Prompt 1[low/medium/high]— how much extra capacity the team has for new initiatives[well-resourced/stretched/overwhelmed]— the team's current workload status[sprint length]— sprint duration (repeated for clarity)
What to expect
You'll receive specific action items tied to each theme, with an owner, a success metric, and a feasibility assessment. The output will prioritize quick wins to build momentum.
When to skip it
Skip this if your retrospective was purely celebratory (all "what went well") or if you've already drafted action items and just want to validate them. This prompt is most useful when you need help translating themes into commitments.
Plan Your Retrospective Infographic Evolution
Your first infographic sets a baseline. This final prompt helps you plan how to iterate: What data should you track differently next sprint? How should the visual evolve? What feedback should you gather from your audience?
You are a continuous-improvement-minded Scrum Master. You treat retrospective infographics as artifacts that should evolve each sprint based on what you learn about your team and your audience.
Context: I just created a retrospective infographic for [audience]. The team is [team size] people in [sprint length]-week sprints. This is sprint [number] of [total sprints completed], so we're [early in our Agile journey/well-established]. The infographic focused on these themes: [your themes].
Task: Suggest how to evolve the retrospective infographic format and content for the next 2–3 sprints, and identify what feedback you should gather from your audience.
Constraints:
- Suggest one structural change (layout, format, or data type) that will improve clarity or engagement.
- Suggest one new metric or data point to track that wasn't visible in this sprint's retro.
- Identify 2–3 specific questions to ask your audience (team or stakeholders) about what worked and what didn't in this infographic.
- Do not suggest adding more data or themes; suggest replacing or refining existing ones.
- Output format: three labeled sections (Structural Evolution, New Metric, Feedback Questions) with 1–2 bullet points under each.
- Consider your team's appetite for change; if they're early-stage, suggest small, low-friction iterations. If they're established, suggest bolder experiments.
Input: [Describe your current infographic: what it shows, how it's received, and what feedback you've heard so far]
Variables to fill in
[audience]— who sees the infographic (team, leadership, stakeholders)[team size]— number of people on the team[sprint length]— sprint duration in weeks[number]— which sprint this is (e.g., "sprint 5")[total sprints completed]— how many sprints the team has done[early in our Agile journey/well-established]— team maturity[your themes]— the themes from your current infographic
What to expect
You'll receive a concrete evolution plan: one structural change, one new metric to pilot, and specific feedback questions. The suggestions will be calibrated to your team's maturity and change capacity.
When to skip it
Skip this if this is your first retrospective infographic and you want to see how it lands before iterating. Come back to this prompt after you've shared your first infographic and gathered initial reactions.
How to Use These Prompts
Start with Prompt 1 immediately after your retrospective, while the conversation is fresh. Move through Prompts 2–5 in order as you design and refine your visual. Use Prompt 6 to ensure your infographic drives action, not just awareness. Return to Prompt 7 after you've shared your infographic and gathered feedback.
Not every team needs all seven prompts. A small, co-located team might skip Prompt 4 (copy writing) and hand-draft their layout. A distributed team might lean heavily on Prompts 2 and 4 to ensure the infographic is self-explanatory. Adapt the prompts to your context.
The goal isn't to automate retrospectives. ChatGPT can't replace the conversation or the team's judgment. What these prompts do is compress the design and synthesis work so you spend more time on what matters: the team's insights and their commitment to change.
If you want to deepen your retrospective facilitation skills beyond infographics, consider the Certified Scrum Master (CSM) certification or join one of our upcoming training sessions. Giora Morein and the ThinkLouder team have trained over 45,000 professionals in Scrum practices, and we've seen firsthand how strong retrospectives compound over time. A well-run retro that's communicated clearly can shift team culture in a single sprint.
One short email, every other Friday. Real-world Scrum lessons, no fluff. Unsubscribe anytime.