DAO steward discussion today:

There are so many DAO tools to use, but we are still experimenting with org structure so we can’t implement any of them until we figure that out.

We run experiments by hand and then once we find a structure that works we can spend the time integrating automation.

Working on autonomous builder economies @tenfold, nounish channel client /comint
More: rubinovitz.com

what if there were a tool to help design, experiment, and iterate on org structure

building /hatsprotocol | 
proudly mid-curving it since 1995

what might be some properties or features of a tool that didn't care such onboarding/implementation risks?

Putting it into “the cold start problem” terms:
I think we still need to figure out what our “atomic network” is.

Then when we go to “copy paste” the atomic network across the DAO we could look at doing that using hats.

But onboarding and implementing a new tool we may not use or need to change is risky.