Author: Shivam Tiwari

From Bootstrapped to $6B: Inside 1Password’s B2B Pivot, GTM Engine, and CEO Playbook

I’m endlessly fascinated by companies that scale with discipline, humility, and a relentless focus on customer trust. 1Password’s arc checks every box. Used by over 100,000 businesses and millions of individuals worldwide, it’s a rare story of going from a small, family-run operation to a $6B company without losing the plot. As I dug into this journey, I found a masterclass in product management leadership, intentional go-to-market sequencing, and the hard choices required to balance security with usability.

Here’s the quick snapshot that framed my takeaways: Jeff Shiner joined 1Password as CEO in 2012, when the team was just under 20 people. Under Jeff’s leadership, 1Password expanded into B2B, launched a SaaS platform, and scaled from a small family-run operation into a global company. In 2019, Jeff led 1Password through its first-ever funding round – a $200M Series A from Accel – to build out its go-to-market team and accelerate product development. Before joining 1Password, Jeff held senior roles at IBM and led teams through multiple acquisitions and integrations. That resume matters; it shows up in the way the company navigated pivotal transitions without spinning out.

The first lesson that landed for me: bootstrapping isn’t always what it’s cracked up to be. Staying bootstrapped for 15 years created incredible product discipline and customer-centricity, but there was an opportunity cost in go-to-market velocity. The decision to raise a $200M Series A from Accel in 2019 wasn’t about vanity—it was a surgical call to build the commercial muscle and accelerate product development at the moment the category was tipping. I’ve seen similar inflection points in my own work: the right capital, at the right time, can turn a strong product into a dominant platform.

The consumer-to-B2B pivot is the second big lesson. The lightbulb moment was recognizing team adoption patterns and the unmet enterprise needs around provisioning, policy, and audit. That shift required more than features; it demanded a reframe of the product roadmap, with crisp outcomes over output across security, UX, and administration. This is product discovery 101 at scale—listen for systemic patterns in user behavior, then align the organization on the few bets that unlock product-market fit in the new segment.

One of my favorite strategic choices was launching the SaaS platform before billing. It sounds counterintuitive, but it worked because it prioritized trust and usage over immediate monetization. By validating real-world adoption first, the team bought itself the context to introduce pricing and metering that mapped to customer value. When we’ve run similar plays, I’ve found the keys are transparent communication, clean migration paths, and a metrics spine that ties engagement to eventual revenue.

Security is the brand. But “being too secure” can kill usability—and adoption. I appreciated how candidly the team confronted this. Over-indexing on friction (even for good reasons) can block activation, expansion, and the very outcomes security teams care about. The craft is in reducing cognitive load while preserving principled guardrails. It’s a practical reminder that the best security UX eliminates unnecessary choices and defaults to safety without making people feel punished for doing the right thing.

There’s also a leadership chapter I found especially human: becoming CEO without telling anyone. Titles aside, the work was about creating alignment—clarifying purpose, simplifying decision rights, and protecting a culture that had been forged by builders like David Teare, Sara Teare, Roustem Karimov, and Natalia Karimov. In my experience, this is where outcomes vs output OKRs pay off: they force teams to anchor on the customer result, not the feature list, which becomes crucial as the org scales across B2C and B2B motions.

On go-to-market, the sequencing was clean: invest deliberately across sales, marketing, and customer success to support the B2B motion while keeping a strong consumer brand. The thread through all of it was customer-centric focus at scale. One tactic I advocate to preserve that focus is to embed product and engineering tightly with the field—think forward deployed engineers for high-signal accounts—so the roadmap stays tethered to real-world constraints, not just internal narratives.

Competitors matter, but the posture matters more. I liked how Jeff framed it: know the market, including players like LastPass, but don’t let competition dictate the roadmap. Use it as a directional signal, not an existential script. The companies that win don’t chase parity; they compound differentiated value and limit context switching for customers.

Not every bet landed. The first B2B product failed. That failure, and the iteration that followed, is precisely how strong product cultures are built. You tighten the feedback loops, double down on product discovery, and refine the jobs-to-be-done until adoption becomes the leading indicator. What stood out is how those learnings later informed the most pivotal moments in the company’s climb.

If you want to trace the journey end to end, there are a few sections I flagged for a deeper listen and reflection: how Jeff got involved at 0:03, the consumer-to-B2B pivot at 16:13, the first B2B product failure at 30:40, the funding decision after 15 years bootstrapped at 52:45, and a candid look at the most pivotal moments at 1:02:00.

Referenced for context and further exploration: 1Password: https://1password.com, Accel: https://www.accel.com, Arun Mathew: https://www.linkedin.com/in/arun-mathew-b7186412/, David Teare: https://www.linkedin.com/in/daveteare/, Floodgate: https://floodgate.com, LastPass: https://www.lastpass.com, Mike Maples: https://www.linkedin.com/in/maples/, Natalia Karimov: https://1password.com/company/meet-the-team/natalia-karimov, Roustem Karimov: https://www.linkedin.com/in/roustem/?originalSubdomain=ca, Sara Teare: https://1password.com/company/meet-the-team/sara-teare, Shopify: https://www.shopify.com, Tobi Lütke: https://www.linkedin.com/in/tobiaslutke/.

Where to find Jeff: LinkedIn: https://www.linkedin.com/in/jshiner

My biggest takeaway: this is a blueprint for scaling trust. From “too secure” to just secure enough, from consumer to B2B, from bootstrapped to $200M Series A, the throughline is disciplined learning. For product leaders, the invitation is clear—align the roadmap to outcomes, validate value before billing, and build a go-to-market engine that amplifies customer love rather than distracting from it.

October 20, 2025
How a Weekend Hack Hit 7-Figure ARR: My Product Playbook from Reducto’s Rise

I’m often asked how to spot and scale an AI wedge quickly without over-engineering. Recently, I studied how one founder did exactly that—and it’s a masterclass in product-market fit, go-to-market speed, and customer-centric execution. Adit Abraham is the co-founder and CEO of Reducto, which helps leading AI teams extract and structure data from complex documents and spreadsheets in their pipeline. Within 6 months of launching, Reducto went from 0→7 figures in ARR. Reducto has grown to process tens of millions of pages monthly for companies ranging from startups to Fortune 10 enterprises. They just announced a $24M Series A. Before Reducto, Adit was a Product Manager at Google, working on Ads and Search, and conducted machine learning research at MIT’s Media Lab. Here’s what stood out to me as a product leader: the fastest path to traction wasn’t a grand platform vision—it was a weekend project that nailed one painful, universal job to be done: turn messy PDFs and spreadsheets into structured, reliable data that AI teams can trust. Listening to customers revealed an important pivot. Instead of forcing a preconceived product roadmap, the team followed customer signal to PDF processing. The turning point wasn’t a feature bomb—it was clarity: when your users repeatedly drag you toward a narrow, high-pain workflow, follow that pull with urgency. The weekend project that became Reducto’s breakthrough embodied a principle I push with my teams: ship a thin slice that solves one gnarly, repeatable problem end-to-end. It creates credibility, accelerates learning loops, and makes it obvious what to build next. From there, Reducto focused on “transferable features”—capabilities that compound across adjacent use cases (think normalization, validations, lineage, and auditability), so every new customer increases product surface area without bespoke reinvention. Landing a Fortune 10 customer didn’t come from a flashy deck. It came from enterprise-grade reliability, ruthless attention to accuracy, and a willingness to be hands-on. This is where forward-deployed engineering shines: sit with users, work their real documents, and treat integrations, SLAs, and observability as first-class features. In AI document processing, precision and proof beat promises every time. For technical founders, sales can feel unnatural. My guidance mirrors what worked here: reframe sales as active product discovery at the edge of pain. Use the customer’s language, quantify ROI in minutes saved and errors avoided, and reduce the perceived risk with quick pilots, deterministic evaluation, and transparent quality metrics. Caring beats perfect pitches—responsiveness, iteration speed, and real ownership of results build trust faster than theatrics. The strategy behind Reducto’s horizontal expansion was pragmatic: start with a narrow ingestion problem, then generalize through connectors, schemas, and review workflows that serve multiple industries. When a wedge market behaves like infrastructure, platformize the capabilities that every adjacent use case will need. That’s how you broaden TAM without losing product sharpness. I also appreciate the operating cadence: hire slow, go-to-market fast. Keep the bar high on IC excellence while removing friction from the path to revenue. Early-stage advantage comes from fewer handoffs, shorter feedback loops, and tighter alignment between product, engineering, and customer outcomes. On mindset, one line resonated deeply: “You’re going to fail”. The point isn’t pessimism—it’s preparation. Design processes that surface weak signals early, celebrate invalidated hypotheses, and compress the time between insight and iteration. In my experience, the teams that win treat failure as data and speed as a cultural norm. Fundraising-wise, momentum compounds when narrative and metrics rhyme. 0→7 figures in ARR in six months, tens of millions of pages processed monthly, and a clear enterprise motion make a compelling arc for a $24M Series A. The lesson: sequence your proof points—pain, precision, and production scale—so investors can see inevitability rather than potential. If you’re building in document AI or adjacent data ingestion, study the tooling landscape (Anthropic, Scale AI, Stripe, Textract, Y Combinator) not as competitors but as ecosystem rails. Your goal is reliable transformation from unstructured inputs to structured outputs with measurable quality, strong governance, and smooth downstream integration. I’ll leave you with a practical playbook I use with my teams: Listen for intense pull, not polite praise. Pivot when usage—not opinions—clusters around a painful workflow. Ship a narrow, decisive wedge that solves the full job end-to-end. Measure accuracy, speed, and reliability. Invest early in “transferable features” that travel across verticals—validation, audit trails, observability, and schema tooling. Treat sales as discovery. Quantify ROI, shorten time-to-value, and make evaluation deterministic. Scale with forward-deployed engineering until patterns stabilize. Then platformize. Grow revenue faster than headcount. Hire slow, raise the bar, and keep iteration loops tight. If you want to explore more, start with Reducto (https://reducto.ai/) and connect with Adit on LinkedIn (https://www.linkedin.com/in/aditabraham/). Whether you’re chasing your first customer or your first Fortune 10 logo, the blueprint is the same: focus the wedge, prove precision, and move fast where it matters most.

October 20, 2025
From Skeptic to $2B: The Hard-Won Product Playbook Behind Persona’s Platform

I’m drawn to product stories where skepticism sharpens strategy, and this one delivers. The arc from reluctant founder to a $2B valuation is more than a feel-good headline—it’s a masterclass in platform thinking, principled decision-making, and founder-led execution under pressure. As a product leader, I unpack the choices, inflection points, and habits that turned uncertainty into enduring advantage.

Here’s the snapshot: Rick Song is the co-founder and CEO of Persona, the identity verification platform used by some of the world’s largest companies. Before starting Persona, Rick worked on identity fraud and risk products at Square, which laid the groundwork for what would become Persona’s highly technical, horizontal platform. Since founding the company, Rick has scaled Persona into a category-defining leader, recently raising a $200M Series D at a $2B valuation.

What stands out most to me is how Rick’s skepticism shaped Persona’s early strategy. Rather than chasing hype, he pressure-tested assumptions, constrained scope, and let customer reality—not pitch-deck mythology—pull the roadmap forward. That mindset is foundational when you’re building a true platform company: it forces depth over decoration and compels teams to solve hard, horizontal problems that generalize beyond the first few customers.

The journey begins with “Life before Persona” and “The push from Charles,” followed by “Early reluctance and low expectations.” I’ve been in those rooms—where the idea is simultaneously promising and premature. In that moment, measured doubt is a feature, not a bug. It sharpens your discovery, clarifies hypotheses, and aligns the team around learning velocity rather than vanity milestones.

From there, the real work starts: “Winning the first $50 customer” and the discipline of “Invalidating” Persona. I love this framing; it’s the antidote to confirmation bias. Persona “found their edge” by embracing the unglamorous details of identity, investing in reliability, and resisting the urge to overfit to early signals. When you treat each small win as a constrained experiment, you naturally build antifragility into the product.

The hardest product transition came next: “Transitioning from MVP to platform.” That shift requires you to zoom out from features to primitives, from integrations to orchestration, from point solutions to reusable systems. One defining moment—“Turning down a $5K deal on principle”—shows how clear product tenets safeguard long-term leverage. Pair that with the discipline of “Generalizing bespoke solutions,” and you get a durable platform instead of a services treadmill.

As traction compounds, the focus turns to “Finding product-market fit,” “Founder-led sales and consultative approach,” and “Building a culture of reactivity.” Founder-led selling isn’t just about closing deals—it’s deep discovery at the frontier, where your customers’ edge cases become your platform’s next capabilities. That reactivity, when systematized, accelerates learning loops and helps land “the first enterprise customers” without compromising architectural integrity.

Finally, there’s a mindset layer: “Silicon Valley’s obsession with frameworks” can distract from the harder habit of “Developing first principles thinking.” I’m a fan of frameworks when they’re earned, not borrowed. The right balance is to “Stay competitor-informed” while remaining customer-anchored and principle-driven. In practice, that means monitoring the market, but letting your roadmap be pulled by real-world constraints and outcomes.

For those who want to explore the broader ecosystem referenced along the way, here are a few touchpoints that shaped the conversation and context: Accenture: accenture.com, Anthropic: https://www.anthropic.com/, Braze: https://www.braze.com/, Bridgewater Associates: https://www.bridgewater.com/, Charles Yeh: https://www.linkedin.com/in/charlesyeh/, Christie Kim: https://www.linkedin.com/in/christiekimck/, Clay: clay.com, Kareem Amin: https://www.linkedin.com/in/kareemamin/, MIT: mit.edu, Newfront: newfront.com, Palantir: https://www.palantir.com/, Persona: withpersona.com, Rippling: rippling.com, Scale AI: scale.com, Snowflake: https://www.snowflake.com/, Square: squareup.com, Y Combinator: ycombinator.com, Zachary Van Zant: https://www.linkedin.com/in/zacharyv/.

If you want to follow Rick directly, here’s where to find him: LinkedIn: https://www.linkedin.com/in/rick-song-25198b24/.

October 20, 2025
Persuasive Leadership for Founders: My Take on Wes Kao’s Playbook to Influence and Win

Influence starts with clarity. That’s the throughline I return to when I’m coaching founders and product leaders, and it’s why I keep revisiting the frameworks that sharpen how we communicate, persuade, and lead under pressure. Recently, I synthesized several powerful ideas that map directly to the realities of startup execution and product management leadership—ideas I’ve seen transform how teams align, how roadmaps get prioritized, and how outcomes (not outputs) become the default.

Wes Kao is an executive coach, advisor, and instructor, best known for her newsletter on high-impact communication, and for co-founding course platform Maven and the AltMBA with Seth Godin. Across her career, Wes has helped leaders communicate with clarity and conviction, whether it’s rallying a team, pitching investors, or influencing stakeholders.

From a founder’s seat, or in a VP of Product role, the question is always the same: How do I become more persuasive, play to my strengths, and raise the bar for myself and my team? Here’s how I’ve put these principles into practice—and what I recommend.

First, I rely on a “personality-message fit” mindset. The goal isn’t to copy someone else’s style; it’s to package your message so it amplifies your natural strengths. If you’re analytical, use structure and crisp logic. If you’re a storyteller, build vivid narrative arcs around data. In product reviews, I’ve seen the same idea land (or fall flat) entirely based on whether the delivery aligned with the speaker’s authentic style.

Charisma is often misunderstood. It’s not about volume or showmanship—it’s about presence, intent, and calibration. Authenticity isn’t performative; it’s the consistency between your values and your behavior. In practice, that looks like stating trade-offs plainly, owning uncertainty, and being consistent in how you make decisions. Teams don’t need theatrics; they need reliability and conviction.

Clarity in communication is the single highest ROI skill in leadership. Start with your ideal outcome: what do you want your audience to think, feel, and do? Then reverse-engineer your message. I frame every major communication around outcomes vs output, just as I would with OKRs. This shifts the discussion from activity (“we shipped”) to impact (“we moved this metric”). When the outcome is explicit, the argument becomes self-reinforcing—and far more persuasive.

Power dynamics shape how your message is received. Different stakeholders hear the same words through very different lenses. In board updates and investor pitches, calibrate not just content but posture: what decision are you asking for, what risks are you proactively naming, and what constraints are you strategically acknowledging? Influence often hinges less on brilliance and more on aligning incentives and expectations.

On the perennial question—should you work on weaknesses or double down on strengths?—I’ve found the most durable gains come from role-strength fit. Eliminate spiky weaknesses that are career-limiting (for example, unreliable follow-through), but invest disproportionately in the strengths that create asymmetric value. This is how leaders move from competent generalists to compelling, irreplaceable operators.

Effective self-reflection is a force multiplier. A deceptively powerful prompt I use with teams is: What do you resent? Resentment often points to violated boundaries, unclear roles, or recurring misalignments. Surface it, re-contract responsibilities, and redesign rituals. This isn’t soft work; it’s operational hygiene that protects focus and velocity.

When someone tells you to “be more strategic,” they’re rarely asking for more slideware. They want clearer time horizons, sharper prioritization, and better sequencing. I lean on stack ranking to make trade-offs explicit. If everything is a priority, nothing is. Show what’s first, what’s second, and what you’re explicitly saying no to—and why. Strategy is the discipline of exclusion.

Two ideas I return to often: how formative programs start and how craft gets defined. The origin story behind community-driven learning like the AltMBA reminds me that great products are built with a point of view and a tight feedback loop. Defining your craft—naming it, practicing it, and holding a higher standard for it—creates a culture where excellence becomes normal, not exceptional.

If you’re a founder or product leader, a practical way to apply all of this next week is simple: decide the outcome, tailor the message to your natural style, acknowledge power dynamics up front, and stack rank your asks. Then, debrief with the team: What landed? What didn’t? What will we do differently next time? Communication is a craft, and like any craft, standards rise with deliberate practice.

AltMBA: https://altmba.com/

Maven: https://maven.com/

Seth Godin: https://www.sethgodin.com/

Udemy: https://www.udemy.com/

Where to find Wes:

LinkedIn: https://www.linkedin.com/in/weskao

October 20, 2025
Inside Linear: How Craft, Focus, and Small Teams Build Category-Defining Products

I’ve long believed that craft and focus are the two most reliable levers in product management, and listening to Karri Saarinen articulate how those principles shaped Linear reaffirmed why they still win. Karri is the co-founder and CEO of Linear, the project management tool built for high-performance software teams. Since its founding in 2019, Linear has achieved a valuation of $1.25B as of 10th June 2025 and now counts companies like OpenAI, Ramp and Vercel as customers. Before founding Linear, Karri led design at Airbnb and Coinbase, and previously co-founded Kippt, a bookmarking tool acquired by Coinbase. From the opening moments (1:37), his childhood love for computers and design felt familiar. Many of us who lead product today started by tinkering—not for a resume line, but out of curiosity. That early bias toward making things, paired with taste, often becomes the quiet engine behind strong product discovery and product-market fit lessons. At (6:54), the story of founding Kippt and the lessons from a failed bookmarking startup reminded me how much scar tissue can accelerate good judgment. Failure clarified what really matters: build for a specific user, ship faster than your uncertainty, and let the market teach you. The thread continues at (13:14) with lessons from a serial entrepreneur—how pattern recognition, not stubbornness, is what you carry forward. The segment at (19:32) hits a nerve for anyone scaling: why teams shouldn’t grow too quickly. I’ve seen small, senior teams accomplish in weeks what larger groups struggle to deliver in quarters. Velocity isn’t headcount; it’s clarity, trust, and an obsession with quality. Smaller teams keep craft close to the metal and reduce coordination tax. At (25: 03), Linear’s early beginnings emphasize how tight validation loops shape a product. Early validation strategies used to shape the product weren’t about chasing breadth—they were about earning depth with a narrowly defined customer. It’s the purest form of product discovery, and it sets the foundation for everything that follows. The conversation at (36:55) on the unexpected power of intuition resonated with how I coach teams: treat intuition as a hypothesis generator, then use data to reduce risk. It’s not intuition versus evidence; it’s intuition prioritized, evidence instrumented. That’s also how outcomes vs output OKRs stay honest—by measuring what matters without drowning product sense in dashboards. Linear’s unusual approach to user growth (42:41) rejects growth theater in favor of signal-rich adoption. Rather than boil the ocean with generic funnels, they doubled down on the right users, in the right sequence. That ties directly to (57:30) and the power of extreme focus, and the reminder at (59:18) to Design “something for someone”. It’s a crisp antidote to generic, over-configurable tools that try to be everything to everyone. If you’re curious what shaped Linear’s early product roadmap (47:29), the answer is principled constraint: a maniacal focus on performance, reliability, and a workflow that feels frictionless to high-performance software teams. When the product coheres around a few non-negotiables, teams can ship faster and with higher quality. The tension between flexibility vs. simplicity (1:04:29) shows up in every roadmap debate I’ve ever led. Flexibility sells demos; simplicity earns daily active usage. Picking simplicity early forces better defaults, clearer information architecture, and fewer surface areas where complexity can metastasize. Principled leadership shows up again at (1:17:27): Lead your team with strong principles. The best teams don’t need long memos to decide; they need clear tenets to align. Finally, (1:24:45) surfaces a nuanced distinction: design founders vs. engineering founders. The best outcomes emerge when design taste and engineering rigor compound—not compete—inside a product culture. A few references that stood out and helped frame the context: Airbnb, Coinbase, Y Combinator, Brian Armstrong, Brian Chesky, Jori Lallo, and Tuomas Artman. The through-line is unmistakable: high-taste product builders who pair speed with standards. If you want to jump to specific moments, here are the timecodes I found most actionable: (1:37), (6:54), (13:14), (19:32), (25: 03), (36:55), (42:41), (47:29), (52:02), (57:30), (59:18), (1:04:29), (1:17:27), (1:24:45). Each one reinforces a simple truth: focus compounds. If you’d like to follow Karri’s work directly, find him on LinkedIn: https://www.linkedin.com/in/karrisaarinen/ and Twitter/X: https://x.com/karrisaarinen. My takeaway for product leaders: revisit your scope, trim the excess, and put a small, senior team on the sharpest problem in your roadmap. Start with a principled bet, instrument outcomes, and keep the bar for craft uncomfortably high. That’s how you build products that feel inevitable—because they’re intentionally, relentlessly focused.

October 20, 2025
Reimagining Product Teams with Generative AI: A Bold, Practical Vision for the Next 24 Months

In this article, I want to talk about where I believe generative AI is going to take the roles on a product team, and the team topologies of product organizations. I’m motivated to write this both because I think a vision of where we should try to go is important, and also because I see…

That conviction has only grown as I’ve led cross-functional teams through real deployments. The traditional boundaries between product management, design, engineering, and customer success are blurring as generative AI moves from novelty to dependable copilot. What follows is the vision I’m using to guide our roadmap, hiring, and rituals—practical, near-term, and focused on outcomes.

First, on roles: product managers will spend less time drafting artifacts and more time validating assumptions and sequencing bets. AI will draft PRDs, summarize interviews, propose opportunity trees, and even flag risks. But we will anchor decisions on outcomes vs output OKRs, using AI to widen the option set, not to outsource accountability.

Design will accelerate dramatically. With gen ai for product prototyping, designers can turn rough concepts into interactive flows in hours, stress-test copy for clarity, and explore accessibility states before code is written. The craft shifts toward problem framing, system thinking, and quality thresholds—where human judgment remains the differentiator.

Engineering becomes even more product-facing. Forward deployed engineers will pair with PMs and designers at customer sites (or virtually) to co-create solutions, integrate LLMs, and harden edge cases. Model-aware engineering, evaluation harnesses, and data pipeline stewardship become core competencies, while “prompt engineering” becomes a skill embedded across functions rather than a standalone role.

On team topology: our default unit stays the autonomous, outcome-owning squad, but we add an enablement layer. An AI platform team supplies shared services—feature stores, evaluation datasets, observability, and safety guardrails—so product teams can move fast without reinventing infrastructure. Guilds or communities of practice steward reusable prompts, patterns, and model cards across squads.

Discovery evolves too. We’ll pair classic product discovery with AI-accelerated research: large-scale synthesis of qualitative feedback, scenario exploration with synthetic data, and rapid hypothesis testing through simulated cohorts. Human-in-the-loop remains non-negotiable; generative AI helps us see more options, but customers still tell us what’s true.

Customer support becomes a flywheel. A thoughtful customer support ai strategy turns conversations into structured insights, feeds prioritization, and powers in-product guidance. The same signals that resolve tickets should inform discovery, experimentation, and roadmap trade-offs.

Governance and safety must be proactive. We’ll define golden datasets, create red-team playbooks, and adopt model-level SLAs alongside product SLAs. Evaluation goes beyond accuracy to include fairness, latency, explainability, and cost, with clear escalation paths when models drift or fail.

Measuring impact changes as well. Beyond feature delivery, we’ll track time-to-learning, reduction in cycle time, precision of targeting, and the quality of decisions AI actually improves. The goal is durable product-market fit lessons, not vanity metrics or demo-driven development.

Here’s a pragmatic 90-day starter plan: identify two high-signal use cases where latency, cost, and safety are manageable; form a cross-functional pod with a PM, designer, forward deployed engineers, and a data partner; instrument robust evaluation gates; align on outcomes vs output OKRs; ship, learn, and codify the playbook. In parallel, stand up the minimal AI platform services your squads will reuse.

This is a leadership challenge as much as a technical one. Product management leadership must set the bar for ethical use, invest in upskilling, and reorganize incentives around outcomes. The teams that win will treat generative AI as a force multiplier for curiosity, learning, and craftsmanship—not a shortcut around them.

If we do this well, our product teams will be faster, more customer-obsessed, and more resilient. The tools are ready. The real question is whether we are ready to evolve how we work, measure progress, and lead.

Inspired by this post on SVPG.

October 20, 2025
Outcomes Are Hard: How I Lead Teams Beyond Output with OKRs, Discovery, and Focus

Outcomes are hard. I’ve felt that tension in every product organization I’ve worked with, especially when the pressure to ship is loud and the signal from customers is faint. Moving a team from measuring success by output to measuring success by outcomes requires clarity, patience, and a willingness to rethink how we plan, prioritize, and learn.

Here’s how I frame the distinction. Output is what we build and launch. Outcome is the meaningful change for customers and the business—adoption, retention, reduced time-to-value, improved conversion, lower cost-to-serve. When we focus on outcomes, we stop celebrating activity and start optimizing for impact.

Why is this shift so difficult? Outcomes depend on human behavior, not just code. They emerge from messy, interconnected systems: customer jobs-to-be-done, go-to-market motions, pricing, onboarding, and even customer support. That complexity makes outcomes slower to observe, harder to attribute, and easy to dismiss when a deadline looms. It takes leadership, consistent product discovery, and strong instrumentation to stay the course.

OKRs are the most practical tool I use to make outcomes concrete. The Objective expresses a meaningful change we seek. The Key Results quantify that change in customer and business terms. Great KRs describe effects, not activities: increase weekly active usage of the new workflow by X%, reduce onboarding time to first value to Y minutes, lift self-serve conversion by Z%, cut support tickets per account for feature A by N%.

The common pitfalls are predictable. If your KRs read like a roadmap (“ship X,” “integrate Y”), you’re back to output. If they’re vanity metrics (“page views” with no linkage to value), you won’t learn. If they’re sandbagged, you’ll get a false sense of progress. And if time horizons are mismatched—quarterly KRs for outcomes that need a semester—you’ll churn without insight.

This is where product discovery earns its keep. I connect outcomes to discovery by starting with the problem, not the feature. I map assumptions, prioritize the riskiest ones, and test with the lightest-weight experiments—prototypes, concierge tests, or data slices. The goal is to find the smallest bet that can move the needle on the Key Results, then iterate. When discovery is continuous, the roadmap becomes a living hypothesis tied to outcomes rather than a fixed list of outputs.

Instrumentation is non-negotiable. If we can’t measure customer behavior reliably, we can’t manage outcomes. I invest early in event schemas, product analytics, and clear operational definitions for metrics. I also bring forward deployed engineers and designers into customer conversations to compress feedback loops. Being close to the user is a force multiplier for outcome thinking.

Cadence matters. I prefer weekly reviews on leading indicators and monthly deep dives on lagging metrics, with quarterly OKR retrospectives to distill lessons. We celebrate learning—insights that invalidate a bet are just as valuable as wins—because that culture keeps the team curious, honest, and resilient.

As product management leaders, our job is to create the conditions where outcome focus can thrive. That means setting a crisp product operating model, aligning stakeholders on a North Star metric, empowering teams to choose solutions, and protecting time for discovery. It also means having hard conversations about stopping work that doesn’t move the numbers, even if it’s already in flight.

How do you know you’re making progress? You’ll see fewer features, clearer narratives, faster cycles, and better results: improved activation, deeper engagement, and stronger product-market fit signals. Your roadmap will read like a portfolio of bets tied to Key Results, not a calendar of releases.

If outcomes feel hard, that’s normal—and it’s a sign you’re working on what matters. Start small: pick one team, define one consequential outcome, and run one disciplined discovery cycle. Measure honestly, learn in public, and repeat. Over time, you’ll build the muscle memory to move beyond output and deliver durable customer and business impact.

Inspired by this post on SVPG.

October 20, 2025
From Vision to Value: How Generative AI Elevates Product Design and Product Management

Product, design, and AI now converge at the center of how we build value. In my role leading product teams at HighLevel, Inc., I’ve experienced firsthand how generative AI amplifies the craft of product management and product design when we keep the fundamentals tight: clear problems, measurable outcomes, and deep collaboration across disciplines.

The mission hasn’t changed—deliver useful, usable, and trustworthy experiences—yet the means have. Generative AI expands our exploration space, speeds up iteration, and helps us reason over messy, real-world data. When we marry rigorous product discovery with thoughtful design and responsible AI strategy, we move from novelty to durable impact.

In discovery, I use AI to frame hypotheses, generate research questions, cluster customer feedback, and synthesize interview notes—without replacing direct conversations with customers. The goal is sharper insight, faster. I define outcomes in customer language, pressure-test assumptions, and trace every proposed AI capability to a clear job to be done. These habits keep us anchored to product-market fit lessons rather than shiny demos.

For prototyping, I pair designers with forward deployed engineers to build realistic vertical slices quickly. We practice gen ai for product prototyping by wiring prompts, system instructions, constrained outputs, and lightweight evaluators into clickable flows so we can test usefulness early. This reduces risk and helps the team learn which interaction patterns—chat, form, or guided workflows—fit the problem best, especially in product creator experiences.

Designing AI-powered UX means embracing uncertainty without eroding trust. I favor patterns like transparent confidence cues, citations or references where possible, editable outputs, easy undo/redo, and clear pathways from draft to commit. Good empty states, contextual examples, and progressive disclosure teach users how to get high-quality results while keeping them in control.

Quality requires a measurement backbone, not vibes. I define target tasks and build golden datasets, then run offline evaluations before online experiments. The core metrics stay consistent: task success rate, user confidence, time-to-first-value, latency budgets, and cost per resolution. We harden experiences with guardrails, hallucination checks, safe fallbacks, and escalation paths to humans when the model is uncertain.

Responsible AI is a product requirement, not a checkbox. I design for privacy-by-default, PII minimization, and secure data handling; I track prompt and model versions; and I test for bias and accessibility from the outset. Human-in-the-loop review, auditability, and transparent change logs protect users and the business as features evolve.

Go-to-market is part of the product. Clear onboarding, explainers, and in-product education reduce time to value. I align customer support ai strategy with telemetry so support teams can triage AI-specific issues, capture edge cases, and channel learning back into prompt libraries, data pipelines, and design improvements.

From a leadership standpoint, I set strategic guardrails and empower autonomous teams. Product management leadership owns outcomes and decision quality; design leads shape multimodal experiences; engineering owns reliability and performance; and our AI platform team standardizes evaluation, safety, and cost controls. This clarity accelerates learning and throughput.

Recently, we shipped an AI-assisted creation flow that reduced manual steps, improved time-to-first-value, and drove adoption among new users. The win wasn’t a clever prompt; it was disciplined product discovery, fast iteration with realistic data, and a crisp definition of success before we scaled.

If you’re just starting, pick one high-value, low-risk use case, define success in customer terms, and build a thin vertical slice with evaluations and guardrails. Put it in front of real users, instrument everything, and iterate until the experience feels fast, predictable, and genuinely helpful.

The intersection of product, design, and AI will keep evolving, but the bar remains the same: ship outcomes customers care about. When we combine the leverage of generative AI with sound product discovery and strong product design, we turn vision into value—reliably and repeatably.

Inspired by this post on SVPG.

October 20, 2025
Unlocking Team Autonomy in the Age of Generative AI: Practical Guardrails and Wins

I’ve been working on the longer-term implications of generative AI on product teams, and especially since “A Vision for Product Teams” made the rounds, I’ve had many meaningful conversations with leaders and practitioners about the consequences and second-order effects of generative AI. Through these discussions, one thing I’ve learned is that when it comes to product teams, there’s no one-size-fits-all playbook—autonomy only works when it’s matched with clarity of strategy, measurable outcomes, and explicit guardrails.

In practice, that means generative AI doesn’t replace product judgment; it accelerates learning loops. When teams can quickly prototype ideas, summarize research, and simulate user flows, they gain speed. But speed without direction amplifies noise. The teams that benefit most from AI pair autonomy with a crisp product strategy, a clear definition of success, and strong alignment on customer value.

Team autonomy in the AI era means owning problems, not features. Cross-functional squads should be accountable to outcomes, with the freedom to choose tactics—human-centered design, data-informed decisions, and responsible AI practices. Autonomy thrives when teams understand the company narrative, the strategic constraints, and the ethical boundaries that protect customers and the business.

The most underestimated shifts are the second-order effects. As AI reduces the cost of ideation and validation, teams can move faster with smaller surfaces—but the risk of local optimization increases. Without a unifying product strategy, shared data foundations, and platform standards, autonomy fragments the user experience. The solution is not to centralize decisions, but to centralize intent: common objectives, consistent metrics, and reusable capabilities that teams can compose.

Discovery also evolves. Generative AI can help synthesize qualitative feedback at scale, draft experiment variants, and stress-test hypotheses. I encourage teams to treat AI as an assistant for product discovery—use it to explore breadth, then validate depth with customers. Rapid prototyping is more powerful when tied to clear hypotheses, structured experiments, and tight feedback loops.

The role of product management expands from roadmap stewardship to system design. I focus my teams on framing problems, defining outcomes, and setting the rules of engagement: data access policies, model selection criteria, human-in-the-loop checkpoints, and standards for explainability. When we make these guardrails explicit, engineers and designers can move faster with confidence, and leaders can trust the results.

Operationally, I’ve found a few practices to be especially effective: outcome-based roadmaps instead of feature lists; a shared experimentation platform; golden datasets with clear provenance; evaluation rubrics for model quality; and policies for privacy, security, and bias mitigation. These enable autonomy at the edges while maintaining coherence at the core.

Adoption should be staged. Start with internal workflows and low-risk use cases, instrument everything, and expand as confidence grows. Celebrate wins that compound—shorter discovery cycles, better customer insights, and higher-quality decisions—not just raw automation. The goal is augmented teams, not automated teams.

Day to day, I ask teams to make their thinking legible. Treat prompts, hypotheses, and decision logs as living artifacts. When assumptions, constraints, and outcomes are explicit, autonomy scales. And when AI helps us reason faster and see farther, we can reserve human judgment for the choices that truly matter.

My takeaway: generative AI is a force multiplier for autonomous product teams that align on strategy, instrument outcomes, and operate with clear guardrails. Give teams ownership of problems, equip them with responsible AI practices, and hold them accountable to customer and business impact. That’s how we turn speed into sustainable progress.

Inspired by this post on SVPG.

October 20, 2025
Why INSPIRED Still Matters in the Generative AI Era: Access, Insights, and Practical Playbooks

In the Generative AI era, I keep returning to the enduring playbooks that shape great product teams. INSPIRED remains a cornerstone for how I coach on product discovery, product operating models, and product management leadership. I’ve used its principles to align cross-functional squads, empower product creators, and accelerate product-market fit lessons across both startups and scaled organizations.

The book INSPIRED is available in hardcover, digital, and audio versions, but until now, the audio version was only available in an exclusive arrangement with Amazon, on audible.com. The audio versions of our other books have been available from all major audio book providers. The exclusive contract with Amazon has now expired, and…

Why this matters: when knowledge moves beyond a single platform, more of our teams can absorb it in the flow of work. Distributed PMs, designers, data scientists, and forward deployed engineers can learn on their preferred apps during commutes or deep work breaks. That accessibility compounds learning velocity—especially when we’re iterating weekly on discovery insights, opportunity assessments, and bet selection.

What’s changed in our craft is the tooling: gen ai now augments how we validate assumptions, run product discovery, and prototype. Pairing the timeless practices in INSPIRED with gen ai for product prototyping helps my teams get to evidence faster—turning ambiguous narratives into testable artifacts, instrumented experiments, and real customer signals. It also sharpens our product operating model by making continuous discovery the default behavior across the product team.

Here’s how I operationalize this shift: I anchor a short “learning sprint” around one chapter at a time, then immediately translate insights into a concrete discovery activity (problem framing, assumption mapping, or opportunity sizing). We run a gen ai prototyping spike to visualize flows, draft UX copy, and simulate edge cases, followed by quick customer sessions to validate usefulness and usability. We capture outcomes in a working taxonomy of product-market fit lessons and update our decision logs so learning compounds sprint over sprint.

This is also a practical boost for enablement: new hires, customer support leaders crafting a customer support ai strategy, and forward deployed engineers can now engage with the same source material on their own schedules. When the whole team shares a common vocabulary—shaped by proven practices and accelerated by gen ai—the quality of debate improves, discovery cycles compress, and execution becomes more predictable.

If you’ve been meaning to revisit INSPIRED, this is an ideal moment. With access broadening, pick the format that fits your routine and turn insights into action the same day. Use it to pressure-test your product operating model, refine your discovery cadence, and elevate product management leadership across the organization. The combination of timeless principles and modern gen ai tools is exactly what our product teams need right now.

Inspired by this post on SVPG.

October 20, 2025
What I Learned Building AI Teacher Assistants: RAG, Evals, and Designs Teachers Love

How do you build an AI-powered assistant that teachers will actually use?

As a VP of Product Management who ships AI features to real users, I’ve learned that the answer starts with deep empathy and ends with disciplined engineering. I recently dug into a compelling case study of K–5 edtech, where a team with more than a decade of experience building adaptive learning tools launched an AI-powered Teacher Assistant to help educators align supplemental lessons with district-mandated core curricula. The result is a practical blueprint for product leaders navigating gen AI in high-stakes environments.

In this episode of Just Now Possible, Teresa Torres talks with Thom van der Doef (Principal Product Designer), Mary Gurley (Director of Learning Design & Product Manager), and Ray Lyons (VP of Product & Engineering) from eSpark. Listening through a product lens, I focused on what translated from vision to value in busy classrooms—and why some early instincts (like a chatbot-first UI) didn’t survive contact with reality.

Listen to this episode on: Spotify | Apple Podcasts

Here’s what stood out to me. Post-COVID shifts in education created new pressures for teachers and administrators, amplifying the gap between top-down mandates and classroom realities. The team’s first instinct—a chatbot interface—failed in testing, and what ultimately worked was a more structured workflow that mapped to how teachers actually plan, select, and assign lessons. That’s a timeless product discovery lesson: meet users where they are, especially when their cognitive load is already maxed.

On the technical side, their first RAG system surfaced all the usual suspects—and all the usual surprises. The team had to learn to wrangle embeddings, debug semantic search vs. keyword search, and tune retrieval to the nuance of curricula, standards, and lesson objectives. As someone who has shipped RAG-backed features, I appreciate how much of the work happens in the unglamorous middle: data quality, ontology decisions, metadata hygiene, and evaluation strategy.

Speaking of evaluation, their background in education shaped a surprisingly rigorous eval process, long before “evals” became a buzzword. They leaned on rubrics, Braintrust, and a human-in-the-loop approach to ensure the assistant’s recommendations were accurate, aligned, and classroom-ready. It’s a reminder that in domains like education and healthcare, model observability and structured evaluation are non-negotiable for product-market fit.

The most energizing signal for me: they’ve learned from thousands of teachers using the product this school year—and they’re already translating that learning into roadmap bets. What’s next for Teacher Assistant: more contextual recommendations using student data. Done well, that shift moves the product from “helpful” to “indispensable,” grounding gen AI in student outcomes rather than generic assistance.

Show notes for context: Guests include Thom van der Doef, Principal Product Designer at eSpark; Mary [last name], Director of Learning Design & Product Manager at eSpark; and Ray Lyons, VP of Product & Engineering at eSpark. Topics covered span the origin story of Teacher Assistant (connecting administrator mandates with teacher needs), why the team abandoned a chatbot interface in favor of a more structured workflow, how retrieval augmented generation (RAG) and embeddings shaped the product architecture, lessons learned from debugging semantic search vs. keyword search, building evals with rubrics, Braintrust, and a human-in-the-loop approach, and what’s next for Teacher Assistant: more contextual recommendations using student data.

If you like to follow along chronologically, the chapter flow is tight and practical: 02:05 Overview of Epar's Adaptive Learning Program; 07:19 Challenges and Insights from COVID-19; 17:06 Developing the Teacher Assistant Feature; 24:55 User Experience and Interface Evolution; 34:29 Chat GPT-5's New Features; 35:16 Balancing Engagement and Efficiency; 35:40 Seasonal Business and Real Traffic; 36:29 Technical Decisions and RAG Implementation; 38:28 Challenges with Embeddings and Metadata; 41:24 Improving Recommendations and Data Enrichment; 55:18 Evaluating the Teaching Assistant; 01:05:51 Future Plans and User Feedback; 01:07:57 Conclusion and Final Thoughts.

Useful links if you want to go deeper: eSpark Learning; Braintrust.dev – evals and observability for LLM applications; AI Evals Maven Course by Hamel Husain and Shreya Shanker.

My product takeaways for anyone building AI in complex, regulated, or mission-driven domains: First, resist the chatbot reflex; many users need structured, high-signal workflows. Second, treat retrieval as a product surface—data modeling, metadata, and domain language matter as much as model choice. Third, invest early in evals with rubric-based scoring and human-in-the-loop reviews to protect trust. Finally, plan for seasonality and “real traffic” patterns; the strongest eval is usage in production with tight feedback loops from your most demanding users.

Gen AI is only as valuable as the outcomes it enables. In classrooms, that means saving teachers time, raising instructional alignment, and ultimately improving student learning. This case study shows that when we combine empathetic product discovery with disciplined RAG architecture and rigorous evals, AI stops being a demo—and starts being a difference-maker.

Inspired by this post on Product Talk.

October 20, 2025
Turn AI into a Strategic Thought Partner: Real Workflows, UX Shifts, and Personal Agents

I’ve been leaning hard into AI as a strategic thought partner, not a shortcut—and this episode captured exactly why. Listening to Teresa Torres and Petra Wille explore how AI sharpens writing, coding, and product decision-making felt like a mirror of what I’m seeing on real teams: when we treat AI as a collaborator, we unlock quality, speed, and clearer thinking without sacrificing our voice or product judgment.

If you want to dive in, listen on Spotify or Apple Podcasts. There’s also a YouTube version here: watch the episode.

Two themes stood out immediately. First, Petra’s voice-first workflow and how she uses AI to mine her own archive for consistency is a brilliant approach to preserving authorial intent while scaling content creation. Second, Teresa’s claim that “Claude Code in the terminal completely changed her workflow—from planning mode for coding projects to using reviewer “sub-agents” when drafting blog posts” maps closely to how I’ve reshaped my own product and engineering cadence.

On Petra’s side, the combination of voice input and bilingual transcription isn’t just a convenience—it’s a cognitive unlock. By capturing high-fidelity thinking in real time and surfacing relevant prior material, AI becomes a continuity engine for product discovery and leadership communications. I’ve applied a similar pattern for product briefings and executive updates: record voice notes, let AI surface connected fragments from prior docs, and then reconcile differences to maintain a single, coherent narrative over time. Tools like WisprFlow make this feel natural rather than mechanical.

Teresa’s setup with Claude Code resonated as well: planning mode, context from local files, and project planning before writing code is exactly how I prefer to work with engineers and forward deployed engineers. Bringing in local context—sometimes via RAG (retrieval-augmented generation) or MCP (Model Context Protocol)—keeps the assistant grounded in the reality of our repositories and docs. In my experience, that pre-work pays off with cleaner interfaces, tighter tests, and faster reviews when we shift from ideation to implementation.

The framing that matters most to me: using AI as an editor and reviewer rather than as a ghostwriter. I still write every word myself, but I rely on structured critique to reduce blind spots. Creating sub-agents (copy editor, skeptic, devil’s advocate) to critique drafts mirrors how strong product teams stress-test PRDs, strategy docs, and UX copy. When I need a deeper critique, I’ll even spin up dedicated Subagents to review assumptions, risk, and edge cases.

One practical takeaway you can apply immediately: pair models for complementary strengths. How ChatGPT and Claude differ in strengths (structure vs. tone) is a pattern I see daily in gen ai for product prototyping. I often draft structured scaffolds or test plans in ChatGPT, then refine tone, clarity, and nuance in Claude. For “vibe coding” experiments in Python or Node.js, I’ll start in planning mode with Claude Code, anchor on tests and interfaces, and only then move into implementation.

The UX implications are profound. The shift toward personal agents as the interface for products accelerates a world where English becomes the interface for everything we do. That means our information architecture must increasingly be legible to agents, not just humans. It also means onboarding, accessibility, and error recovery will be mediated through conversational patterns, not just screens. For product management leadership, this demands new standards for observability, prompt governance, and cross-model evaluation—core ingredients for trustworthy AI strategy.

If you’re mapping this to your roadmap, here’s how I’d operationalize it: treat AI as a strategic thought partner in product discovery; define explicit roles for sub-agents in reviews; codify planning mode as a precondition to writing code; and document model choices (structure vs. tone) so your team knows when to use what. This is how we turn gen ai into durable product-market fit lessons rather than sporadic wins.

Resources and links mentioned or relevant to the workflows discussed: ChatGPT, Claude & Claude Code (Anthropic), WisprFlow, Vibe coding, Python, Node.js, RAG (retrieval-augmented generation), MCP (Model Context Protocol), agents and workflows, and Subagents.

I’d love to hear how you’re deploying AI in your own stack. What’s working in your editor-and-reviewer setup? Which combinations of models are giving you leverage? Drop your thoughts below—let’s compare notes and sharpen our collective practice as product creators.

Inspired by this post on Product Talk.

October 20, 2025