I’m often asked how to hire the right marketer at the right time for a startup. In my role, I take a magnifying glass to the core components of a startup’s marketing org and share a practical playbook you can apply today to reduce hiring risk and accelerate impact.
I start by breaking down the three pillars of marketing roles — product, brand, and growth. Understanding which pillar you need first is a function of your stage, strategy, and the specific gaps on your team.
I explain the leading indicators that your startup is ready to hire folks within each of these pillars — which starts with analyzing your sales motion and sizing up the founders’ strengths and weaknesses. For example, if founder-led GTM is working but messaging is inconsistent across deals, prioritize product marketing; if awareness stalls and the story doesn’t travel, invest in brand; if sign-ups outpace activation or conversion, it’s time for growth.
Next, I pull back the curtain on how I architect interview loops for each of these different roles, and the unique capabilities that separate good candidates from great, must-hire folks. For product marketing, I look for crisp problem framing, narrative craft, and enablement chops; for brand, taste plus discipline in category design and communications; for growth, rigorous experiment design, data fluency, and full-funnel thinking.
I also reflect on what it takes to be one of the earliest marketing hires at a fast-growing company. In the first couple of years, the mandate is to build the marketing org to keep up with the shifting needs of the growing startup—moving from zero to one, to repeatability, to scale—without losing the builder mentality or your bias for outcomes.
For product leaders, founders, and hiring managers, this is a must-read if you’re trying to pluck out the best and the brightest to join your org. The nuances of startup marketing are easy to miss until you’ve lived them; my goal is to translate those lessons into clear signals and repeatable processes you can use.
Use this guide to diagnose where you are, time your next hire, and design an interview loop that reveals real signal. When you align the right marketer with the right moment, you accelerate product-market fit, uplevel cross-functional execution, and create durable growth.
I sat down with Sandra Oh Lin, founder and CEO of KiwiCo, which creates hands-on learning kits for children. After executive roles at PayPal and eBay, she started KiwiCo over ten years ago to give her own kids more hands-on projects to exercise their creativity — a spark that led to entrepreneurship. Today, KiwiCo has expanded to include 8 different lines of crates that are shipped out monthly. As a product creator, I was eager to unpack how she turned a personal need into a scalable, beloved physical product line.
We dug into the thornier challenges of building physical products and her biggest aha moments as a first-time founder. She described creating the first KiwiCo crate — from the product development process to spinning up a supply chain and shipping department. We discussed how KiwiCo approaches new product lines, particularly in the last year when KiwiCo demand skyrocketed. She also shared how the team gathers quality consumer feedback when your customer is often a toddler — an audience that demands observational research, short feedback loops, and thoughtful proxies through parents and caregivers.
From a product discovery perspective, I found KiwiCo’s approach refreshingly pragmatic: iterative prototyping, tight learning cycles, and early validation that inform product roadmapping and sprint planning. When demand surges, operational excellence becomes a product feature — and Sandra’s experience reinforced that product-market fit lessons don’t end at the moment of traction; they expand into forecasting, inventory strategy, and resilience across partners. The throughline is an outcomes-over-output mindset that keeps the team anchored on value delivered to families rather than feature velocity.
We then shifted to culture — the often overlooked engine behind durable execution. Sandra is a strong believer in manager training for everyone, from folks that manage just one person to executives that have been managing for decades. She outlined the specific management training modules they leverage at KiwiCo and made the case for having everyone at the company fill out a motivations spreadsheet. For leaders navigating the IC to manager transition, these guardrails accelerate consistency, empathy, and decision quality across teams.
Finally, we explored how she creates a feedback-rich environment for herself as a CEO. I appreciated the intentionality — structured forums, explicit invitations for critique, and clear norms that make feedback safer and more actionable. Whether you’re shipping crates or software, the lesson holds: sustained product management leadership depends on mechanisms that convert diverse signals into aligned action. If you’re building physical products or scaling a product organization, these practices offer a blueprint for learning faster, de-risking complexity, and keeping customers — even the tiniest ones — at the center.
I’ve long admired Giancarlo ‘GC’ Lionetti, the former CMO of Confluent and VP of Self-Serve Growth at Dropbox. (GC also previously spent 6 years at Atlassian, as a sales engineer and product marketing manager for developer tools.) He describes his career as more of a maze than a ladder, and that functional breadth across standout B2B companies resonates with my own approach to product management leadership.
In this deep-dive, I make the case for a hybrid go-to-market strategy that brings together more traditional selling with modern product-led growth. I’ve seen this blend unlock efficient, scalable growth without sacrificing enterprise-grade rigor — especially when you’re balancing self-serve and sales-assisted motions before and after product-market fit.
I start by mining lessons from GC’s time at Atlassian and Dropbox, comparing their business models and translating what it takes to make a multi-product go-to-market motion work. For me, the critical levers include crisp segmentation, clear packaging, intentional cross-sell paths, and an obsessive focus on the end-to-end customer journey.
From there, I share my advice for a hybrid approach, including my litmus tests for picking the right metrics and the structure of my weekly meetings. I distinguish inputs from outcomes, leading indicators from lagging indicators, and align each metric to a specific stage of the funnel with a single accountable owner. My weekly operating cadence ties product-led growth health (acquisition, activation, conversion, monetization) to sales pipeline, forecast accuracy, and deal health so both motions reinforce one another.
I also sink tons of time into understanding the customer journey, mapping out the delta between reality and the ideal vision. That means pairing qualitative insights with product analytics, instrumenting key aha moments, and documenting friction so the team can remove blockers in priority order. The result is a shared, visual narrative that turns strategy into execution.
On pricing, packaging, and activation, I lean on a few battle-tested principles: anchor pricing to customer value, keep the pricing metric intuitive, right-size tiers for clear upgrade paths, and design first-session experiences to reduce time-to-value. In SaaS pricing, even small tweaks to entitlements, limits, and paywalls can meaningfully shift activation and expansion, so I validate with experiments before rolling changes broadly.
To holistically evaluate any go-to-market strategy, I apply a simple diagnostic framework that scores acquisition, activation, monetization, expansion, and retention, then layers in organizational alignment and operating cadence. This clarity exposes whether issues are strategy, execution, or enablement problems — and where a hybrid model can create compounding gains.
Finally, I focus on team building for a hybrid go-to-market strategy — from hiring profiles to team structure. I look for product builders who can speak revenue, growth leaders who respect product quality, and sales partners who embrace product-led signals. A shared dashboard, a single planning calendar, and joint post-mortems keep incentives aligned.
If you’re a founder, or part of the broader community of founders, product and go-to-market leaders, you’ll find this playbook packed with examples of specific impactful experiments I’ve run, metrics that did or didn’t work out, and common traps that I see teams falling into. The goal is simple: create a durable growth engine that compounds by uniting product-led growth and enterprise selling.
I recently sat down with Gretchen Howard, COO of Robinhood. Gretchen joined Robinhood in early 2019 as the company’s COO and just its second executive hire. She climbed aboard the Robinhood rocketship after 5 years building CapitalG, Alphabet’s investment fund. That lens—hypergrowth, scale, and rigor—made for a candid, deeply practical conversation about the art and science of executive hiring.
My first principle: align the hiring profile to the trajectory of the business. Before I draft a role spec, I map where the company will be in 12–24 months and work backward—org design, critical outcomes, decision rights, and the interfaces this leader must own. This prevents over-hiring for prestige or under-hiring for comfort, and it keeps us investing in the right places where leadership leverage is highest.
We also dug into the balance between domain and operating DNA. For certain roles, industry context matters, but in high-velocity environments I prioritize builders who can scale ambiguity into systems. Put differently, I look for leaders capable of balancing financial industry expertise with an innovative, hands-on mindset that’s critical for startups. That balance avoids the two common failure modes: executives who can “talk the talk” but can’t ship, and specialists who struggle once the playbook runs out.
On the executive interview process, I keep a tight loop that tests judgment, learning velocity, and execution. I probe for whether someone has a “knower” versus a “learner” attitude by asking for specific instances where they reversed a strongly held view based on new data, what broke when they scaled from one stage to the next, and how they built successor benches. I also ask candidates to walk me through decisions they owned end-to-end—the context, options considered, trade-offs, and how they measured outcomes.
My feelings toward interview exercises are intentionally mixed. Over-engineered “strategy cases” can select for presentation polish over operating truth, yet lightweight, job-relevant exercises can surface depth and working style. I time-box collaborative work sessions on a real (sanitized) problem we’re facing, making expectations explicit: I’m evaluating how we think together, not a perfect answer. This yields a more authentic read on communication, prioritization, and bias-to-action.
Reference checks are non-negotiable and high-signal when structured. I run both provided and backchannel references, triangulating on scope, followership, and change management. My go-to questions: What did this leader make better that stayed better? How did they handle a miss? Would you rehire them for this stage and why? I also ask references to predict the candidate’s most likely struggle in the first 90 days; those predictions often become my onboarding guardrails.
Even great hires can fail without intentional onboarding—what I call preventing “organ rejection.” I co-create a 30/60/90 plan that includes outcomes, decision rights, and the first 10 relationships to cement. We align on a cultural narrative (how we build, decide, and escalate), clarify non-negotiables, and schedule fast feedback loops at weeks 2, 6, and 12. Success here looks like early, compounding wins and a clear rhythm with peers—before muscle memory hardens in the wrong direction.
If you’re struggling with your executive hiring—whether it’s coming up with the right candidate profile, aligning on culture fit, or finding that your interview process doesn’t seem to be surfacing the best candidates—this playbook will help you de-risk the decision. The combination of a stage-appropriate profile, a learning-oriented interview loop, disciplined reference checks, and deliberate onboarding dramatically increases the probability that your next executive hire will unlock leverage instead of friction.
I recently dug into a powerful conversation with Alisa Cohn, an executive coach with nearly 20 years of experience working with companies like Etsy, Venmo, InVision, The Wirecutter, Google and IBM. Her new book, From Start-Up to Grown-Up: Grow Your Leadership to Grow Your Business, just came out this week, and it’s a timely playbook for anyone navigating the shift from founder to CEO.
What resonated most with me is how central self-awareness is to startup leadership—and how hard it is for executives to get truly candid feedback. As an expert in the art of conducting 360 feedback, Alisa highlights both the right questions to ask and how to get at the root of what people are actually saying in their feedback. In my own practice leading product management, I’ve learned that a multi-source feedback loop is non-negotiable if you want to grow faster than your company’s complexity.
To invite real candor, I set clear expectations up front, guarantee anonymity when appropriate, and ask for specific examples. Prompts I rely on include: What should I start, stop, and continue? When have I been most and least effective? What’s one behavior that would most improve my impact? I also ask for a confidence rating and context (e.g., cross-functional vs. team settings), which surfaces patterns that one-off comments miss. This simple structure keeps feedback actionable for product management leadership and founder-led GTM environments where speed can mask weak signals.
Of course, the hardest part is what to do with what you hear. Not every piece of feedback is useful, and Alisa’s guidance aligns with my own rubric: look for themes across sources, weigh input by proximity to the work and blast radius, separate facts from feelings, and test changes through small, time-boxed experiments. I operationalize changes in my day-to-day routine with calendar nudges, pre-commitments (e.g., publish decision criteria before important calls), and a trusted peer who can observe and nudge me in real time. Small, consistent behavior changes compound faster than sporadic big swings.
We also surface the most common opportunities for growth that show up again and again: communication and decision-making. I’ve seen how a CEO’s personality is unconsciously reflected in the company culture—pace, rigor, appetite for risk, how we treat “no,” and whether we bias toward outcomes vs output. To counter the “shadow of the leader,” I make these drivers explicit: write down decision guardrails, publish decision logs, and define what “good” looks like for communication quality and speed across functions.
Another area we dig into is how to have effective conversations about layering and letting people go. Layering—bringing in experienced leaders above early high performers—works when expectations are clear, roles are well-scoped, and dignity is preserved throughout. My playbook: share the business rationale, define success metrics and timelines, offer a growth path where possible, and avoid ambiguity that erodes trust. When exits are necessary, clarity, compassion, and speed protect both people and culture.
Finally, I’ve adopted a brief reflection ritual that Alisa recommends every founder incorporate into their daily routine. Mine takes ten minutes at day’s end: What mattered most today? What did I learn? What will I do differently tomorrow? This lightweight cadence keeps me honest about progress, especially in the messy middle of the IC to manager transition and the broader journey from scrappy founder to established CEO. It’s also a lifesaver for leaders who struggle to give away their Legos.
Today, I sat down with Max Mullen, co-founder of Instacart, to dig into the craft of company culture with the precision it deserves. As a product leader, I’ve learned that culture is the operating system of the business—and Max’s journey from early generalist (running everything from product to payroll) to culture-focused executive offers a rare, tactical lens on how to build that OS with intent.
What struck me first was how deliberately he and the Instacart team approached company values. We unpacked the process behind defining distinctive principles—like “Every minute counts,”—and the mechanisms that ensure those values actually guide behavior. I shared how, on my own teams, we translate values into observable behaviors, interview rubrics, and operating rituals so they aren’t posters on a wall—they’re decisions in motion.
We then got practical about embedding values so employees truly feel connected to them. Max offered creative tactics that go beyond all-hands slides: narrative storytelling in onboarding, leader “value spotlights” in weekly reviews, and lightweight recognition loops that reward values-aligned choices. I added my playbook for hiring for values early on—using structured prompts, scenario-based assessments, and scorecards that map back to the behaviors we expect to see on day 30, 90, and 180.
From there, we dug into measuring culture—because what you don’t measure turns into mythology. We discussed using eNPS and pulse surveys, but also the importance of qualitative signals: skip-levels, anonymous async forms for hard feedback, and decision postmortems that reveal if incentives are aligned with stated values. I emphasized closing the loop publicly to build trust and make feedback feel consequential.
We also confronted the pitfalls that creep in as companies scale: easy-to-make founder mistakes, factions that emerge between early employees and newcomers, and the slow drift toward politics and bureaucracy. I shared a few guardrails I rely on: structured re-onboarding during hypergrowth, rotating “culture ambassadors” across functions, publishing decision logs for transparency, and codifying “how we decide” to reduce shadow politics.
The throughline is simple and powerful: founders and product leaders can and should take a deliberate role in shaping culture from day one. If you’re scaling now, run a quick audit: Are your values specific enough to create trade-offs? Do they appear in hiring, performance, and artifacts like PRDs and roadmaps? Can your newest team member explain how to live them in a tough decision? If not, you’ve found your next sprint.
You can follow Max on Twitter at @Max.
If you’re interested in learning more about how Cocoon makes employee leave easy, visit https://www.meetcocoon.com/
I recently sat down with Hareem Mannan, who was a product design leader at Segment for nearly four years, and joined Twilio as a Senior Director of Product, Enablement & Design following the company’s acquisition of Segment. As I reflected on the conversation through the lens of product management leadership, I saw clear patterns any design org can use to go from good to great.
We dug into her three pillars of what makes a great designer: a product quality ambassador, serve as the glue across product areas, and intricately understand the go-to-market motion. I break down why each pillar matters, along with practical ways I’ve coached designers and PMs to build these capabilities without slowing momentum.
First, being a product quality ambassador isn’t just about visual polish—it’s about product discovery rigor, clarity of problem definition, and crisp acceptance criteria that translate seamlessly into engineering execution. I look for designers who raise the bar in design reviews, connect craft to outcomes, and protect user experience end-to-end, not just at the surface layer.
Second, serving as the glue across product areas is the multiplier. The best designers broker alignment among product, engineering, marketing, sales, and support. They see around corners, anticipate dependencies, and drive coherence across journeys. In practice, this shows up in cross-functional collaboration during product roadmapping and sprint planning, where designers orchestrate trade-offs to maintain a cohesive experience.
Third, great designers intricately understand the go-to-market motion. When designers internalize how pricing, packaging, positioning, enablement, and adoption tie back to the product, they make higher-leverage decisions. I encourage teams to sit in on customer calls, shadow sales and support, and map product workflows to GTM milestones so the work lands with real users and real revenue.
We also discussed hiring. She takes me through her hiring loop and how she probes for core competencies in each of these three areas. I’ve found structured work samples, system-thinking challenges, and a cross-functional collaboration exercise to be strong predictors. She also flags some of her own mistakes she’s learned from as a hiring manager—such as over-indexing on visual craft at the expense of product sense, or underweighting GTM empathy. My adjustments: calibrate rubrics to value problem framing and decision quality, not just artifacts; include partners from engineering and solutions in the loop; and debrief on signals tied to these pillars.
On onboarding, her favorite rituals resonated with me. Pairing new designers with a solutions engineer accelerates context, builds credibility with customer-facing teams, and shortens the path to impact. Similarly, crowd-sourcing a “Dear New Designer” document captures tribal knowledge, expectations, and responsive norms in one living artifact—an elegant way to transmit culture and standards at scale.
We then turned to leading a high-impact design org. She unpacks the aha moment that her fear of micromanaging had unintended consequences. I’ve seen this too—hands-off leadership can drift into ambiguity and uneven quality. The antidote is intentional structure: office hours for fast feedback, lightweight checkpoints for consistent quality, and team bonding events that reinforce shared taste and high standards. Done well, these rituals create autonomy with alignment—and a consistently elevated bar for design quality.
To learn more about the “Dear New Designer” onboarding document, visit Hareem’s Medium page: https://medium.com/segment-design/dear-new-designer-1fd006fc7390
You can follow Hareem on Twitter at @hareemmannan.
I’ve been reflecting on the story of Zach Kitschke, CMO of Canva, an online design and publishing tool. Since launching in 2013, Canva has grown from an Australian startup to a global company, with 60 million monthly active users, over 2,000 employees, and a $40 billion valuation. As a product leader, that trajectory is a masterclass in product management leadership, product-market fit lessons, and deliberate go-to-market execution.
Zach was one of Canva’s first employees, leading comms efforts around their initial launch and fundraise. But since then, he’s done everything from answering support tickets and cooking the team lunch, to serving as a product lead and spinning up the people function. That range resonates with my own experience in high-growth environments: early operators wear many hats to unblock the work and accelerate learning loops.
This career history gives Zach a unique vantage point on why Canva worked. I zero in on the early days — from unpacking all the work that went into their launch, to how they improved the early product and focused on the use case for social media managers and content creators. To me, the insight is simple and powerful: obsess over a clear initial ICP, deliver undeniable value for content creators, and let word-of-mouth amplify your early wins. That’s product discovery in action, supported by tight product roadmapping and sprint planning that prioritizes outcomes over output.
Next, I dig into supporting and scaling the team during hypergrowth. Canva has several unique practices around onboarding, learning and development, and keeping the team connected — from vision decks, strategy docs and a specific skills framework, to their ‘chaos to clarity’ spectrum and ‘season opener’ ritual for making company planning more fun. These practices make culture operational: they align teams on strategy, reduce ambiguity, and create repeatable rituals that sustain speed without burning people out.
From a leadership lens, I appreciate how these mechanisms turn tacit knowledge into shareable playbooks. Vision decks codify narrative; strategy docs create traceability; the skills framework clarifies expectations for IC to manager transition; and the ‘chaos to clarity’ spectrum gives product teams a shared language to navigate uncertainty. This is the scaffolding great product organizations rely on to scale quality, autonomy, and accountability.
Zach also shares what he figured out personally along the different chapters in his career at Canva, including how to leverage advisors and when to bring someone else in to take over your role. I’ve found those two moves to be force multipliers: advisors compress time to insight, and timely succession unlocks what the business needs next. Whether you’re a marketer, a founder, a people leader, or a product manager, there are tons of helpful takeaways for everyone here.
I was energized by the depth and clarity in this conversation. Today’s episode is with Dharmesh Shah, the co-founder and CTO of Hubspot. In today’s conversation, we deeply explore some of the marquee moments along the 15-year journey building Hubspot. From my vantage point leading product at HighLevel, Inc., I zero in on what product leaders can operationalize right away: co-founder alignment, deliberate operating systems, and engineering-driven culture.
Early in the discussion, Dharmesh unpacks the very specific way he and his co-founder Brian Halligan approached evaluating their compatibility as co-founders. As someone who has built and led cross-functional product organizations, I appreciated the rigor behind this compatibility testing—clear expectations, explicit decision rights, and pre-agreed escalation paths. My takeaway for potential founding pairs: align on values and working agreements up front to increase the likelihood of success and smoother sailing.
What keeps Dharmesh engaged after all these years are foundational building blocks that make the role intrinsically rewarding. I loved his approach to eliciting feedback through “bug reports.” Treating leadership behaviors and team processes like software defects creates a safe, systematic way to surface issues fast. Equally compelling is his decision to never take on any direct reports and remain an individual contributor as a co-founder; IC leadership can be a force multiplier when the organization designs clear ownership boundaries and high-bandwidth interfaces.
The most striking arc in the conversation is how he came to own culture at Hubspot, even as the self-described least social person at the company. He walks us through how he approached culture as an engineering exercise, which continues today in his assessment of the culture as a product. As a product creator, I resonate with this framing: culture needs a roadmap, measurable outcomes, and tight feedback loops—exactly the mechanisms we use to build world-class products.
For product leaders and founders, the practical playbook is clear: test co-founder fit early and explicitly, invite “bug reports” to de-risk blind spots, design IC leadership paths alongside managerial tracks, and engineer culture with the same rigor you bring to the product. These patterns improve product-market fit internally—within your org—long before they amplify results in the market. That’s the compounding advantage I aim to cultivate every day.
I recently sat down with Adrian McDermott, CTO of Zendesk, for a candid conversation on how to scale product and engineering without losing the essence of what makes the product great.
Adrian started at the company back in 2010, when they were only 50 employees. Since then, he’s led product management and engineering teams as the company has gone public and scaled to over 5000 employees. I’ve long admired how that trajectory blends product management leadership with operational rigor, and I wanted to unpack the systems behind it.
We began with the classic scaling fork in the road: double down on what’s working or make a change. In my experience, this decision rarely fits a simple binary, and I asked how he navigates it in practice. He went much deeper than the “what got you here won’t get you there” advice you hear all the time in startups, outlining how to read momentum, market signals, and organizational readiness before flipping a switch.
Next, we explored the tension between venturing into new product areas and keeping the central product brilliant. He shared how they use the zone to win frameworks at Zendesk. I contrasted that with my own approach to product discovery and product roadmapping and sprint planning: protect core experience quality with clear guardrails while allocating explicit capacity for bets that expand the addressable problem space.
We then dug into the evergreen dilemma of whether to build or to buy. He walked through the origin stories of several Zendesk products, from the wins to the lessons learned. His take on the role of competition in product strategy and his definition of a truly great product resonated with me. For my teams, I evaluate buy vs build decisions through a simple lens: strategic differentiation, speed to validated learning, total cost of ownership, and ecosystem leverage; if the capability isn’t core to our unique advantage, I bias to buy and integrate, then instrument relentlessly.
In the back half of our conversation, he shared what he’s learned leading both product and engineering teams, along with practical go-to-market lessons that shape how features actually land with customers. We ended on team building and recruiting. Adrian’s interviewed more than a thousand engineers, and I appreciated the way he adapts hiring profiles and loops to the phase of scale—tight generalists early, then rigor around outcomes vs output as the organization matures.
If you’re scaling a SaaS product, you’ll find actionable insights here: how to avoid false trade-offs, decide when to preserve the core versus explore, operationalize zone to win frameworks, and make smarter buy vs build calls that accelerate learning and customer impact.
As a product leader, these lessons reaffirm a simple truth: sustainable growth comes from deliberate portfolio choices, clear go-to-market alignment, and consistent, values-based hiring that raises the quality bar with every new teammate.
I’ve helped hundreds of early-stage startups build their positioning and brand strategy from the ground up, and certain patterns show up again and again. In this reflection, I’m sharing six early marketing missteps I see most often — plus the practical fixes I use with founders to sharpen positioning, clarify messaging, define brand personality, and orchestrate a high‑leverage launch strategy.
Early marketing can feel like changing the tires while the car is moving. You’re chasing product‑market fit while trying to define a category, articulate company purpose, and build a founder‑led GTM motion that actually converts. The good news: with a few repeatable exercises and a clear sequencing of work, you can avoid costly detours and get to traction faster.
Misstep 1: Chasing category creation too early. Defining a new category is tempting — it feels bold and visionary — but it’s often premature before you’ve nailed a sharp, undeniable problem. My fix: earn the right to a category by first winning a specific use case. Anchor your product positioning to an existing mental model customers already understand, then introduce the “newness” as a step‑change, not a wholesale reinvention. Category creation is a byproduct of repeated wins, not the starting line.
Misstep 2: Treating company purpose as a tagline instead of a true north. A purpose that doesn’t inform roadmap, pricing, brand personality, and go‑to‑market is just wall art. My fix: write a one‑sentence purpose that states who you serve, the change you enable, and why it matters — then pressure‑test every strategic decision against it. If it doesn’t help you prioritize features, target segments, or channels, it’s not actionable enough.
Misstep 3: Leading with emotional benefits while burying functional proof. Emotion matters for brand-building, but in the zero‑to‑one phase, customers buy outcomes. My fix: articulate a crisp value proposition that pairs functional benefits (time saved, errors reduced, revenue unlocked) with specific, credible proof points. Use customer‑validated messaging built from interviews, jobs‑to‑be‑done, and real usage data. Earn the right to emotion by proving the outcome first.
Misstep 4: Allowing brand personality to drift from the product and buyer. When brand voice doesn’t match the problem space or ICP, trust erodes. My fix: choose three core personality traits (for example: authoritative, pragmatic, optimistic) and define both what they are — and what they are not. Audit every touchpoint — website, onboarding, sales enablement, docs — to ensure consistency. This creates a brand people recognize and rely on across the funnel.
Misstep 5: Obsessing over other startup competitors instead of the status quo. The biggest competitor for most startups is inertia — spreadsheets, duct‑taped workflows, or “do nothing.” My fix: frame your positioning against the current workaround first. Show the switching ROI clearly, then differentiate from adjacent vendors. Use side‑by‑side comparisons that include the baseline status quo, not just other tools.
Misstep 6: Expecting PR to be a growth strategy. Launch theater can generate a spike, but it rarely produces sustained pipeline. My fix: treat launch as a process, not an event. Warm up your ICP with problem‑led content, customer stories, and social proof. Invest in owned channels (email, SEO, community) that compound. Set media expectations appropriately and measure what matters: qualified demand, activated users, and retained revenue.
To operationalize all of this, I use a simple positioning framework that keeps teams aligned: for [who], who [have this need], our [product] is a [category] that [delivers this outcome], because [proof]. Then we stress‑test with customers until the language is repeatable, the benefits are measurable, and the story is unmistakable across sales, marketing, and product.
If you want to go deeper into startup brand strategy, positioning, and messaging, I recommend these articles:
Founders who avoid these traps — and sequence brand strategy, product marketing, and go‑to‑market with discipline — build momentum faster. Do less launch theater, more customer‑validated messaging. Less category hype, more proof. That’s how you create a brand that compounds.
I’ve spent years building and scaling products, and I continue to see one pattern derail even the most talented teams: a disconnect between product strategy and what product teams actually work on day-to-day. In this deep dive, I share how I bridge that gap with a practical, battle-tested playbook I’ve used to align teams, accelerate impact, and power growth at scale.
I start by getting brutally clear on the real work my teams are doing versus the outcomes we’re aiming for. Too often, teams are busy shipping features that don’t ladder up to strategy. The fix isn’t more process—it’s sharpening the connective tissue between strategy, planning, and execution so every sprint advances a clear, long-term narrative.
At the core of my approach is the product strategy stack: company mission, company strategy, product strategy, product roadmap, and product goals. When each layer is explicit and connected, prioritization becomes straightforward, trade-offs are defensible, and the team understands not only what we’re doing—but why it matters. I treat this stack as a system, not a document, and I revisit it frequently with my leads to ensure decisions remain aligned.
Here’s how I operationalize it. I anchor every planning cycle in the company mission and company strategy, then translate that into a crisp product strategy that defines where we will play and how we will win. From there, the product roadmap becomes a sequencing tool for outcomes, not a wishlist of features. Finally, I define product goals that are specific, measurable, and clearly tied back to the strategy—so everyone can see the throughline from mission to metrics.
When it comes to goal-setting, I prefer an alternative to traditional OKRs: NCTs. Outlining narratives, commitments, and tasks sidesteps some of the most common headaches when it comes to OKRs. The narrative clarifies the why, the commitments define the measurable outcomes we’re on the hook to achieve, and the tasks capture the critical work we believe will get us there. To implement NCTs, I pilot them with a single squad, ensure each narrative maps to the product strategy, pressure-test commitments against leading indicators, and keep tasks flexible as we learn.
Strategy is often misunderstood and has come to mean all sorts of different things. I’ve found that clarity around terms like “mission” and “vision” changes everything. Mission is enduring and customer-centered; vision is a vivid, time-bound picture of the future we’re building. When teams grasp the difference, alignment snaps into place. I’ve seen this playbook resonate across industries and company stages—from category leaders like Tinder and TripAdvisor to fast-growing startups—because it turns abstract strategy into concrete choices and accountable execution.
If you’re looking to uplevel product management leadership and bring more focus to product discovery and delivery, start by assessing your product strategy stack, then pilot NCTs in your next quarterly planning cycle. Tie every roadmap item to a narrative, stress-test commitments with real metrics, and empower teams to adapt tasks as insights emerge. The result is a more resilient roadmap, tighter alignment, and a team that consistently ships what moves the needle.
