Mastering Sprint Planning for SEOs — with Gus Pelogia | Ep.12
In this episode of SEO Product Unveiled, Björn and Vanda welcome Gus Pelogia, Senior SEO Product Manager at Indeed, to unpack one of the most misunderstood yet critical product ceremonies: Sprint Planning.They discuss how SEOs can collaborate effectively with engineering and product teams, what makes a good sprint-ready ticket, and why understanding technical complexity is essential to avoid frustration and misaligned expectations. Gus shares insights from his unique journey from journalism to tech SEO and then into product management.The conversation explores prioritization frameworks like ICE, how to set meaningful Sprint Goals, why "Big Bets" per quarter improve execution, and how SEOs can bridge the gap between strategic vision and engineering constraints. The trio also reflects on documentation quality, success criteria, capacity planning, and the importance of bringing data, hypotheses, and impact estimates into sprint conversations.A valuable episode for anyone working at the intersection of SEO, Product, and Engineering — whether embedded in a product org or influencing from the outside.Main TakeawaysSprint Planning = Choosing what will realistically be delivered in the next 1–4 weeks, based on ready tickets and team capacity.SEOs must understand technical complexity — simple SEO changes can require deep engineering work.Good tickets matter: clear user story, acceptance criteria, examples, mockups, and impact estimation.Impact frameworks (like ICE) help product teams prioritize SEO requests fairly.Big Bets per quarter improve focus and prevent overloaded roadmaps.SEO must communicate in product/engineering language — not just SEO jargon.Being present in Sprint Planning helps SEOs avoid missed timelines, misinterpretations, and seasonal “dead zones” like release freezes.Impact validation is key: share results back with engineering to build trust and momentum.Listen to engineers: better solutions often emerge from collaboration.Document everything thoroughly — unclear tickets are a major cause of delays.⏱️ Chapter Marks0:00 — Introduction & reconnecting0:40 — Who is Gus Pelogia? Background & SEO/Product journey2:00 — From journalism to tech SEO to product4:20 — Why Sprint Planning matters for SEOs5:10 — Why simple ideas often require complex engineering6:40 — What Sprint Planning actually is8:00 — The importance of “ready” tickets9:05 — Sprint Goals: Why they matter10:00 — Capacity, ad-hoc issues & prioritization challenges11:20 — When SEOs feel blocked by engineering constraints13:10 — Prioritization frameworks (e.g., ICE) for SEO requests14:25 — How engineers allocate story points16:30 — Why SEOs need impact hypotheses18:55 — Using impact scores in product discussions19:35 — How Gus structures quarterly Big Bets21:00 — Understanding complexity & trade-offs22:32 — Overloaded roadmaps & realistic planning24:20 — SEOs working across multiple product teams26:23 — Should SEOs attend Sprint Planning?28:20 — Holiday freeze example & timeline risks29:30 — Importance of clarifying tickets early31:20 — What makes a good, sprint-ready SEO ticket33:35 — Mockups, visual examples & acceptance criteria35:35 — How to deal with success criteria38:16 — Why impact validation is hard but necessary40:33 — Setting expectations with ROI timelines41:17 — What SEOs and PMs can learn from each other42:20 — Using initiatives instead of isolated tasks44:13 — Lessons SEOs can borrow from product thinking47:00 — Listening to engineers & iterating together49:25 — Final tips for SEOs and PMs50:53 — Closing thoughts & outro