Video: How One Chief Product Officer Is Reinventing Product Management At Her Company

Teresa Torres interviews Hope Gurion, Chief Product Officer at CareerBuilder, about how she built product management, UX, and analytics functions at a company that previously lacked them. Gurion describes shifting her team to dual-track Agile, where discovery runs alongside delivery, with qualitative and quantitative validation before engineering builds anything. She explains how her team ranks ideas against business metrics, handles sales and executive requests through beta cohorts, replaces traditional roadmaps with quarterly problem-focused communication, and runs weekly demos to keep outcomes visible. The conversation matters because it shows concrete, adaptable practices for making discovery a habit inside a large company with both consumer and enterprise customers.

01Key takeaways

• Build a shared scoring criteria so cross-functional teams can objectively rank ideas instead of debating them endlessly.
• Validate the problem qualitatively before committing to a solution, and only then size impact through experiments.
• Tie every initiative to a business or customer metric, and check that the metric actually moved after release.
• Use beta cohorts of referenceable customers to test sales-driven or executive ideas before full investment.
• Replace detailed roadmaps with transparent communication about the problems being solved and the market opportunity.
• Hold regular demos across teams so progress, obstacles, and outcomes stay visible and people coach each other.

02Key sections

Building product management from scratch

Gurion traces how business development leadership led to creating product, UX, and analytics functions at CareerBuilder after earlier attempts without dedicated design failed.

Making discovery a habit

Teams use an agreed scorecard to objectively rank the many ideas coming from stakeholders, customers, and users, then validate the shortlist before building.

Qualitative and quantitative validation

Qualitative methods like observation and prototype testing confirm the problem, while experiments measure relative impact against other ideas and tie back to business metrics.

Handling sales and executive requests

Non-team ideas go through the same validation, often via a beta cohort of referenceable customers, with leadership layers helping resolve tensions.

Roadmaps, enterprise releases, and weekly demos

Instead of formal roadmaps, quarterly sessions link releases to long-term problems, enterprise changes are gated through beta groups, and weekly demos create shared accountability.

03From the post

“A few months ago, I sat down with Hope Gurion, Chief Product Officer at CareerBuilder, to talk about her team, how they work, and how she stays current in the fast-moving world of product management. I’ve had the pleasure of knowing Hope for the past two years and”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.