Humanizing product development | Adriel Frederick (Reddit, Lyft, Facebook)
Lenny chats with Adriel Frederick, VP of Product at Reddit, about his journey from Trinidad to tech leadership at Facebook, Lyft, and Reddit. They discuss fostering diversity, leading through controversy, designing for operational control in algorithmic products, and effective growth strategies.
Deep Dive Analysis
12 Topic Outline
Adriel Frederick's Career Journey and Current Role at Reddit X
Structuring R&D Teams to Integrate with Core Mission
Impact of Diversity on Product Design and Team Efficiency
Leading Product at Controversial Companies: Valid vs. Invalid Criticism
Unwinding a Bad Product and the Importance of Operational Control
Why Algorithms Need Human Judgment and Strategic Decisions
AI as a Tool: Amplifying Intent vs. Autonomous Decision-Making
Growth Hacking vs. Fundamental Product Value and 'Cannonballs'
The Power of a Clear, Galvanizing Goal like '7 Friends in 10 Days'
Understanding and Learning from the Marginal User Experience
Experimentation Strategy: Balancing Small Wins with Big Bets
Key Skills for Senior Product Leaders: Organization and Empathy
5 Key Concepts
Techno-Utopians
This term describes individuals who believe that feeding all data to an algorithm with an objective will inherently lead to the 'right' outcome. Adriel argues this view fails because algorithms often lack understanding of long-term effects, human responses, or the product's true intent.
Operational Control
This refers to the necessity of having human oversight and the ability to make real-time, strategic adjustments to algorithmic systems. In a marketplace context like Lyft, it means people need tools to respond to unquantifiable external factors (e.g., snowstorms, competitor actions) that algorithms cannot foresee or understand.
Marginal User
A marginal user is someone who is just on the cusp of taking a desired action, such as signing up for a product, but faces specific barriers. By observing and understanding the experience of this user, product teams can identify fundamental flaws and prioritize improvements that benefit a wider audience.
Cannonballs (in Growth)
These are significant, fundamental changes to a product that require substantial investment and effort, but result in outsized impact on growth. They contrast with 'growth hacks,' which are smaller, often tactical changes.
Human-Computer Interface (ML/Ops)
This concept emphasizes designing the interaction between humans and machine learning/operations research systems as a core product design problem. It involves giving people the right information and tools to make strategic judgment calls, while allowing algorithms to amplify those human intentions across many individual decisions.
9 Questions Answered
R&D teams must be perceived as core and critical to the company's mission, their successes should be seen as everyone's success, and the company must ensure that innovation is not exclusively seen as originating from these teams.
Diverse teams, encompassing various ethnicities, religions, and cultures, significantly increase efficiency by allowing team members to represent and argue for different user perspectives internally, reducing the need for extensive external user research and accelerating product design.
Product leaders must act as a buffer for their teams, dampening both excessive praise and harsh criticism. It's crucial to discern valid criticism from noise, often by staying close to users and experiencing the product firsthand, then focusing on solving the underlying customer problems.
Algorithms excel at optimizing for given objectives but often lack understanding of long-term effects, human responses, or strategic constraints. Humans are necessary to make judgment calls, set strategic choices, and provide context that algorithms cannot perceive.
While 'growth hacking' (small changes for outsized impact) can be valuable for initial traction, sustainable growth comes from providing fundamental value to users. The most impactful growth initiatives are often 'cannonballs' – significant, fundamental product changes that remove friction and solve real user problems through hard work, not just tricks.
Such a goal serves as a powerful rallying cry and a galvanizing force for an organization. Its brilliance lies not in the magic of the specific numbers, but in its ability to create a clear, measurable, and memorable objective that drives collective action and momentum, cutting through academic debate.
Identify a marginal user (e.g., someone on the cusp of conversion in a challenging environment) and observe their experience firsthand. This reveals all the product's flaws, including those not apparent from data alone, providing a comprehensive list of issues to address.
A healthy approach involves a portfolio of bets. Early-stage products might prioritize 'cannonballs' (big, fundamental changes) with less experimentation, while mature products benefit from a balance of larger initiatives and numerous smaller refinements, as the cost and time of experimentation become lower.
The most critical skills are organization, design, and empathy. This involves building great teams, creating effective incentives, unblocking and guiding team members, and fostering a smooth operational environment, alongside the ability to truly understand and connect with peers and users by 'taking one's own shoes off'.
11 Actionable Insights
1. Define Algo & Human Roles
As a product manager working on algorithmic products, define what algorithms are responsible for and where humans make judgment calls, designing interfaces that empower people to make strategic decisions and amplify their intent. Algorithms often lack understanding of long-term effects, human response, or product intent, necessitating human oversight.
2. Cultivate Org Design & Empathy
As a senior leader, prioritize organization design (building great teams, clear goals, smooth processes) and cultivate empathy for peers and team members. The latter involves setting aside your own perspective to understand others’ motivations and fears, fostering collaborative solutions.
3. Observe Users Beyond Data
Supplement data analysis with direct observation and conversation with users, especially “marginal users” (those on the cusp or struggling most), to uncover problems and insights that data alone cannot reveal. This helps understand their real-world context and motivations.
4. Prioritize Operational Control
For products with significant operational components, treat operational requirements and control as a first-order design problem, integrating human judgment into algorithmic systems. Algorithms alone cannot account for dynamic, real-world variables like local events, taxes, or competitor actions.
5. Grind on Core Product Value
Focus growth efforts on continuously improving the core product experience and making fundamental actions “stupid easy” for users, rather than relying solely on “growth hacks.” Sustainable growth comes from providing real, fundamental value and removing friction for marginal users.
6. Buffer Team During Controversy
As a product leader, buffer your team from external chaos and bad press by reminding them of the mission and the truth of their work, while also staying close to users to discern valid criticism from noise. This helps maintain focus and morale.
7. Value Diversity for Growth
Recognize that diversity provides concrete business value, making teams faster and more efficient at building global products by incorporating varied perspectives directly into design discussions. Foster an environment that values, utilizes, and rewards diverse talent to ensure retention and facilitate recruitment.
8. Integrate R&D Teams
When setting up R&D or incubation teams, ensure their work is perceived as core to the company’s mission and contributes to everyone’s success, not just their own. This prevents “organ rejection” and fosters a culture where innovation is encouraged across all teams.
9. Balance Experiment Portfolio
Develop a balanced experimentation portfolio that includes both “cannonball” (large, fundamental changes) and “lead bullet” (small, incremental) initiatives, adjusting the mix based on product maturity. Avoid the trap of focusing solely on easy, small experiments that don’t add up to significant impact.
10. Use Milestones as Rallying Cry
Create discrete, memorable activation milestones (e.g., “10 friends in 14 days”) not for their exact magical correlation, but for their power to galvanize teams and provide a clear, concrete goal for everyone to chase.
11. Ask “Teach Me Something”
Use the interview question “Teach me something you don’t think I know” to assess a candidate’s empathy, breadth of knowledge, and ability to communicate complex ideas effectively. This question often leads to mutual learning and reveals multiple valuable skills.
5 Key Quotes
The reason that falls down is the algorithms don't understand long-term effects often, nor do they understand how people might respond to it, nor do they understand your intent for the product.
Adriel Frederick
You've got to have your teams look like the world. It just makes you so much faster.
Adriel Frederick
I don't think you're going to have any meaningful influence on the world without changing some pattern of behavior.
Adriel Frederick
The hardest part of it is they say getting in somebody else's shoes. The hardest part is taking my own shoes off.
Adriel Frederick
There's nothing meaningful that gets done by any single person, even though people like to make you think that in their hustle porn that they post online.
Adriel Frederick