Alright, I have a solution. The last time I worked with a team of generalists we would get into sticky situations of division of work. We came up with the idea of appointing "First Speaker"[1] for each project. Though the Wikipedia article doesn't say much, in the Foundation book, first speaker is someone who spoke first and it does not indicate hierarchy. The first speaker is someone who first initiates or formulates a (reasonable)plan of execution. The rest of the team would follow with inputs on the same plan making it better(instead of creating new plans). It was more than shouting "dibs".
One of the reasons I think it worked out was because the team members were all of the same work and skill experience(i.e equally bad or equally good). We also had equal stakes in the project. I don't see an all generalist team working out at all if they are not of equal mileage.
Yeah, it might be nice to have a mule for every project (might affect the dynamic well, slow things down etc.) and if somebody specialized in being the mule, it'd be funny, but it might work.
One of the reasons I think it worked out was because the team members were all of the same work and skill experience(i.e equally bad or equally good). We also had equal stakes in the project. I don't see an all generalist team working out at all if they are not of equal mileage.
[1]http://en.wikipedia.org/wiki/First_Speaker