Sharp Problems, Real Virality: Oji Udezue's Playbook for Product-Led Growth

Udezue starts from the premise that the last decade of product thinking, with its lean and fail-fast methods, over-corrected toward process. He argues that customer science is not the answer to everything, since otherwise OpenAI would never have built anything, so the problem space still predicts a great deal about success. To make that concrete in B2B SaaS, he sorts workflows along two axes: how many departments use them and how often they are run.

Tools everyone uses daily, such as email, Slack, Notion and Confluence, are the most profitable but the hardest to enter because Microsoft and Google dominate them. Tools aimed at one department that is in them every day, like Jira, recruiting software, martech and sales tech, form what he calls the high-frequency niche. That quadrant is where B2B SaaS really thrives, and landing in one of the two top quadrants with an important problem can lead to a billion-dollar company.

The framework is not a fixed destiny, Udezue stresses, and strategy means moving toward higher frequency or wider reach. Atlassian is pushing from high-frequency niche toward everyone through Confluence. Typeform, which he places in the low-frequency quadrants, is trying to become the first tool marketers and salespeople think of for customer-facing interactions, a move he compares to what Qualtrics and SurveyMonkey are attempting.

Udezue describes product management as matching technology to humans, and says people only pay for things that shrink their workflow or give them a superpower. His "zone of benefit" says the improvement has to be noticeable. A product that is 20% better usually registers with nobody, so it needs to be at least two or three times better before people care enough to part with money.

The same idea helps locate the ideal customer profile. Your best customers are not price sensitive because they fundamentally get the value. Once a startup has an audience of a hundred or more people, he says, it should watch for those who clearly care, and that tells it who to target.

He then runs through his own examples. Atlassian's ICP is developers and tech teams, and Calendly's is people who schedule with outsiders for business reasons, such as salespeople, marketers and recruiters. Typeform's is marketers, product people and UX people who want the web to feel conversational. Twitter, he says, had a hidden business side, since about 30% of its customers were media organizations like the NFL, the NBA and HBO, and a bifurcated consumer ICP of experts with something to say and people who want to connect with them.

Udezue says he collects frameworks, which he prefers to call mental models, because they package dense thinking into a shortcut. But he insists that product people should understand the fundamentals behind them, the way a mathematician can derive the equation. Product management is not a science, he says, and programming is not really one either, so the art of building a profitable software company is full of uncertainty and timing issues.

As an investor and advisor, he gives different advice to companies that are just starting, in the middle or scaling, and he makes the same distinction throughout the book he is writing. People who understand the fundamentals can adapt a framework to their stage and problem. He sees many people using frameworks blindly and considers that harmful to them and to their businesses.

The book, which he describes as product management for product-led growth, rests on his bet that even enterprise companies will drift toward consumer-style product management over the next decade. Using the product itself to sell its value is, in his view, the shift from how products were built twenty years ago. The title is still undecided, with his original idea, "Building Rocket Ships", competing against a wide range of suggestions from his audience.

A sharp problem, Udezue explains, is one that steals customers' time, energy, money or focus, and that many people feel intensely enough to pay to fix. The best founders have felt the problem themselves and know that millions share it, as opposed to a pain only 100,000 people mildly care about. He has built a startup on a non-sharp problem and says working on a sharp one is a huge tailwind, because customer obsession can carry you through mistakes that would otherwise kill you.

Asked for a counterexample, he points to mmhmm, the pandemic-era video camera tool from a venture studio tied to an Evernote founder. It was fun, he says, but it did not change the world of your Zoom camera or your collaboration. For a founder in the trenches, he suggests drawing the customer's current workflow and the workflow after using your software as two horizontal lines, then measuring whether the second is two or three times shorter.

After launch, he recommends talking to the most enthusiastic customers and deriving their before and after workflows. He also mentions the "whites of their eyes" test, where people get visibly excited or spontaneously ask when they can pay. But he is wary of excitement alone, saying it can be noise, and trusts workflow compression more than nods and dilated pupils.

Udezue separates three activities. Discovery is targeted research on a specific workflow you want to improve. Continuous conversations mean customer calls land automatically on the calendars of PMs, designers, engineering managers and product marketers, because "the death of customer discovery is friction" and individuals asked to do it themselves will not.

The third activity is customer listening, which he plans to talk about at an industry product conference. It means collecting signals that already exist, including social posts, app store reviews, G2 reviews, churn surveys, NPS verbatims, bug reports, Zendesk tickets and closed-lost notes in Salesforce. One of product management's big goals, he says, is processing those signals efficiently, and at Calendly he built a rig with workflows and Slack where people triaged them.

Lenny mentions Teresa Torres's tactic of a site popup that links to a Calendly booking, and Udezue says Calendly did this in its community. The catch is that you need to target the right customers, since talking to one is useless and talking to a hundred is valuable. He notes it works especially well in activation or conversion journeys, because people who have already churned rarely want to talk.

For Udezue, onboarding substitutes for sales and account management across millions of customers, and the goal is to approximate a friendly, approachable human. He says it is an exercise in the psychology of an evaluator who arrives knowing nothing and gradually builds confidence, so inspiration is better drawn from offline retail than from other software. The journey runs from understanding the value proposition, to checking simplicity, to kicking the tires, to making the decision.

He splits onboarding into a mandatory setup and an optional layer. The mandatory part should be spare, ideally no more than three screens, and at Calendly it covered connecting a calendar and setting default hours. Optional material should be available at random access for people who want help later. His experience is that wizards have limited benefit, while one or two examples of what good looks like work well because they are mimetic, and clarity about where someone is in a trial helps conversion.

On activation, he says Calendly and Typeform each use three escalating thresholds. At Calendly, it is creating a first meeting and then five within a week, while Typeform looks at publishing a form, getting responses and viewing insights. At Twitter the key milestone is following someone or being followed, because the follow graph is how people build an informal community around what they are passionate about.

Udezue defines a network effect as value that accrues to passive members when others join, and ties it to critical mass. With enough people already there, more people want to come, regardless of anyone's effort. He calls it the most powerful feature a product can have, and notes that the last telegram was sent in 2016, more than a hundred years after the invention, and had to be shut down manually.

Twitter, in his view, is the perfect case study. Lenny points out that Elon Musk's team stripped away the brand, about 80% of the staff and much else, leaving mostly the network effect, and Twitter did not die even when Threads arrived. Udezue says he saw it as the best example he has encountered in a Berkeley business school course on technology companies.

The real vulnerability, he argues, is on the revenue side. If advertisers left, people would keep coming, but the money to improve the network would vanish, producing a negative spiral. He expects Threads to prosper because it can win through the advertising revenue spiral, as Facebook's ad marketplace is far easier to access than Twitter's.

Udezue says virality is not a tagline at the bottom of an email but high-quality word of mouth, where customers market your product for you. Products that chase "synthetic virality" fail if users arrive and the product is poor. Hotmail succeeded because webmail solved real problems, Uber spread because it compressed the workflow of getting a cab, and Slack spread through lunchtime conversations between floors despite having no viral mechanics.

His recipe is to build a great product that solves a sharp problem and only then add referral tactics. Calendly won against earlier scheduling tools such as Acuity because it was so simple and respectful of the invitee's time that the virality actually worked. Customer support, signing documents, network effects like Calendly's green availability dots and execution quality all contribute to net virality, but the foundation is the product.

He frames virality as customer-augmented marketing, which lets a company spend less on marketing or reinvest the savings in the product. Atlassian, he says, spends perhaps 10 to 20 percentage points less on marketing than comparable competitors because of virality and network effects. Customers either push, shame or create FOMO in others to adopt the tool.

Udezue says operators are so absorbed in the tug of war that they lose the bird's-eye view he can take as an advisor. "Forest time" is deliberate time, in a week or a month, to see the forest rather than the trees and spot alternative paths around current problems. He has published a workflow document for it and creates the time for his executive team too, since PMs in particular swing between shaping problems and captaining execution.

In practice, he gives his team a full day or two at month's end to complete a worksheet, which is not just a round of golf. Managers may ask why people get a day off, but he says it is about working smarter, since a wrong aim can waste one or two million dollars of people's time. Forest time, he says, should improve your aim before the big investment.

He also draws lessons from his time at Bridgewater Associates, where he sat in senior management. The company records meetings and had a dot collector for rating people in real time, which he found theoretically sound but emotionally exhausting. What he took away is that Bridgewater evaluates people on skills, attributes and values rather than skills alone, and he now looks for all three when interviewing.

Udezue observes that engineers have agile and pair programming, and designers have design thinking and sprints, but product and business work has no named abstraction for organizing itself. He is co-creating a "product system" framework with his wife, Ezinne, that could be boiled down to a checklist of the systems a cohesive R&D organization needs. He teases it without going deep, saying someone else will probably cover it more fully.

In the lightning round he recommends *The Halo Effect* for deconstructing business books built on storytelling and form-fitting evidence, along with the science fiction classics *Dune* and *Foundation*. His favorite interview prompts are asking candidates to introduce themselves, then to describe what they are great at and what they need to learn. His current product pick is Unlocks, a one-person tool that logs him into his Mac by detecting his phone.

His life motto is that there is more knowledge outside his head than inside it, which he calls a plea for curiosity, skepticism and humility. His three guiding principles are originality, curiosity and wisdom. He publishes on Substack, is on Twitter, and plans a freemium book, with a free version aimed partly at readers in Africa and India, and invites people to sign up for updates and join a pre-read.