The before-you-share checklist I use so a feedback themes one-pager stays honest

Mid-review honesty is necessary. Before-you-share is different. The morning you decide "I will send this themes one-pager to the client / stakeholder today" is when duplicate themes still sit under three names, a single loud opinion still looks like a roadmap, praise is buried under friction, orphan quotes float with no theme, "alignment" is still pretending to be a finding, and a raw Slack dump screenshot quietly hitchhikes into the share view.

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, marketer, or product coach — and this is not financial, tax, legal, marketing, or professional consulting advice. It is the checklist I run the day I am about to share (the final pass before anyone treats the page as the client-facing truth) so themes are not duplicated, one-offs are not roadmap, praise is not buried, quote orphans are fixed, and fake alignment vibes do not ship.

This is complementary to my earlier posts — not a rewrite. For the full messy client feedback dump → clean themes one-pager workflow, see How I turn a messy client feedback dump into a clean themes one-pager. For the mid-review honesty pass while feedback is still arriving, see The mid-review checklist I use so a feedback themes one-pager stays honest. This third pass is the before-you-share check: mid-review honesty is not enough once a real human is about to read it as settled.

What "honest enough to share" looks like

• Themes are named in plain English — not vibes like "energy," "alignment," or "resonance"
• Duplicate complaints under three theme names are already merged — the reader should not fix the same thing thrice
• Praise and friction are both visible — wins are not footnotes under a wall of complaints
• One-off opinions are labeled one-offs — they do not read as commitments or roadmap
• Every shareable quote maps to a theme — orphan quotes are parked or cut, not floating
• Raw dump artifacts (Slack screenshots, named complainers, unfinished notes) are out of the share view
• Suggested next actions are concrete and owned — "improve communication" does not ship as an action
• You can answer "what did people actually say?" without reconstructing twelve Looms

If the only share plan you have is a sticky labeled "send the feedback doc?" before-you-share honesty has already slipped.

The before-you-share checklist (run it before anyone hits send)

Use this against the near-final themes one-pager and the live artifacts (Notion page, quote bank, Loom notes, Slack threads, survey export) before anyone treats the page as the client-facing or stakeholder-facing truth.

1. Collapse duplicate themes before a human reads three versions

• [ ] Same complaint under three theme names is merged — do not ship "slow replies," "response lag," and "comms delay" as three findings
• [ ] Synonym piles are named once in plain English — vibes and thesaurus entries are not themes
• [ ] Time window on the page matches what you are claiming (last 30 days vs last year vs one project)
• [ ] Soft "someone said once" rows still say one-off — they are not auto-promoted to Top Theme because the list looked thin
• [ ] Skim test: every theme left on the share view is something you would still defend out loud today

2. Keep praise visible — do not bury wins under friction

• [ ] Praise-to-protect section is present and above-the-fold enough that a skim finds it
• [ ] Marketing-ready praise is separated from operational friction so neither eats the other
• [ ] You did not delete praise to make the page "look serious" for a tough stakeholder
• [ ] Wins that must not be "fixed" by accident are named (keep the kickoff call, keep the summary email)
• [ ] Skim test: a friendly reader and a skeptical reader both see what clients already like

3. Stop one-offs and vibe labels from becoming the roadmap

• [ ] One-off opinions stay labeled one-offs — a single loud comment does not get a theme row of its own unless it repeats
• [ ] Requests ("can you add X?") stay labeled requests — not silently promoted to product strategy on the share page
• [ ] Vibe labels ("alignment," "energy," blank) are mapped to plain themes or flagged Needs-confirm — they do not ship as findings
• [ ] Incomplete / partial claims stay Needs-confirm — not silently promoted to "top 3 fixes" because the page looked sparse
• [ ] Skim test: sorting by action priority shows a real week, not a graveyard of May sticky notes dressed as strategy

4. Fix quote orphans and strip dump artifacts from the share view

• [ ] Every shareable quote maps to a named theme — orphan quotes without a theme are parked, cut, or flagged
• [ ] Quotes that must stay anonymous are anonymized — named complainers do not hitchhike into a client-facing page unless that was the ask
• [ ] Raw Slack / Loom / Doc dump screenshots are out of the share view — evidence lines stay short
• [ ] Threads titled "quick thoughts" without a usable sentence are labeled artifact thin and stay off the share list
• [ ] Skim test: you could paste the quote bank into a proposal without reopening the dump or outing someone

5. Before-you-share honesty tripwires

• [ ] You did not invent a theme just to fill the column before a stakeholder meeting
• [ ] You did not promote one-offs to themes because the theme column looked empty
• [ ] Audience for this share is named (you / team / client stakeholder) so tone and anonymization match
• [ ] Actions assign work to named owners on your side where needed — "the client should feel heard" is not an action
• [ ] One sentence of scope on the page: "themes one-pager — not a full research study, brand strategy, marketing brief, or therapy session"
• [ ] Non-advice line present: not CPA / legal / marketing / consulting advice; confirm themes with humans before treating this as gospel
• [ ] You would be willing to sit in the room while this exact page is read aloud

6. Last skim before send

• [ ] One-pager answers: what themes, what evidence, what praise vs friction, what one-offs, what to do next — without opening the dump
• [ ] Needs-confirm / One-off / Resolved sections (or labels) are visible — not deleted so the page looks tidy for the meeting
• [ ] You know which items are share-today vs wait-for-confirm
• [ ] Anything that should not leave the building (raw names, unfinished notes, twin duplicate themes, vibe "alignment") is already off the share view

What I do not do on this pass

I do not rebuild their research practice, rewrite their product roadmap, write marketing copy from unverified quotes, set pricing policy, or give legal/therapy/consulting advice. Before-you-share honesty is about one trustworthy themes one-pager a human can read without getting lied to by duplicates, one-offs, buried praise, orphan quotes, or fake alignment vibes — 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