Feb 9, 2022 · 45m · 20product
20 Product: Scott Belsky on How to Hire Your Product Leader and Team, 3 Questions All Great Product Leaders Ask, How To Structure and Run Effective Product Reviews & Is Product More Art or Science?
0:00 / 0:00
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In the inaugural episode of 20 Product, host Harry Stebbings interviews Chief Product Officer at Adobe Scott Belsky to explore core product design principles, effective review structures, founder hiring frameworks, and strategies for balancing data with intuition.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 27.1% of the talking time here. How this is scored →
Harry as informed peer 2.3 Guest teaching 4.3 Guest disagreement 0.3 Harry pushing back 0.4
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 26:12 Pushback on Hiring Early Product Leaders
Scott directly challenges Harry's premise about hiring a product leader early, telling Harry that founders whose superpower is product should keep leading product themselves rather than delegating it too soon.
Hardest push from Harry ▶ 42:03 Challenging Design vs Product RolesHarry pushes back on Scott's comment about changing the wall between design and product, asking if existing modern software tools are already bringing down that barrier.
Biggest teaching moment ▶ 7:30 Three Core Questions for Every Product ScreenScott educates Harry on the fundamental user psychology framework for product design, laying out the three mandatory orientation questions every screen must answer alongside the 'lazy, vain, and selfish' user principle.
Harry holds his own ▶ 37:05 CEO Revenue Pressures vs Product VisionHarry demonstrates deep operational expertise in startup dynamics by challenging Scott on the realistic tension between meeting board ARR targets and allowing product leaders room for future innovation.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Podcast Audio Transition and Welcome | 1 | 3 | 0 | 0 | Harry opens with welcoming context and asks about Scott's background leading product at Behance and Adobe. Scott shares his philosophy on product lifecycles and simplification. | |
| Designing the First Mile Product Experience | 2 | 5 | 1 | 1 | Harry prompts Scott on first mile experiences and asks whether defaults provide user comfort. Scott educates on user psychology (lazy, vain, selfish) and explains Adobe Photoshop's redesign of its default start screen. | |
| How to Conduct Effective Product Reviews | 2 | 5 | 0 | 0 | Harry asks Scott how he conducts product reviews based on suggestions from audience members. Scott delivers a masterclass on anchoring reviews around prototypes rather than slide decks. | |
| Structuring Product Review Meetings and Alignment | 2 | 4 | 0 | 0 | Harry asks about optimal meeting sizes and maintaining control over product review agendas. Scott explains the Disney three-room methodology and stresses immediate note-taking. | |
| Product Prioritization: Optimizing for the Right Problems | 2 | 5 | 0 | 0 | Harry asks how leaders should handle prioritization when deciding what gets built next. Scott presents his mental framework of distinguishing between problems you want to have versus problems that stop initial onboarding. | |
| Balancing Data with Intuition in Product Decisions | 2 | 5 | 0 | 0 | Harry asks about balancing data against gut intuition in product decisions. Scott uses a mountain-climbing analogy and recounts how Behance focus groups misdirected them until they asked about underlying user struggles. | |
| Feature Creep, Insecurity, and 'The Killing Spree' | 2 | 4 | 0 | 0 | Harry prompts Scott to share a specific past product mistake and how to prevent team insecurity. Scott details Behance's bloated early features and their subsequent 'killing spree' that boosted engagement. | |
| Setting Objective Metrics to Evaluate Product Success | 3 | 5 | 2 | 1 | Harry introduces a hypothetical founder hiring scenario and asks how to structure early product hires. Scott pushes back on the premise, advising that founders whose superpower is product should not hire a head of product too early. | |
| Evaluating and Interviewing Product Candidates | 3 | 4 | 0 | 1 | Harry pushes Scott to give granular meeting-by-meeting interviewing steps rather than high-level advice. Scott details specific questions to test design philosophy and psychological customer empathy. | |
| Onboarding and Grafting New Product Talent | 2 | 5 | 1 | 0 | Harry asks how to stress-test candidates and onboard new product hires effectively. Scott explains why he avoids standard case studies and introduces his concept of suppressing the team's immune system to graft new leaders. | |
| Balancing Current Revenue with Future Innovation | 3 | 4 | 0 | 1 | Harry presses Scott on how CEOs can push for revenue targets without crushing product innovation. Scott explains that revenue and customer happiness must be designed as aligned narratives rather than opposing forces. | |
| Scott Belsky's Philosophy as a Product Investor | 3 | 3 | 0 | 0 | Harry and Scott discuss investor identity, with Scott framing himself as a pure product investor rather than a traditional VC. Harry candidly admits his own failed attempt at financial/cap-table modeling early in his career. | |
| Quickfire Question Round with Scott Belsky | 3 | 4 | 0 | 1 | Harry runs a quickfire question round covering MVPs, user feedback, and role definitions. When Scott suggests collapsing design and product roles, Harry briefly pushes back asking if modern tools are already dissolving that barrier. |
Statements from this episode (32)
Belsky: Bloated products are inevitably disrupted by simpler new alternatives
“I mean, life cycle, the life cycle of a product is somewhat perverse. It starts simple, And all these people, you know, flee the products they're using because they're fascinated by this new simple alternative on the market. And so customers flock to a simple …”
Belsky: Snapchat consistently rethinks its first-mile onboarding for new cohorts
“You know, Snapchat, I think, is probably one example. Of a company that I feel has consistently rethought their first mile experience for a different cohort of new customers.”
Belsky: Successive cohorts of new users become increasingly pragmatic
“What few teams realize is that every new cohort of new customers is increasingly pragmatic. You know, needs a different type of first mile experience.”
Belsky: Twitter persisted with outdated onboarding even as user motives shifted
“You know, Twitter really persisted with making people build their own timelines, even past the moment where people weren't joining Twitter to follow people. They were just joining Twitter for news, and then they were faced with this prospect of having to culti…”
Belsky: Product leaders must ask three core questions for every screen
“There are three questions you should ask in every screen you look at to ensure that it is accessible and navigatable for new customers. Right? The first is, how did I get here? What do I do now? And then what do I do next?”
Belsky: Users in the first 90 seconds are lazy, vain, and selfish
“Every customer, at least initially in their 1:30 seconds of a product experience, is lazy, vain, and selfish, right? You know, you don't want to read stuff, you don't want to watch a video, you don't want to take a tour. You kind of want things done for you.”
Belsky: Users overwhelmingly stick with default product settings and landing screens
“As humans, we typically just take and stick with the default of every experience that we're given. Wherever I land you is where you stay. You know, whatever I outfit you to use in the product by default is what you keep.”
Belsky: Adobe replaced Photoshop's blank start page with templates and tutorials
“When I came back to Adobe four years ago in this chief product officer role, I looked at products like Photoshop that literally opened up with a blank black page of, you know, just nothingness, right? And it's like, there was no orientation of what to do now o…”
Belsky: A prototype is worth a hundred meetings
“A prototype is worth a hundred meetings. And if you can have a discussion around a PowerPoint with bullet points and stuff, I mean, you're going to miss so much. You're going to have unnecessary disagreements and debates, and you're not going to have everyone …”
Belsky: Most product teams review features without full customer journey context
“If the product review is about a particular part of the product, you're not doing the customer service if you're just jumping in and looking at that, which is, by the way, what most teams do.”
Belsky: Initial product reviews should exclude engineers to preserve creative freedom
“First of all, I believe that some of the initial product reviews should only be with the product and design team. Engineers are really there to discuss the cost of something, but how can you reconcile the cost of something while you're actually first starting …”
Belsky: Company misalignment stems from discussing generalities instead of customer experiences
“I think most companies, you know, suffer from a lack of alignment because they talk about generalities, but they're not all really anchoring on the exact experience we want to enable for customers.”
Belsky: Real-time feedback tracking during reviews dictates product success
“I am maniacal about capturing things during these conversations. So, you know, if there's a piece of feedback shared, but I don't see the pen move of the designer that's on that area, you know, I will say, like, did you capture that? Because I feel like that's…”
Belsky: Defer feature enhancements until after achieving product-market fit
“You should not try to do those things for launch. You should not try to do those things before you have product market fit. It's really important. They're great ideas, but just do them later. The things you need to do now are the things that would get in the w…”
Belsky: Guiding users through the first mile puts products in top 10%
“And if you can just get people through that first mile and then get them to some level of success quickly, you are already in like the top 10% of products out there.”
Belsky: Intuition sets product direction, while data guides execution
“Intuition is what brings you to a mountain to climb. Data is what helps you climb it.”
Belsky: Iterate MVPs with data until the next strategic transformation
“When you build that MVP and put it out there, you should be iterating based on data from there on out until the next big transformation where you have to lead with some intuition.”
Belsky: Shutting down secondary features immediately boosted Behance's core engagement
“We killed groups, and three days later, you know, some people complained, but the engagement on the platform went up on Project And then we killed tip exchange, another uptick over the next few days.”
Belsky: Product teams need a three-year prototype as a strategic anchor
“I love not only a prototype of what you're building now, but even a reachy prototype of what you believe the world will look like in three years with your product, because then it's like an anchor. It's like, okay, that's our conviction over the long term. Let…”
Belsky: Set objective success metrics before launch to avoid post-launch bias
“You know, I mean, listen, you have to set metrics, objective metrics, of what you believe progress looks like up front for a few different reasons. First of all, you know, as the messy middle Is you get lost in it, right? And along the way, the progress you're…”
Belsky: Founders should delegate everything except their core superpower
“I think you should abstract yourself out of almost every function. Except for the one that is your superpower, that you are the unique person in the world to do, and you should keep doing that as long as humanly possible.”
Belsky: Very few product leaders master both design vision and data iteration
“There are different types of product leaders for different stages of a product. You know, some are very comfortable being very design-driven, setting a product strategy, a vision, rallying the troops around this, and ensuring that the experience is exactly wha…”
Belsky: A product always reflects its team's organizational DNA
“I feel like a product Always speaks to the DNA of the team behind it. You can tell who wasn't talking to one another, you know, what the values were, whether there was a designer outsourced or in the room sufficiently empowered, et cetera.”
Belsky: Design solves product performance issues faster than engineering replatforming
“You know, even when it comes to the speed and performance of a product, you know, design is actually oftentimes a solution before engineering is a solution, just based on the fact that sometimes you have to replatform something, right? Sometimes you have to ch…”
Belsky: Products miss product-market fit due to insufficient customer proximity
“The reason that most products are 30 degrees off of what the customer needs, or more, and fail to really achieve that product market fit where it just sings, right, is that we're not shoulder to shoulder with customers enough.”
Belsky: Companies focus too much on hiring talent, not grafting it
“I think we focus too much on hiring talent and not enough on grafting talent once you've hired it.”
Belsky: Several of my best hires were initially rejected by existing teams
“Some of the best, most critical hires I've made over the years were instantly rejected by the team at first”
Belsky: Existing teams must adjust to accommodate star hires
“I think that's a mistake most leaders do, because you hire an all-star, and then you're like, oh, she's an all-star. She'll figure it out, when in fact, if she's in a great team, you know, the team needs to adjust in order to accommodate her.”
Belsky: Startups lack funnel reach while incumbents lack modern tech stacks
“You know, startups have the opposite problem. They are working on the most novel news Stacks of technology. They're all building, you know, web apps or AI natively, et cetera. However, they don't have any top of funnel, whereas Adobe has this massive top of fu…”
Belsky: Customer usage and revenue generation should align, not conflict
“Well, you know, sometimes people posit it as, Customer happiness and usage versus revenue. When in fact, you know, they should be designed to work together. And the narrative, especially in an early stage venture, you know, needs to be about how one leads with…”