Skip to content
Academy
Marketing Academy · Field Work●Growth Marketing
MiniTeardown· 25 minutes

The Pre-Publish Review: Teardown of Four Post Drafts

Care.com

Objective: Given four synthetic build-in-public post drafts queued for the week, apply the share/keep-private framework to catch the ones that would leak competitive intel, post an unverified number, or fail to say anything specific.

You're the growth marketer at Care.com, the online marketplace for family, child, senior, and pet care services, doing the Friday pre-publish review of next week's build-in-public queue.

Read each draft, decide whether it's safe to publish as written, and cite the specific rule it breaks if not.

Before you start

What you'll need

Free path (everything below is enough to finish)

Notion
FreemiumRun the pre-publish checklist against the lesson's share/keep-private rules

Free, works as a lightweight review doc before anything goes out

The process

Specimens to review

Safe to publish as written?

Sample output
Draft post: 'Huge news brewing — we're deep in talks with a major daycare chain about a co-marketing partnership, terms are looking great and we might announce pricing details next week!'

Specimen: synthetic, realistic

Safe to publish as written?

Sample output
Draft post: 'Such a great month for the team, momentum is really building and we're excited about where things are headed!'

Specimen: synthetic, realistic

Safe to publish as written?

Sample output
Draft post: 'Sharing our full growth playbook: we're spending $18K/month on TikTok ads targeting new-parent lookalike audiences at a $6.40 CPA, up 40% MoM since we found this exact targeting combo.'

Specimen: synthetic, realistic

Safe to publish as written?

Sample output
Draft post: 'We crossed 50,000 active families on the platform this week, up from 41,000 three months ago. That's the number, pulled straight from this morning's dashboard.'

Specimen: synthetic, realistic

Final deliverable

A hold/publish decision for each of the 4 drafts, with the specific rule cited for every hold.

See a reference example
Sample output
Zendesk, pre-publish queue review (excerpt)

DRAFT 1 (partnership talks): HOLD — active negotiation
DRAFT 2 ('great momentum'): HOLD — no specific number, rewrite before it goes out
DRAFT 3 (exact TikTok spend/targeting): HOLD — channel spend + moat leak
DRAFT 4 (verified user count): PUBLISH — specific, dashboard-checked number

Success criteria

You're done when you can:

  • Holds the negotiation-leak and channel-spend-leak drafts with the correct cited rule
  • Flags the vague-momentum draft for lacking specificity rather than approving it
  • Approves the verified-milestone draft without flagging a false defect