Microtraumas in IT - The Silent Enemy of Tech Teams | Minimal Dose of Empiricism - Why Every Experiment is a Mini Sprint
Issue #218 / Wydanie #218
In today's edition, among other things:
💜 Microtraumas in IT - The Silent Enemy of Tech Teams (by Katarzyna Dahlke)
💜 Minimal Dose of Empiricism - Why Every Experiment is a Mini Sprint (by Łukasz Domagała)
💪 Interesting opportunities to work in product management
🍪 Product Bites - small portions of product knowledge
📚 Monthly Book Club for Product Managers
🔥 MLA week#29
Join Premium to get access to all content.
It will take you almost an hour to read this issue. Lots of content (or meat)! (For vegans - lots of tofu!).
Grab a notebook 📰 and your favorite beverage 🍵☕.
Editor’s Note by Alex 💜
The Servant Leadership Imperative: Why Collaborative Leadership Is Our Only Path Forward in VUCA Times
The product management community is having the wrong debate about leadership in uncertain times. Last week, during a conversation with Aga Szóstek at WaysConf—a leader I deeply admire both professionally and personally—we found ourselves questioning whether servant leadership has become obsolete in our era of VUCA conditions and violent political upheaval. The implication was clear: maybe these unprecedented times demand a return to authoritarian, command-and-control leadership styles that can cut through chaos with decisive action.
This line of thinking is not just wrong—it's dangerously seductive precisely because it feels intuitively correct. When everything is uncertain, when markets are volatile, when political systems are fragmenting, our instinctive response is to grasp for control, hierarchy, and strong decisive leaders who promise order. But here's the uncomfortable truth the product management community must confront: the research overwhelmingly demonstrates that servant leadership doesn't just outperform authoritarian approaches in VUCA environments—it's the only sustainable strategy that consistently delivers superior outcomes.
The seductive trap of authoritarian thinking
The conversation with Aga crystallized something I've been observing across our industry: a quiet retreat from collaborative leadership principles in favor of more directive approaches. Product leaders are defaulting to top-down decision-making, centralizing authority, and prioritizing speed over inclusion. The justification is always the same: "These aren't normal times. We need strong leadership."
This represents a fundamental misunderstanding of what strength means in uncertain environments. We're conflating the feeling of control with actual effectiveness. Daniel Kahneman's research reveals why this happens: under stress and uncertainty, our brains default to System 1 thinking—fast, automatic, and prone to cognitive biases. The authoritarian approach feels decisive because it reduces cognitive load and provides the illusion of certainty. But feeling decisive and being effective are entirely different things.
The product management orthodoxy has confused psychological comfort with strategic advantage. When leaders choose authoritarian styles during crises, they're optimizing for their own emotional regulation rather than team performance. This isn't leadership—it's anxiety management disguised as strategic thinking.
Amy Edmondson's groundbreaking research on psychological safety provides the empirical foundation that demolishes authoritarian assumptions. Her studies of 51 work teams revealed that psychological safety—the belief that one can speak up without risk of punishment—becomes even more critical during uncertain times. Teams with higher psychological safety engage in significantly more learning behavior, which directly mediates performance outcomes. In VUCA environments, where incomplete information and rapid change are constants, this learning advantage becomes the difference between adaptation and extinction.
The evidence from our VUCA laboratory
The COVID-19 pandemic provided the ultimate natural experiment in leadership effectiveness under extreme uncertainty. The winners tell a consistent story that should shame every executive who retreated to command-and-control thinking.
Eric Yuan at Zoom faced 418% user growth and a security crisis that threatened the company's existence. Instead of issuing directive commands and controlling information flow, Yuan chose radical transparency. His weekly "Ask Eric Anything" webinars, public admission of mistakes, and collaborative approach to solving "Zoombombing" built trust that enabled the company to scale from 10 million to 300+ million daily users while maintaining customer satisfaction. This wasn't weak leadership—it was the kind of strength that only emerges when leaders prioritize collective success over personal control.
Brian Chesky at Airbnb lost 80% of his business in eight weeks. Rather than making unilateral decisions or hoarding decision-making authority, Chesky increased communication frequency, made principle-based rather than outcome-based decisions, and treated laid-off employees with unprecedented generosity. The result? A company that recovered from near-collapse to an IPO in December 2020 that valued the company at over $100 billion on its first day of trading.
Compare these outcomes to the countless examples of authoritarian leadership failures during the same period. Traditional corporate responses that prioritized damage control over transparent problem-solving, leaders who made isolated decisions without stakeholder input, and companies that retreated to hierarchical command structures consistently underperformed their servant-led competitors.
Product management's unique vulnerability to the authoritarian trap
Product management presents particularly compelling evidence against authoritarian leadership because of the discipline's inherent structure. Product managers typically lack direct authority over engineers, designers, and other team members. They must lead through influence rather than hierarchy—making the psychological and social dynamics of leadership style crucial to success.
Marty Cagan's research emphasizes that empowered product teams depend not on less leadership, but on better leadership. His principle of "lead by context, not control" requires providing strategic framework while enabling team autonomy. Teresa Torres's continuous discovery methodology similarly demands collaborative customer research and shared learning across teams. These aren't idealistic preferences—they're pragmatic requirements for product success in complex environments.
The cognitive science here is decisive. Product management involves constant decision-making under uncertainty, balancing user needs with technical constraints and business goals. Dan Ariely's research shows that under high-stress situations, individual decision-makers become more prone to systematic biases and less capable of processing complex information. Collaborative approaches provide cognitive diversity and bias correction that no individual leader can achieve alone.
When product leaders retreat to authoritarian styles, they systematically impair their teams' ability to process information, adapt to changing conditions, and innovate solutions. The very qualities that make product management challenging—uncertainty, complexity, interdependence—are precisely the conditions where servant leadership provides maximum advantage.
The devastating cost of authoritarian leadership in innovation contexts
The research on creativity and innovation provides perhaps the most damning evidence against authoritarian leadership in product contexts. Studies consistently demonstrate that authoritarian approaches stifle creative thinking by enforcing strict rules and limiting autonomy. Teams become "mere executors of top-down directives rather than active contributors"—exactly the opposite of what's required when market conditions change rapidly.
Netflix's transformation from DVD rental to streaming giant to global content creator illustrates the innovation advantage of servant leadership. Reed Hastings and Ted Sarandos succeeded through adaptive leadership that combined strategic vision with tactical flexibility. Their willingness to cannibalize existing revenue streams and make strategic decisions collaboratively with deep stakeholder input enabled multiple successful pivots that more traditionally managed companies couldn't achieve.
The fundamental mismatch is clear: VUCA environments require continuous adaptation, experimentation, and learning from failure—capabilities that authoritarian structures systematically suppress. When leaders default to command-and-control thinking, they optimize for short-term psychological comfort at the expense of long-term adaptive capacity.
The pattern repeats across industries. Harvard Business School case studies reveal that 85% of successful business pivots involved collaborative decision-making processes, while 70% of failed adaptations were characterized by top-down, directive approaches. The data doesn't lie: authoritarian leadership is a systematic vulnerability in uncertain environments.
The false promises of authoritarian speed
The most persistent defense of authoritarian leadership centers on decision speed—the notion that collaborative approaches slow decision-making when rapid response is critical. This argument rests on a false premise that individual decisions are higher quality than team decisions.
Behavioral research reveals the opposite. Stress impairs individual decision-making through cognitive overload, emotional interference, and bias amplification. Collaborative processes, when properly structured, actually accelerate high-quality decision-making by distributing cognitive load and leveraging diverse expertise.
Eric Yuan's rapid response to Zoombombing, Brian Chesky's quick pivot during COVID-19, and Stewart Butterfield's agile product development at Slack all demonstrate that servant leaders don't abdicate decision-making—they create systems that enable better decisions faster. The key insight is that servant leadership isn't about consensus-building or endless consultation—it's about building organizational capabilities that enable rapid, high-quality responses to uncertainty.
The economic evidence is equally compelling. Research consistently demonstrates that defensive decisions made in low psychological safety environments lead to substantial foregone opportunities and reduced innovation. In volatile markets where missed opportunities can be existential, this cost becomes prohibitive. Organizations that retreat to authoritarian leadership during crises don't just perform worse—they systematically destroy value.
Redefining strength for the modern era
The deepest challenge to adopting servant leadership in VUCA environments isn't methodological—it's psychological. Traditional organizational cultures equate leadership strength with control, decisiveness, and invulnerability. Servant leadership requires leaders to show uncertainty, admit mistakes, and empower others—behaviors that feel weak in command-and-control cultures.
This perception represents a fundamental misunderstanding of what strength means in uncertain environments. Brené Brown's research on vulnerability and leadership reveals that the courage to show uncertainty and ask for help actually builds stronger team connections and enables better collective performance. In VUCA environments, the ability to learn quickly matters more than the illusion of having all the answers.
Simon Sinek's research reinforces this insight: leaders who make their teams feel safe consistently outperform those who rely on authority and control. The biological basis is clear—when team members feel psychologically safe, they access higher cognitive functions and engage in more creative problem-solving. When they feel threatened by authoritarian leadership, they default to fight-or-flight responses that impair complex thinking.
The servant leadership imperative for product management
My conversation with Aga at WaysConf ultimately revealed a critical inflection point for our profession. We can either evolve our understanding of leadership to match the demands of our environment, or we can retreat to outdated paradigms that feel familiar but systematically fail.
The evidence across multiple disciplines points to an inescapable conclusion: servant leadership isn't idealistic in VUCA environments—it's the pragmatic choice for leaders who want to win. The academic research, behavioral science, real-world case studies, and product management expertise all converge on the same insight: collaborative leadership that prioritizes psychological safety, empowerment, and shared decision-making outperforms authoritarian approaches across every meaningful metric.
For product managers operating in our era of permanent uncertainty, the choice isn't between different leadership styles—it's between approaches that work and approaches that systematically fail. The organizations and leaders who recognize this distinction will create sustainable competitive advantages. Those who cling to authoritarian paradigms will find themselves increasingly unable to adapt to the pace of change that defines modern markets.
The future belongs to leaders brave enough to serve rather than command, to ask rather than decree, and to build rather than control. The conversation with Aga reminded me that our industry's greatest leaders aren't those who retreat to authoritarian comfort when times get tough—they're those who double down on the collaborative principles that enable teams to thrive under pressure.
In VUCA times, servant leadership isn't obsolete—it's our only path forward.
💪 Product job ads from last week
Do you need support with recruitment, career change, or building your career? Schedule a free coffee chat to talk things over :)
Junior Product Manager - Canonical
Product Manager Assistant - Colibrix One
Senior Product Manager - OpenX
Product Manager - Sauce Lab
Product Manager - Deblock
🍪 Product Bites (3 bites 🍪)
🍪 The Adoption Cliff
Why Users Abandon Products After Initial Success
In the world of product management, we often celebrate those magical moments when users first engage with our product. The sign-up spike, the initial feature usage, the promising early metrics—all signals that we're onto something. But lurking just beyond this honeymoon phase lies one of the most treacherous challenges in product development: the adoption cliff.
The adoption cliff is the sharp drop-off in user engagement that occurs after the initial period of product exploration, typically between days 7-30 of the user lifecycle. While 73% of mobile apps lose 80% of their daily active users within the first three days, the adoption cliff represents a more insidious challenge—the gradual abandonment by users who initially showed promise.
The Anatomy of Abandonment
Think of the adoption cliff like a hiking trail that starts gently but suddenly becomes treacherous. Users begin their journey enthusiastic and well-prepared, but as the path steepens and becomes more complex, many turn back before reaching the summit of true product value.
Research from Mixpanel shows that while the average app retains 25% of users after 90 days, products that successfully navigate the adoption cliff can achieve retention rates of 35-40% or higher. The difference? Understanding that initial engagement and sustained adoption are fundamentally different challenges requiring different solutions.
The Five Stages of the Adoption Cliff:
Honeymoon Phase (Days 1-3): High engagement driven by novelty and curiosity
Reality Check (Days 4-7): Users encounter first friction points and complexity barriers
The Struggle Valley (Days 8-21): Motivation wanes as effort-to-value ratio becomes unclear
Decision Point (Days 22-30): Users either commit to deeper engagement or abandon
Habituation or Abandonment (Days 31+): Clear bifurcation between power users and churned users
Why Smart Users Make Irrational Decisions
The adoption cliff isn't just about product complexity—it's about human psychology. Dr. Nir Eyal's research on habit formation reveals that users need to experience value faster than their motivation decays. This creates what we call the "motivation-value race."
Consider Slack's early growth story. Despite having product-market fit, Slack noticed that teams who didn't reach 2,000 messages in their first month had a 93% chance of eventual churn. The product worked, but users weren't climbing high enough up the value curve before their initial motivation expired.
The Psychology Behind the Cliff:
Cognitive Load Accumulation: Each new feature or process adds mental overhead
Expectation Deflation: Initial excitement gives way to mundane reality
Switching Cost Inertia: Returning to familiar tools becomes increasingly attractive
Social Proof Absence: Without seeing others succeed, users doubt their own potential success
The Adoption Cliff Framework
Successful products don't prevent the adoption cliff—they build bridges across it. The BRIDGE framework provides a systematic approach to reducing cliff casualties:
B - Behavioral Momentum Create small, achievable wins that build confidence and engagement before introducing complexity. Duolingo masters this by starting with incredibly simple lessons that feel like games rather than work.
R - Relevance Mapping Connect every early interaction to specific user outcomes. Users should understand not just what they're doing, but why it matters to their goals.
I - Incremental Complexity Introduce advanced features gradually, only after users have mastered foundational capabilities. Think of it as a video game progression system rather than a feature dump.
D - Data-Driven Intervention Identify leading indicators of cliff risk and intervene proactively. If users haven't completed specific actions by day 14, trigger targeted support.
G - Goal Alignment Ensure that product goals and user goals remain synchronized throughout the early experience. Misalignment is often the root cause of cliff abandonment.
E - Emotional Investment Create moments that make users feel ownership, progress, and belonging. The IKEA effect shows that people value things more when they've invested effort in creating them.
Implementation: Building Cliff-Resistant Products
Week 1: Diagnostic Phase
Map your current user journey from signup to day 30
Identify the specific day when engagement typically drops
Survey recent churned users to understand their abandonment triggers
Analyze feature usage patterns among users who successfully crossed the cliff
Week 2-3: Intervention Design
Create micro-goals for each stage of the cliff journey
Design progressive disclosure for complex features
Implement early warning systems for at-risk users
Develop targeted re-engagement campaigns
Week 4: Testing and Optimization
A/B test different cliff-crossing strategies
Measure both short-term engagement and long-term retention
Iterate based on user feedback and behavioral data
Case Study: How Notion Conquered the Adoption Cliff
Notion faced a classic adoption cliff challenge: their product was incredibly powerful but overwhelmingly complex for new users. Initial users loved the concept but abandoned when faced with the learning curve.
Their solution was brilliant in its simplicity: templates. Instead of presenting users with a blank canvas, Notion provided pre-built templates for common use cases. This gave users immediate value while gradually introducing the product's flexibility.
The results were dramatic: users who started with templates had 3x higher 30-day retention rates than those who started with blank pages. More importantly, template users eventually became power users who created their own complex workflows.
The Measurement Paradox
Here's where things get counterintuitive: traditional engagement metrics can actually hide adoption cliff problems. High day-3 retention might mask a severe day-21 drop-off. We need new metrics that capture the cliff phenomenon:
Cliff-Specific Metrics:
Value Realization Rate: Percentage of users who achieve first meaningful outcome by day 14
Engagement Sustainability Index: Ratio of week-4 engagement to week-1 engagement
Feature Progression Score: How quickly users advance through product complexity levels
Cliff Recovery Rate: Percentage of declining users who can be re-engaged
The Emotional Architecture of Adoption
Beyond metrics and frameworks, successful cliff navigation requires understanding the emotional journey users experience. Initial excitement must evolve into competence, then into confidence, and finally into habit.
Netflix understood this intuitively. Their recommendation algorithm isn't just about finding content—it's about making users feel confident in their choices. By reducing decision fatigue and increasing satisfaction with selections, Netflix helps users cross from "trying the service" to "trusting the service."
Building Anti-Fragile Adoption
The best products don't just survive the adoption cliff—they become stronger because of it. This requires building what Nassim Taleb calls "anti-fragility" into your user experience.
Anti-Fragile Adoption Principles:
Failure Integration: Turn user mistakes into learning opportunities rather than frustration points
Personalization Engines: Use cliff struggles to customize the experience for individual users
Community Leverage: Connect struggling users with successful ones for peer support
Progressive Stakes: Gradually increase user investment as competence grows
Remember: the adoption cliff isn't a product flaw—it's a natural part of any meaningful learning curve. Our job isn't to eliminate challenge but to ensure that users have the support, motivation, and clear progress indicators they need to persist through temporary difficulties.
The companies that master cliff navigation don't just build better products; they build more resilient users who become advocates, power users, and ultimately, the foundation for sustainable growth.
🍪 The Adjacent Possible
How Product Innovation Happens at the Edges
Innovation feels magical when we experience it as users, but from the inside, breakthrough product development often resembles careful exploration rather than sudden inspiration. The secret lies in understanding what scientist Stuart Kauffman called "the adjacent possible"—the realm of potential that sits just beyond what currently exists.
The adjacent possible represents all the ways the present can reinvent itself through one incremental step. It's not about distant, revolutionary leaps but about recognizing which doors have become available to open next. For product teams, this concept transforms how we think about innovation from unpredictable lightning strikes to navigable territory.
The Geography of Innovation
Imagine innovation as exploring an endless mansion where each room represents a current solution or capability. From any room, you can see several doors leading to adjacent rooms—new possibilities that build directly on what exists. You cannot, however, jump to distant rooms without first passing through the connecting spaces.
This spatial metaphor explains why certain innovations seem "inevitable" in hindsight. The iPhone wasn't a random stroke of genius—it became possible only after the adjacent technologies converged: touchscreen manufacturing, miniaturized computing, wireless networks, and battery technology. Apple's brilliance lay in recognizing that these adjacent possibles had aligned.
The Three Layers of Adjacent Possible:
Technical Adjacent: What becomes possible when existing technologies combine or evolve
Market Adjacent: What becomes valuable when user behaviors and needs shift
Organizational Adjacent: What becomes feasible when team capabilities and structures evolve
Why Most Innovation Fails at the Edges
The adjacent possible explains a frustrating paradox: companies often miss breakthrough opportunities that seem obvious in retrospect, while breakthrough innovations frequently come from unexpected players. Kodak invented digital photography but couldn't commercialize it. Netflix started as a DVD-by-mail service before revolutionizing streaming.
This happens because the adjacent possible is often invisible to those closest to the current solution. Success creates what we call "adjacent blindness"—the inability to see possibilities that threaten or transcend current business models.
The Four Types of Adjacent Blindness:
Resource Blindness: Focusing only on innovations that leverage existing assets
Competency Blindness: Pursuing only innovations that use current skills
Customer Blindness: Seeing only possibilities that serve existing user bases
Revenue Blindness: Exploring only innovations that fit current monetization models
The Network Effect of Adjacent Innovation
The most powerful aspect of the adjacent possible is how innovations create new adjacencies. Each breakthrough doesn't just solve a problem—it expands the universe of what's possible next. Consider how the smartphone didn't just improve phone calls; it created entire new adjacencies: app ecosystems, location-based services, mobile payments, augmented reality.
This network effect explains why innovation often comes in waves. The personal computer created adjacencies for software, which created adjacencies for the internet, which created adjacencies for e-commerce, which created adjacencies for mobile commerce.
Mapping Your Innovation Network:
Current State Inventory: Document existing capabilities, technologies, and market positions
Adjacency Identification: List what becomes possible with one incremental step
Connection Analysis: Understand how potential innovations might connect to create new adjacencies
Timing Assessment: Evaluate which adjacencies are ready for exploration now
The Adjacent Possible Framework: EXPLORE
Successful navigation of the adjacent possible requires systematic exploration rather than random wandering. The EXPLORE framework provides structure for this inherently uncertain process:
E - Environmental Scanning Continuously monitor technological, market, and social trends that might create new adjacencies. Amazon's Jeff Bezos famously spent 30% of his time on activities unrelated to current business priorities.
X - eXperimentation Design Create small, reversible experiments to test adjacent possibilities. Google's "20% time" policy recognized that adjacent innovation requires dedicated exploration space.
P - Pattern Recognition Identify recurring themes across multiple adjacencies. Often, breakthrough innovations emerge at the intersection of several adjacent possibles.
L - Learning Velocity Accelerate the feedback loops between experiments and insights. The faster you can test adjacent possibilities, the more territory you can explore.
O - Opportunity Assessment Develop frameworks for evaluating which adjacencies deserve deeper investment. Not all possible adjacencies are worth pursuing.
R - Resource Allocation Balance resources between exploiting current successes and exploring adjacent possibilities. Clayton Christensen's research suggests successful companies allocate 70% to core business, 20% to adjacent innovations, and 10% to transformational bets.
E - Ecosystem Building Create partnerships and platforms that expand your adjacent possible. You don't need to explore every adjacency internally.
Case Study: How Slack Navigated the Adjacent Possible
Slack's origin story perfectly illustrates adjacent possible navigation. The team was building a gaming company called Tiny Speck when they created an internal communication tool to coordinate their distributed team. They recognized that their internal tool addressed a universal problem and represented a valuable adjacency to explore.
The key insight was recognizing that their gaming expertise created unique adjacencies in business communication:
Game design principles could make business software more engaging
Real-time collaboration technology could transform workplace communication
Community building mechanics could create network effects in professional settings
Instead of forcing their original gaming vision, they explored this adjacent possibility and discovered a billion-dollar market opportunity.
The Platform Strategy: Expanding Others' Adjacent Possible
The most successful products don't just explore their own adjacent possible—they expand the adjacent possible for others. Platforms like iOS, AWS, and Shopify succeed by making previously impossible things possible for their users.
This platform approach to the adjacent possible creates powerful advantages:
Network Effects: Each new use case attracts more developers and users
Innovation Acceleration: Others explore adjacencies you might never consider
Ecosystem Defense: Competitors must match not just your product but your entire ecosystem
Platform Adjacent Possible Principles:
Make your core capabilities available as building blocks for others
Reduce barriers to experimentation in your ecosystem
Share success when others create value using your platform
Continuously expand the toolkit available to your ecosystem
Timing the Adjacent Possible
One of the most challenging aspects of adjacent possible navigation is timing. Move too early, and the supporting ecosystem isn't ready. Move too late, and competitors have claimed the territory.
The "Goldilocks Zone" for adjacent innovation occurs when:
Technical Prerequisites: Required technologies are mature enough for reliable implementation
Market Readiness: Users are experiencing pain points that create demand for solutions
Competitive Landscape: The space isn't overcrowded but has enough activity to validate market potential
Resource Availability: Your organization has the capability to execute effectively
Measuring Adjacent Innovation
Traditional product metrics often fail to capture the value of adjacent exploration. Success in the adjacent possible requires different measurement approaches:
Leading Indicators:
Number of adjacencies identified and evaluated
Speed of experimentation cycles
Quality of learning from failed experiments
Cross-functional collaboration frequency
Lagging Indicators:
Revenue from products launched in past 2-3 years
Market share in emerging categories
Patent applications in adjacent areas
Platform adoption rates (if applicable)
The Patience Paradox
Perhaps the most counterintuitive aspect of the adjacent possible is that it requires both urgency and patience. Urgency in exploration and experimentation, patience in allowing adjacencies to mature and reveal their full potential.
Many companies fail at adjacent innovation because they apply inappropriate timeframes—either demanding immediate returns from exploration or failing to move quickly enough when adjacencies become clear.
Building an Adjacent-Possible Organization
Organizations that consistently navigate the adjacent possible share common characteristics:
Cultural Attributes:
Intellectual Curiosity: Reward exploration even when it doesn't lead to immediate results
Cross-Pollination: Encourage knowledge sharing between different domains
Failure Tolerance: Treat failed adjacency exploration as valuable learning rather than waste
Long-Term Thinking: Balance quarterly pressures with multi-year exploration horizons
The adjacent possible reminds us that innovation isn't about predicting the future—it's about recognizing opportunities that exist right at the edge of the present. The companies that master this edge-walking don't just build better products; they expand the universe of what's possible for everyone.
🍪 The Onboarding Paradox
Why First Impressions Are Often Last Impressions
We live in an age of infinite choice where users can abandon your product faster than they can learn to use it. Yet paradoxically, the most successful products often require significant initial investment from users to realize their value. This tension—between the need for immediate gratification and the reality of valuable complexity—defines the onboarding paradox.
The onboarding paradox states that the most valuable products are often the hardest to onboard users to, while the easiest products to onboard users to are often the least valuable over time. Resolving this paradox isn't about choosing sides—it's about understanding how to bridge the gap between first impression and lasting value.
The Attention Economics of First Impressions
In the modern attention economy, you have approximately 15 seconds to convince a user that your product deserves more than 15 seconds. Research from Microsoft shows that the average human attention span has decreased from 12 seconds in 2000 to 8 seconds today—shorter than that of a goldfish.
Yet meaningful products often require what researchers call "initial cognitive investment"—the mental effort needed to understand how something works before it becomes valuable. This creates a fundamental mismatch between user psychology and product reality.
The Onboarding Tension Spectrum:
Shallow-Fast: Products that provide immediate but limited value (social media, casual games)
Steep-Powerful: Products that require significant learning but offer transformational value (professional software, complex platforms)
Gradual-Sustainable: Products that reveal value progressively (learning platforms, habit-building apps)
Instant-Profound: The rare products that achieve both immediate value and deep capability (rare and often category-defining)
The Three Laws of Onboarding Physics
Understanding the onboarding paradox requires recognizing three fundamental laws that govern user behavior in early product experiences:
First Law - Conservation of Motivation: User motivation is finite and decreases with each friction point encountered. Like physical energy, motivation can be stored, transferred, or dissipated, but never created from nothing.
Second Law - Value Velocity: The rate at which users experience value must exceed the rate at which their motivation decreases. If value delivery is too slow relative to motivation decay, users will abandon the product.
Third Law - Complexity Uncertainty: Users will not invest effort in learning complex features until they're confident the investment will pay off. This creates a chicken-and-egg problem where value requires investment, but investment requires confidence in future value.
Case Study: The Figma Breakthrough
Figma's approach to the onboarding paradox offers a masterclass in threading the needle between complexity and accessibility. Design tools traditionally required extensive training, but Figma needed to appeal to non-designers who might use the product occasionally.
Their solution was brilliant: they created multiple onboarding paths based on user intent. Professional designers got a comprehensive, feature-rich introduction. Marketing team members got a simplified path focused on basic editing. Developers got integration-focused onboarding. Same product, different first impressions.
The result? Figma achieved both high initial adoption rates and deep long-term engagement. They solved the paradox by recognizing that "first impressions" aren't singular—they're contextual.
The Progressive Disclosure Philosophy
The most successful approach to the onboarding paradox involves progressive disclosure—revealing complexity in proportion to user readiness and need. This isn't about hiding features; it's about sequencing revelation.
The Four Stages of Progressive Disclosure:
Immediate Value Stage: Users experience benefit within the first interaction
Confidence Building Stage: Users develop trust in the product's capabilities
Capability Expansion Stage: Users discover advanced features as needs evolve
Mastery Stage: Users become proficient enough to teach others
Consider how Slack handles this progression. New users can send messages immediately (immediate value), quickly discover channels and threading (confidence building), gradually learn about integrations and workflows (capability expansion), and eventually become workspace administrators (mastery).
The Onboarding Success Framework: FIRST
The FIRST framework provides a systematic approach to resolving the onboarding paradox:
F - Friction Mapping Identify every point where users must exert effort during onboarding. Not all friction is bad—some friction indicates valuable learning—but all friction should be intentional.
I - Intent Recognition Understand what users are trying to accomplish and tailor the onboarding experience accordingly. One-size-fits-all onboarding often fits no one well.
R - Reward Scheduling Design a progression of rewards that maintains motivation throughout the learning curve. Early rewards should be frequent and immediate; later rewards can be less frequent but more substantial.
S - Social Proof Integration Show users how others have succeeded with the product. Seeing others' success reduces uncertainty about whether learning investment will pay off.
T - Time Investment Transparency Be honest about how long mastery will take and what users will gain at each stage. Uncertainty about future value kills motivation faster than high effort requirements.
The Motivation Bank Account
Think of user motivation as a bank account. Users arrive with a certain balance based on their needs, expectations, and alternatives. Every friction point makes a withdrawal; every value moment makes a deposit.
The onboarding paradox occurs when products require large early withdrawals (learning complex interfaces) before making significant deposits (delivering transformational value). Successful onboarding manages this cash flow problem.
Motivation Banking Strategies:
Early Deposits: Provide immediate value before asking for significant effort
Transparent Withdrawals: Explain why effort is needed and what it will accomplish
Interest Payments: Offer increasing returns on motivation invested
Emergency Funds: Provide help and support when motivation runs low
Compound Growth: Design experiences where early learning accelerates later value
The Personalization Imperative
Generic onboarding experiences fail because they assume all users have identical motivation levels, goals, and contexts. The onboarding paradox can often be resolved through intelligent personalization.
Personalization Dimensions:
Role-Based: Different experiences for different job functions or use cases
Experience-Based: Novices get more guidance; experts get more efficiency
Goal-Based: Onboarding varies based on what users want to accomplish
Time-Based: Different flows for users with different available time investments
Context-Based: Onboarding adapts to device, situation, and environment
Measuring Onboarding Success
Traditional metrics like completion rates or time-to-value often miss the nuanced success patterns of complex onboarding. Better metrics focus on progression quality rather than speed.
Advanced Onboarding Metrics:
Value Realization Rate: Percentage of users who achieve their primary goal during onboarding
Learning Velocity: How quickly users progress through capability levels
Motivation Sustainability: User engagement levels throughout the onboarding journey
Mastery Progression: Advancement from basic to advanced feature usage
Onboarding NPS: User satisfaction specifically with the learning experience
The Emotional Architecture of First Impressions
Beyond functional considerations, successful onboarding manages emotional progression. Users typically experience a predictable emotional journey: excitement → confusion → frustration → understanding → confidence → advocacy.
The key is minimizing the depth and duration of negative emotions while accelerating the journey to positive ones.
Emotional Design Principles:
Confidence Before Complexity: Help users feel competent before introducing advanced capabilities
Progress Celebration: Acknowledge and celebrate learning milestones
Failure Reframing: Turn mistakes into learning opportunities rather than dead ends
Social Connection: Connect users with communities or support systems
Future Vision: Help users imagine their potential success with the product
The Long-Term Onboarding Perspective
The onboarding paradox becomes more manageable when we expand our definition of "onboarding" beyond the first session or week. True onboarding often takes months for complex products, with multiple phases of discovery and mastery.
Extended Onboarding Phases:
Days 1-7: Basic competency and immediate value
Weeks 2-4: Feature discovery and workflow development
Months 2-3: Advanced capabilities and customization
Months 4-6: Integration with other tools and processes
Month 6+: Mastery and potential advocacy
The Platform Paradox Solution
Platforms face an especially acute version of the onboarding paradox: they need to simultaneously onboard multiple user types with different needs and capabilities. The solution often involves creating ecosystem-based onboarding where different participants help onboard each other.
Consider how YouTube resolves this challenge. Viewers need minimal onboarding—they can watch videos immediately. Creators need much more complex onboarding involving video production, audience development, and monetization. But successful creators help onboard viewers by creating compelling content, while engaged viewers motivate creator onboarding by providing audience.
Building Paradox-Resilient Organizations
Companies that consistently solve onboarding paradoxes share certain organizational characteristics:
Cultural Attributes:
User Empathy: Deep understanding of user contexts and constraints
Learning Orientation: Treating onboarding as an ongoing learning laboratory
Cross-Functional Collaboration: Breaking down silos between marketing, product, and customer success
Patient Capital: Willingness to invest in long-term user success rather than just short-term activation
The onboarding paradox reminds us that in a world of infinite choice, the products that survive aren't necessarily the easiest to start with—they're the ones that most effectively bridge the gap between initial curiosity and lasting value. The companies that master this bridge-building don't just acquire users; they develop advocates who become the foundation for sustainable growth.
Remember: first impressions aren't about perfection—they're about progression. The goal isn't to hide complexity but to sequence it in service of user success.
📚 Monthly Book Club for Product Managers
The Design of Everyday Things by Don Norman
Why Every Product Manager Should Read This Design Psychology Classic
Originally published in 1988 and revised in 2013, Don Norman's "The Design of Everyday Things" remains one of the most influential books on design psychology and user experience. For product managers navigating the complex landscape of digital products, this book offers timeless insights into how humans interact with designed objects and systems.
The Foundation: Understanding Human-Centered Design
Don Norman's masterpiece begins with a deceptively simple premise: when people struggle to use something, the fault lies not with the user, but with the design. This fundamental shift in perspective—from blaming users to examining design flaws—forms the cornerstone of human-centered design thinking that every product manager should internalize.
Norman, a cognitive scientist turned design advocate, argues that good design should be invisible. When we effortlessly open a door, send an email, or navigate an app, we're experiencing the result of thoughtful design that aligns with human psychology and behavior. Conversely, when we push a door that should be pulled, struggle to figure out which button to press, or abandon a signup flow, we're encountering the consequences of design that ignores fundamental human needs.
For product managers, this perspective is revolutionary. Instead of training users or writing better documentation to overcome usability issues, Norman advocates for designing products that work intuitively with human cognition. This approach not only improves user experience but also reduces support costs, increases adoption rates, and drives product success.
The Psychology Behind Great Product Design
Affordances: What Actions Are Possible?
One of Norman's most influential concepts is "affordances"—the perceived and actual properties of an object that determine how it could possibly be used. A button affords pushing, a slider affords dragging, and a text field affords typing. In digital products, affordances help users understand what actions are possible without explicit instruction.
For product managers, understanding affordances is crucial for feature design and user onboarding. Consider the evolution of mobile interfaces: early touchscreen phones struggled because they relied on affordances borrowed from desktop computing (small buttons, hover states). The iPhone's success partly stemmed from embracing touch-specific affordances—large, finger-friendly buttons, swipe gestures, and pinch-to-zoom functionality that felt natural on a touchscreen.
When evaluating product features, ask yourself: "What affordances does this interface element communicate?" A grayed-out button should clearly afford nothing (disabled state), while a bright, elevated button should obviously afford clicking. Mismatched affordances create confusion and friction in the user experience.
Signifiers: How Do Users Know What to Do?
While affordances determine what actions are possible, signifiers communicate how to perform those actions. Norman distinguishes between these concepts because good design requires both: something must be possible to do (affordance) and users must understand how to do it (signifier).
In digital products, signifiers take many forms: icons, labels, colors, animations, and layout patterns. The shopping cart icon has become a universal signifier for "purchase items here," while the hamburger menu (three horizontal lines) signifies "more options available." For product managers, choosing the right signifiers means balancing innovation with user expectations.
Consider Slack's approach to signifiers in their messaging interface. New users immediately understand how to send messages (text input field with obvious "send" affordances), but Slack also uses subtle signifiers like typing indicators, emoji reactions, and threaded conversation visuals to communicate more complex interaction patterns. These signifiers help users discover advanced features naturally rather than through extensive tutorials.
Mental Models: How Users Think About Your Product
Perhaps Norman's most valuable insight for product managers is the concept of mental models—the internal representations people have of how things work. Users approach every product with existing mental models based on their experience with similar tools, physical objects, and conceptual frameworks.
Successful products either align with existing mental models or gradually reshape them through consistent, logical design patterns. Email applications succeeded partly because they borrowed mental models from physical mail (inbox, folders, drafts), making the digital experience instantly familiar. Conversely, products that violate established mental models create cognitive friction.
For product managers, understanding your users' mental models is essential for feature prioritization and design decisions. When Spotify introduced their shuffle feature, they had to contend with users' mental model of "random" (truly random) versus what actually created a good listening experience (weighted randomness that avoided repetition). The product team ultimately chose to optimize for user satisfaction rather than pure randomness, demonstrating how mental models should guide product decisions.
The Six Fundamental Principles of Design
Norman outlines six principles that form the foundation of good design, each with direct applications for product management:
1. Visibility: Making Important Elements Obvious
Good design makes the most important elements visible and prominent. In product management, this translates to clear information hierarchy, prominent call-to-action buttons, and obvious navigation patterns. Netflix exemplifies this principle by making their "Play" button the most visible element on any content page, reducing decision fatigue and driving engagement.
2. Feedback: Communicating System Status
Users need immediate and clear feedback about their actions. Loading spinners, confirmation messages, error states, and progress indicators all provide crucial feedback. Product managers should ensure every user action receives appropriate feedback, even if it's as simple as a button changing color when pressed.
3. Constraints: Limiting Possible Actions
Strategic constraints guide users toward correct actions and prevent errors. Form validation, disabled buttons for incomplete actions, and guided workflows all use constraints effectively. Airbnb's booking flow uses progressive disclosure and smart constraints to guide users through complex decisions without overwhelming them.
4. Mapping: Creating Logical Relationships
Good mapping creates obvious relationships between controls and their effects. In digital interfaces, this might mean placing related controls near each other, using consistent interaction patterns, or designing layouts that mirror user expectations. The best product interfaces feel predictable because they maintain consistent mapping throughout the experience.
5. Consistency: Maintaining Design Patterns
Consistency reduces learning time and increases user confidence. This applies to visual design, interaction patterns, terminology, and feature behavior. Product managers should establish and maintain design systems that ensure consistency across features and platforms.
6. Affordances: Designing for Natural Interaction
As discussed earlier, good affordances make possible actions obvious. Product managers should regularly audit their interfaces to ensure that interactive elements look interactive and non-interactive elements don't mislead users.
Practical Applications for Product Managers
Feature Discovery and Onboarding
Norman's principles directly address one of product management's biggest challenges: helping users discover and adopt new features. Rather than relying on tutorials or tooltips, apply human-centered design principles to make features discoverable through good affordances and signifiers.
Duolingo's gamification approach succeeds because it uses familiar mental models (games, progress bars, achievements) with clear signifiers (bright colors, progress indicators, celebration animations) to guide users through language learning. The product feels intuitive because it aligns with users' existing mental models while providing clear feedback and constraints.
Reducing User Error and Support Costs
By designing for human psychology rather than fighting it, products can dramatically reduce user errors and support requests. Norman's concept of "slips" (unconscious errors) versus "mistakes" (conscious but wrong decisions) helps product managers identify whether usability issues stem from poor signifiers or mismatched mental models.
Amazon's one-click purchasing succeeds because it eliminates opportunities for slips (fewer steps, fewer decisions) while providing clear feedback (immediate confirmation, easy cancellation). The feature's success demonstrates how understanding human psychology can drive business results.
A/B Testing and User Research
Norman's framework provides a lens for interpreting user research and A/B test results. When users struggle with a feature, examine whether the issue stems from unclear affordances, poor signifiers, mismatched mental models, or inadequate feedback. This systematic approach helps product managers identify the root cause of usability issues rather than just the symptoms.
Beyond Digital: Universal Design Principles
One of the book's strengths is its focus on physical objects and environments, which provides product managers with analogies and insights that translate to digital experiences. Norman's analysis of door design (push vs. pull handles), stovetop controls, and everyday appliances offers timeless lessons about human-centered design.
The infamous "Norman door" (a door that requires a sign to explain how to open it) has become shorthand for design that ignores human psychology. Product managers can apply this concept to identify "Norman features"—functionality that requires explanation because the design doesn't communicate its purpose clearly.
Limitations and Criticisms
While "The Design of Everyday Things" remains highly relevant, product managers should be aware of its limitations. The book focuses primarily on individual usability rather than collaborative features, social dynamics, or complex workflows that characterize many modern digital products.
Additionally, Norman's emphasis on error prevention and constraint sometimes conflicts with the need for powerful, flexible tools. Professional software often requires complexity that casual users might find overwhelming, forcing product managers to balance ease of use with functionality depth.
The book also predates many digital interaction patterns (touch interfaces, voice UI, AI-powered features) that modern product managers must consider. While the underlying psychological principles remain valid, their application continues to evolve with new technologies.
Key Takeaways for Product Managers
Blame the design, not the user: When users struggle with your product, examine whether the design adequately supports human psychology and behavior.
Align with mental models: Understand how users think about your product category and either work with those models or systematically reshape them.
Make actions obvious: Use clear affordances and signifiers to communicate what users can do and how to do it.
Provide immediate feedback: Every user action should receive appropriate feedback about its success, failure, or progress.
Use constraints strategically: Guide users toward success by limiting inappropriate actions and making the right path obvious.
Maintain consistency: Establish and enforce design patterns that reduce cognitive load and increase user confidence.
Conclusion: Timeless Wisdom for Modern Product Management
Nearly four decades after its initial publication, "The Design of Everyday Things" remains essential reading for product managers because it addresses fundamental aspects of human psychology that transcend specific technologies or design trends. Norman's insights help product managers create experiences that feel intuitive, reduce user frustration, and drive business success.
The book's greatest contribution to product management is its systematic framework for evaluating and improving user experience. Rather than relying on intuition or copying competitors, product managers can apply Norman's principles to make evidence-based design decisions that serve both user needs and business objectives.
In an era of rapidly evolving technology and increasing product complexity, the human-centered design principles outlined in this book provide a stable foundation for creating products that truly serve their users. For product managers committed to building better experiences, "The Design of Everyday Things" offers both philosophical grounding and practical tools for success.
As Norman himself notes, good design is actually much harder than it appears—precisely because when it's done well, it becomes invisible. For product managers, mastering these principles means creating experiences that feel effortless, intuitive, and delightful. In a competitive marketplace where user experience often determines product success, these timeless insights remain more valuable than ever.
🔥 MLA #week 29
The Minimum Lovable Action (MLA) is a tiny, actionable step you can take this week to move your product team forward—no overhauls, no waiting for perfect conditions. Fix a bug, tweak a survey, or act on one piece of feedback.
Why it matters? Culture isn’t built overnight. It’s the sum of consistent, small actions. MLA creates momentum—one small win at a time—and turns those wins into lasting change. Small actions, big impact
MLA: Bring the Customer Voice to Your Team
Why This Matters
Product teams often work with filtered, summarized feedback rather than hearing customers directly. When your team hears raw customer voices—the pauses, the sighs, the excitement, the confusion—it creates immediate empathy that no user story or dashboard can replicate. It's the difference between knowing that "users find onboarding confusing" and hearing Sarah say, "I honestly don't know what I'm supposed to click next. This is making me feel really stupid."
How to Execute
Choose the Right Recording
Look for 2-4 minute segments that showcase authentic user emotion:
Customer support calls where users explain their frustration
User interviews where customers describe workflow challenges
Sales demos where prospects ask clarifying questions
Onboarding calls where confusion is evident
Avoid: Purely transactional calls or sessions dominated by your team talking.
Prepare the Session
Get proper consent to share (anonymize if needed)
Choose a segment with clear customer emotion and language
Set context for your team: "This is Sarah, she's used our product for 3 months..."
Ask team to focus on emotions and specific words customers use
Guide the Listening Experience
Play the recording, then immediately ask:
"What emotions did you hear in the customer's voice?"
"What surprised you about how they described the problem?"
"What words did they use that we don't typically use?"
"What does this make you think about our current priorities?"
Capture Insights and Act
Document:
Customer's emotional state and specific language
Gaps between how customers vs. your team think about problems
Team "aha moments" or perspective shifts
Create next steps:
Identify one improvement that could address this customer's concern
Note customer language to incorporate into product communications
Set up a shared folder for future customer voice recordings
Expected Benefits
Immediate Wins
Emotional connection: Team develops genuine empathy for user struggles
Language alignment: Discover how customers actually describe problems
Priority clarity: User emotion helps distinguish must-have from nice-to-have improvements
Cultural Improvements
User-centric decisions: Teams start asking "What would this customer think?"
Reduced assumptions: Direct input challenges team assumptions about user behavior
Cross-team empathy: Shared customer voices create common understanding
Long-term Impact
Better product-market fit: Consistent customer exposure keeps teams aligned with real needs
Faster problem identification: Teams recognize patterns in customer feedback more quickly
Cultural transformation: Organizations develop customer-first mindset
Get Started Today
Your challenge: Find one customer recording that showcases genuine emotion and play it for your team within 5 days. Pay attention to team reactions and insights that emerge.
Share your experience using #MLAChallenge:
What customer emotion surprised your team most?
What immediate action did your team decide to take?
How did this change your perspective on a current product decision?
Let's inspire each other to make customer feedback everyone's business!
📝 Microtraumas in IT - The Silent Enemy of Tech Teams
Introduction: "It's Just a Joke"
The IT industry is associated with technology, logic, and code. But behind every line of code are people - with their emotions, sensitivities, and needs. And it's precisely in this sphere that things happen which rarely make it into sprint reports or Jira boards: microtraumas.
These aren't major traumas - we're not talking about open mobbing, shouting, or
