[sigre]

Exactly. I imagine this breaks down when you have a designer that prefers to work starting at 3pm, and a developer who's in at 7am. Do you allow the deadline to slip, or ask the designer to come in earlier (or the developer to stay later)?

I'm much more a fan of "core hours": i.e. a company that says everyone should plan to be available between, say, 12 - 2pm either in person or online. Then everyone can set their own hours around that.

[aantix]

The designer and developer are both professionals; they both have a mutual problem to solve one of which it to make sure they're both on the same page of logistics and design.

If they can't figure out that they have to meet together at some point early in the process, then I'd say you have a bigger issue.

The need to define core hours feels like a band-aid to a bigger issue.

[rdouble]

Core hours are usually used as a punishment for a team that isn't doing well. Other times it means a dud manager was hired who gets anxious when there isn't enough real or perceived face-time.

[gte910h]

I hate core hours.

If your workers are too big of cowards to negotiate among themselves when they need to meet to get things done, then you have bigger problems.

[bkbleikamp]

There aren't really any deadlines.

For the most part people are working on things they're excited about, so everyone wants to ship as quickly as possible.

While we have fun, goof off, and can work whenever we want, we're all professional and respect each other. If I am blocking someone I am not going to take the day off.