[Brian]

OmniFocus 1.x is designed around a single-user workflow. It's possible on a theoretical/technical level to do something like this, but in practice, 11 folks working on the app simultaneously behave differently than one person with 11 devices.

(The more simultaneous users you add, the more likely it becomes that 2 or more people edit the same item between syncs. If it's just one person using a bunch of different devices round-robin style, that doesn't happen as much.)

When two folks that are between syncs edit the same item in the database, it's called a "sync conflict"; OmniFocus resolves them by letting the edit that occurred later trump the earlier one.

(We resolve conflicts this way in order to keep sync times acceptably fast on iOS devices. Sorting out the overlapping changes would make sync take longer than customers have told us they want to wait.)

I've seen smaller groups make something like this work by being careful to sync before and after any changes they make in the database; with 11 folks, though, I'm not sure how successful that would be.

This all said, support for team-based workflows is something we're considering for future versions of the app. :-)