A product manager’s guide to web3

2. Search: Find teams you love

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

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

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.

Everything is open source and composable in web3, preventing incumbency/market domination.

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.

10. Regulatory concerns have mostly shifted from web2 to web3.

2. You have to do user research, business development, and marketing directly, yourself.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.

What’s the best path into a web3 gig?