This case study is a PM exercise, not a live LinkedIn product. The strategy, metrics, and architecture are my own work — built to demonstrate how I'd approach a cold-start trust problem in a two-sided marketplace.
My first instinct was that this is a friction problem — verification is too hard, so users skip it. That turned out to be wrong, or at least incomplete.
When I worked through the actual behaviour: job seekers who have tried to verify aren't blocked by friction, they're blocked by indifference. The badge does nothing visible for their career. Recruiters, on the other side, don't filter for it because the verified population is too thin to produce a real signal.
The deeper structural problem is this: badge adoption is currently owned by a trust/safety team with no revenue metric attached to it. It will keep losing in every sprint prioritisation until someone with a P&L stake owns it. That is the real fix, and the product strategy has to reflect it.
Reframed goal: Grow the share of LinkedIn-originated hires where the hired candidate held a Verified Badge (L1+). That's a metric every revenue stakeholder — Recruiter, Jobs, Premium — has a reason to care about.
This is labelled "5 Whys" but it's really a doom loop, not a linear chain. Each Why reinforces the next. You can't break it from either end alone.
| Why | Observation | Why It Causes the Next |
|---|---|---|
| W1 | Badge is framed as a safety/compliance step at signup | Users see no career upside → skip it |
| W2 | Job seekers don't verify → verified pool stays sparse | Recruiters can't rely on it as a filter |
| W3 | Recruiters don't filter → no workflow pressure on candidates | Job seekers see zero FOMO from peers who did verify |
| W4 | No FOMO → no organic adoption → no density growth | Signal stays too weak to trust → back to W2 |
| Root | No internal team owns badge adoption with a revenue target | Demand-side pull has never been engineered — that's what needs to change first |
DigiLocker's exclusion matters at the W4 layer, but it's not the root. Even with DigiLocker, the cold-start loop persists if no one engineers recruiter-side demand first.
Thesis: Stop treating the badge as a standalone identity product. Make it a revenue multiplier embedded inside Recruiter, Jobs, and Premium — so those PMs co-own its adoption with a financial stake.
Pillar 1 — Demand anchor first
Partner with 10 large India employers (HDFC, Infosys, TCS, Reliance-tier) to add a "Verified Preferred" tag on Easy Apply job posts — same UX as the existing Easy Apply toggle, no new workflow for recruiters. Each anchor employer touches ~40–50K applicants/year. We seed visible demand before the product goes GA.
Pillar 2 — Campus bulk supply
University placement offices already hold student records and send bulk employer data over CSV. We flip that relationship: they attest graduating cohorts to LinkedIn via a simple CSV upload + email OTP confirmation. IIT/IIM/top state schools alone represent 400–600K graduates per semester. This solves supply density without asking individuals to do anything.
Pillar 3 — Revenue rail integration