A product manager’s guide to web3

2. Search: Find teams you love

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

Product managers aren’t yet very common in web3.  Most projects have become successful without PMs.

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.

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

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

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

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.

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.