This Week #2: Tackling the chicken-and-egg problem, building a growth team from scratch, and addressing overlap with PM peers 🤔
Welcome to the third edition of the Q&A series! Thank you for all of the feedback and kind words so far. It means a lot. 💛
Keep the questions coming! Anything you’re struggling with at work around business growth, personal growth, building product, people issues, management, org design, or communication is game. If I don’t have anything insightful to say on a topic, I’ll find someone amazing to help answer your question.
New addition this week: A bit of inspiration for your week ahead at the end of each newsletter.
If you’re finding value in this newsletter, please share it with a friend and click the little gray heart above. The bigger this community gets, the more we all learn.
On to this week’s questions…
Q: When creating a new product, what are some strategies and tactics for minimizing the cold start problem — making the product useful with zero users and data?
I’ll assume your product involves a marketplace, since that’s where “cold start” (a.k.a. chicken-and-egg) problems are most common.
Based on many conversations with folks at about a dozen marketplace companies, these five tactics seem to be the most common solutions to the chicken-and-egg problem:
Single-player mode: Make your product immediately useful to one side of the marketplace, which seeds that side and then draws in the other side. Examples: OpenTable handling reservations for restaurants before getting into guest discovery — bootstrapping supply, GrubHub scanning restaurant menus and putting them online — bootstrapping demand.
Pay one (or both) sides: Instead of relying on the marketplace to support both sides immediately, pay the supply or demand to stay in your marketplace. Examples: Lyft and Uber paying early drivers a salary, and also giving early users free credits.
Employees are early supply: Have your employees offer the service early on. Examples: Airbnb founders hosting their apartment, Rover employees doing dog-sitting.
Focus on one market: If your service is location-specific, you’ll need to solve the chicken-and-egg problem in every market. To make your life easier, start with getting critical mass in just one market. Examples: Rover in Seattle, Airbnb in NY.
Focus on one niche: Similar to the above, for companies that aren’t location-specific, pick a niche and build critical-mass around it — then expand out. Examples: eBay and Beanie Babies, Eventbrite and tech events.
In most cases you’ll be supply constrained from the start (you need something to sell after all), thus most of the solutions focus on growing supply.
Q: I recently started a new product manager role and some of my work overlaps with a technical program manager that's been with the company much longer. There's been some tension because of that overlap — I'm wondering how to manage that relationship and make it effective so we work together productively.
Tricky spot. Not only do you have to deal with the traditional fuzziness of a product manager’s role, you’re also dealing with the power of tenure and history within an org. Labels like product manager, program manager, and project manager can mean substantially different things at different companies, and there’s no hard rule that says you get to do X if your title is Y. However, in the abstract, a program manager has a meaningfully different skillset from a product manager, and thus there should be a distinction between these roles and the people you hire to fill them. At the risk of not getting these totally right and upsetting people, here’s how I think about these three roles:
Project Manager: Responsible for project success. This includes making sure everyone is aligned around the same deadlines, that the right people are talking when they need to be, and that the project launches on time. Success generally means these projects launch on time and under budget. Projects, unlike products and programs, are one-off and come to an end.
Product Manager: Responsible for product success. Examples of products include the Substack website, the Google Maps mobile app, and the Slack onboarding flow. Success means these products drive business impact. This role often encompasses the project management responsibilities and includes a direct relationship with the people building product — engineers, designers, researchers.
Program Manager: Responsible for program success. Examples of programs include running the Bird scooter charging program, the Airbnb Superhost program, and the Lyft ambassador program. What’s the difference between a product and a program? In my view, it’s whether the core of the work is building a product (i.e. working with engineers, designers, researchers), or using existing products (i.e. working with ops, sales, marketing), respectively. What’s the difference between a program and a project? This is even fuzzier, but generally, a program is made up of multiple projects and requires longer-term thinking.
With that out of the way, here’s my advice for how to find clarity in your specific situation:
First, try to work it out the person directly — If at all possible, talk to the person about this one-on-one first. I bet you they are feeling the same frustration. Point out that you want what’s best for the team (and company), you’re feeling hampered and frustrated with a lack of clarity around your roles, and that you’d like to resolve this to make both of your lives better. If you can get to a place you are both happy, then codify it and share this with your manager(s) — it’s important that they’re also aligned with your worldviews.
If that doesn’t work, go to your manager(s) — If you don’t think the first option will work, or you’ve tried and it failed, then talk to your manager (and possibly their manager). Share concrete examples of where you see overlap, the negative impact this has been having, and your perspective on how to address it. Lean on them to clarify roles with you and the other person (and their manager). Don’t be afraid to bring this to their attention early — in my experience, these things rarely get worked out without a manager being involved.
Differentiate between historical roles vs. ideal roles — Encourage everyone to take a step back from what the world is today and to think about what the ideal roles and responsibilities for each role should be. As you scale your org, what should program managers be responsible for, and what should product managers be responsible for? What kind of skillsets should you hire for in each? What is the career progression for each role? Work backward from that ideal.
Avoid waiting for the perfect answer — As a corollary to the above, don’t wait for all of the details to be worked out before you make changes. This can often take months (or years.) Instead, figure out the biggest issues, align on a few improvements, and act on them.
Consider changing titles or teams — Maybe this program manager should be a product manager? Maybe you two should be on different teams? Think about the best long-term change, not just short-term solves.
The worst thing you can do is nothing — these kinds of things rarely get fixed organically. So I’m glad you are recognizing that this issue, and working to resolve it. Keep at it!
Q: How do you build a growth team from scratch?
Read these three essays and you’ll be on your way:
A few additional thoughts:
Everyone in a company should feel responsible for helping it grow — from the CX team to the IT team to the product team. Though it’s extremely valuable to have a dedicated growth team (you should have one), don’t ever think you can delegate growth to just that one group.
Early on, focus on the things that can give you 2x - 10x growth. Unless your product is designed to grow through viral loops, a % increase in conversion in the early days isn’t going to have the best ROI.
In most cases, once you’re retention is healthy, your biggest growth wins will come from the top of the funnel. You should put a significant portion of your budget and resources there. This includes things like referrals, performance marketing, SEO, and landing page optimization.
A bit of inspiration for the week ahead:
How the economy works by Ray Dalio - Learned more about the economy in 30 minutes than I have in 30 years
Tycho's sunrise set at Burning Man - Live from the Dusty Rhino in Black Rock City