3. You have to focus on perfecting the details rather than expanding features.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. Instead you must rely on qualitative information l... See more

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.

What’s the best path into a web3 gig?

[No points 4-6)

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. t... See more

9. You must prioritize user security, because with every transaction there are funds at stake. Security is paramount in the space because all transactions stem from the same place: the web3 wallet.

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

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.

1. You have to prioritize execution over vision/strategy.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.