A product manager’s guide to web3

How PM'ing in web3 is different, the pros and cons of going web3, how to break in, and how to be successful—by guest author Jason Shah, head of product at Alchemy

👋 Hey, Lenny here! Welcome to a ✨ monthly free edition ✨ of my weekly newsletter. Each week I tackle reader questions about building product, driving growth, working with humans, and anything else that’s stressing you out about work. If you’re not a subscriber, here’s what you missed this month:

1. Lessons from 140+ angel investments

2. How to get promoted

3. What is good monthly churn

---

Q: I’ve been a PM for a few years and I’m thinking about getting into web3. How is PM’ing different at a web3 startup, and what’s the best path into web3?

With so many smart friends jumping into web3, this question has also been on my mind. The PM role is already so strange and varied—how does the web3 way of working change the role further? Is it fun to be a PM in web3? Are PMs even necessary?

To understand this myself, I reached out to my good friend Jason Shah, who I was lucky to work with at Airbnb for many years and who now leads product at Alchemy. Alchemy is essentially AWS for web3, and has quickly become a fundamental infra layer in the web3 startup stack. And just last week, the company announced a raise of $200M at a $10B valuation. Through Jason’s experience scaling Alchemy, working with hundreds of web3 startups in the process, and having just recently (and methodically) made the transition into web3, I knew Jason would be an incredible source of insight on the PM role in web3. He did not disappoint 🔥 Below, he shares the most in-depth guide to product management in web3 you’ll find anywhere. I learned so much about the wild and wonderful world of web3 from Jason, and I hope you enjoy it as much as I did.

In true web3 fashion, Jason minted the core artwork from this post, “WAGMI: Web2 PM Meet Web3 PM,” and will be auctioning it off to raise funds for Girls Who Code and PadawanDAO in a two-day OpenSea auction.

Thanks, Jason!

P.S. You can now hear this post in audio form:

---

If you hadn’t noticed, web3 is exploding. Everyone is talking about NFTs and DeFi, and investment and job postings in web3 both grew by more than 400% in 2021. What does that mean for you, anon web2 product manager? There are countless opportunities to make a big impact and grow your career by transitioning into web3. But it can be an opaque process and a risky decision. So let’s prepare you for web3.

In this article, we will explain three core concepts:

1. The unique attributes of a web3 PM

2. The advantages and disadvantages of PM’ing in web3

3. How to make the transition into web3

Let’s get into it.

How is PM’ing different at a web3 startup?

Web3 product managers are still cross-functional leaders driving outcomes, but web3 product management is different in three primary ways:

1. It’s more versatile

2. It’s more art than science

3. It’s more public

It’s more versatile because to find product-market fit, PMs also own incentives, partnerships, and community. This requires a more flexible skill set and the ability to learn quickly.

It’s more art than science because there is very little user data and A/B testing given web3 values and the small user bases. This requires more intuition and the ability to make decisions in a very high-ambiguity environment.

It’s more public in that discussions about decisions tend to happen in Discord, Crypto Twitter, and public Snapshot proposals. This creates more inclusiveness but also requires a PM to be effective at community engagement rather than purely analytical and influential behind closed doors.

Product managers aren’t yet very common in web3

Most projects have become successful without PMs.

Creating a DeFi protocol? You need a protocol specialist. Building an engaged community for an NFT project? Hire an anon community manager with 50K Crypto Twitter followers and a penchant for meme mastery. Need to write smart contracts? Solidity or Rust developers can help.

The most important things a web3 team needs usually don’t have that much to do with product managers. The Ethereum Foundation that has 97 employees and stewards a $500B Layer 1 protocol with virtually zero PMs. A leading NFT project like World of Women has artists, a head of philanthropy, and legal counsel, but no PMs. When creating a DeFi protocol or running an NFT drop, teams mainly just need a developer, a community manager, and a protocol designer (DeFi) or an artist (NFTs).

PMs have had 20 years to demonstrate value and carve out a role in Big Tech, becoming the leaders of a company’s vision or a feature’s execution. Not here. When I explored roles with 20+ web3 teams in 2021, nearly half of them didn’t understand what PMs were for.

Product managers aren’t as necessary for the web3 0-1 phase

In web2, the founder or early product manager can be crucial in deciding what and how to build, which helps get to the holy grail of product-market fit. In web3 the product experience, such as features and perceptible user experience, doesn’t actually matter as much to the success of the project relative to the token incentives (Staking and AMMs), trading pairs (DEX), artwork (NFTs), network design (L1s/L2s), transaction speed (L1s/L2s), security (L1s/L2s), or other attributes. These are areas where PMs are secondary, if relevant at all.

In the case of the Ethereum Name Service, the website and front-end interface to register a domain is fairly simple for a developer to do compared with building complex blockchain infrastructure or structuring DAO governance. Web3 0-1 is more about technical infrastructure, cryptoeconomics, and/or online community to find product-market fit. At this time, PMs in web3 are usually better for 1-10, not web3 0-1 when you are going from an idea to initial product-market fit.

Product managers need different core skills in web3

Many PMs develop skills like “communication” and “influence” at larger organizations, or even startups where they need to work closely with founders and rally overworked teams. This makes sense because persuasion and coordination have been core to the web2 PM job. Those skills don’t matter as much here. Web3 PM is more focused on execution and community—like signing a big new protocol partner or getting tons of anon users via Twitter.

In web2 I was afraid to tweet much, for professional consequences. Now I’d be untrustworthy if I didn’t tweet a lot. Making a viral meme is more important than writing a good email. That is because getting positive attention in the frenetic world of web3 is more valuable than “alignment.” There are almost no PM career ladders or performance reviews, so teams are purely focused on making a project successful, not politics.

When web3 startups generally hire a PM

All that being said, there are several situations that create a need for a PM at a web3 startup:

1. Engineers have become inefficient: The engineering team has grown too large to prioritize and self-coordinate projects; a PM adds efficiency (e.g. multiple Layer 1 protocols and EVM solutions).

2. The product experience is complex or critical to traction: The product suite is large and the UX is complex/consumer-facing, as in gaming (e.g. the Sky Mavis play-to-earn game Axie Infinity). Some products compete initially by cloning products (e.g. Sushiswap forked Uniswap) and adding tokens, so that requires less product management support and is more focused on technical and cryptoeconomic changes than gaming or wallets.

3. There’s a mix of externally facing activities that a single specialist couldn’t do, but a versatile PM can: There is marketing, growth, business development, and community work the devs don’t want to do and don’t need a dedicated hire for, such that a versatile PM can help. Over time, there are needs for specialist PMs as well (e.g. an L1 like Flow or a marketplace experience like NBA Top Shot), but less at early-stage web3 startups.

What is a web3 PM?

One oversimplified, universal definition of a web3 PM is:

Web3 PMs are responsible for the success of communities rather than increasing acquisition, engagement, or revenue. 

Hearts over charts.

We have seen the past 10 years of web2 demonstrate scenarios where the interests of the community (e.g. internet-addicted teenagers, underpaid ride-share drivers, local restaurants stuck with high platform fees) are deprioritized in favor of company-first north-star metrics. In web3, if the community—such as the NFT creators, liquidity providers, or software developers—is not successful, you are NGMI. Community first.

But how do you make a community successful? To do this, web3 PMs have to think about protocol design, tokenomics, user safety, security, growth marketing, community engagement, and much more that encompasses the interconnected people, technology, and economics of web3 products. Let’s unpack this further.

Ten truths of web3 product management

1. You have to prioritize execution over vision/strategy

Web2 PM careers reward setting long-term vision and crafting a nuanced strategy to achieve OKRs. Execution is expected but not what is most recognized as one progresses from a junior PM to a more senior product leader. Not in web3. I have not seen a single PM vision document; vision lives in whitepapers by technical architects who know cryptography and sharding.

Web3 instead requires PMs to be more focused on execution: quickly hammering out a spec over Telegram with devs, QA’ing carefully and setting up a smart contract audit given the risk of vulnerabilities, building hype on Twitter, launching—and repeating.

Web3 moves too quickly for pontification; new protocols launch daily and DeFi concepts like bonding curves and OHM forks are being tested in real time, so visions and strategies quickly become outdated. This may change over time as the space matures and product vision becomes more of a competitive advantage. But instead, today the best web3 PMs spend 95/5 on execution/vision, not 70/30.

Web3 PM emphasizes building, marketing, and iterating rather than planning, managing, and measuring. Given the pace in web3, this prioritization of execution with the right principles has led to greater success.

2. You have to do user research, business development, and marketing directly, yourself

As web2 matured, the PM role was unbundled: user researchers, UX and UI designers, data scientists, QA testers, product marketing managers, social media managers, and more. Because web3 is so new, the 2020s talent market is tight, and web3 teams lack much of the traditional organizational design of web2 companies, PMs have to do everything again: listen to the community on Discord and Crypto Twitter (user researcher), run some on-chain analysis through a tool like Dune Analytics (data scientist), sketch out the token swapping UX and the AMM’s proposed liquidity incentives (designer and tech lead), form partnerships with stablecoin protocols (BD manager), write the launch blog post (product marketing manager), and make the memes and virality happen on Twitter (social media manager).

Web3 requires one person to do all of this right now, because the tasks above are uniquely technical and interdependent such that they can’t be easily unbundled.

3. You have to focus on perfecting the details rather than expanding features

Front-end interactions are extremely limited, and winning is based on a marginally more secure or higher-yielding product. Web3 products don’t need to maximize engagement by adding more features. The web3 model doesn’t depend on advertising or a freemium SaaS model that converts free users to paid plans. Those models inherently incentivize web2 PMs to focus on getting people to extensively use a product, rather than simply benefiting from a product.

It’s the quality of the artwork for a collection like Bored Ape Yacht Club, or the ease of setup for a DAO, or the availability of liquidity on a DEX to minimize price impact that determines the success of a web3 project. 

Consider native staking through a Layer 1 blockchain like Cosmos. What matters to a user are details like the annual percentage yield (APY, or the return on investment) and if there’s a cooldown period where the tokens remain staked and cannot be accessed—not so much the UI. The UI is a commodity in part because of open-source and composability where teams fork each other’s products.

The UX tends to be either a commodity, like a simple token swap two-field design that Uniswap pioneered, or out of your control if gas fees are high and transactions are slow. So the few details you control really matter. The actual flow of clicking to stake doesn’t matter as much, and, in fact, the ecosystem is optimizing for you to not visit the app very frequently because staked collateral is more stable for the network. But the APY and speed do matter. Engagement less so.

4. You have to understand your users without their email addresses, tracking tools, or running A/B tests

Moreover, airdrop farming and liquidity incentives can make it difficult to tell if you truly have product-market fit. In web3, users can take their data with them at any time and use multiple wallets that can’t easily be linked despite blockchain transparency, and the ethos around decentralization limits one’s ability to use something like Google Analytics, Mixpanel, or Amplitude, let alone cookies or a customer data provider to match email address to demographic information. Without this data, it can be incredibly difficult to know how people are using your product and whether you have achieved product-market fit.

Instead you must rely on qualitative information like user feedback, network-wide information like TVL and floor prices/distribution of NFT holders, and concrete but pseudonymous information like wallets that have deposited funds or swapped tokens. Additionally, many products bootstrap communities by offering native tokens either through liquidity provider incentives for putting capital into a DeFi protocol or giving away free tokens to early believers, like when LooksRare ($LOOKS) gave tokens to high-volume OpenSea users to attract them to its decentralized platform. This lack of data and incentivized engagement, including airdrop farming, make measuring utility very unclear.

5. You have to design your product around the trade-offs of a given L1/L2 blockchain like Ethereum or Solana

Rather than a product fully controlled by your company or mediated by a closed platform like iOS, your product isn’t in a silo. Instead of a product your team fully controls the user interface for, like a travel booking website built on top of AWS or a social networking app distributed in the iPhone App Store that uses iOS design primitives, web3 products are largely subject to the behavior of the Layer 1/Layer 2 protocol they’re built on top of, like the fast transactions on Solana or high gas fees on Ethereum Layer 1.

For example, if you are building a marketplace for NFTs that cost less than $1 geared toward consumers in emerging markets with less disposable income, you may choose a lower-cost blockchain, like Solana or Avalanche, or a mobile-friendly protocol like Celo. Using Ethereum Layer 1 may routinely result in gas fees above $100 and not be accessible to your user base, unless you use a Layer 2 solution like Polygon, Arbitrum, or Optimism. Your choice of which chains you support will impact user adoption, development time, and scalability.

Web3 PMs need to understand different blockchains so they can select which chains to support and design accordingly, whereas in web2, PMs today rarely need to be involved with technical infrastructure decisions because it may not directly impact the end-user experience being created.

6. You have to be extremely careful about what you deploy in smart contracts, and that slows development time

In web3, you can’t just do a quick patch if it’s buggy. In blockchain, code is immutable. Immutability means the code can’t easily be changed unless there is a proxy contract, which can also undermine trust in a project because users can’t trust that it won’t change.

This is different from web2 code, where a bug can just be fixed or a database edited. If there is a security vulnerability, it can lead to massive financial loss that cannot be reversed, since there is no central party or customer support line to call to resolve an issue. This can slow development time and require you to plan around audits.

7. You cannot rely on proprietary code, trade secrets, and data moats as your competitive advantage

Everything is open source and composable in web3, preventing incumbency/market domination: whether it’s Sushi forking Uniswap and dropping tokens to all of its users to jump-start usage in a vampire attack or all the protocols forking OHM, code in web3 is generally open source.

Moreover, your user interface is visible to anyone and usually not that complicated, unlike vast and complex web2 social networks or SaaS product suites. This means anyone can fork your product and compete on tech/product in an instant. Combine this with how users can take their data with them, and you see how the user base isn’t locked in.

By contrast, if all of Facebook’s code were public and user data was portable, it’s not hard to imagine a competitor emerging. This means that web3 PMs must continue to compete with better products, stronger communities, and continuous new value to end users, and can’t rest on having an intellectual-property moat or high switching costs to succeed.

8. You cannot make all product decisions unilaterally and may not control your roadmap

User ownership over the protocol or dapp means that the community is a participant in decision-making. Communities need to be engaged early and often as opposed to being an afterthought or just part of a launch marketing campaign. Users generally hold tokens and have the ability to vote on the future of products, like the Ethereum Name Service (ENS) or the proposal to merge Rari Capital and Fei Protocol. While not every decision, like the canonical-but-overly-satirized web2 decision to test the color of blue on a signup button, would need to be approved by a DAO, there isn’t full autonomy either.

For example, Uniswap is one of the most popular DeFi protocols and needed a vote from the community to deploy its protocol to Polygon. The proposal was submitted by Polygon in November 2021, and this affected the Uniswap product’s roadmap thereafter. Another example is the ENS core team realizing that bots were snapping up three-letter domain names because the threshold for the bit was too low at $2K and needed to be $100K to prevent squatting. The proposal was submitted in January 2022, approved, and will be implemented through a change to an ENS oracle. Communities structured as DAOs govern most protocols; product leadership must happen through them.

9. You must prioritize user security, because with every transaction there are funds at stake

Even if the application is for decentralized music listening or a social network, given how web3 wallets work, there is no real separation between funds and user engagement. Web3 can be a scary place; imagine that clicking a button in a Chrome extension can transfer a $100K JPEG to another wallet without your even realizing it. Security is paramount in the space because all transactions stem from the same place: the web3 wallet.

Here is an example: Some PMs at NFT marketplaces prefer to prompt users for “approve all” permissions in some Metamask transactions to avoid needing to repeatedly give this permission. Repeatedly doing so would be cumbersome and expensive. But then a risk is that the user could have the entire collection transferred out of their wallet if the marketplace turns out to be malicious or gets hacked. The user just intended to give one-time access to sell an NFT. But if they don’t give that broader access, the user might have to pay repeated fees and have a cumbersome UX every time they want to execute a sale. This is an example where security may be prioritized over UX by requiring repeated approvals despite the expense, given how high the risks are. This would likely never be a consideration for a web2 marketplace like eBay or Etsy because listing an item for sale doesn’t put all of your other assets at risk due to the asset ownership model, and there is always a centralized party and team such as customer support to reverse transactions and mediate.

Moreover, in web3, users realistically cannot audit every smart contract, so the burden of ensuring that an app is secure and trustworthy on behalf of your users is higher in web3 given what is at stake in each interaction. This is part of why Crypto Twitter provides social proof when users can’t complete their own diligence to trust products.

10. Regulatory concerns have mostly shifted from web2 to web3

Crypto is on the mind of every congressperson in the U.S. and on the radar of most federal governments, from China to India to Brazil to Nigeria. Many congressional hearings about Facebook’s power have turned into sound-bite-generating floggings—but not much has happened, no matter how many times Zuck shows up on C-SPAN. On the other hand, regulators can’t stop talking about crypto, from Senator Elizabeth Warren to SEC chairperson Gary Gensler. The 2021 infrastructure bill was passed with a provision with onerous tax and tracking requirements that directly affect the entire crypto ecosystem and caused an extreme stir among the web3 community and policy advocacy organizations.

The IRS, SEC, Commodity Futures Trading Commission, and other U.S. agencies have different rules about crypto, not to mention the international landscape that has chased after companies including Binance and PoolTogether. As a PM, you have to consider these matters far more directly than in most web2 organizations, where legal is more secondary at this point. You liaise with counsel to understand a fragmented and undefined legal environment, unlike today in web2, where most legal matters have been settled and product counsels are there to enable but not guide business direction.

What are the best and worst parts about being a web3 PM?

Web3 has a lot of promise as a career path for those who are low-ego, curious, and interested in building. But it’s not all cryptokitties and ATHs:

Best parts:

• Build the future: Web3 remains uncertain. You get to design the next generation of the internet.

• Impact: Because web3 PM is so nascent, what you do and how you do it uniquely matters.

• Use all parts of your brain: Product, partnerships, meme-posting, growth hacking, community—do it all.

• Learn every day: There is so much going on at the intersection of computer science, economics, and sociology.

• Fun: Web3 is much less formal—people post memes, Crypto Twitter always has some new drama. It’s weird.

Worst parts:

• Start again: Think you know PM? Web3 is so different, you must unlearn what you worked so hard to develop.

• 24/7: Web3 is nonstop. Builders are in every country, and what was new is now old. This can be exhausting.

• You’re not as important: Engineers, community leaders, artists—these people are all more important than you.

• Immutability and low data: Experimentation and data are a PM’s best friend at times; not so much in web3.

• Financialization of everything: Token prices, airdrops, and floor prices—everything has a dollar figure (or ETH).

What’s the best path into a web3 gig?

Web3 can be strange and scary. Paid in magical internet tokens? The founder is an anonymous giraffe? What?

But web3 is at a special moment. It is both risky and inevitable. This makes the upside very high for passionate PMs because the space is not yet flooded with people who might be interested for less authentic reasons.

Here’s how I’d advise approaching it:

1. Learn: Read, use, build

Start here: Peruse the Bitcoin whitepaper. Watch “The Potential of Crypto” from Chris Dixon. Follow influential accounts on Crypto Twitter and go down the rabbit hole. Once you’re ready for more: Read the Bitcoin and Ethereum whitepapers. Watch a16z Crypto School. Listen to Bankless, The Defiant, and Unchained. Read The Sovereign Individual for philosophical context, The Infinite Machine (Ethereum), and Crypto Assets. Read Snow Crash, Ready Player One, Dune, and other sci-fi for the culture. Check out recent videos like the EthCC4 conference (here’s a talk from Vitalik) and these interviews by Tim Ferriss with Naval and Vitalik (March 2021) and Nick Szabo (August 2017) and Chris Dixon (Chris Dixon/Naval: Wonders of Web3—October 2021), as well as Balaji (November 2021) and Hosseeb’s talk in 2022 with the Layer 1 founders from Solana, Avalanche, and NEAR, or Brian Armstrong’s interview with Bankless (November 2021). Read everything Linda Xie has written here, and look at Preethi Kasireddy’s guide to Web3 or Web3 University. Follow insightful people on Crypto Twitter (here are some lists) and start posting your own views to learn in public.

Use it: Buy some (e.g. Coinbase, FTX, Binance), send it to a web3 wallet (e.g. Metamask for Ethereum or BSC or Phantom for Solana), stake it (e.g. Staked.us), swap it (e.g. Uniswap), yield-farm to participate in DeFi (e.g. Compound); find an NFT collection or 1/1 that you love (e.g. World of Women, Crypto Coven, or Zed Run), get one or two through OpenSea/Rarible/Foundation/LooksRare, join the Discord for that NFT community, and get engaged with it; try using cross-chain bridges (e.g. Synapse or Wormhole) to move some ETH to different chains or an L2 like Polygon or any other two-way transfer. You have to really live it to build it.

Build it: Try a Buildspace project. Search and read contracts on Etherscan. Mint an NFT. Join a DAO and start contributing to something like Developer DAO or Friends with Benefits. Create something, whether you are technical or not—code, documentation, an event, anything!

2. Search: Find teams you love

Search: Review top web3 VC portfolios (a16z crypto, Pantera, Paradigm, Dragonfly Capital, Electric Capital, Fabric Ventures, Variant Fund) and filter for well-respected teams while looking for missions you care about and a stage that you are well-suited to and where you’re able to have an impact. Create a spreadsheet of the top teams in the space and make notes on what you like, don’t like, and need to understand.

Research: Read those project websites, research what they have shipped, and understand how you can help by reviewing community forums (e.g. Lido/staking) and Twitter (e.g. Frax/fractional stablecoins).

Explore: Join the project Discords to get a sense for the project momentum and community culture.

3. Ape In: Reach out, evaluate, and join a web3 team

• Define your role: Figure out what value you can add based on the project’s status and your experience.

• Reach out: DM the founder or a core contributor with a concise pitch (e.g. three sentences via Twitter DM).

• Connect and decide: Interview with 5+ teams, evaluate your options, make a decision, and have fun! 

Many teams may not even know they need a product manager. Focus on the value you can offer by working backward from their problems, their goals, and their community ethos, and find alignment in your own interests and experience.

In conclusion: web3 needs you—join us!

Web3 is an exciting new frontier, and product management in web3 will require a lot of unlearning, thinking from first principles, and hard work. But who would want it any other way? See you down the rabbit hole, anon. WAGMI.

Thanks so much to lennysan.eth for the opportunity to share this perspective with you. And thanks to contributors for perspectives and feedback on the web3 ecosystem, including Christina Beltramini (Aave), Mike Garland and Rob Boyle (Alchemy), Matt Henderson (Aurora), Rachel Mayer (Circle), Georgiana Mirea (Dapper Labs), Mike Sall (Goldfinch), Veronica Saron (Mirror), Aadil Mamujee (OpenSea), Pooja Shah (Protocol Labs), Nassar Hayat (Radicle), and Ian Lee and Will Papper (SyndicateDAO).

None of this is financial advice. Please do your own research. You can follow Jason on Twitter and LinkedIn.

---

🔥 Featured job openings

1. Alchemy: Product Manager (SF, NYC, Remote)

2. Elevate Labs: Senior Product Manager, Balance (Remote)

3. Oath Care: UX Designer (Remote-US)

4. Oath Care: Community Marketing Manager (Remote-US)

5. Hex: Growth Product Manager (SF, Remote-US)

6. Monarch: Data Lead - Growth (Remote-Global, Remote-US)

7. Monarch: Performance Marketing Manager (Remote-Global, Remote-US)

8. Convosight: Sr Product Owner (Remote-Global, Remote-US, Remote-India)

9. Siteline: First Product Manager (SF, Remote-US)

10. Koodos: Product Engineer (NYC, Remote-US)

11. Mynd: Senior Product Manager, Communications (Remote-US)

12. Empower: Product Manager (Remote-Global)

13. Superjoi: UI/UX Designer (LA, Remote-Global)

14. Superjoi: Full Stack Engineer (LA, Remote-Global)

15. HireArt: Senior Full-Stack Engineer (Remote-US)

16. Universe: Product Lead - Commerce Tools (Remote)

17. Universe: Product Lead - Creation Tools (Remote)

18. Clubhouse: Growth Product Manager (SF, Remote-US)

19. Earthly Technologies: Senior Product Manager (Remote-US, Remote-Canada)

Browse more open roles, or add your own, at Lenny’s Job Board.

---

If you’re finding this newsletter valuable, consider sharing it with friends, or subscribing if you haven’t already.

Sincerely,

Lenny 👋