Build Stuff

What kind of development model or process do you use, when everyone dislikes processes? More so, how do you do that when the team is very distributed, working from offices or homes at dozens of places around the world? How do you let people just do thework, instead of worrying about reports, meetings or hierarchies?
I don't know the answer, but I do know what has (and has not) worked at Unity Technologies, all the way from 3 to 100+ developers. We don't have a name for our process, but it is fairly chaotic, random and always changing; with a goal of "as little rules as possible". Hence, Lightweight Chaos could be a name.