News for hackers. Stuff that matters.
Re:Amazon is piloting teams with a 30-hour workweek by Spooky23 on Friday August 26, 2016 @11:21PM (#12370778)
No, it's just a different viewpoint.

If you don't have measurable inputs and outputs (i.e. Tickets, service requests, widgets, cases, etc), you typically lose productivity. Not necessarily because of the employee, but also because of managers who don't function well with out of sight people.

Personally, I think in many cases you'd get better outcomes out of sending people home at noon on Fridays than having them telework.

Re:Amazon is piloting teams with a 30-hour workweek by Falkon1313 on Saturday August 27, 2016 @01:48AM (#12371194)
> If you don't have measurable inputs and outputs

Of course if you're not giving employees anything to do, you'll get reduced productivity. That's also true if you force them to sit in a chair in the office and do nothing. If you can't come up with anything for them to do (slow season, sales pipeline stalled) maybe let them pitch ideas for things they'd like to work on and give the ok on some.

Either way, if they have something to do and you keep in touch with them on how things are going, things should keep moving even without specific granular measurements. But why not use tickets or tasks or something to make it visible?

> also because of managers who don't function well with out of sight people

Those people probably shouldn't be managers, at least not working with remote workers. Communication is critical. A remote team should feel like they're communicating at least as much as an in-office team, if not more.