💡

InsightHunt

Hunt the Insights

D

Dharmesh Shah

Episode #75

Co-founder and CTO

HubSpot

🎯Product Strategy🚀Career & Leadership👥Team & Culture⚡Execution

📝Full Transcript

20,615 words
Dharmesh Shah (00:00:00): Some of the best startup advice I've heard is startups should focus on one thing and be really, really exceptionally world-class at that one thing. And one of our early zigs is we are going to do exactly the opposite of that. Lenny (00:00:11): You have no direct reports and I don't believe you've ever had direct reports at HubSpot? Dharmesh Shah (00:00:16): I could become passively okay at management with some training, with some coaching. I don't want to spend any years of my life becoming passively okay at something. Lenny (00:00:23): What was that process like to define the culture? Dharmesh Shah (00:00:26): My co-founder and I were having one of our founders meetings and he said, "Oh, Dharmesh, I hear this culture thing is really important. By the way, can you go do that?" I'm like, "Okay. Brian, of all the people in all the company, is like, I am the worst possible person." It's not that I don't like people, I just don't like being around them a whole lot. Lenny (00:00:40): Something that's really unique and interesting about you is you're obsessed with comedy and keynote prep. Dharmesh Shah (00:00:44): It comes down to this metric that stand-up comedians use called LPM laughs per minute. I have custom software that I've written that will say, "Okay, here are the points at which the audience laugh." Lenny (00:00:57): Today my guest is Dharmesh Shah. Dharmesh is the co-founder and CTO of HubSpot and also one of the most fascinating and first principled thinkers I've ever met. In our conversation, we cover a lot of ground. Dharmesh's hilarious and ingenious approach to putting together a talk, including measuring laughs per minute, his biggest lessons from being a public company exec for over 10 years now, especially while being a startup guy at heart, how he approached creating and scaling the culture of HubSpot, which you'll find both hilarious and inspiring. (00:01:28): Why founders and product teams are all fighting the secon...

💡 Key Takeaways

  • 1Treat culture as a product: Iterate on it like software using feedback loops (NPS) rather than trying to 'preserve' it.
  • 2Fight organizational entropy by imposing artificial constraints, such as the 'one feature in, one feature out' rule during early growth.
  • 3Use 'Flashtags' (#fyi, #suggestion, #recommendation, #plea) to clarify the intent and required action of your communication.
  • 4Evaluate ideas by calculating Potential first, then Probability, to avoid filtering out high-upside opportunities too early.
  • 5In SaaS, 'reverse gravity' naturally pulls companies upmarket; staying focused on SMBs requires fighting this force intentionally.
  • 6Apply 'Dimensional Complexity' thinking: The cost of a new product line isn't just development time, but the exponential complexity added to every future decision.
  • 7Public speaking is an engineerable skill: Optimize for 'Laughs Per Minute' (LPM) to maintain audience retention in high-stakes presentations.

📚Methodologies (4)

🎯 Product Strategy

A quantitative approach to weighing opportunities that forces a separation between the size of the outcome and the likelihood of success, preventing risk aversion from stifling innovation.

Core Principles

  • 1.Step 1: Estimate Potential (0-10). Ask 'If this works, how big could the outcome be?' Do this before assessing risk.
  • 2.Step 2: Assess Probability. What is the likelihood of success? Don't use low probability to kill high-potential ideas (Expected Value = Potential × Probability).
  • 3.Step 3: Evaluate Passion/Proximity. Do you care enough about the problem? Are you close enough to the customer pain?
  • +1 more...

"If you apply a filter that says, 'Oh, I only have a one in 10 chance to pull this off... not going to do that.' Well, if it's a one in 10 chance at 10 billion, it might be worth it."

#opportunity#strategy#product
View Deep Dive →
🚀 Career & Leadership

A system of explicit tags used in written communication (email, Slack) that clearly defines the expected weight of the feedback and the required response level.

Core Principles

  • 1.#fyi: 'I found this interesting. No response expected. Go on with your life.'
  • 2.#suggestion: 'A thought I had. You don't have to do it, but consider it. No response required.'
  • 3.#recommendation: 'I have researched this. I would do this if I were you. If you don't do it, I expect a response explaining why (to foster learning).'
  • +1 more...

"The challenge is people will take [an opinion] and over-index on what was an opinion... Flashtags are an escalating set of the 'dying on the hill' spectrum."

#flashtag#communication#protocol
View Deep Dive →
👥 Team & Culture

Treating company culture as the 'product' you build for employees (your customers). Just as you wouldn't freeze code on a product, you shouldn't freeze culture.

Core Principles

  • 1.Step 1: Run Employee NPS. Measure employee satisfaction quantitatively (0-10) and qualitatively (Why?).
  • 2.Step 2: Identify Bugs. Treat cultural complaints as 'bugs' in the product. Publicly acknowledge them at all-hands meetings.
  • 3.Step 3: Fix or 'Won't Fix'. Commit to fixing valid bugs, or explicitly state 'It works as designed' (e.g., 'Yes, transparency is uncomfortable, but it's a feature, not a bug').
  • +1 more...

"Every company builds two products: one is the product they build for their customers, and the other is a product they build for their team. That's what culture is."

#culture-as-product#team#culture
View Deep Dive →
⚡ Execution

A deliberate imposition of artificial constraints and simplification rules to counteract the natural organizational drift toward complexity.

Core Principles

  • 1.Step 1: Acknowledge the Drift. Accept that without intervention, the company will become slower and more complex.
  • 2.Step 2: Impose Artificial Constraints. Use binary rules to force simplicity (e.g., 'No meetings before 11am' or 'One feature in, one feature out').
  • 3.Step 3: Calculate Dimensional Complexity. When adding a new product line, factor in that *every* future decision (hiring, marketing, reporting) now requires a decision between Product A and Product B.
  • +1 more...

"Complexity does kill companies... It's never too early to plant the seeds of simplicity."

#entropy#defense#mechanism
View Deep Dive →
← Browse All Episodes