TL;DR: Reframed LinkedIn's Verified Badge from a stalled trust/safety feature into a revenue multiplier by diagnosing the real blocker as organizational (no team owns adoption with a P&L stake) rather than user friction, then designed a three-pillar strategy — demand anchors, campus bulk supply, and revenue-rail integration — to break the resulting cold-start doom loop. Outcome labeled modeled/projected.

Context & Strategic Framing

The brief: badge adoption had stalled. The obvious diagnosis — "verification is too hard" — is incomplete and, I'd argue, wrong. Job seekers who tried to verify weren't blocked by friction; they were blocked by indifference. The badge did nothing visible for their career, so completing it had no payoff.

Root Cause — A Doom Loop, Not a Linear Chain

A standard 5-Whys assumes a linear cause chain. This isn't one — it's self-reinforcing, and you can't break it from either end alone:

• W1 — Safety framing: Badge is framed as compliance at signup → users see no career upside → they skip it.
• W2 — Sparse pool: Verified pool stays thin → recruiters can't rely on it as a search filter.
• W3 — No workflow pressure: Recruiters don't filter on it → job seekers see zero social proof/FOMO from peers who verified.
• W4 — No density growth: No organic adoption → the verified signal stays too weak to trust → loops back to W2.

Structural root: no internal team owns badge adoption with a revenue target. Demand-side pull was never engineered — that's the actual lever, not a friction-reduction UX pass.

Reframed Goal

Grow the share of LinkedIn-originated hires where the hired candidate held a Verified Badge (L1+) — a metric every revenue stakeholder (Recruiter GM, Premium GM) has a reason to own, replacing the vanity metric of raw badge count.

Strategy — Three Pillars

Thesis: stop treating the badge as a standalone identity product; embed it inside Recruiter, Jobs, and Premium so those PMs co-own adoption with a financial stake.

1. Demand anchor first — partner with 10 large India employers (HDFC, Infosys, TCS, Reliance-tier) to add a "Verified Preferred" tag on Easy Apply posts. Each anchor touches ~40–50K applicants/year — this seeds visible, real demand before the general-availability push, rather than hoping supply creates its own demand.
2. Campus bulk supply — university placement offices attest graduating cohorts via CSV upload + email OTP. IIT/IIM/top state schools alone represent 400–600K graduates/semester, solving supply density without requiring 400K individual verification actions.
3. Revenue rail integration — gate the "Verified Pipeline" filter behind Recruiter Pro; add "Verified Boost" as a Premium benefit. This gives the Recruiter PM and Premium PM each a badge-adoption OKR with a dollar figure attached, which is what actually wins internal prioritization fights.

Honest tension flagged explicitly: paywalling the Verified filter too early could slow recruiter adoption in the critical seeding window. My instinct — offer it free to Recruiter Basic for the first 90 days, then move to Pro — is stated as a hypothesis needing pilot data, not a certainty.

Solution Architecture — Progressive Trust Ladder