<aside>
đź’ˇ Please comment and challenge anything written here. Trying to make this as helpful as possible to the product/eng team without overwhelming them.
THIS IS A LIVING DOCUMENT.
Last updated 2023-05-05
</aside>
PREFACE
This document is meant to illuminate where we (the Gitcoin Passport team) fit into the web3 landscape and world. It is a WORK IN PROGRESS, and will be revisited at least quarterly. Will be likely updated every week as new info relevant to Gitcoin Passport product development strategy comes in.
A NOTE on “COMPETITIVE ANALYSES”:
Studying what people in your sector/industry/mission area are doing is really helpful:
- You get a feel for what matters—when smart people are increasingly focused on the same tech, tech use case, design pattern, or problem area, you should take notice. However, this is not the same as treating other people as competitors, and hoping they mess up so we get ahead.
- THAT SAID: Gitcoin Passport team should not operate from a spirit of competition. This is a losing mentality.
THE CASE FOR A POST-COMPETITION APPROACH TO PRODUCT DEVELOPMENT
- What if unlike most product teams, the Gitcoin Passport team was, yes, aware of the most interesting and trending products and patterns, but it is not threatened by the excellence of other Sybil, Identity, and Reputation-focused products.
- We want everyone to win. And be an aggregator of the excellence of all these products. That’s the whole value prop of Gitcoin Passport!
- We want to be seeking to partner and integrate and interoperate more than defeat in a zero sum competitive manner!
- Inspired in part by Bruce Lee: https://www.audible.com/pd/1250759838?source_code=ASSORAP0511160006&share_location=player_overflow
MACRO TRENDS THE TEAM SHOULD FOLLOW
THE MOST INTERESTING PRODUCTS TO STAY AWARE OF