Category: Uncategorized

How Retool Hit $2M ARR Pre‑Launch: My Playbook on Developer Focus, Product‑Market Fit, and GTM

I spend my days building and scaling B2B products, and Retool’s journey to $2M in ARR before launch is a masterclass in focus. It’s also a case study I revisit when coaching teams on developer evangelism and founder-led GTM.

Listening to David Hsu recount the early decisions made the strategy crisp: stay laser‑focused on developers, remove the boilerplate of internal tools, and earn trust with speed.

Retool, a low-code platform for developers building custom internal tools.

Today, Retool is valued at over $3 billion and has some of the biggest companies in the world building apps on its platform.

Early on, plenty of smart folks thought the idea for Retool would fail and that the product’s developer focus would sink the company. I’ve heard variations of this skepticism whenever a team doubles down on a specific persona—especially developers.

What struck me is the clarity around the target customer and the discipline to pursue language-market fit. When you get the words right for developers—their jobs-to-be-done, primitives, and constraints—you lower friction across product discovery, onboarding, and activation.

Equally instructive is how Retool nabbed its earliest customers (which includes Brex, DoorDash and a Fortune 500 BigCo) and the way the team prioritized creating incredibly tight feedback cycles with these early evangelists. That’s founder-led GTM at its best: sit with users, ship fast, instrument everything, and turn customer conversations into a roadmap.

On the surface, Retool’s path to product-market fit seems incredibly smooth. But as David tells it, there were plenty of bumps in the road — and he’s got tons of advice for early-stage founders that are finding their footing. I’ve lived those bumps, too; they’re signals to tighten the loop, not reasons to pivot away from your core user.

My takeaways for product leaders: start with developer empathy, not feature breadth. Use founder bandwidth to run high-frequency user sessions, shadow internal tool builds, and test copy until you hit language-market fit. Treat docs, templates, and examples as part of the product; they often outperform UI tweaks for time-to-value.

Operationally, stand up a lightweight, metrics-driven pipeline that connects discovery to delivery. I like a weekly cadence that pairs qualitative insights with activation, time-to-first-value, and expansion signals—classic product-market fit lessons that prevent local optimizations. When you see pull, lean into developer evangelism and zero to one B2B marketing, not paid acquisition.

If I were replicating this playbook today, I’d deploy a small, forward-deployed team to embed with design partners, capture real workflows, and ship improvements daily. Pair that with clear outcomes vs output OKRs so the team optimizes for customer outcomes, not just shipping velocity. That’s how you earn trust with developers and translate it into durable ARR.

Retool’s story reinforces a principle I teach often: conviction in the right user beats broad appeal every time. Focus wins, feedback compounds, and the market rewards teams that can turn skepticism into traction—especially when the users are developers.

October 21, 2025
Defeat Inertia: A Product Leader’s Playbook to Lower Barriers and 10X Adoption

Change is the job. I build and sell products to reshape behaviors and markets, yet I’m constantly reminded that change is hard. Going back to chemistry, catalysts don’t just create change by pushing harder or exerting more energy — they remove or lower the barriers to change. That framing has reshaped how I approach product strategy, go-to-market, and adoption.

One lens I return to is “The Catalyst: How to Change Anyone’s Mind.” It underscores a simple truth: the obstacle isn’t always the idea; it’s the friction around it. The book outlines 5 specific barriers to change, called REDUCE — which stands for reactance, endowment, distance, uncertainty, and corroborating evidence. I’ve found that when we diagnose which barrier is in the way, our product and GTM decisions get sharper, faster, and far more effective.

Do you really need a 10X better product? Sometimes yes—but not always. In practice, the biggest competitor I face isn’t another vendor; it’s inertia. Prospects cling to the status quo because switching feels risky, expensive, or cognitively heavy. My job is to make staying put feel riskier than moving forward. That means de-risking the decision, shrinking the perceived switching cost, and removing “homeostasis hooks” like entrenched workflows and sunk costs. When I design onboarding, migration tooling, and progressive rollouts, adoption climbs—even when the product advantage is 2–3X, not 10X.

Urgency matters, but pressure backfires. I aim for urgency that respects autonomy. Instead of “buy now or else,” I show windows of compounding value—why acting this quarter creates momentum, unlocks ROI, or secures outcomes that are harder to capture later. Time-bound pilots, seasonal use cases, or milestone-based pricing can motivate action without triggering reactance. The goal is momentum, not manipulation.

Freemium isn’t just for software. I apply the same principle—reduce uncertainty and upfront commitment—to physical products and services through pilots, limited-scope deployments, try-before-you-buy programs, refundable deposits, warranties, and modular packaging. The point is to let customers experience value with minimal friction. If it lowers uncertainty and builds confidence, it belongs in your arsenal.

On pricing and negotiation, I default to clarity, not concessions. I anchor on measurable outcomes, map tiers to value ladders, and use give-get rules so price changes are tied to scope or risk, not arbitrary discounts. This avoids signaling lower quality and keeps identity intact—buyers want to feel like smart stewards, not bargain hunters. Framing around business impact (“Here’s the cost of staying put versus the ROI of switching”) consistently outperforms feature recitations.

Identity and category creation are powerful accelerants. When a prospect feels an offer threatens who they are—or what team norms demand—adoption stalls. I reframe the story so the decision aligns with their identity (“modern operator,” “data-driven leader”) and, when needed, I redefine the category to reduce comparison shopping. If you’re a new category, you’re not asking buyers to replace an incumbent—you’re inviting them to adopt a better lens. That shift diffuses reactance and opens the door to new budgets and metrics.

Corroborating evidence matters most when stakes are high. I equip champions with proof that speaks to their peers: credible case studies, ROI models, third-party benchmarks, and pragmatic references. Multiple independent signals—especially from customers “like them”—shorten the distance between interest and commitment. I’ve seen adoption jump when we pair a hands-on pilot with peer validation at each gate.

Here’s the throughline I use with teams: don’t push harder—remove friction. Diagnose which barrier in REDUCE is at play, then pick a targeted tactic: restore agency to counter reactance, offset endowment with easy reversibility and migration, bridge distance with progressive steps, shrink uncertainty with trials and proof, and stack corroborating evidence at the right moments. When we build products and GTM motions around lowering these barriers, we don’t just sell better—we make change feel inevitable.

Inspired by this post on First Round.

October 21, 2025
Inside X1’s Pivot: The Playbook Behind a 600K Waitlist and a $15 Million Raise

I gravitate toward consumer fintech stories that show how product-market fit is earned through conviction, narrative, and execution. In that spirit, I dug into the journey of Deepak Rao, co-founder and CEO of X1, a consumer fintech startup that’s building a credit card for a new generation. The arc of this build is a masterclass in pivoting under pressure and orchestrating a high-velocity launch without losing sight of fundamentals.

Just last week, X1 announced a $15 million funding round. To understand how they got here, I rewound the tape and focused on the pivotal decisions that transformed uncertainty into momentum.

First, the human side of the pivot: “The emotional journey of how the pandemic forced them to abandon the initial idea for a personal loan product.” I’ve been through moments like this, and the lesson is consistent — you can’t cling to sunk costs when the world changes. Teams need psychological safety to grieve the old plan, and leadership must reframe the mission quickly so energy channels into discovery, not denial.

Second, the demand-side proof: “How the team validated demand for the new idea by focusing on the launch announcement and getting all of the branding exactly right — before building anything.” This is a powerful consumer move. Before a single line of code defines the product, the market should be able to tell you — via signups and sentiment — whether your story resonates. In practice, that means sharpening positioning, crafting a memorable name and visual identity, and pressure-testing the value prop across landing pages, press briefs, and social. Treat the narrative as an MVP.

Third, the launch mechanics: “The launch strategy that crashed X1’s website and built up a 600K long waitlist.” When a launch overpowers your infrastructure, it’s both a win and a wake-up call. The playbook here blends scarcity (invites, phased access), social proof (credible press, testimonials), and a tight referral loop that rewards participation. In my experience, the secret is sequencing: tease, announce, then escalate with proof points — all while instrumenting analytics, scaling infrastructure, and staffing support for the surge.

Finally, the strategic lens: “Why finding product-market fit is different for consumer companies, plus advice on fundraising in tough times.” Consumer PMF hinges on emotion and habit, not just utility; you measure it through retention curves, organic growth engines (word of mouth, referrals), and depth of engagement. For fundraising in tough markets, the bar is higher: show authentic demand (waitlist-to-activation conversion), defensible economics (unit economics, risk controls), and a credible path to moats (brand, data, network effects). Narrative clarity matters — investors respond when your story, metrics, and roadmap triangulate.

Whether you’re in the early innings of starting a company, going through a tough pivot yourself, or planning out your product’s launch there are tons of helpful tactics here. My takeaway: lead with story, validate with signal, operationalize for scale, and keep the team emotionally aligned through the change. That’s how you turn a pivot into a product-market fit flywheel.

You can follow Deepak on Twitter at @drao1.

October 21, 2025
Nail Your Founder-Led Sales Pitch: My Proven Playbook to Build Rapport, Validate Narrative, and Win

Building is comforting; selling is confronting. I’ve lived both realities, and I coach founders through this transition every week. The moment you leave the quiet sanctuary of product discovery and step into founder-led GTM, everything gets noisier—buyers, budgets, and objections all collide. That’s precisely why a crisp, testable sales narrative matters as much as your MVP.

When I need to re-center on first principles, I often recommend “Founding Sales: The Early Stage Go-to-Market Handbook.” It’s a practical touchstone for zero to one B2B marketing and a great companion as you stress-test your early motion. What follows is the playbook I use to get a founder-led sales pitch into ship-shape—fast.

First, build your selling muscles with deliberate practice. I use a lightweight daily regimen: 10 targeted outbound touches, two discovery calls, and a 15-minute retro where I review call recordings and tighten my talk-to-listen ratio. I timebox every section of the call—agenda, discovery, narrative, proof, and next step—so I can diagnose exactly where I’m losing altitude. The goal is compound learning, not one-off heroics.

Next, try the “turbo rapport” challenge. In the first 60–90 seconds, find an authentic point of human connection that’s relevant to the business problem. Mirror the customer’s language, confirm their goals, and demonstrate that you’ve done the homework on their context. This isn’t small talk; it’s the foundation for high-fidelity discovery and a more truthful read on product-market fit.

Then, self-diagnose your selling narrative with five hard questions: 1) Do I articulate the customer’s problem crisply in their words? 2) Do I quantify the cost of the status quo? 3) Do I present a differentiated approach that’s easy to verify? 4) Do I offer credible proof (customer evidence, metrics, or a quick pilot)? 5) Do I secure a concrete next step tied to value realization? If any answer is shaky, the narrative—not just the delivery—needs work.

If you’re creating a new category (and trying to create a new budget), the bar is higher. Anchor on the economics of change: identify the trigger events that make the problem urgent, quantify the value unlocked, and pre-negotiate where budget can reallocate from (sunset tools, process inefficiencies, or adjacent line items). Provide a one-slide business case and a time-bound pilot so stakeholders can say “yes” without political risk. This is product management leadership in the wild.

For inspiration, I often point to the playbooks used building Atrium: instrument your process with activity and outcome metrics, run tightly scoped pilots to surface early leading indicators, and codify a crisp one-page narrative that any seller (including you) can deliver consistently. Treat every call as a mini-experiment and adjust the message weekly based on data, not vibes.

Don’t overlook the power of building a customer advisory board. Hand-select design partners who feel the pain viscerally, and co-develop the narrative with them. Their language becomes your message; their metrics become your proof. This closes the loop between discovery and go-to-market and accelerates signal on what resonates.

Finally, operationalize feedback. Tag call snippets by objection type, correlate deal progression with talk tracks, and track conversion by segment to learn where the pitch truly lands. Founder-led GTM thrives on short learning cycles: ship a narrative, measure outcomes, refine, repeat. Do this for four to six weeks and your pitch won’t just feel tighter—it will convert.

The shift from building to selling is supposed to feel uncomfortable. Lean into it with structure, heart, and discipline, and you’ll turn early chaos into a repeatable motion. That’s how you earn the right to scale.

October 21, 2025
Scale With Your Startup: Proven Lessons from Mike Boufford’s Decade at Greenhouse

Scaling a company is only half the battle; scaling your own career in lockstep is the harder, more enduring challenge. I’ve seen high-growth environments reward those who adapt early and often, which is why the arc of Mike Boufford’s journey resonates deeply with me as a product leader.

Mike Boufford, CTO of Greenhouse, an applicant tracking system and recruiting platform.

He wrote the first line of code at Greenhouse in May 2012, and he’s still there — over a decade later.

This isn’t the typical path of non-co-founding engineers, who usually get layered or leave to start their own ventures.

Drawing on his story, I zero in on how founders build an environment that makes early employees want to stay, and importantly, how leaders can build the career skills and self-awareness they need to succeed at a startup long-term. In my experience, that combination—healthy culture plus relentless personal development—is what keeps top talent growing rather than going.

How his own motivation changed over time and how he managed his relationship with the company’s co-founders. I’ve learned that motivations naturally evolve—from creation and ownership, to scale and stewardship, to legacy and leverage. Naming those shifts early helps you reset expectations with co-founders before friction builds. Practically, this means recurring check-ins on roles, decision rights, and the tradeoffs you’re willing to accept as the organization matures.

The techniques he used to prepare himself for every next phase of growth and how his role would have to change in 18-24 months. I encourage leaders to keep a running “future job description” and refresh it quarterly. Ask: What will break at our next order of magnitude? Which systems, skills, and successors must I develop now so that I’m qualified for the job I’ll have in two years? This future-back planning keeps you ahead of the curve as the startup compounds.

Why he read two books on every other executive’s area of the business when he joined the leadership team. That habit builds cross-functional fluency fast. In my teams, this kind of immersion reduces friction with peers, sharpens strategy, and anchors debates in shared constraints—exactly what product and engineering leaders need to operate credibly at the executive level.

For a nuanced perspective on retention and healthy team evolution, I recommend reading: Why This Engineering Leader Thinks You Shouldn’t Aim for Zero Regrettable Attrition. Embracing the right amount of change—especially at senior levels—can unlock growth for both the organization and the individual.

If you’re navigating startup leadership, product management leadership, or the IC to manager transition, take this playbook to heart: anticipate the next phase, invest in cross-functional competence, and renegotiate your role before the org structure forces it. That’s how you scale with your startup, not in spite of it.

Inspired by this post on First Round.

October 21, 2025
Build Culture Like a Product: Anna Binder’s Asana Playbook for High-Performing Teams

I’ve long believed that culture deserves the same rigor we bring to product management. That view crystallized in a recent deep dive with Anna Binder, Head of People at Asana, where we explored what it truly means to build culture like a product — with clear goals, tight feedback loops, and iterative learning.

We revisited the earliest days when she first took on the role, zeroing in on how she prioritized the initial things to tackle as a new People exec and combed through a slew of opinions that bubbled up from other folks at the company. What stood out to me is how much this mirrors product discovery: define the problem precisely, gather qualitative signals, and validate with small, high-leverage experiments before scaling.

Translating that into my own operating system, I treat cultural work like a roadmap. I write crisp problem statements, hypothesize the behavioral change we seek, run lightweight pilots, and measure adoption and sentiment. I anchor success on outcomes vs output OKRs so we avoid mistaking activity for impact. This mindset not only accelerates learning, it also builds trust because leaders can explain the why behind each cultural bet.

Anna shared her tactical playbook for creating a culture of feedback for not just low-performers, but high-performers, too. That nuance matters. High performers often get praise but little developmental tension; I’ve seen careers plateau when strengths go unsharpened. My practice: institutionalize upward feedback, time-box “bright spots and blind spots” in 1:1s, and ensure managers are trained to ask for evidence and examples, not just opinions. It’s an essential step in the IC to manager transition as well, where modeling curiosity sets the tone for the entire team.

She also unpacked her methodology of conscious leadership, and how the best leaders always interrogate how the opposite might be true. I’ve adopted that as a mental circuit breaker when I feel certain: I write the opposite hypothesis and list evidence for it. This habit reduces ego, surfaces hidden risks, and leads to more durable decisions — a hallmark of product management leadership.

From working on Asana’s executive team for nearly 7 years, Anna emphasized building habits that keep the exec team a healthy nucleus at the center of the company. I’ve seen the same: meeting hygiene (clear intents, pre-reads, decision logs), decision-making cadences that separate debate from decide, and transparent communication that closes loops with the broader org. Treating the exec group as a high-trust product squad prevents thrash and models the behaviors we want everywhere else.

We ended with a rapid-fire exchange that maps cleanly to everyday leadership. On onboarding: design a 30-60-90 plan with explicit outcomes, shadowing for context, and early relationship-building across functions. On all-hands meetings: prioritize clarity over spectacle, celebrate learning (not just wins), and reserve time for unscripted Q&A to keep the dialogue authentic. On mentors: build a personal board of advisors with complementary strengths — operators for execution, coaches for reflection, and domain experts for sharp edges.

If you’re looking to uplevel your culture, start small and think like a product creator: define outcomes, run thoughtful experiments, and iterate in the open. The compound interest from these practices shows up in engagement, execution velocity, and ultimately, sustainable performance.

Inspired by this post on First Round.

October 21, 2025
Hard‑Won M&A Playbook: Lessons from Daniel Debow on Selling Three Startups

Founders often ask me how to navigate startup acquisitions without losing focus on product, customers, and culture. I view M&A as an extension of product strategy: it’s about creating long-term value, not just closing a deal. That’s why I study practitioners who’ve done it repeatedly and well—and few have a clearer track record than Daniel Debow.

I draw on insights from Daniel Debow, a VP of Product for Demand at Shopify. Daniel is a three-time founder and a seasoned M&A pro. Daniel oversaw the process of all three of his companies’ acquisitions and has helped continue to grow them at scale inside larger corporations. His most recent startup, Helpful, was acquired by Shopify in 2019. Before that, he co-founded Rypple which was acquired by Salesforce in 2011. His first startup, Workbrain, was acquired by Infor in 2007.

From my vantage point leading product teams, Daniel’s journey underscores a core truth: the moving parts of an M&A process as a startup demand the same rigor we apply to product discovery and go-to-market execution. When I’m advising founders, I concentrate on aligning strategy, timing, and relationships so the outcome—whether you sell now or later—remains squarely in your control.

First, I assess conditions at potential acquirers with the same discipline I’d use to qualify enterprise customers. I look for executive sponsorship, a clear product adjacency, an integration path (org and technical), and real ownership of outcomes post-close. If I don’t see resourcing commitments, aligned incentives, or a P&L that will house the asset, I assume the environment won’t be “founder-friendly.” On the flip side, established companies that want to be more founder-friendly should make the sponsor and decision-maker map explicit, publish their integration playbook, define success metrics early, and commit to retaining key builders.

Next, I differentiate between clear buying signals and the companies that are just “tire kicking.” Buying signals include rapid access to senior decision-makers, diligent technical and security deep-dives, direct discussions about deal structure and integration, and proactive work on a joint customer narrative. Anti-signals include vague interest without a timeline, refusal to share org charts or decision rights, and perpetual “one more meeting” cycles led only by corp dev. When signal strength drops, I reset expectations or pause the process to protect the team’s focus.

Relationships make or break outcomes, so I build meaningful relationships with executives of all types, not just corp dev teams. I cultivate trust with the GM who owns the P&L, the product and engineering leaders who will operate the asset, the sales leader who needs a story customers will buy, and the finance lead who models the upside. I share roadmaps, customer win stories, and integration hypotheses, then ask for honest pushback. This turns diligence into joint problem-solving and sets the tone for post-acquisition execution.

Finally, I’m deliberate about techniques for including your investors in the M&A process, as well as messaging tips when opening up about the process to the wider team. With investors, I align on valuation guardrails, role clarity in negotiations, and information sharing protocols. Internally, I limit the circle early, establish a single source of truth (a lightweight data room and weekly update), and script what we’ll tell managers if rumors surface. If and when a deal becomes likely, I plan retention, customer communication, and integration milestones concurrently so momentum carries through day one.

The through line in all of this: treat M&A like a high-stakes product launch. Validate intent, qualify the buyer, insist on ownership of outcomes, and protect your team’s energy. Drawing on Daniel’s example, you can structure an acquisition process that preserves optionality, increases deal quality, and—most importantly—sets you up to scale the impact of what you’ve built.

Inspired by this post on First Round.

October 21, 2025
Why Communications Deserves a Seat on the Exec Team: Hard‑Won Lessons from Square

Communications isn’t a PR afterthought — it’s a strategic lever that shapes product perception, credibility, and go-to-market outcomes. When I look at the companies that out-execute their peers, they elevate comms to the executive level, align it tightly with product strategy, and treat it as a system — internal and external — not a series of press moments. That’s the lens I brought to a deep dive on startup communications with one of the sharpest operators in the field.

After a comms career at Google, Aaron joined Square in 2011 to lead corporate communications. He went on to join the exec team, reporting directly to Jack Dorsey and leading the comms strategy for Square’s IPO in 2015. In an interesting move, he also took on leading the people organization as well, running both orgs up until he left in late 2020. In addition to lecturing at UC Berkeley’s School of Law, Aaron now runs Background Partners, a communications consulting firm.

In today’s conversation, we dive deep into what founders need to know about both external and internal comms. Aaron shares more on:

Why comms deserves its own spot on the exec team and why most founders shouldn’t hire PR agencies. I’ve seen comms drive strategic clarity across product, GTM, and people operations — and when it reports into the CEO alongside product and revenue, you get tighter narratives and faster decisions. Early-stage founders often think an agency will manufacture momentum; in reality, founder-led storytelling, disciplined messaging, and consistent execution are far more effective (and cost-efficient) than outsourcing too early.

The jobs-to-be-done of the comms function in the early days of a startup — and why it’s not a good customer acquisition strategy. In the zero-to-one phase, comms should align the company around a sharp narrative, build trust with early users and talent, and reduce confusion in the market. Media coverage can be a credibility accelerant, but it’s rarely a dependable pipeline channel. Treat it like air cover for your product-led or founder-led GTM, not a replacement for it.

A 3-question framework for simplifying your company message early on. The most resilient narratives fit on a single slide and answer three things crisply: What problem do we solve? Why now? Why us? I map this directly to product positioning and roadmap priorities so every launch, customer story, and executive communication reinforces the same core promise.

How to prep for interviews and deal with difficult lines of questioning. Great media training looks a lot like great product reviews: anticipate the hard questions, practice concise answers, and bridge back to your core message without dodging. I keep a living Q&A doc, run red-team drills with my staff, and record mock interviews to tighten delivery, tone, and body language. When challenged, acknowledge, answer, and anchor — it earns credibility.

How to think about commenting on events in the news, or message layoffs to the team. Not every headline requires your voice; when you do comment, ensure it’s authentic, relevant to your mission, and aligned with your stakeholders. For sensitive internal communications — especially layoffs — specificity, empathy, and accountability matter most. Explain the why, the what, and the what’s next, and ensure managers are equipped to support their teams in real time.

Given how much the media landscape has changed in recent years, and how many founders are grappling with internal comms issues these days, Aaron’s advice makes for a valuable listen. The explosion of owned channels, the speed of social, and the blurring of internal and external narratives mean your messaging framework must be simple, repeatable, and durable across audiences — customers, candidates, investors, and employees.

We also recommend checking out his two excellent Medium posts:

–What’s Your Hour in ‘Silicon Valley Time’?

No, you don’t need to hire an agency

You can follow Aaron on Twitter at @zamosta.

Inspired by this post on First Round.

October 21, 2025
Inside Stripe’s Culture: Powerful Documentation Rituals from Kickoffs to Retros and Slack

Culture is a company’s operating system, and documentation is the code that keeps it performant. As I lead product teams, I’ve learned that great cultures don’t just happen—they’re intentionally designed, scaled, and maintained. When founders and operators ask me which organizations model this best, Stripe reliably tops the list.
I recently sat down with Brie Wolfson to compare notes on how documentation, rituals, and communication norms shape high-velocity teams.
Brie spent nearly 5 years at Stripe, where she worked on bizops and launched Stripe Press, followed by a stint at Figma where she worked on education. She then started her consultancy, named The Kool-Aid Factory, to share her lessons on building team cultures. And now she’s operating as a first-time founder building Constellate, a new productivity and communications tool for teams.
In our conversation, we zeroed in on company culture—what it looks like when it’s working, how to codify it early, and how to scale it without diluting what makes it special. A decade ago, many teams tried to emulate the playbooks of companies like Google and Amazon. Today, a newer guard has emerged, and Stripe is often the culture benchmark that startups aim to emulate.
Brie peels back the layers into not just the cultural pillars that drove Stripe’s meteoric rise, but also how these showed up in day-to-day work.
We also zoom out beyond Stripe to talk about her work teaming up with companies with The Kool-Aid Factory, seeing culture and company-building up close. Brie shares advice on codifying your operating principles, establishing meaningful rituals, and growing this kernel of culture as the company scales.
Here’s what resonated most for me—and what I’ve seen pay dividends in product management leadership. First, treat kickoffs as the contract between intent and execution. A strong kickoff doc aligns on the problem statement, the “why now,” the DRI and decision log, risks and non-goals, and success measures tied to outcomes vs output OKRs. This single artifact becomes the source of truth for product discovery, scope decisions, and stakeholder communication.
Second, close the loop with retros that are structured and searchable. Think of retro docs as compounding assets: what worked, what didn’t, what we’ll change, and where decisions deviated from the kickoff. Over time, these narratives accelerate onboarding, reduce repeated mistakes, and strengthen operating principles.
Third, make Slack channels work like living documentation. Clarify a channel’s purpose, pin an index post, standardize naming conventions, and link to the latest kickoff and retro. When Slack is curated—not chaotic—it becomes a lightweight knowledge system that complements your docs rather than competing with them.
Finally, remember that rituals are the scaffolding for culture. Whether it’s weekly written updates, decision memos, or quarterly operating principle reviews, the goal is to make writing a team sport. Writing sharpens thinking, scales context, and reduces the cost of coordination as headcount grows.
Read the full essay Brie recommended during the interview: Reality has a surprising amount of detail and the article she penned for First Round Review: Ditch Your To-Do List and Use These Docs to Make More Impact.
You can follow Brie on Twitter @zebriez
If you’re building a product organization—or evolving from IC to manager—this playbook helps you replace ambiguity with clarity, reactive busyness with intentional outcomes, and scattered updates with a coherent, documented operating rhythm. Start with one ritual, write it down, and let the practice compound.

October 21, 2025
What I Learned from Don Faul on Leading with Radical Transparency in Hard Times

Leading teams through volatility demands more than strategy decks—it demands conviction and clarity. That’s why I was eager to learn from Don Faul, CEO of CrossFit, whose leadership journey spans a combat zone and a corporate board room. He spent 8 years as a platoon commander in the U.S. Marine Corps, then took on roles at Google, Facebook and Pinterest, the latter of which he served as the Head of Operations. Few leaders have stress-tested their principles across cultures this different, and that perspective is invaluable for product management leadership. One theme we explored head-on: whether micromanagement is always a bad thing. In my experience, it isn’t binary. In moments of genuine risk—customer incidents, safety-critical launches, or brand-defining bets—short, explicit periods of hands-on leadership can help a team move faster and learn safely. The key is to set clear exit criteria, communicate the why, and anchor on outcomes vs output OKRs so the team understands what success looks like—and when autonomy returns. We also dove into what it takes to build a long-term company vision that actually energizes people. A credible vision marries a bold, emotionally resonant narrative with a concrete path of near-term milestones. In my role leading product management at HighLevel, we anchor that narrative in the customer’s pain, make the outcomes measurable, and translate the vision into crisp, sequenced bets. When teams can see how this quarter’s work ladders to a multi-year north star, execution energy skyrockets. All-hands meetings are another place where leadership either compounds trust—or depletes it. The most common mistakes I see: status-report theater, a sea of vanity metrics, and avoiding the hard questions everyone is already whispering about. My playbook is simple: lead with what’s hard, be explicit about trade-offs, highlight real customer stories, and tie priorities back to outcomes vs output OKRs. Then make space for unfiltered Q&A and follow up with written decisions so the operating system stays transparent. We also discussed what it takes to lead when things feel like they’re going off the rails, which plenty of startup folks are feeling right now. In uncertain markets, I default to over-communication: weekly updates on goals, financial runway and scenario plans; decision logs that explain what changed and why; and repeated clarity on the next three most important priorities. When the path gets rocky, transparency isn’t a virtue signal—it’s an operating mechanism that preserves momentum and dignity. Don unpacked lessons on embracing transparency when things aren’t going well, and also shared his experience having to wind down a company. My own approach in that situation is to move quickly and humanely: communicate early, share the specific criteria behind the decision, offer as much support as possible, and be crystal clear on timelines and logistics. People can handle tough news; what erodes trust is ambiguity and delay. For anyone navigating the IC to manager transition, there’s a powerful throughline in these lessons: leadership is context-aware. Your job shifts from owning tasks to designing systems—communication cadence, decision frameworks, and coaching—so that outcomes persist without your constant presence. The earlier you learn to set vision, define outcomes, and create feedback loops, the sooner your team compounds value. If you’re building in this market, remember: radical transparency is not just about sharing everything; it’s about sharing the right things at the right altitude, at the right time. Clarity on vision, grounded metrics, honest all-hands, and humane leadership in adversity—these are the habits that keep teams inspired and resilient. You can follow Don on Twitter @donfaul

October 21, 2025
From Narrow ICP to Broad Adoption: Customer Empathy That Fueled Webflow’s PMF

I recently sat down with “Bryant Chou”, co-founder and founding CTO of Webflow, a no-code visual web design platform built with freelance designers and developers in mind. We discussed how a sharp initial focus and deep customer empathy paved the way for expansion into a far broader market — and what that journey teaches about product-market fit.

Today, Webflow is valued at over $4 billion and has millions of users all over the world. More than 200,000 freelancers, agencies, small businesses and enterprises use Webflow to help design and power their websites at businesses large and small.

But Webflow didn’t always market to such a wide customer base. In our conversation, Bryant rewinds the clock to Webflow’s early days — when it was just a co-founder team of three building a better tool to design a website.

We explore why the Webflow co-founding team had such a strong conviction that designers were their ICP, and why they took much longer to launch than other folks in their Y Combinator cohort. He also explains how Webflow wrangled their viral launch on Hacker News into a sustainable revenue and shares his root cause analysis framework for collecting customer feedback.

On the surface, Webflow’s path to product-market fit seems incredibly smooth. But as Bryant tells it, there were plenty of bumps in the road — and he’s got tons of advice for early-stage founders that are finding their footing.

What resonated most with me was the discipline to start with a narrow ICP and earn the right to expand. Customer empathy wasn’t a slogan — it was the operating system. By obsessing over the designer workflow and outcomes, the team drove crisp product discovery, clear problem statements, and a roadmap that compounded into broader market relevance. That’s the unlock: depth before breadth.

Their go-to-market choices also underline a powerful principle of founder-led GTM: move slower at first to move faster later. Taking longer to launch than other folks in their Y Combinator cohort was a strategic trade — prioritizing quality, credibility with the core user, and a coherent onboarding path. Momentum from a launch matters, but only if the product can convert that attention into activation, retention, and sustainable revenue.

The “viral launch on Hacker News” was a spark, not a strategy. The meaningful lift came from translating that spike into durable usage through onboarding clarity, education, and community. I’ve seen the same dynamic repeatedly — channels create discovery, but product value creates habit. If your ICP receives unmistakable value on first run, you’ve turned a moment into a motion.

I also appreciated the rigor behind their root cause analysis framework for collecting customer feedback. In my practice, we mirror this by tying every request to a specific job-to-be-done, measuring frequency and impact, and validating the existing workaround. That structure keeps us from shipping surface-level features and instead solving the underlying problem that advances product-market fit.

For leaders navigating early-stage ambiguity, the lesson is clear: empathy is the fastest route to evidence. Anchor on a specific ICP, instrument discovery with uncomfortable honesty, and earn expansion by repeatedly delivering outcomes for your earliest, most demanding users. Do that, and widening your addressable market becomes a natural consequence — not a gamble.

October 21, 2025
Decentralized Community Masterclass: Bottom‑Up Growth, Creator Partnerships, First Hires

I recently sat down with Ben Lang, Head of Community at Notion, to unpack how a decentralized, bottom‑up community can power durable, compounding growth. In my day-to-day leading product, I’ve seen community-led growth move markets—hearing the detailed playbook behind it brought the strategy into sharp focus for operators and founders alike.

Since joining the company in 2019, Ben has had his hand in several high-impact projects at Notion that has grown its tight-knit community of passionate Notion evangelists into millions of users today.

But before he was doing this as a full-time job, Ben was already spreading his love for Notion in his free time as a voracious product user. After discovering the tool on Product Hunt, he became obsessed. He got on the company’s radar after launching his own Notion template gallery on Product Hunt and joined as one of the first 15 employees.

In our conversation today, we focus on the nuts and bolts of building a global community that drives user growth. Ben shares tactical advice on: Tackling community organically from the bottom-up, and why you shouldn’t go top-down; What companies are best suited to a centralized vs. decentralized community approach; Partnering with YouTubers and other creators; His advice to founders on finding your own first community hire.

Here’s my biggest takeaway on the bottom-up vs. top-down decision: bottom-up wins trust before it asks for anything. When you enable passionate users to teach, build, and share—then get out of their way—you unlock authentic advocacy that no paid campaign can replicate. Practically, this looks like community-led onboarding (templates, live office hours, and user-run meetups), lightweight governance (clear brand and safety guardrails), and a creator toolkit (assets, sample briefs, and success stories) that fuels developer evangelism and product discovery without stifling creativity.

On centralized vs. decentralized approaches, fit matters. Centralized communities shine when your product is compliance-heavy, your ICP requires curated expertise, or you need consistent, high-signal feedback loops. Decentralized communities thrive when your value compounds through remixing and sharing—think modular templates, integrations, and a vibrant ecosystem of product creators. My operating rule: start centralized for quality and learning, then progressively decentralize as playbooks harden and local leaders emerge. Instrument the handoff with clear roles, lightweight certifications, and community health metrics (activation, contribution velocity, and sentiment).

Creator partnerships—especially with YouTubers and niche educators—act as force multipliers. Treat creators like product partners, not channels: co-develop curricula, share early product roadmaps where appropriate, and equip them with data-backed talking points and reusable assets. Build a transparent value exchange (rev share, affiliate programs, early feature access), define success upfront (reach, engagement, and downstream activation), and keep content evergreen with updates tied to releases. The result is a repeatable growth loop that blends PLG, social proof, and zero to one B2B marketing.

For founders hiring the first community leader, optimize for a builder-operator hybrid: someone who has shipped programs, written docs, hosted events, and can close the loop from insight to iteration. Look for evidence of creator empathy, editorial judgment, lightweight product instincts, and the ability to scale through systems (templates, playbooks, and tooling). Define outcomes, not activities: measure community-led pipeline, activation lift, retention improvements, and the velocity of high-quality user feedback feeding product management leadership.

The throughline is simple: community is a product. Design it with the same rigor—clear ICPs, onboarding, retention hooks, and feedback loops—and it becomes a durable moat. Whether you lean centralized or decentralized, start bottom-up, enable your best users, and let creators help you tell the story the market actually wants to hear.

October 21, 2025