They specifically say there are two annoying issues this solves:
1. having to"CTRL-S–ALT-TAB–CTRL-SHIFT-R–JOY!", and
2. editing in Firebug "then trying to extract those tweaks back out of Firebug and into your website’s CSS files".
As far as working on teams, they're "thinking about how to expose your CSS in a versioned way so that you can keep it in Mercurial (with Kiln!), or Git, or whatever other version control software you might be using". Perhaps you're right, it's better to wait until that is implemented if you have that kind of setup.
EDIT: I've started testing it, and you can add other admins and editor users for sites, very nice.
If you try it out, you'll see that there are two modes, Preview and Published. Your changes don't go to anyone else until you are done with them, so we won't serve up half-baked CSS while you're still working on it. Once you're done, you hit Publish and only then is it live.
The hosting of your CSS files on their servers is also not suited for a development environment that has more than 1 environment, as I would not want to be editing files that are on a live server on a regular basis without first making those changes locally (and possibly checking them into an SCM of some sort first) because my css would quickly become out of sync across environments.
May I ask, the projects that you work on, do you have more than 1 environment that you use and do you collaborate with any other developers on these projects?