[seanstickle]

The same it applies anywhere. You want results from people in the restaurant business, hospitality industry, or retail environments, right?

A Results-Only Work Environment isn't a Remote-Only Work Environment. You work where and when you want, as long as your work gets done. If you need to be in the restaurant during certain hours to achieve your results, then that's where you are.

The focus is first and foremost on the results, and everything follows from that.

[nhebb]

So a Results-Only Work Environment works because it focuses on results. Got it. That may work fine for programmers, but when knowledge worker theory meets the reality of a mass workforce, you're resorting to a circular argument. The GP cited businesses that need employees available at all hours when the business is open. That's the only way to get results. So in the context of a 35 hours work week, I don't see it as applicable. Convenience stores, restaurants, and hospitality businesses would just end up hiring more part time workers.

[enjo]

I would encourage you to read the book "Maverick" which examines a lot of this in detail. It's interesting the environments they've applied these types of structures to. Including line-manufacturing.

http://en.wikipedia.org/wiki/Maverick_%28book%29

[mattm]

Disagree. It only really works for workers that are actively producing. For jobs that are reactionary (mainly service jobs where customers come to them and they are expected to deal with them) it doesn't really work. You need someone in the store or answering the phones during certain hours.