Lenny's PodcastAn inside look at how CNN builds product | Upasna Gautam
CHAPTERS
- 0:00 – 0:45
Breaking news chaos: why buffers and backup plans are non-negotiable
Upasna opens with a real day-to-day reality at CNN: carefully planned research sessions can be instantly derailed by breaking news. She explains the mindset shift required—expect disruption, build buffers, and always have a backup plan ready.
- •Breaking news regularly interrupts planned user research and testing
- •Frustration is natural, but teams must be ready to pivot immediately
- •Buffer time and contingency plans are designed into schedules
- •Editors/journalists must prioritize news over product sessions
- •Resilience and adaptability are core to product work in news
- 0:45 – 4:16
Upasna’s role at CNN and why meditation unexpectedly fits product work
Lenny introduces Upasna’s responsibilities—leading product for CNN’s journalist-facing CMS—and her parallel work as a meditation and mindfulness teacher. The episode frames CNN product as a uniquely high-chaos environment where emotional regulation becomes a professional advantage.
- •Upasna leads the CMS platform journalists use to publish stories
- •She supports product thinking in news via the News Product Alliance
- •Her mindfulness background is positioned as a practical leadership tool
- •The conversation’s two threads: CNN product operations + mindfulness tactics
- 4:16 – 6:34
Equanimity as a PM skill: thriving in chaos, not just ambiguity
Upasna explains equanimity—staying steady under pressure—and argues it’s essential for product managers in news. She connects mindfulness to better stakeholder management, morale, and faster, clearer decision-making.
- •News PMs must “thrive in chaos,” beyond standard ambiguity tolerance
- •Equanimity = pausing before reacting; reducing workplace reactivity
- •Emotional self-management is more powerful than trying to control others
- •Calm composure improves stakeholder management and team morale
- •Mindfulness supports clearer interpretation of user feedback
- 6:34 – 11:04
Practical pivoting: serving journalists’ realities (and planning around them)
Using the example of canceled research sessions, Upasna describes how CNN product teams accommodate journalists as customers with unpredictable schedules. She outlines how buffer sizing depends on the work phase—especially for large-scale onboarding to a new platform.
- •Journalists are the customer; product must adapt to their constraints
- •Backup plans prevent blocked progress when sessions get canceled
- •Onboarding cycles are intentionally long: training, testing, dialogue, feedback
- •Buffers vary widely (days to months) depending on scope and risk
- •Objective assessment and quick decisions help regain momentum
- 11:04 – 15:31
How product collaborates with editorial: a four-touchpoint intake system
Upasna details the operating cadence her team uses to stay tightly connected to newsroom needs. The system includes weekly demos, collaborative working sessions, breaking news dress rehearsals, and office hours—each designed to surface feedback and build trust.
- •Four recurring touchpoints: demo days, working sessions, dress rehearsals, office hours
- •Weekly demo days evangelize features and preview what’s coming
- •“Working sessions” reframe user testing into collaborative workflow recreation
- •Dress rehearsals simulate breaking news to stress test tools and process
- •Office hours provide open troubleshooting and continuous feedback loops
- 15:31 – 19:06
CNN Digital product org: squads, platform ownership, and behind-the-scenes scale
Zooming out, Upasna explains how CNN Digital is organized into multiple product areas (CMS, personalization, video, podcasts, infrastructure, etc.). She clarifies her platform team’s dual mandate: build a new CMS and onboard the entire editorial organization.
- •CNN Digital is separate from linear TV; different platforms power each
- •Many product areas exist beyond what audiences see on air
- •Teams operate in squad-like structures with PM, eng, design, delivery
- •Core platform team builds the new CMS and migrates users off legacy
- •Direct customer access (journalists/editors) is constant—helpful and challenging
- 19:06 – 20:13
OKRs and planning cadence: multi-year goals down to daily execution
Upasna describes OKRs as the anchor for long, complex platform rewrites. Planning spans 2–3 years at the top level, then breaks down to quarters, months, weeks, and even daily plans during rapid development phases.
- •OKRs are used widely and provide long-term continuity
- •Core platform work is a ‘long game’ with multi-year horizons
- •Goals are decomposed: 2–3 years → quarter → month → week
- •Rapid development phases can require daily planning
- •Execution depends on clear goal alignment despite changing realities
- 20:13 – 21:46
Roadmaps with autonomy: firm on the goal, flexible on the process
CNN uses an overarching roadmap tied to company/product-org OKRs while allowing teams flexibility in how they deliver. Upasna emphasizes autonomy because different squads (platform vs. video vs. podcasts) require fundamentally different approaches.
- •A top-level roadmap aligns to company and product-organization OKRs
- •Squads have their own OKRs that roll up to broader goals
- •Teams have autonomy to choose methods appropriate to their domain
- •Different product scopes make standardization impractical
- •Principle: stay firm on the goal, flexible on the process
- 21:46 – 23:50
Product & design reviews: why engineers join discovery early
Upasna explains that review rituals vary by phase, but a key evolution was embedding the tech lead and engineers into discovery and editorial conversations. This improves feasibility decisions, shared understanding of user pain, and overall delivery efficiency.
- •Reviews can be standing ceremonies or ad hoc based on phase
- •Tech lead and engineers are included in discovery, testing, and planning
- •Shared context helps engineering define ‘how’ with clarity and precision
- •Engineers become partners, not just execution resources
- •Knowledge is intentionally propagated from tech lead to the wider eng team
- 23:50 – 27:45
Remote morale and small celebrations: making launches feel meaningful
Upasna discusses the challenge of sustaining team energy in a mostly remote environment. Her team intentionally celebrates launches and onboardings—sometimes with playful gift boxes—to counteract the anticlimax of ‘just hitting publish.’
- •Remote work makes rituals harder compared to in-newsroom teams
- •Launching can feel anticlimactic without deliberate celebration
- •Team sends small gift boxes/tchotchkes to mark milestones
- •Celebrations happen for both feature launches and successful onboardings
- •Explores the idea of using CNN’s internal talent to promote product work
- 27:45 – 29:26
Maintenance vs. new builds: incident protocols and 24/7 editorial support
Balancing platform innovation and reliability is a constant juggling act, especially when production incidents override planned work. Upasna outlines escalation layers and the value of a dedicated, global editorial support team as the first line of defense.
- •Priorities shift sprint-to-sprint: features, optimizations, bug fixes
- •Production incidents take precedence over everything else
- •Decision-making relies on clear goals plus situational judgment
- •24/7 global editorial support triages and escalates issues
- •Layered processes reduce stress and protect engineering focus
- 29:26 – 31:27
When CNN.com went down: the 2020 election fallback that validated the new platform
Upasna recounts how layered fallback plans became real during the 2020 election when parts of the system failed. Even though the new CMS wasn’t fully ready, it served as a successful fallback—proving its stability under extreme load and scrutiny.
- •Elections are ‘Super Bowl x100’ for CNN operations
- •Multiple infrastructure fallbacks are planned in granular detail
- •During 2020 election downtime, the system failed over as designed
- •The new platform—still in progress—helped ‘save the day’
- •Real incidents provide powerful validation of platform resilience
- 31:27 – 33:53
Breaking news dress rehearsals: scripted simulations to stress test workflows in minutes
Upasna explains how CNN runs scripted, end-to-end rehearsals—from the initial breaking-news email to publishing—to test both product and process. Engineers and editorial support observe, while facilitators collect rapid feedback on what breaks under speed.
- •Rehearsals are scripted because real breaking news can’t be replicated
- •Simulates the full chain: email alert → content creation → publish
- •Involves many roles (writers, producers, photo desk, etc.)
- •Engineers and support teams observe to detect failure points
- •Goal: if it can’t handle breaking news speed, the tool isn’t useful
- 33:53 – 41:27
Superpowers from news product: high agency under high pressure + mindful communication
Upasna summarizes what she’d carry to any company: rapid development with risk reduction and a culture of high agency under pressure. She then connects meditation to better communication—especially listening, pausing before reacting, and speaking in the listener’s language.
- •Modern news demands rapid iteration with controlled risk
- •Complex CMS work requires fast testing of hypotheses and integrations
- •Team’s ‘superpower’: high agency under high pressure
- •Mindful communication starts with listening and pausing before reacting
- •Effective PMs adapt vocabulary to stakeholders (journalists vs. engineers)
- 41:27 – 44:16
How to start meditating: make everyday moments fully present
Upasna demystifies meditation as present-moment awareness rather than long, monk-like sessions. She offers a simple starter practice—mindfully brushing your teeth—and recommends Insight Timer as an accessible resource.
- •Meditation isn’t limited to long seated sessions
- •Core definition: deep awareness of the present moment
- •Starter exercise: brush your teeth and only brush your teeth
- •Use sensory attention (feel, sound, smell) as the anchor
- •App suggestion: Insight Timer (free version is strong)
- 44:16 – 51:07
News Product Alliance: building product thinking in newsrooms + getting involved
Upasna describes why product management in news is still emerging and how resource constraints push journalists into pseudo-product roles. She explains how the News Product Alliance supports education, resources, mentorship, and a global community—and how to join via newsproduct.org.
- •Many newsrooms lack resources for dedicated product/tech roles
- •Journalists often take on product-like work out of necessity
- •News Product Alliance formed in 2020 to grow product thinking in news
- •Produces newsroom-specific PM resources and runs mentorship programs
- •Join via newsproduct.org; active Slack and job board; open to diverse backgrounds
- 51:07 – 58:11
Lightning round: books, media picks, interview question, and the anchor of impact
In quick-hit questions, Upasna shares influential books and an HBR article, favorite shows and a standout film, and a high-agency interview question. She closes with what makes CNN work meaningful: seeing world events unfold through a platform she helped build.
- •Book recs: Mindfulness in Plain English; How to Win Friends and Influence People
- •Article rec: ‘The New Product Development Game’ (HBR, 1986)
- •TV/Movie picks: The Mandalorian, Ted Lasso, Everything Everywhere All at Once
- •Interview question: ‘What wouldn’t exist without your initiative?’ (tests agency)
- •Election seasons are intense, but impact on the world is a grounding motivator
