AIDiveForge AIDiveForge
AIDiveForge — Workflow Pack Implementation Guide

Customer Feedback Evidence Brief

Group supplied feedback into themes without turning a small sample into a market claim.

Difficulty: Intermediate Tools: 2 Updated: October 17, 2026
Tools Required
#ToolRoleWebsite
1 Your AI assistant Code and summarize the supplied evidence https://chatgpt.com/
2 LibreOffice or your document editor Review the feedback ledger and follow-up plan https://www.libreoffice.org/
In This Guide

# Customer Feedback Evidence Brief

Group supplied feedback into themes without turning a small sample into a market claim.

1Overview

A coded feedback table, theme summary and follow-up questions.

2Requirements

Provide the feedback, collection context and any allowed segmentation fields.

3Steps

1. 1. Preserve feedback identifiers and remove unnecessary personal data from the analysis copy.

2. 2. Define a small coding scheme and allow multiple themes where the text supports them.

3. 3. Count statements and respondents separately; retain disagreement and negative cases.

4. 4. Write theme summaries with representative source locators and explicit sample limitations.

5. 5. Propose follow-up questions or product checks; do not trigger customer messages or changes automatically.

4Worked example

6. Input

```text F1: setup was confusing, support helped. F2: setup was confusing. F3: setup was easy but export was slow. ```

7. Expected result

```text Themes: setup confusion appears in F1/F2; positive setup experience in F3; helpful support in F1; slow export in F3. This three-item sample does not establish market prevalence. Follow up on the exact setup steps and export conditions. ```

5Acceptance checks

Retain the contradictory setup experience and do not call two comments a population percentage.

6Limits

Themes depend on the collection method and sample. No automatic customer outreach or product prioritization decision is included.

7Suggested tools

Use your browser's print dialog to save as PDF (Ctrl+P / Cmd+P)