Growth Experiment Brief & Lifecycle Tracker

Most experiment briefs are written after the solution is already half-designed. By then, the problem is written to justify the solution — and the guardrails are aspirational. This template applies two moments where a brief helps most: first, before you have a solution (when you're still in problem space and need input); second, at roughly 70% through solution design (when you need structured feedback before handing off to engineering). Adapted from Japna Sethi's methodology at Productboard — where structured briefs became the coaching mechanism for junior PMs across a PLG motion. You get an 18-record Experiment Briefs workbook covering every lifecycle stage (Problem Space through Killed), a kanban pipeline showing where every experiment stands, and a 6-step task that enforces problem/solution sequencing. The brief exists before the solution. That's the feature. For Growth PMs and growth leads building experimentation rigor on their teams — especially when coaching junior PMs toward tighter hypothesis thinking.