Find the Flaw: Auditing a Proposed Segmentation Plan
Objective: Given a written 14-segment plan for a company's next quarter, apply the lesson's segment-quality tests to find which segments should be killed, merged, or fixed.
You're a lifecycle marketer at Casper Sleep reviewing a proposed 14-segment plan before it ships to the whole list.
Score each proposed segment against the lesson's tests for size, stability, and actionability, and recommend which to kill, merge, or keep.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, no account friction
Paid upgrades (optional, faster/deeper)
Confirms which proposed segments are actually static tags versus live behavioral rules
No access? Google Sheets scoring alone is enough to complete the exercise
The process
1 step
Step 01 of 01
The lesson requires every segment to be large enough for meaningful data (a few hundred-plus subscribers), stable across multiple campaigns, and actionable with genuinely different copy.
The plan includes a segment of 40 subscribers ('bought a pillow AND a topper AND left a 5-star review') alongside a static 'joined before 2023' segment. What's wrong with each?
Procedure
- List each of the 14 segments with its subscriber count
- Mark segments under a few hundred subscribers as 'too small, merge or kill'
- Mark any segment defined by a fixed join date instead of ongoing behavior as 'static, needs a behavioral rule'
SEGMENT AUDIT (14 proposed, excerpt) KILL: 'pillow + topper + 5-star review' (40 subscribers, too small for meaningful data) FIX: 'joined before 2023' (static date, replace with 'no purchase in 18 months') KEEP: 'active in past 90 days' (2,400 subscribers, behavioral, actionable)
Healthy
Each surviving segment clears a few hundred subscribers, uses a rule that updates automatically, and has a genuinely different message planned.
Unhealthy
Segments stay in the plan purely because they sound precise, even at 40 subscribers or a frozen join date.
What this means
Precision-sounding segments that fail the size or stability test cost more in campaign overhead than they return in relevance.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| 14 micro-segments planned for one send cycle | Cut to the 3-5 segments that pass all three quality tests before building any campaigns | 30 min |
Final deliverable
An audit table scoring all 14 proposed segments as kill/merge/fix/keep with the reason.
See a reference example
Lenskart Q3 segment audit (excerpt) KILL: 'bought blue-light glasses in March' (85 subscribers) FIX: 'newsletter subscriber since 2022' -> replace with 'no click in 6 months' KEEP: 'cart abandoners, past 30 days' (610 subscribers, behavioral)
Success criteria
You're done when you can:
- Flags the 40-subscriber segment as too small
- Flags the static join-date segment as needing a behavioral rule
- Recommends a final segment count in the 3-5 range consistent with the lesson