someone-build

Exploring something...

What would your ideal DAO-focused / web3-native project management system look like?

Some thought-starters:
- embedded compensation (incl RFPs, bounties, etc)
- programmable access ctrl
- crowdsourced prioritization?
- decentralized deployment approval?

building /hatsprotocol | 
proudly mid-curving it since 1995

What it looks like is less important to me than what it's made of.

There are already a ton of PM tools. Obvs there could be improvememts to them all (like Hats compat) and there's no perfect solution.. But pretty much all of them are siloed and really not very interoperable.

Everyone seems to think that slapping a fucking kanban board on an dapp makes it "web3 project management", and doesn't think twice about what constitutes a task or role.

So we now have onchain representations of roles that work (sort of, if one has access to help).. But what about tasks?

If I had to guess what my ideal pm tool would be, it would be one which makes tasks portable and interoperable. It would be aware of my org graph in a useful way. It would help me interact with my tasks regardless of which client/stack I choose, and it would be aware of basic project lifecycle stuff like making my fucking discovery and planning data persistently available until the project wraps. It would teach good PM BP's to users passively.

/vent