I Was Tasked With Enrolling Millions of Developers in 2FA - Here's What Happened
summary
GitHub plans to require all code contributors to enable 2FA by end of 2023 after voluntary adoption sits under 20%, and the rollout uses push-based 2FA, a new opinionated config flow and a 28‑day verification check plus a public passkeys beta for easier enrollment. Early results: a 42% drop in 2FA support tickets, 33% fewer lockout recovery attempts and a 38% rise in users downloading recovery codes, showing the UX and staged enrollment approach materially reduces incidents.
AI-written summary · about
chapters (12)
- 0:00TFA enrollment challenge
- 2:49Why TFA adoption is low
- 7:03Security versus business goals
- 10:09Strategic planning
- 16:34Building trust in teams
- 20:22Pragmatic decisions
- 23:31UX improvements before enrollment
- 27:04Gradual rollout
- 31:01Communicating change
- 33:48Measuring success
- 35:16GitHub’s TFA lessons
- 37:26Q&A








