Lessons from Alex Komoroske

Lessons from Alex Komoroske

Alex Komoroske spent 13 years at Google and later ran corporate strategy at Stripe, studying how large organizations handle uncertainty. Known for his "slime mold" theory of management, he argues for gardening ecosystems rather than building them from the top down. This profile collects his observations on product strategy, complex systems, and why the hardest problems in tech are rarely technical.

Part 1: Product Management & The Labyrinth

1. On the nature of product challenges: "Imagine the problem space as a labyrinth that you must navigate to arrive at your goal." — Source: [Product Management and the Foggy Labyrinth]
2. On blind speed: "Velocity in impenetrable fog in unknown parts of the labyrinth would be foolhardy." — Source: [Product Management and the Foggy Labyrinth]
3. On careful navigation: "Any given step could have you collide with a wall or fall into a pit, so it's important to carefully consider each move." — Source: [Product Management and the Foggy Labyrinth]
4. On finding direction: "The general direction of the goal is your only beacon for you to rely on." — Source: [Product Management and the Foggy Labyrinth]
5. On the difficulty of ambiguity: "Unit for unit, complexity is significantly more difficult than complication." — Source: [Product Management and the Foggy Labyrinth]
6. On clear problem spaces: "If you're in a non-complicated and non-complex problem, a wide open room with no fog, point toward the goal, strap a rocket on, and light it!" — Source: [Product Management and the Foggy Labyrinth]
7. On the origins of uncertainty: "Complexity arises primarily due to the novelty of a problem space." — Source: [Product Management and the Foggy Labyrinth]
8. On decreasing friction: "As the novelty of the labyrinth fades the complexity will diminish." — Source: [Product Management and the Foggy Labyrinth]
9. On practical PM skills: Good product management often involves mapping the parts of the maze that are already known so the team can focus on the fog. — Source: [Bits and Bobs]
10. On adapting tactics: You must match your working style to the environment you are in, rather than applying a single strategy to every problem space. — Source: [Bits and Bobs]

Part 2: Slime Molds & Organizational Dynamics

1. On corporate reality: "Google is basically a slime mold." — Source: [Business Insider]
2. On embracing the organism: "Organizations are like slime molds. If you had fought that fact you would have gotten frustrated and burned out." — Source: [Slime Molds Deck]
3. On unlocking value: "By embracing that truth, you're able to unlock value, sustainably." — Source: [Slime Molds Deck]
4. On emergent structure: "So slime mold is a colony of single-celled organisms that operate as a coherent individual." — Source: [Smart Friends Podcast]
5. On collective action: "Often, they just kind of bleh out and it has this emergent structure that will find the food or whatever, but under stress, they can cohere into a coherent entity that works together." — Source: [Smart Friends Podcast]
6. On coordination headwinds: As an organization scales, the very independence that fuels innovation creates friction that slows down decision-making. — Source: [Saloni's Blog]
7. On self-organization: Decentralized teams naturally route around obstacles to find nutrients, much like a biological network. — Source: [Clearer Thinking Podcast]
8. On misdiagnosing issues: When you expect a large company to function like a machine, you fail to see the problems that arise from its organic growth. — Source: [Clearer Thinking Podcast]
9. On organizational kayfabe: People inside large corporations often perform their roles as if reading from a script to maintain the illusion of top-down control. — Source: [Lenny's Podcast]
10. On centralized planning limits: Planning fails in a slime mold because the organism reacts to local stimuli faster than a central brain could process them. — Source: [Lenny's Podcast]

Part 3: Gardening vs. Building

1. On distinct mindsets: "The builder gets immediately to work, but the gardener understands that other things can be alive." — Source: [Smart Friends Podcast]
2. On relinquishing control: "I like the word gardening because it underlines that you are not in control of this system. You are influencing it." — Source: [Smart Friends Podcast]
3. On interacting with systems: "I think that to really wrestle with systems you have to let go and just dance with the system." — Source: [Smart Friends Podcast]
4. On shifting focus: "Focus less on being a builder, frustrated that your building materials refuse to behave. Instead, think of yourself more as a gardener." — Source: [Slime Molds Deck]
5. On the Saruman archetype: The builder operates with a focus on direct control, detailed planning, and immediate output. — Source: [Deciphr.ai Transcripts]
6. On the Radagast archetype: A gardener focuses on nurturing potential, pulling weeds, and creating environments where positive outcomes emerge organically. — Source: [Smart Friends Podcast]
7. On planting seeds: Instead of expecting full control over the final product, a leader should nurture ideas and environments. — Source: [Lenny's Podcast]
8. On platform coevolution: Platforms must grow alongside their ecosystems, requiring a strategy that is fluid rather than static. — Source: [Discourse Forums]
9. On mitigating frustration: When you accept that you are managing a living system, the unpredictable behavior of your teams becomes a feature to work with rather than a bug to fix. — Source: [Boundaryless]
10. On farming miracles: Creating the right conditions allows you to optimize for serendipity and let unexpected successes bloom. — Source: [Smart Friends Podcast]

Part 4: The Adjacent Possible

1. On defining the concept: "The adjacent possible is a set of actions that you can actually choose from." — Source: [Clearer Thinking Podcast]
2. On practical design: "The adjacent possible is a design thinking frame, and it's the set of actions that are within your reach, that if you did them, they would almost certainly work." — Source: [Smart Friends Podcast]
3. On perceived options: "Your adjacent possibles are often much smaller than people think they are." — Source: [Clearer Thinking Podcast]
4. On the constraints of reality: "The system of constraints operating on us at any point leave very little maneuvering room and box us in significantly." — Source: [The Iterative Adjacent Possible]
5. On iterative hope: "It's also not as bad as we thought that our adjacent possible is small. This is not a one-shot game." — Source: [The Iterative Adjacent Possible]
6. On avoiding moonshots: "Big ambitious moonshots are taking on two huge risks: The risk of aiming in the wrong direction, and the risk of not getting there." — Source: [Felix Crux Blog]
7. On incremental progress: "Incrementally feel your way toward the right solution, which lets you learn and chart new courses as you make progress." — Source: [Felix Crux Blog]
8. On identifying bad plans: "A lot of plans kind of say, 'And then we're going to do this massive thing that we're going to ship in three months.' It's like no, wait a second. This is definitely not a new adjacent possible." — Source: [Clearer Thinking Podcast]
9. On achievable targets: Real progress comes from taking the steps that are immediately available, rather than trying to jump to a distant future state. — Source: [Bits and Bobs]

Part 5: Complexity vs. Complication

1. On different rewards: "Complication rewards velocity, organization, and execution." — Source: [Product Management and the Foggy Labyrinth]
2. On thoughtful action: "Complexity rewards judgement, thoughtfulness, and reason." — Source: [Product Management and the Foggy Labyrinth]
3. On execution speed: In a complicated environment, moving fast is an asset; in a complex environment, moving fast will cause you to crash. — Source: [Product Management and the Foggy Labyrinth]
4. On problem framing errors: Most organizational failures occur when a complex problem is treated as merely a complicated one. — Source: [Product Management and the Foggy Labyrinth]
5. On distilling issues: The goal of strategy is often to break down complex challenges into complicated tasks that teams can execute against. — Source: [Product Management and the Foggy Labyrinth]
6. On hazard assessment: Complication is a measure of how many known hazards exist, while complexity is the measure of the fog that hides them. — Source: [Product Management and the Foggy Labyrinth]
7. On managing ambiguity: Leadership in complex environments requires the patience to let the fog clear before making irreversible decisions. — Source: [Bits and Bobs]
8. On project management limits: You cannot project-manage your way out of complexity, because project management tools are designed for complication. — Source: [Bits and Bobs]
9. On converting complexity: As you explore a complex space, you map the terrain, effectively converting complexity into complication over time. — Source: [Bits and Bobs]

Part 6: Systems Thinking & Ecosystems

1. On finding engines: Instead of relying on heroic individual efforts, leaders should identify the inherent dynamics or compounding loops within their organizations and harness them. — Source: [Medium]
2. On unintended consequences: When you intervene in a complex system without understanding its equilibrium, your fix will likely generate new problems. — Source: [Lux Capital]
3. On open ecosystems: Open ecosystems succeed because they rely on the decentralized intelligence of their participants, rather than bottlenecking decisions at the top. — Source: [Boundaryless]
4. On tight feedback loops: A healthy system requires tight feedback loops so that the organism can sense changes and adapt its behavior immediately. — Source: [Bits and Bobs]
5. On removing friction: Sometimes the best way to accelerate a system is not to push it harder, but to find and remove the friction that is holding it back. — Source: [Lenny's Podcast]
6. On observing actual behavior: You must watch what the system actually does, rather than what the system claims it is doing in its official documentation. — Source: [Lenny's Podcast]
7. On local incentives: The behavior of the whole is driven by the incentives of the individual nodes; change the local incentives, and the global structure shifts. — Source: [Bits and Bobs]
8. On sustainable growth: A system that relies on constant manual intervention is fragile; a system that sustains itself is resilient. — Source: [Boundaryless]
9. On systemic inertia: Organizations resist change because their internal structures have optimized for the current state, acting as a defensive immune system against disruption. — Source: [Clearer Thinking Podcast]

Part 7: Intentional Technology & Artificial Intelligence

1. On intention alignment: Technology should be designed to help people grow toward their long-term goals rather than merely maximizing short-term engagement. — Source: [Every (AI & I)]
2. On new manifestos: The future of software requires a more human-centric, adaptable, and privacy-focused framework. — Source: [Simon Willison's Weblog]
3. On avoiding enshittification: To reverse the degradation of online platforms, we must build architectures that do not rely on capturing and exploiting users. — Source: [RiskGaming Podcast]
4. On open vs closed networks: We should favor interoperable, open ecosystems over closed, aggregated platforms that trap user data. — Source: [Revolution.Social]
5. On AI as a collaborator: Artificial intelligence should act as a collaborator that enhances human capability, rather than a replacement that diminishes human agency. — Source: [Every (AI & I)]
6. On digital spaces: We need to reimagine digital environments so that they facilitate deep thinking and connection, rather than fractured attention. — Source: [Every (AI & I)]
7. On AI complexity: AI introduces a new level of emergent complexity to software development, requiring builders to adopt the gardener mindset more than ever. — Source: [AI Native Dev]
8. On technological advantage: The actual utility of new technology is not in doing old things faster, but in making previously impossible adjacent steps accessible. — Source: [Every (AI & I)]
9. On user agency: A resonant computing environment respects the user's intent and provides tools that bend to their needs, rather than forcing the user to adapt to the software. — Source: [RiskGaming Podcast]

Part 8: Mindset, Growth, & Iteration

1. On public thinking benefits: Documenting your raw, weekly reflections helps clarify your logic and exposes your ideas to constructive critique. — Source: [Komoroske.com]
2. On intellectual humility: Acknowledging the fog is the first step to navigating it; pretending the path is clear only leads to avoidable disasters. — Source: [Product Management and the Foggy Labyrinth]
3. On updating mental models: The environment is always changing, which means your mental models must be updated constantly to remain useful. — Source: [Bits and Bobs]
4. On learning from small steps: Taking a small step and learning from the result provides far more information than spending months on theoretical planning. — Source: [The Iterative Adjacent Possible]
5. On managing energy: Working with the natural flow of a large organization prevents the exhaustion that comes from trying to force it to behave like a machine. — Source: [Slime Molds Deck]
6. On finding influence: The most effective people in a company are those who understand the informal network of the slime mold, rather than just the formal org chart. — Source: [Lenny's Podcast]
7. On realistic ambition: True ambition is not about setting impossible goals, but about rigorously executing the next viable step in a given direction. — Source: [Felix Crux Blog]
8. On staying calm in ambiguity: The ability to stay calm when you do not know the answer is a required skill for modern knowledge work. — Source: [Bits and Bobs]
9. On planting seeds for the future: Enduring impact comes from planting seeds today that will compound into thriving ecosystems years down the line. — Source: [Smart Friends Podcast]