Menu

Posts tagged “startups”

The primary cause of disruption, and how incumbents should respond

Thales S. Teixeira distills years of research on how companies are disrupted in his HBR article Disruption Starts with Unhappy Customers, Not Technology:

For eight years I’ve visited leading companies in more than 20 industries around the world that claimed to be in the process of being disrupted. Each time, I’d ask the executives of these incumbent companies the same question: “What is disrupting your business?” No matter who I talked to, I would always get one of two answers: “Technology X is disrupting our business” or “Startup Y is disrupting our business.” But my latest research and analysis reveals flaws in that thinking. It is customers who are driving the disruption.

He goes on to explain why disruption is a customer-driven phenomenon, and how incumbents should respond.

How to talk to customers: lessons from a journalist

I usually stay away from article titles like these, but I thoroughly enjoyed Chris Cannon’s What a Journalist Can Teach Lean Startups about Customer Interviews. If you talk to customers at all as part of your work, in any context, this is a goldmine of good advice:

Problems are stories — it’s a dull tale that has no conflict to resolve. The customer on the other side of that table is the protagonist in their own adventure. We’ve selected them as a persona that might be interested in casting us as their hero (or even in a supporting role that lets them be the hero of their own story).

So be accommodating: Engage the customer on their terms. Be perceptive: Listen for gaps in the customer’s story that might be worth investigating further. Be a listener: Only talk to make the customer comfortable or to dig for details. And then shut up.

Amen to that.

Guy Raz: Innovation lessons from famous entrepreneurs

My kids are obsessed with the podcast Wow in the World (and, to be fair, it’s really good). Guy Raz is such a goofball on that show that it was a little weird to see the headline Guy Raz: Five Lessons PMs Can Take From Famous Entrepreneurs. But I thoroughly enjoyed Laura Baverman’s write-up of one his recent talks at the first ProductCraft conference. He gives several recommendations for PMs on how to run successful products, including “Focus on What’s Different, Special, or Better Than Anything out There”:

Advisors to Allbirds were concerned that launching just a single shoe design in only four colors was a recipe for failure. To succeed in the direct-to-consumer retail market, they’d need to provide options for shoppers, those experts said.

But founders and co-CEOs Tim Brown and Joey Zwillinger were most concerned with creating a superior product—an environmentally-friendly shoe made of superfine Merino wool. They were convinced that getting these values right would help them sell the shoes, and expansion into other types of shoes or products would happen from there.

They were right. Within 30 days of launch, they sold out of a year’s worth of inventory. Three years later, the company is valued at $1.4B, and according to Raz, still offers something better than anything else comparable. Allbirds ignored what the competition was doing and create a truly differentiated product.

There are some great lessons in these stories.

How to effectively onboard additional team members on a customer’s primary account

This is a helpful article from Jeff Vincent about the “nth user problem”. This is a not-so-great term for a very real problem: how to make sure you’re able to effectively onboard additional team members on a customer’s primary account. From SaaS has an nth user problem:

A huge driver of churn in the most successful SaaS businesses is loss of champion churn — or when your product’s greatest advocate within a customer company moves on to another job or department and the replacement admin abandons your product in favor of a new platform. This is the end result of the nth user problem at work.

Jeff shares lots of good advice on how to take care of additional account users and make sure they become engaged users and advocates.

Product growth relies on the right balance between optimization and innovation

Andy Johns wrote a 4-part series on product growth that is worth digging into. In Part 1: A Single-Minded Perspective on Growth he points out the trap many product companies fall into:

The point I’m making is that today’s startups very quickly fall into the optimization trap where they think future growth will largely come from optimizing their existing product. The better approach is finding the right balance between optimization and innovation since both methods can produce future growth.

This is why I am still, after all these years, such a big fan of the Kano model. It forces teams to think about these two questions separately: (1) what can we do to make our existing product better (optimization), and (2) what can we add to or change about our product to create unexpected value for customers (innovation).

Breaking down the multiple variables required to develop successful products

This interview with Ryan Hoover from Product Hunt on how to develop products people love is really interesting. For example, here he makes a really good point about the importance of systems thinking in product management:

Most products can be broken down into a math equation, where multiple variables need to be true for it to work. Many newer product managers don’t break this equation down as much as they should. Then, they don’t test some of their hypotheses soon enough. If you have x, y, and z, and you’ve figured out the x and the y but you failed to resolve z, then it won’t work.

Sometimes people focus on the easier things. They resolve two hypotheses that are easier to figure out, and then defer the last one. A lot of people don’t think about user acquisition. They think, “We’re going to build an awesome product, we’ll get press, and we’ll launch it on Product Hunt and that’s it.” They should probably reverse it — think about distribution and marketing first, and then figure out how to build that into the product itself.

I also love their approach to experimentation, which can basically be summed up as “do it as cheaply as humanly possible.” Great interview.

Culture/market fit is more important than product/market fit

I really like the NOBL team’s focus on Culture/Market fit in their article The Only Thing More Important Than Product/Market Fit:

Find yourself a healthy market, yes. Then develop a culture that can deliver product/market fit. Your culture is what produces your products and services. You know you have culture/market fit when both talent and customers flock to your company for who you are, even above what you make. You know you have product/market fit when legions of customers buy your product.

Without culture/market fit, sustainable product/market fit (at any size, scale, or maturity) is impossible.

They go on to describe four competing flavors of organizational culture, each with unique traits and competitive strengths.

Why it’s important to watch (and understand) your product churn

Shaun Juncal has a good overview of the importance of watching your churn numbers carefully in his post Churn: The Most Important Product Metric for SaaS. It’s especially important to figure out why people leave when they do:

But you can also learn something from that lost customer, namely why they left. Were they drawn to a competitor? Did the value your solution offered fade over time? Was a missing key feature causing them to bail out? Answering these questions can inform what should be done to retain your current stable of paying customers and attract new ones.

A simple churn number can’t tell you why someone leaves, so this is data that has to be collected qualitatively. But how? You don’t want to provide a negative user experience to customers on the way out, so putting a giant hurdle in front of them is not a good look. We solve this problem at Postmark by providing an optional text field on the page where you select your downgrade option:

I’m sure we would get more responses if we made this a required field, or turned it into a pop-up. But at what cost to negative perception would we do that? Following someone as they exit a store is creepy. Don’t be creepy.

Pinterest and the value of focus and moving slowly

Seth Fiegerman’s history of Pinterest and their approach to business and product is a breath of fresh air. In The anti-Facebook: Inside Pinterest’s slow and quiet rise, Fiegerman describes a company whose motto might as well be “move slow and debate things”:

Pinterest resisted throwing money at its problems, debated product tweaks extensively and did not rush to copy features that helped larger competitors achieve viral growth, employees said. Fond of touting itself as an anti-social media platform, Pinterest never introduced live-streaming or standalone messaging apps, nor did it become a primary hub for news. These features attracted press and users for other companies, but were also later abused by bad actors.

That is such a good example of a company that knows how important focus is. Their approach reminds me of Richard Rumelt’s succinct summary in Good Strategy, Bad Strategy:

Good strategy works by focusing energy and resources on one, or a very few, pivotal objectives whose accomplishment will lead to a cascade of favorable outcomes.

Product management lessons from the history of Evernote

Hiten Shah’s deep-dive into the history of Evernote is a very interesting read from a product management perspective. Of particular interest is the immense damage they inflicted on themselves due to a lack of focus on their core mission:

It’s hard to understate the damage that the branded products sold through the Evernote Market inflicted on the Evernote brand. It made absolutely no sense. Users didn’t want Evernote-branded tablet styluses or Evernote Moleskine notebooks or Evernote backpacks. They wanted an organizational and productivity product that worked.

The fact that the 2013 version of Evernote was widely considered the buggiest, most unstable version the company had released at that point added insult to injury. Rather than fixing the software problems that users actually cared about, Evernote started selling branded backpacks instead.

This is such a good example of the importance of knowing the core value of your product, and deepening that reach instead of trying to broaden into unrelated areas where you don’t have a core competency.