I’ve been reflecting on what it really takes to scale a product organization through hypergrowth, and I keep coming back to the discipline and mindset modeled by Claire Hughes Johnson. Her approach to operating at scale, executive hiring, and leadership development aligns closely with the highest standards of product management leadership.
Claire joined Stripe as its COO back in 2014 and, over the course of her nearly seven years in the company’s executive suite, she oversaw rapid growth as Stripe scaled from under 200 employees to over 7,000. Prior to Stripe, she spent 10 years at Google leading various high-impact business teams. That arc of operating experience sets the context for her new book, “Scaling People: Tactics for Management and Company Building.”
One story that particularly resonates with me is the inside look at her lengthy, no-stone-unturned interview process with the Collison brothers for the COO role. I’ve learned that this level of rigor is not just about due diligence; it’s a signal of shared standards and cultural alignment. When I hire for critical roles, I mirror this depth: clarify the mandate, pressure-test values, and evaluate for the long arc of decision quality—not merely short-term execution.
Hiring exceptional talent demands systems thinking. Claire’s emphasis on doing reference checks the right way—structured, targeted, and focused on observed behaviors—maps to my own playbook. I’ve found executive hiring is hard because the signals are noisy, the roles are often ambiguous, and it’s tempting to over-index on brand or storytelling. The antidote is to define success as outcomes, not activities, and then assess candidates against those outcomes. This is where outcomes vs output OKRs become indispensable for preventing mis-hiring and aligning expectations.
Her personal backstory also underscores a foundational leadership trait: curiosity. The way her parents instilled deep curiosity and fierce independence at a very young age is more than biography—it’s a blueprint. In practice, it translates to cultivating an owner’s mindset across the org, which is crucial for anyone navigating an IC to manager transition and for leaders who must empower teams without micromanaging.
I also appreciate her belief that all high-performers are “learning organisms.” I’ve seen the best product leaders systematize learning with deliberate feedback loops, postmortems, and explicit mechanisms to turn insight into action. In product discovery, this shows up as rapid cycles of hypothesis, experiment, and synthesis—creating a culture where learning velocity compounds just as reliably as revenue can.
This is why I recommend “Scaling People: Tactics for Management and Company Building” to operators who want pragmatic tools, not just abstractions. For complementary perspective, the book she recommended from Fred Kofman titled “Conscious Business” pairs well with these themes of ownership, integrity, and clear commitments—essentials for leaders who manage complexity at scale.
If you’re looking to stay close to her work, you can follow Claire on Twitter at @chughesjohnson. I’ve found her ongoing reflections a useful calibration point for raising the bar on leadership systems, executive hiring, and operating rigor.
My key takeaway is simple but powerful: scale rewards clarity, discipline, and humility. Hiring is a product in itself. Culture is a system, not a slogan. And the leaders who keep compounding are the ones who choose to be “learning organisms,” building teams that do the same.
Early user research is the single highest-leverage activity I recommend to founders who want to validate an idea quickly and confidently. In my work leading product strategy, I’ve seen high-quality customer interviews compress months of guesswork into a few focused days, turning vague concepts into clear signals about product-market fit.
I often point founders to the practical wisdom from Jeanette Mellinger, whose approach aligns closely with how I guide teams through product discovery. Her lens on rigorous, respectful, and insight-rich conversations has shaped how I structure research plans, prepare teams, and synthesize findings into actionable decisions.
In this piece, I unpack the core pillars I rely on for early validation: The three-step framework for a thorough user-research process; The biggest mistakes she’s noticed after working with dozens of early-stage companies; and Specific advice for structuring an interview flow and crafting better questions that unlock essential insights. These simple, durable principles help founders avoid common pitfalls and focus on what truly matters: how customers behave, what they value, and where the product should go next.
On process, I guide teams to adopt The three-step framework for a thorough user-research process. While the tactics can vary by market, the intent is consistent: define the learning goals up front, prepare a tight interview plan, and commit to rapid synthesis. When founders do this well, they speed up discovery, reduce bias, and make sharper decisions about which problems are worth solving.
On mistakes, I see patterns repeat. The biggest mistakes she’s noticed after working with dozens of early-stage companies mirror what I encounter: pitching instead of listening, over-indexing on opinions instead of behaviors, asking leading questions, and trying to validate a solution rather than deeply understanding the problem. The antidote is discipline—stay curious, probe for real stories and workflows, and keep the conversation anchored in what customers actually do, not what they say they might do.
On interview craft, I lean on Specific advice for structuring an interview flow and crafting better questions that unlock essential insights. Start with context (role, goals, current workflows), move into concrete behaviors (last time they tried to solve the problem, tools used, success criteria), and finish with pain points and opportunities (workarounds, constraints, moments of friction). Use open-ended prompts, ask for specific recent examples, and consistently follow up with “what happened next?” and “how did you decide?” to surface the underlying mental models that should shape your product.
If you’re a founder running a founder-led GTM motion, this approach keeps you grounded in customer reality while accelerating product discovery. It also equips you to communicate insights clearly to your team, turning interviews into alignment and momentum. Over time, this rigor compounds—your roadmap becomes crisper, your experiments get smaller and faster, and your conviction grows with each conversation.
You can follow Jeanette on Twitter at @jnetmell. If these practices help you validate faster or avoid costly detours, share what you learned and what you’ll try next—I’d love to hear how your discovery work is evolving.
Product-market fit is measurable — and the REV (revenue, engagement and value) model is one of the most practical ways I’ve found to quantify it while aligning product, go-to-market, and category strategy.
I’m continually inspired by how Artem Kroupenev, VP of Strategy at Augury, operationalized this thinking to scale a new category. Augury is a leader in a category they helped to define known as “machine health.” The company sells products that combine hardware, AI, and SaaS within industrial manufacturing.
Artem joined the team at the very beginning of its journey and helped shape strategies for how the team measured product-market fit, go-to-market, and eventually, a strategy for designing a brand new market category they could compete in. Those lessons map closely to how I build and scale products today.
Here’s how I translate these ideas into a practical playbook you can apply right now: Augury’s storyboard-based approach to product vision, how to sell to a limited pool of customers, the REV (revenue, engagement and value) model for measuring product-market fit, and when founders should start exploring creating a new category to operate in.
Augury’s storyboard-based approach to product vision resonates with how I align teams and customers. I start with narrative storyboards that depict the current pain, the first “magic moment,” and the end-to-end value realization. These storyboards become a shared contract between product, sales, and customers — clarifying what must be true for adoption and value. They also drive ruthless prioritization: if a feature doesn’t move a storyboard frame closer to value realization, it waits.
When the market has a limited pool of customers, precision matters more than volume. I’ve found success by sequencing accounts into tight cohorts, running deep discovery with forward-deployed product teams, and setting explicit learning goals per cohort. Lighthouse wins matter, but only if they’re repeatable — so I anchor early deals to a clear “who/what/why” ideal customer profile and instrument the entire journey from pilot to expansion to prove repeatability.
The REV (revenue, engagement and value) model gives me a crisp, triangulated view of product-market fit. Revenue shows willingness to pay and expand (e.g., pilot-to-paid conversion, logo retention, net revenue retention). Engagement reveals product stickiness (depth, frequency, and breadth of usage; time-to-first-value; activation and expansion milestones). Value proves that outcomes are real (business impact metrics tied to the customer’s objectives, such as cost savings, yield improvement, or risk reduction). I don’t rely on a single metric; I set threshold targets for each dimension by cohort and track deltas over time to see whether the product is getting easier to sell, faster to adopt, and more valuable to customers.
I also treat REV as a lifecycle score. Early on, I’m comfortable with weaker revenue signals if engagement and value are strong and accelerating — that’s a prompt to invest in packaging, pricing, and sales enablement. Later, if revenue is strong but engagement lags, I pause new segments and sharpen onboarding, “aha” moments, and workflows until usage curves show healthy compounding. The point is to let each dimension guide the next set of investments.
On category creation, timing is everything. I only lean in when evidence shows the existing labels constrain the value story, the product reliably produces unique outcomes, and customers start using our language organically. That’s the moment to name the problem space, codify proof (case studies and benchmarks), rally an ecosystem, and publish a crisp narrative that explains what’s new, why it matters now, and how success is measured. Attempt it too early and you confuse buyers; do it once REV signals are strong, and you accelerate market pull.
If you’re leading in industrial manufacturing or building hardware–AI–SaaS solutions, these principles are especially vital: storyboard the vision to align complex stakeholders, sell with intent to a limited customer pool, and instrument the REV score to prove outcomes at every stage. Even in pure SaaS, the same playbook applies — the mechanics are different, but the signals of fit are universal.
My challenge to your team: within two weeks, storyboard your core value journey, define three to five REV metrics per lifecycle stage, and review them by cohort. You’ll not only see where product-market fit truly stands, but you’ll also know exactly what to do next — whether that’s sharpening onboarding, revisiting packaging, or laying the groundwork for a category you can own.
I’m often asked how elite teams compress the journey to product-market fit. One story I keep returning to is Jessica McKellar, co-founder and CTO of Pilot, which is the largest accounting firm for startups. For the past six years, she’s built Pilot alongside her two co-founders, Waseem Daher and Jeff Arnold — and what makes this trio extraordinary is that they’ve stuck together across three startups.
As repeat founders, the team learned a ton from their first two ventures, K Splice and Zulip, and both netted some positive outcomes. Yet there were mistakes that prevented those products from becoming an outsized success. From a product management leadership perspective, I see a clear evolution in how they approached problem selection, product discovery, and go-to-market.
With Pilot, they prioritized picking an acute problem and a huge market to tackle. That simple but rigorous reframing matters: identify a customer segment with a painful, high-frequency workflow; quantify the market; and ensure a compelling “why now.” This is classic founder-led GTM discipline and the essence of practical product-market fit lessons.
They also embraced a deliberately tedious build process for v1: looking over Waseem and Jeff’s shoulders as they manually did the bookkeeping for early customers, while she wrote code alongside them. In my experience, this “do the job, then automate” approach functions like forward deployed engineers for founders — embed with the real workflow, capture edge cases, then translate that knowledge into the system of record.
Even going back to the earliest days, Pilot had some really strong product-market fit signals, with customers agreeing to pull out their credit card and pay for the product right away when it was just an idea on paper and eventually pulling the Pilot team into expanding their product suite. That willingness-to-pay signal, coupled with pull-based requests for adjacent capabilities, is exactly what I look for before scaling zero to one B2B marketing or hiring beyond the founding team.
My playbook from this story is straightforward: choose a narrowly defined, acute pain in a massive category; run founder-led discovery inside the customer’s workflow; ship code alongside the service until the workflow is reliable; price early to validate value; and align outcomes vs output OKRs so the team optimizes for customer impact, not feature volume. Do this, and you convert messy service learnings into a repeatable product engine.
Make no mistake about it — being a founder is incredibly difficult — but choosing the right problem to tackle can drastically smooth the path ahead of you. For product creators, that choice — and the discipline to live in the customer’s workflow early — is the difference between meandering and momentum.
I sat down with Douglas Hanna, Chief Operating Officer at Grafana Labs. Grafana Labs is an observability stack built around Grafana, a leading open-source technology for dashboards and visualization.
Douglas is a seasoned revenue leader, previously leading operations and GTM strategy at Zendesk. At Grafana Labs, Douglas has been instrumental in scaling GTM at the open-source company — building up both team headcount and its revenue model.
In our conversation today, Douglas dives deep into the process of bringing products to market at an open-source company. That focus on disciplined go-to-market execution resonates with my own experience building product-led motions that respect the community while establishing clear, sustainable paths to revenue.
We explore the different facets of building and scaling a revenue model at an open-source company. Douglas opens up the GTM playbook at Grafana Labs sharing: I found these principles especially actionable for open source monetization, SaaS pricing, and zero to one B2B marketing.
“When to commercialize a feature vs. switch to a hosted version of a product” — In practice, I look for telltale signals: features that impose heavy operational burden (security, scale, multi-tenant reliability), generate significant infrastructure or support costs, or require advanced governance. That’s when a hosted version can deliver outsized value. For individual features inside the core, I favor commercialization only when the value metric is unambiguous and the user experience remains seamless for the community. The key is a clear migration path from self-managed to hosted, with pricing aligned to usage or outcomes.
“Tried and tested frameworks for pricing and packaging” — I anchor on a few staples: value metrics that correlate with customer outcomes, willingness-to-pay testing, and the 3C lens (customer, competition, company). For packaging, a tiered “good/better/best” model helps segment needs, while usage-based or consumption pricing can unlock elasticity for developer-led adoption. I’ve seen price fences (SSO, RBAC, advanced analytics, scale limits) work well when they map to enterprise readiness rather than core functionality.
“How Grafana Labs thinks about what to put behind a paywall” — I share the same philosophy: keep community-loved, foundational capabilities open to preserve trust and growth, and place enterprise-grade scale, compliance, and governance behind the paywall. This often includes SSO/SAML, audit logs, granular access controls, advanced alerting, longer retention, and premium SLAs. The litmus test is whether the paywalled capability primarily serves larger teams’ risk, reliability, and control requirements.
“How the GTM team was built over time” — The sequencing matters. Early on, lean into product-led growth with strong developer evangelism, documentation, and onboarding. As adoption accelerates, add sales-assist, solutions engineering, and forward deployed engineers to convert complex use cases. Over time, layer in customer success, pricing operations, and ecosystem partnerships. Hiring profiles evolve from generalists to specialists, but the connective tissue remains a tight loop between product, community, and revenue.
Throughout our discussion, I appreciated the rigor in tying pricing and packaging decisions to measurable value, while safeguarding the open-core experience. That balance is the difference between short-term monetization and durable category leadership in observability.
You can follow Douglas on Twitter at @douglashanna.
If you’re building or scaling an open-source business, these GTM patterns provide a pragmatic blueprint: lead with community, monetize enterprise needs, and align pricing to real-world usage. It’s a playbook that rewards trust, clarity, and iteration — and it’s one I’ve seen drive repeatable growth when executed with discipline.
I recently sat down with Kesava Kirupa Dinakaran, co-founder and CEO of Luminai, a B2B software tool that helps automate any manual process down to just one click. Coming from years of product leadership, I was immediately drawn to how a seemingly simple promise — one click — can reframe entire operating models and unlock product-market fit in B2B SaaS.
Dinakaran’s path into building software products is anything but conventional. A former Rubik’s Cube champion and back-to-back Hackathon winner, he brings a competitor’s precision and a builder’s curiosity to the craft. The founders stumbled on the idea for its automated “one-click” product by accident, at a corporate hackathon — the kind of serendipity I’ve seen repeatedly catalyze category-defining products when teams are close to customers and willing to ship fast.
Formerly called Digital Brain, Luminai is a Series A startup that’s raised nearly $20 million since its launch out of Y Combinator in 2020. That trajectory underscores a disciplined focus on value creation over vanity features — and the organizational courage to concentrate resources where customers feel the most impact.
In our conversation, we explore the psychology behind the sales process, why sales leaders should consider pitching straight to the CEO and Dinakaran’s decision to scrap hundreds of lines of written code to focus on building out their most beloved customer feature. That decision is a textbook zoom-in pivot — narrowing scope to amplify value — and it’s one of the hardest, yet most effective, moves a product leader can make in the search for product-market fit.
Zooming in is not just about cutting; it’s about conviction. When the data and customer narratives converge on a single, beloved capability, the right move is to double down. My playbook in these moments is simple: validate with qualitative signal (customer pull, urgency, and willingness to pay), quantify usage concentration (feature adoption depth, not breadth), and model the business impact (time-to-value, implementation friction, and sales cycle acceleration). If a feature materially compresses time-to-value and reduces change management, it deserves roadmap primacy.
We also dug into the psychology behind enterprise sales and why sales leaders should consider pitching straight to the CEO. In founder-led GTM, this tactic creates a high-bandwidth feedback loop: the economic buyer frames outcomes, we test narrative-market fit in real time, and we avoid the trap of selling “capabilities” instead of transformational results. In my experience, early alignment with the CEO sharpens qualification, shortens cycles, and forces clarity on the business case.
On the surface, Luminai may seem like just another B2B SaaS startup, but with nearly half the team comprising of former founders (seven of which are ex-YC founders), Luminai is a true example of how the co-founders can really make their mark on shaping their company on the path to product-market fit. That founder density matters — it accelerates product discovery, normalizes rapid iteration, and builds organizational muscle for decisive pivots like the zoom-in. The result is a culture that prizes customer outcomes over internal preferences.
My takeaway for product leaders: don’t wait for perfect certainty. If a single feature repeatedly earns love, compresses onboarding, and closes deals, earn the right to focus — even if it means scrapping code and saying no to adjacent asks. Pair that focus with founder-led GTM, pitch the true economic buyer, and measure success by outcomes, not output. That’s how teams move from zero to one in B2B and create durable, defensible product-market fit.
The leap from individual contributor to manager looks straightforward on paper, yet it’s one of the trickiest transitions I’ve seen in high-growth environments. In my role at HighLevel, I’ve watched brilliant engineers stumble when the job changes from building the product to building the people who build the product. The difference isn’t incremental—it’s a complete shift in identity, incentives, and daily habits.
Most startups get it wrong because they promote for technical excellence and throughput, then keep the new manager doing their old job with “a little people stuff on the side.” That’s a recipe for burnout and underperformance. The first principle is simple: management is a different job. Success is no longer measured by your code, but by your team’s clarity, velocity, and outcomes.
Set expectations and goals with precision on day one. I establish a clear role charter, spell out decision rights, and align to outcomes vs output OKRs so the new manager understands what “great” looks like. We define a 30/60/90 plan that includes team health metrics, delivery goals, and collaboration routines with product and design. The aim isn’t to ship more tickets—it’s to reliably ship the right outcomes.
To turbocharge a team’s effectiveness, I focus on operating cadence and flow. That means crisp intake, visible priorities, lean WIP, tight feedback loops, and regular retros that drive real change. I remove systemic blockers, protect focus time, and make psychological safety a non-negotiable. When people feel safe, they surface risks early, challenge assumptions, and accelerate learning.
High-impact feedback is fast, frequent, kind, and specific. I coach managers to use situation–behavior–impact, to separate people from problems, and to balance reinforcing and redirecting feedback. Written summaries after key conversations prevent drift, while short feedback cycles create compounding growth. Recognition is not an afterthought—it’s a performance tool.
Going from peer to manager requires an explicit reset. I encourage managers to communicate the new expectations, re-establish boundaries, and commit to fairness over familiarity. This includes confidential 1:1s, transparent decision-making, and a clear stance on performance bars. Trust grows when people experience consistency, not when they hear platitudes.
Delaying action on low performance is one of the most costly leadership mistakes. It silently taxes your top performers, normalizes mediocrity, and corrodes culture. Diagnose if the issue is skill or will, offer targeted support with time-bound milestones, and be decisive. Managing someone out can be both humane and necessary—clarity and dignity can coexist.
For first-time managers, I use a simple playbook. In the first 30 days, run a listening tour and baseline the team’s delivery, quality, and morale. By day 60, implement the new operating cadence, align on outcomes vs output OKRs, and tighten cross-functional rituals. By day 90, complete career conversations, calibrate performance, and publish a team charter that codifies how you plan, build, and learn.
The throughline in all of this is ownership: own the outcomes, the culture, and the system. When you make the mindset shift from doing the work to enabling the work, you’ll find that the manager role is not a detour from impact—it’s a force multiplier. With clear expectations, disciplined execution, and courageous feedback, you’ll transform a promotion into a platform for sustained, compounding results.
Expanding from a single hero product to a resilient multi‑product portfolio is one of the most consequential moves a SaaS company can make. I’ve navigated this shift firsthand and studied how leaders approached it at companies like Stripe and Watershed. What follows is the playbook I use to assess new product ideas, structure teams for 0‑1 execution, and run rigorous product reviews without losing momentum on the core business.
I start by clarifying the type of multi‑product strategy we’re pursuing. Are we building adjacent features that deepen adoption, launching true net‑new products for new buyers, extending a platform with new primitives, or assembling a bundle that compounds customer value? That choice dictates everything else—resource allocation, hiring profiles, team topology, and the shape of our product discovery.
Stories from Stripe’s multi‑product success reinforce a principle I believe deeply: launch with small, high‑trust teams and a brutally clear problem statement, then iterate fast with real customers. When adding products like Stripe Billing and Stripe Treasury, the work required not only great execution but also adapting to new buyer profiles and purchasing motions. The lesson I apply is simple—don’t assume the new buyer is just a variant of the old one.
Resource allocation is where strategy meets courage. I protect the core product’s roadmap while ring‑fencing a few exceptional builders to pursue secondary bets. These squads operate with clear, outcome‑based goals and tight feedback loops, not sprawling OKR spreadsheets. The aim is to make small, reversible bets at first, then scale conviction with evidence—market pull, repeatable use cases, and early revenue signals.
Team structure matters even more than headcount. I form new‑product squads that behave like a startup within the company—full‑stack ownership, minimal dependencies, and direct access to customers. The early team must combine product discovery instincts with the ability to ship. Great early‑stage product thinkers show crisp problem framing, a bias for learning, and the humility to change course. One common fail‑case I watch for is hiring purely for potential over demonstrated ability to drive ambiguous work from zero to one.
Hiring the right people for 0‑1 work is its own craft. I look for signals of self‑direction, obsession with customer outcomes, and the ability to reason from first principles under uncertainty. I use five interview questions to unearth hidden talent among product candidates, all designed to reveal how they validate problems, reduce scope intelligently, earn trust with engineers, and handle the uncomfortable middle of product discovery.
Even the best teams stumble when product, packaging, and go‑to‑market are misaligned. I’ve seen what happens when an organization assumes the existing buyer will adopt the new product in the same way—pricing misses the mark, activation drops, and sales enablement lags. The fix is to revisit the buyer, refine the value proposition, and rebuild the path to value so the first‑run experience matches the new buying journey.
To keep new bets honest, I treat them with “definite optimism”—a clear, written view of what success looks like and a pragmatic path to get there. I focus on the sequence of proof: problem validation, consistent user pull, and evidence of repeatable adoption. In a new or early market, I combine a methodical approach (milestones, stages of validation) with analytical rigor (leading indicators, customer expansion patterns) to decide which products to prioritize and when to scale.
Goal‑setting for new products must be measurable yet forgiving of discovery. I favor outcome‑centric checkpoints over vanity metrics, and I evaluate bets by expected learning speed and cost of delay. This keeps us moving fast without confusing activity for progress.
My product reviews are anchored by 12 questions that force clarity on problem, user, value, and risk. I often share these questions as a pre‑read so teams can self‑diagnose and come in focused on decisions rather than updates. “The Enterprise Rent‑A‑Car Story” is a helpful reminder for me that distribution and execution are as decisive as the product idea itself. When building for net‑new‑customers, I re‑focus the questions on buyer change, activation friction, and early‑life cycle signals.
User feedback is the lifeblood of 0‑1. I collect inputs across interviews, product analytics, and support tickets, but I interpret them through the lens of the problem statement rather than raw feature requests. Product development must start with problem validation; otherwise, speed becomes a liability and discovery masquerades as delivery.
I also learn from builders who think in systems and act with urgency. Jack Dorsey: https://twitter.com/jack. Patrick Collison: https://twitter.com/patrickc. Shreyas Doshi: https://twitter.com/shreyas. Their public writing on product strategy, execution, and outcomes vs output informs how I evaluate talent, decide what not to build, and keep teams aligned as we scale beyond one product.
I’ve spent enough cycles scaling product organizations to know that leaders grow—or their companies stall. In this reflection, I distill the practices I rely on to scale an org, develop myself, and raise the performance ceiling across teams, especially when the economic environment demands sharper focus and better decisions.
To ground this discussion, I often point leaders to exemplary people-first operators. Jack Altman is the co-founder and CEO of Lattice, a people success platform for building engaged, high-performing teams. Lattice has raised over $330M, and was last valued at $3B. His work on culture and performance—captured in “People Strategy”—reinforces many of the principles I use daily.
I start with self-awareness because it’s the keystone. If I can’t see my own patterns—when I’m avoiding conflict, over-controlling, or confusing activity with outcomes—everything else degrades. I cultivate self-awareness by writing brutally honest weekly retros, asking my staff for one piece of constructive feedback every month, and running periodic 360s to reveal blind spots. The goal isn’t comfort; it’s truth. When I improve my signal on reality, my decisions get faster and my team gains confidence.
Difficult conversations are a gift to performance. I’ve learned to tackle them quickly, with empathy and specificity. I name the gap between expectation and outcome, share observable examples, state the impact on the team, and propose a clear path forward with timelines. If emotions run hot, I slow down, seek to understand, and stay on the behavior and results—not the person. Avoidance compounds culture debt; candor repays it with interest.
Scaling a company introduces predictable failure modes. I’ve seen leaders confuse hiring errors with management errors; it matters which you’re facing. A hiring error shows up as persistent gaps in role fundamentals even after clear expectations, coaching, and time-bound support. A management error usually stems from ambiguous goals, poor context, or inadequate resources. I assume management error first and fix the environment. If results still lag, I revisit the hire.
Delegation versus control is a healthy tension. Early, I’ll “micro-mentor” on critical work to teach quality, taste, and judgment—then expand autonomy as pattern recognition develops. My rule: delegate outcomes, keep ownership of standards and context. I never give up the responsibility to set the bar for the team and to protect the product vision; those are one-way doors that define the company’s trajectory.
Building a product organization that compounds requires clarity and context. I ensure every product trio understands the strategy, customer segments, and constraints. We anchor on outcomes vs output OKRs, maintain a living strategy doc, and write decision memos that document trade-offs. When context flows, people need fewer approvals and produce better work, faster.
On so-called micro-management, here’s my take: it’s a tool, not an identity. Early in a function or with a new leader, I may be intentionally hands-on to transfer judgment. The moment competence and trust are proven, I deliberately pull back. The mistake isn’t micro-managing; it’s forgetting to stop.
CEO-level context setting is non-negotiable. I articulate the narrative behind the plan—the why, the constraints, the risks, and what we’re not doing. Transparency isn’t oversharing; it’s sharing the right information at the right fidelity so people can make aligned decisions. I model this with written updates, open Q&A, and by explaining how major calls were made.
Some of the most valuable leadership work happens in uncomfortable conversations. I prepare by drafting the core message, testing it for clarity and fairness, and deciding what success looks like for the person and for the business. I also own the decision. When the stakes are high, I don’t outsource the final call or feedback to a proxy; accountability builds trust.
Speed versus accuracy in decision-making is situational. For reversible bets, I bias to speed, time-box the experiment, and set clear kill criteria. For one-way doors, I slow down, increase the sample of perspectives, and pressure-test assumptions. I counter hidden biases in group discussions by starting with silent written proposals and independent scoring before we debate out loud.
I’ve even experimented with removing myself from recurring meetings for a cycle. The outcome: decisions kept moving, and I learned where my presence added value versus created drag. Now I show up intentionally—for feedback on taste, to unblock cross-functional issues, or to deliver context—then get out of the way.
Here are four practices that consistently pay off for me: protect deep work blocks for strategic writing, conduct weekly customer calls, review hiring quality monthly, and keep a running list of hard problems only I can solve. This keeps me oriented toward leverage, not busyness.
Talking to customers is an art. I avoid solution-leading questions and ask about current workflows, pains, and the last time the problem showed up. I go five whys deep, quantify the value of a better outcome, and listen for language customers use to describe success. The best product discovery lives in those unpolished details.
Great leaders are constant learners. I rotate through books, operator peer groups, product management leadership communities, and curated newsletters. I also treat my own organization as a learning system—post-mortems, pre-mortems, and lightweight experiments build institutional knowledge faster than any single playbook.
To maximize employee performance, I use a simple model: Clarity x Capability x Motivation x Environment. Clarity means crisp expectations and definitions of done. Capability is skills and experience, which I grow via coaching and targeted practice. Motivation blends purpose, recognition, and meaningful goals. Environment covers tools, psychological safety, and focus time. If any factor is near zero, performance collapses; my job is to diagnose and raise the lowest one.
When long-time employees stop scaling with the company, I address it early. Sometimes a role redesign or releveling unlocks success. Other times, a dignified, well-supported transition is the right call for everyone. Avoiding the issue erodes trust; handling it with clarity and care strengthens culture.
Low-performing but well-liked employees create a leadership test. I separate likability from impact. If values are strong but performance lags, I set a time-bound plan with clear checkpoints. If progress doesn’t materialize, I act. Keeping someone in a role they’re not meeting hurts the team and the individual by delaying a better fit.
When someone is let go, I’m thoughtful about what to share. I communicate the change promptly, state the role-level rationale without gossip, thank the person for their contributions, and reinforce the plan going forward. The aim is to honor privacy while maintaining clarity about standards.
In today’s tougher macro environment, I refocus on capital efficiency, ROI-driven roadmaps, and slower, more deliberate hiring. I raise the bar for product bets, validate earlier with customers, and price for value. Constraints, when embraced, sharpen strategy and execution.
Aligning career goals with company goals is ongoing work. I use growth frameworks, individual development plans, and quarterly conversations that link business outcomes to skill-building. When people see a path to mastery and impact, performance accelerates.
Most leaders underestimate their team’s potential. I raise expectations with ambitious, outcome-based goals, ensure people have the context to operate like owners, and celebrate learning velocity as much as wins. When standards, support, and trust rise together, teams routinely outperform even optimistic forecasts.
I get asked constantly how I decide when to trust my gut, when to lean on data, and when to take a big swing versus iterate. As a product leader, my answer has been shaped by hard-won lessons building B2B SaaS, product-led funnels, and enterprise features. Recently, I revisited Slack’s approach to decision-making, product reviews, and balancing product-led vs sales-led growth—and distilled a set of practices I use with my teams today.
Noah Desai Weiss is the Chief Product Officer of Slack, and has an accomplished track record inside and outside of the company. He started Slack’s Search, Learning, and Intelligence division, led the Self-Service (SMB) Business, and led the Expansion and Virtual HQ product areas (responsible for Huddles, Clips, and more). Before joining Slack, Noah was the SVP of Product Management at Foursquare (raised over $390m), and was a Product Manager at Google.
The throughline for me starts with a simple truth: not all decisions should be data-driven. Early in a product’s life—or when exploring a novel experience—data is often either unavailable or misleading. That’s where intuition, taste, and judgment come in. I treat intuition as a hypothesis generator and momentum maker, then instrument quickly to validate direction. This blend of “When to use intuition vs data to drive decisions” has saved me from overfitting to small datasets and from analysis paralysis when speed was the real advantage.
I’ve learned that “Taste and judgment are learnable.” You can coach it. Review artifacts together. Run side-by-side comparisons of design explorations. Write down what “good” looks like and why. My teams keep a living gallery of exemplary UX patterns and empty-state copy that exemplifies our bar. Over time, this scales the craft of intuition across a larger org—just as “How Slack scales intuition across their product org” suggests.
Of course, there are “Challenges of intuition-led product building.” The biggest are founder or leader overreach and survivorship bias. I mitigate this with timeboxed discovery: we commit to a clear decision date, capture our priors in writing, and express our confidence as a range rather than a point estimate. This sets up a healthy dynamic for “Managing pace vs accuracy in decision-making.” We move fast when reversibility is high, we move slower when the blast radius is large.
Matching people to the work matters too. Some product problems are inherently ambiguous and benefit from researchers, designers, and PMs who derive energy from the unknown. Others are best led by optimization-oriented builders who light up when the metric moves. I’m explicit about “Matching people to data vs intuition-driven work,” and I rotate folks so they can build both muscles.
In remote and hybrid environments, I’ve found the most underrated traits are proactive context-sharing, crisp written communication, and the ability to create signal in Slack and docs. “Underrated qualities for remote workers” aren’t just stylistic preferences—they are execution speed ups. I look for people who make everyone around them smarter asynchronously.
On product process, I’m inspired by “How Slack runs product reviews.” My rubric: one problem statement, a tight narrative memo, the bet framing (assumptions, risks, kill criteria), and outcomes tied to “outcomes vs output OKRs.” We align on the decision owner, consent vs consensus, and the next irreversible checkpoint. This keeps reviews from becoming theater and pushes decisions to the right altitude.
Culture shows up in small moments. “The importance of a team’s ‘vibe’” is tangible: Do we demo early? Do we celebrate learned negatives as much as wins? Do engineers, designers, and PMs feel joint ownership of the experience, not just their function’s slice? When the vibe is right, latency from idea to insight collapses—and that compounding is everything in product discovery.
Portfolio balance matters. I aim for a mix that lets us keep shipping customer-visible improvements while reserving room for breakthroughs. “Balancing “big swings” with incremental improvements” requires explicit ring-fencing: 70/20/10 works well for many orgs. Big swings get stage gates and PR/FAQ-like artifacts; incremental bets get weekly ship cadence and tight measurement. When we miss, we run pre-mortems and decision journals, reinforcing “Rituals for good decision-making.”
Go-to-market is where strategy meets friction. My guidance on “Advice on product-led vs sales-led growth” is to design the handshake up front. Let product-led growth do the land—self-serve activation, collaborative aha, bottoms-up virality—and let sales-led growth do the expand—security, compliance, procurement, multi-workspace governance. Instrument the handoffs, define eligibility heuristics, and ensure pricing doesn’t punish adoption. This is also where “Which products should focus on end-users versus executives” gets real; optimize early journeys for end-user success while giving executives the portfolio-level control and analytics they require.
I’m continually impressed by “What Slack learns from Salesforce.” Enterprise trust, admin controls, and scalable GTM motions can coexist with consumer-grade product craft. That hybrid DNA is powerful. I’ve adopted similar patterns: build for end-user joy, layer enterprise-grade controls, and price to match value realization, not procurement theatrics.
Speaking of pricing, “Pricing lessons from Salesforce and Marc Andreessen” pushed me to keep pricing simple enough for PLG while being flexible enough for enterprise. Seat-based pricing remains intuitive for collaboration products, but usage and “SaaS pricing” add-ons can map value to heavy features without overcrowding your price page. The key is to test willingness to pay early, avoid grandfathering yourself into a corner, and treat packaging changes like product changes—with discovery, rollout plans, and success metrics.
Humility isn’t fluffy—it’s an execution advantage. “Slack’s humility and why it matters” resonates with how I try to lead: ruthlessly honest about what we don’t know, eager to learn from customers quickly, and unafraid to reverse course when the evidence changes. That humility turns into speed because we stop defending past decisions and start iterating toward truth.
When working with a strong product voice at the top, “How to build product with a product-focussed founder” comes down to mutually agreed principles. Capture the founder’s taste in explicit heuristics, define the moments where their judgment should overrule the process, and codify how dissent and disagree-and-commit work in practice. This protects clarity without stifling creativity.
Here are the topics I unpacked and continue to apply across teams: “When to use intuition vs data to drive decisions,” “The most underrated traits in a remote work environment,” “How Slack runs product reviews,” “The importance of a team’s ‘vibe’,” “Managing pace vs accuracy in decision-making,” “Balancing “big swings” with incremental improvements,” and “Advice on product-led vs sales-led growth.” Each one is a lever that compounds when used together.
Curious to learn more about Slack? You can try Slack Pro and get 50% off using this link.
I’m always looking for crisp, scalable ways to drive product strategy, organizational alignment, and cross-functional performance that actually ship outcomes. Studying Loom’s operating system—and the career arc behind it—offered a masterclass worth sharing. Anique Drumright is the COO at Loom, a video communication tool for streamlining workflows. Loom has raised over $200M, and was last valued at $1.5B. Anique has a proven track record across product development, executive leadership, and building high-performing organizations. Before joining Loom, Anique was the VP of Product at TripActions, where she scaled the team over 8x globally, and she has also held multiple roles at Uber.
In this breakdown, I dig into best-practice product management, how to achieve alignment at scale, the mechanics of cross-functional performance, Anique’s approach to finding top organizational talent, how to hire for roles outside your area of expertise, the most common fail cases with internal and external recruitment, and the specific interview tactics that actually surface the truth.
One theme I return to often is the transition from product management to executive leadership. As a PM, I optimize for customer insight, prioritization, and execution velocity. As an exec, I optimize for clarity, systems, and sustained energy across teams. The job shifts from owning a roadmap to owning the conditions under which many roadmaps thrive—organizing for outcomes, setting non-negotiable standards, and removing ambiguity.
Storytelling sits at the center of launch excellence. I love how Loom anchors launches in a human narrative: define the painful “before,” demonstrate the transformative “after,” and spotlight one memorable capability that makes the switch inevitable. I pair this with a crisp narrative memo, a demo-first internal review, and a simple, outcome-oriented success metric—so product, marketing, and sales sing the same chorus.
Managing cross-functional scope and performance requires ruthless role clarity and shared measures of success. I align on a single definition of the customer problem, agree on leading indicators we can move now, and assign one DRI per decision. When we use outcomes vs output OKRs, we unlock better trade-offs: fewer features shipped, more customer problems solved.
Organizational alignment is both essential and fragile. What looks like misalignment is usually mismatched time horizons, unclear ownership, or different definitions of success. The antidote is explicit agreements: who decides, how we decide, and what “good” looks like this quarter. When in doubt, I over-communicate context, not tasks.
I’ve seen at scale—Uber is a notable example—that alignment travels fastest through shared rituals, not longer documents. Weekly business reviews, lightweight decision logs, and a common operating cadence create a heartbeat the org can follow. The point isn’t ceremony; it’s repeatable clarity.
My go-to alignment rituals are simple. A Monday priorities memo sets the narrative and the week’s must-win outcomes. Midweek, a cross-functional stand-up surfaces risks and unblocks dependencies. Friday, we close the loop with a red-yellow-green on outcomes and a short retro on decisions—not just results—so we compound learning.
One-on-ones are performance multipliers when they’re designed well. My winning format: start with energy and focus (what’s giving or draining energy), review outcomes not activity, walk a single thorny decision to closure, and end with explicit asks in both directions. Over time, this builds trust and speed.
When and how to help functional leaders matters. I jump in when a decision is high-impact and ambiguous, when speed has stalled, or when the problem crosses multiple functions. Otherwise, I coach on principles and expect leaders to own the path. If I’m often in the weeds, we have a structure or talent gap—not a diligence problem.
Hiring outside my domain expertise starts with outcomes, not resumes. I write the first-90-day outcomes, name the decisions the role must own, and recruit with a structured case that mirrors the real job. I bring in a domain advisor to probe depth and run a work-sample test to reduce false positives from polished storytellers.
For senior leaders, my favorite interview questions are simple and hard to fake: Tell me about the last time you changed your mind on a critical decision—what evidence moved you? Walk me through your operating cadence—meetings, artifacts, and decisions—in a typical month. Describe your hardest cross-functional miss and the system you changed to prevent a repeat. The specificity of answers reveals the operator from the commentator.
I adjust the hiring process when I’m outside my depth: heavier emphasis on work samples, more structured rubrics, a domain expert panel, and reference checks that test for actual outcomes. When the role is pivotal, I’ll run a paid trial project with clear guardrails; reality is the best filter.
Common patterns of failed external hires: they manage optics over outcomes, never rewire the system, and don’t create leaders beneath them. Failed internal promotions often show up as scope growing faster than judgment, a reluctance to reset standards with former peers, or success limited to a familiar domain. Avoid over-promotion by decoupling recognition from scope; celebrate excellence without inflating title or span prematurely.
To get honest answers in interviews, I normalize candor and ask for receipts. I request artifacts—planning docs, dashboards, postmortems—and I probe for the counterfactual: what would you do differently if you had to do it again? In reference checks, I ask for moments of truth: the hardest feedback you gave them, a decision you disagreed with and how they handled it, and the exact conditions under which you would rehire them tomorrow.
Sustaining energy is an executive’s quiet superpower. I watch team energy levels as closely as metrics. What inspires people in a company is progress they can feel, standards that mean something, and leaders who tell the truth. If we keep those three alive, performance follows.
A month in the life of a COO (and frankly any executive operator) is a portfolio: setting the narrative and outcomes, running the operating cadence, calibrating talent, and clearing systemic blockers. The best leadership dynamics work because roles are explicit, trust is earned through delivery, and debates resolve into single-threaded ownership—not committee compromises.
Resources for further exploration: Loom (https://www.loom.com/), Navan (formerly TripActions): https://navan.com/, Teach for America: https://www.teachforamerica.org/, Uber: https://www.uber.com/.
Timestamps I mapped my notes to for quick scanning: [00:03:00] similarities and differences between PM and executive leadership roles; [00:06:53] storytelling in launches; [00:10:01] cross-functional scope and performance; [00:13:41] goal-setting with functional leads; [00:16:59] organizational alignment; [00:20:40] alignment at scale; [00:24:06] alignment rituals; [00:25:23] one-on-one format; [00:27:49] supporting functional leads; [00:29:13] hiring outside your expertise; [00:32:55] interview questions; [00:33:55] adapting the hiring process; [00:36:09] failed external hires; [00:37:40] failed internal hires; [00:39:05] avoiding over-promotion; [00:40:51] inspiration; [00:45:40] getting honest answers; [00:47:12] reference checks; [00:51:29] a month in the life of a COO; [00:52:52] energy levels; [00:54:53] leadership dynamics; [00:57:30] outsized career influences.
Early-stage B2B marketing is where momentum is made or lost. In my product leadership work, I’ve seen that getting from zero to one requires uncommon focus, founder-led GTM discipline, and a tight feedback loop between product, sales, and marketing. In this narrative, I share the playbook I use—and the patterns I took from top operators—to help SaaS teams build credibility fast, compound learnings, and scale repeatable growth.
Alex Kracov is the CEO and Co-Founder at Dock, and the former VP of Marketing at Lattice. Alex joined Lattice as the first marketer and third employee, and he helped to grow the business from seed to 1850+ customers. Prior to Lattice, Alex was a consultant at Blue State Digital — the team that elected President Obama and orchestrated projects at Google. Since leaving Lattice in 2021, Alex co-founded Dock, a B2B platform that has streamlined the customer buying experience for clients like Loom, Origin, and Instabug.
Here’s the agenda I use to guide founders and early marketing leaders: the 2023 SaaS marketing playbook; how to start your early-stage B2B marketing; how to prioritize resources across multiple marketing bets; how to think about attribution; Lattice’s unorthodox million-dollar marketing campaign; how to hire for early marketing roles; what makes a standout marketer; and advice for building your first website.
When I spin up early-stage B2B marketing, I start by defining the shortest path to signal. That means a crisp ICP, problem-first messaging, and one or two channels where our buyers already congregate. At this stage, I bias toward founder-led discovery calls, live product walkthroughs, and tight content that proves outcomes—not features. This creates the raw material for positioning, case studies, and a credible top-of-funnel narrative.
Short-term versus long-term goals must be explicitly balanced. I set near-term pipeline and learning targets (e.g., qualified conversations per week, time-to-insight from experiments) alongside long-term brand assets (evergreen content, customer proof, category POV). The rule of thumb I apply: stabilize one growth motion before layering the next, so we don’t overfit to noise or dilute the message.
Allocating resources across marketing bets is a portfolio problem. I structure it as 70/20/10: 70% on the core motion that’s already working, 20% on adjacent bets with clear hypotheses, and 10% on contrarian experiments that could unlock step-change distribution. Weekly syntheses convert experiment data into decisions—double down, redesign, or retire.
On attribution, I’m pragmatic. Early on, precision is less valuable than directionality. I pair multi-touch analytics with qualitative inputs (self-reported attribution, sales notes, community signals). The question I ask: which narratives and channels consistently show up in won deals? That blend avoids over-crediting the last click and keeps us honest about how trust is actually formed in B2B.
Your first website is a conversion engine and a trust anchor. The first thing people should see on your website is the problem you solve, the outcomes you deliver, and a frictionless way to see the product in action. I recommend a tight hero message, social proof above the fold, a short demo video or interactive experience, and clear CTAs for both buyers who are ready now and those who need to explore.
Brand and positioning mature with evidence. I translate discovery insights into a simple hierarchy: category, problem, unique insight, product proof, outcomes. At Lattice, strong brand clarity met operational excellence; at Dock, product-led collaboration sells the value by making the buying experience itself the demo. In both cases, the lesson stands: great B2B brands tell a truth buyers can quickly verify.
Bold bets can be force multipliers. Lattice’s unorthodox million-dollar marketing campaign underscores a principle I use sparingly but decisively: when the narrative, timing, and distribution are aligned, a high-conviction investment can set the agenda for your category. The bar is high. The insight must be non-obvious, the creative durable, and the measurement plan rigorous.
Hiring for early marketing roles, I optimize for learning velocity, narrative craft, and cross-functional empathy. The ideal first marketer is a full-stack generalist who can research, write, ship, analyze, and partner with sales and product. Experience matters, but potential—ownership, curiosity, systems thinking—often outperforms. I scale the team once one motion is repeatable and there’s a clear backlog of work we can’t tackle without specialization.
Conferences and communities are underrated if used deliberately. I set specific objectives (target accounts, partners, customer content) and treat events as field research and content engines. Every conversation informs messaging; every meeting has a next step; every session becomes a clip, post, or asset. The outcome is pipeline plus reusable proof.
My 2023 SaaS marketing stack emphasizes speed to insight: product analytics to observe behavior; a CRM and marketing automation platform to orchestrate journeys; lightweight data pipelines for attribution; a CMS for shipping content fast; and collaboration tools that put buyers and sellers in the same workspace. What matters most is not the logo set—it’s the operating cadence that converts data into action.
If you’re going from zero to one, keep it simple: validate your ICP, ship a compelling narrative, pick one channel to master, and measure what buyers say and do. Sequence beats scope. Credibility compounds. And the best marketing is a mirror of a product that solves a painful, urgent problem—beautifully.
Timestamps: [00:00:00] Intro [00:02:45] The challenges and opportunities in early-stage B2B marketing [00:05:13] How to think about short-term versus long-term marketing goals [00:07:31] Allocating resources across marketing bets [00:09:13] Signs your marketing is working [00:11:20] The most underutilized marketing strategy [00:13:03] Creating your company’s first website [00:14:22] How Lattice formed its brand messaging and positioning [00:18:22] Dock’s innovative approach to marketing software [00:20:14] The first thing people should see on your website [00:23:10] Lattice’s most successful early-stage marketing tactics [00:28:05] Determining which marketing strategies are still relevant [00:30:25] Lattice’s unorthodox million-dollar marketing campaign [00:33:26] Why Alex had an outsized impact at Lattice [00:37:05] Lessons from his first marketing hires [00:39:41] When to scale your marketing team [00:40:55] Building an effective early-stage marketing team [00:42:30] A tough conversation with the CEO & Co-founder of Lattice [00:44:46] Achieving early-stage marketing alignment [00:46:20] Transitioning from employee to entrepreneur [00:49:19] Getting the most out of conferences [00:50:47] Selecting marketing channels in the early stages [00:52:44] Hiring marketers for experience versus potential [00:56:34] The 2023 SaaS marketing stack [00:58:19] Advice for Zero to One marketing [00:60:46] What successful B2B marketing looks like
