The mid-review checklist I use so a feedback themes one-pager stays honest

A Notion page called "feedback," twelve Loom comments, a Google Doc of interview notes, and a Slack thread that starts with "quick thoughts" are not insight mid-week. Mid-review is where the same complaint shows up three ways, one loud opinion becomes a roadmap, praise disappears under friction, and "alignment" pretends to be a theme.

I am a freelancer admin helper. I turn messy client feedback dumps into a clean themes one-pager. I am not a CPA, therapist, lawyer, or product coach — and this is not financial, tax, legal, or professional consulting advice. It is the checklist I run mid-review (and again before anyone treats the page as the action list) so the one-pager stays honest while feedback is still arriving.

(If you want the full messy client feedback dump → clean themes one-pager workflow, see my earlier post. This one is the second-pass checklist so duplicate themes, one-off opinions, buried praise, and vibe labels do not quietly rewrite what clients actually said.)

What "honest" looks like mid-review

• Themes are named in plain English — not vibes like "energy," "alignment," or "resonance"
• Each theme has a short evidence line (who / channel / when) without dumping the raw corpus
• Praise and friction are separated so wins do not get buried under complaints
• One-off opinions are labeled one-offs — they do not become roadmaps
• Suggested next actions are concrete (change onboarding email, clarify scope line, keep the kickoff call)
• The page fits a skim: themes first, quotes second, actions last

If the only "themes" page you have is a sticky labeled "people seem unhappy," mid-review honesty has already slipped.

The mid-review checklist (run it before / while you clean)

Use this against the dump (call notes, survey exports, email threads, Slack/Loom comments, testimonials, support tickets, old VoC docs) before you paste everything into a pretty template and call the action list done.

1. Inventory the dump (same day you open the pile)

• [ ] Every scrap is listed once: source, date seen, claim type (praise / friction / request / one-off / risk), notes
• [ ] Duplicate paste of the same comment across Slack + Doc + Notion is labeled duplicate — not counted as three clients
• [ ] Partial claims ("someone said maybe," a screenshot with no context) are labeled incomplete — not invented into tidy themes
• [ ] Time window that matters is named (last 30 days vs last year vs one project) — older noise stays out or flagged
• [ ] Anything clearly resolved, withdrawn, or "nice someday" is labeled stay-off-action — do not resurrect as this week's fix list

2. Separate themes from vibes before you trust labels

• [ ] Theme names are plain English behaviors or outcomes — not mood words
• [ ] Each theme can answer "what keeps showing up?" without reopening every Loom
• [ ] Praise themes and friction themes are split so wins are not footnotes under complaints
• [ ] Requests ("can you add X?") are labeled requests — not silently promoted to product strategy
• [ ] Skim test: you can answer "what are people actually saying?" without reconstructing the dump

3. Lock evidence, audience, and next actions

• [ ] Evidence line exists per theme (who / channel / when) — anonymous vibes without a source are Needs-confirm
• [ ] Audience for the one-pager is named (you, team, or client stakeholder) so tone stays honest
• [ ] Next actions are concrete and owned — "improve communication" is not an action
• [ ] One-offs stay one-offs — a single loud comment does not get a theme row of its own unless it repeats
• [ ] Skim test: you know what to change this week without reopening twelve Looms

4. Catch duplicate themes and quote orphans

• [ ] Same complaint under three theme names is merged — do not fix the same thing thrice
• [ ] Quote bank items map to a theme — orphan quotes without a theme are parked or flagged
• [ ] Marketing-ready praise is separated from operational friction so neither eats the other
• [ ] Threads titled "quick thoughts" without a usable sentence are labeled artifact thin
• [ ] Skim test: sorting by action priority shows a real week, not a graveyard of May sticky notes

5. Honesty tripwires (before you treat the page as action-ready)

• [ ] You did not promote one-off opinions to themes because the theme column looked empty
• [ ] Vibe labels ("alignment," "energy," blank) are mapped to plain themes or flagged Needs-confirm
• [ ] Feedback from six months ago is labeled window unverified until the time window is confirmed — pretty columns do not renew stale VoC
• [ ] Incomplete sections stay Needs-confirm — not silently promoted to "top 3 fixes" because the page looked sparse
• [ ] Resolved items have an archive note so closed feedback is not deleted into amnesia

6. Hand-back sanity check

• [ ] One-pager answers: what themes, what evidence, what praise vs friction, what to do next — without opening the dump
• [ ] Needs-confirm / One-off / Resolved views (or sections) exist so incomplete and dead items are not mixed into this week's actions
• [ ] One sentence of scope on the page: "themes one-pager — not a full research study, brand strategy, or therapy session"
• [ ] Non-advice line present: not CPA / legal / consulting advice; confirm themes with humans before treating this as gospel
• [ ] You would be willing to run this week's fixes from this page without reconstructing Dana from a sticky note

What I do not do on this pass

I do not rebuild their research practice, rewrite their product roadmap, set pricing policy, or give legal/therapy advice. Mid-review honesty is about one trustworthy themes one-pager you can act on this week — not a voice-of-customer suite in a Doc.

Soft CTA

If you want the messy pile turned into that one-pager for you: Client feedback dump → themes one-pager — usually within 24 hours. Code ADMIN12 takes $2 off. Shop: brittanybonds.gumroad.com · catalog mirror: brittany-bonds.github.io