Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This sometimes leads to valuable insights, but always slows the driver down.

In cases where the insight is genuinely useful that's better than going fast mostly because you were probably going fast in the wrong direction. Ideally you would optimise collaboration to increase the likelihood of valuable feedback (because that saves more time and money) rather than optimizing for speed.

That said, I've lost track of the number of meetings I've been in so that someone can cover their ass by making something a 'collaborative decision' instead of taking responsibility, so I can totally see where the author is coming from.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: