<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The 80-hour Myth</title>
	<atom:link href="http://startupboy.com/2005/11/29/the-80-hour-myth/feed/" rel="self" type="application/rss+xml" />
	<link>http://startupboy.com/2005/11/29/the-80-hour-myth/</link>
	<description>Truth in Startups, and a Whole Lot Less</description>
	<lastBuildDate>Tue, 31 Jan 2012 08:18:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Robert Sandie</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-811</link>
		<dc:creator><![CDATA[Robert Sandie]]></dc:creator>
		<pubDate>Sat, 29 Jan 2011 17:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-811</guid>
		<description><![CDATA[Great post. It&#039;s not about 9-9.. I don&#039;t have 2 week stretches but often I leave the office around 3 to go for a run cause I find myself unproductive. Get back at it around 7.]]></description>
		<content:encoded><![CDATA[<p>Great post. It&#8217;s not about 9-9.. I don&#8217;t have 2 week stretches but often I leave the office around 3 to go for a run cause I find myself unproductive. Get back at it around 7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allen Price</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-797</link>
		<dc:creator><![CDATA[Allen Price]]></dc:creator>
		<pubDate>Sun, 23 Jan 2011 04:34:48 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-797</guid>
		<description><![CDATA[Having managed the People and Recruiting &quot;departments&quot; in 3 start-ups before starting my own company, I mostly agree with your premise. &quot;First, measure outputs&quot;, you say. Absolutely. The whole &quot;job description&quot; concept is a farce as are most attempts at training. Job descriptions focus on tasks not outcomes; training focuses on hours spent, not what was learned. Rather, you should define what success looks like (including milestones and due dates). And, yes, hold people accountable for the quality of their work product, not total hours spent &quot;working&quot;. 

The whole question of &quot;the best place / time to work&quot; is a challenging one. For me, the vital component of a work environment that stimulates maximum inspiration and productivity is not hours worked; it&#039;s the synergistic and unplanned &quot;meetings&quot; when two or more people start to feed off each other and generate bursts of creativity / coding / new ideas that would never have happened had everyone been working alone. In the corporate environment, a lot of this happens around the water cooler. In a start-up it happens where and when you find it. A lot of really creative stuff comes from those chance conversations that almost never happens when people aren&#039;t in the same office at the same time.

So, the answer for me is to forget about counting hours and encourage some amount of &quot;self-directed&quot; work during the time and at the place of the employees&#039; choosing as long as everyone has a core set of hours when they&#039;re in the same place at the same time. Give everyone clear deliverables and time tables and make sure that everyone knows who is responsible for what.

And to all of you who feel that icy pressure to &quot;look like you&#039;re working&quot; I&#039;d say you are working in the wrong company, no matter how hip the product is or how famous the CEO is.]]></description>
		<content:encoded><![CDATA[<p>Having managed the People and Recruiting &#8220;departments&#8221; in 3 start-ups before starting my own company, I mostly agree with your premise. &#8220;First, measure outputs&#8221;, you say. Absolutely. The whole &#8220;job description&#8221; concept is a farce as are most attempts at training. Job descriptions focus on tasks not outcomes; training focuses on hours spent, not what was learned. Rather, you should define what success looks like (including milestones and due dates). And, yes, hold people accountable for the quality of their work product, not total hours spent &#8220;working&#8221;. </p>
<p>The whole question of &#8220;the best place / time to work&#8221; is a challenging one. For me, the vital component of a work environment that stimulates maximum inspiration and productivity is not hours worked; it&#8217;s the synergistic and unplanned &#8220;meetings&#8221; when two or more people start to feed off each other and generate bursts of creativity / coding / new ideas that would never have happened had everyone been working alone. In the corporate environment, a lot of this happens around the water cooler. In a start-up it happens where and when you find it. A lot of really creative stuff comes from those chance conversations that almost never happens when people aren&#8217;t in the same office at the same time.</p>
<p>So, the answer for me is to forget about counting hours and encourage some amount of &#8220;self-directed&#8221; work during the time and at the place of the employees&#8217; choosing as long as everyone has a core set of hours when they&#8217;re in the same place at the same time. Give everyone clear deliverables and time tables and make sure that everyone knows who is responsible for what.</p>
<p>And to all of you who feel that icy pressure to &#8220;look like you&#8217;re working&#8221; I&#8217;d say you are working in the wrong company, no matter how hip the product is or how famous the CEO is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Feature Overload &#187; Blog Archive &#187; NO ONE REALLY WORKS 80-HOURS</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-796</link>
		<dc:creator><![CDATA[Feature Overload &#187; Blog Archive &#187; NO ONE REALLY WORKS 80-HOURS]]></dc:creator>
		<pubDate>Sun, 23 Jan 2011 00:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-796</guid>
		<description><![CDATA[[...] This too has been my experience. I&#8217;ve tried to slowly take a more balanced approach to work. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This too has been my experience. I&#8217;ve tried to slowly take a more balanced approach to work. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Hutchings</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-794</link>
		<dc:creator><![CDATA[Keith Hutchings]]></dc:creator>
		<pubDate>Sat, 22 Jan 2011 06:27:52 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-794</guid>
		<description><![CDATA[Great post.

@Niket You may enjoy this Ted-talk by Jason Fried (co-founder of 37signals). His main argument: The office isn&#039;t a good place to work.

http://www.ted.com/talks/jason_fried_why_work_doesn_t_happen_at_work.html]]></description>
		<content:encoded><![CDATA[<p>Great post.</p>
<p>@Niket You may enjoy this Ted-talk by Jason Fried (co-founder of 37signals). His main argument: The office isn&#8217;t a good place to work.</p>
<p><a href="http://www.ted.com/talks/jason_fried_why_work_doesn_t_happen_at_work.html" rel="nofollow">http://www.ted.com/talks/jason_fried_why_work_doesn_t_happen_at_work.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forget the 80 hour work week &#171; Power Of Two Marriage Blog</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-792</link>
		<dc:creator><![CDATA[Forget the 80 hour work week &#171; Power Of Two Marriage Blog]]></dc:creator>
		<pubDate>Fri, 21 Jan 2011 16:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-792</guid>
		<description><![CDATA[[...] always nice to find a fellow voice for sanity out there &#8211; http://startupboy.com/2005/11/29/the-80-hour-myth/ . Thanks for the reminder [...]]]></description>
		<content:encoded><![CDATA[<p>[...] always nice to find a fellow voice for sanity out there &#8211; <a href="http://startupboy.com/2005/11/29/the-80-hour-myth/" rel="nofollow">http://startupboy.com/2005/11/29/the-80-hour-myth/</a> . Thanks for the reminder [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abigail Hirsch, Ph.D.</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-791</link>
		<dc:creator><![CDATA[Abigail Hirsch, Ph.D.]]></dc:creator>
		<pubDate>Fri, 21 Jan 2011 16:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-791</guid>
		<description><![CDATA[Great post!  Both because the focus on output not hours is so critical for a startup.  In addition, as the CEO of start-up making internet programs to improve marriages (poweroftwomarriage.com), this post implies that folks would be better off just going home and having some recuperative, real time with their loved ones and friends.

That is a great way to have more inspiration, more productivity, and oh yah, happy marriages too!]]></description>
		<content:encoded><![CDATA[<p>Great post!  Both because the focus on output not hours is so critical for a startup.  In addition, as the CEO of start-up making internet programs to improve marriages (poweroftwomarriage.com), this post implies that folks would be better off just going home and having some recuperative, real time with their loved ones and friends.</p>
<p>That is a great way to have more inspiration, more productivity, and oh yah, happy marriages too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; The 80 Hour Work Week Myth Revisited Dan Merton</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-790</link>
		<dc:creator><![CDATA[&#187; The 80 Hour Work Week Myth Revisited Dan Merton]]></dc:creator>
		<pubDate>Fri, 21 Jan 2011 16:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-790</guid>
		<description><![CDATA[[...] in are meaningless, output is everything: http://startupboy.com/2005/11/29/the-80-hour-myth/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] in are meaningless, output is everything: <a href="http://startupboy.com/2005/11/29/the-80-hour-myth/" rel="nofollow">http://startupboy.com/2005/11/29/the-80-hour-myth/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The 80 Hour Myth (via &#8216;Startup Boy&#8217; Naval Ravikant) &#124; Succincity</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-789</link>
		<dc:creator><![CDATA[The 80 Hour Myth (via &#8216;Startup Boy&#8217; Naval Ravikant) &#124; Succincity]]></dc:creator>
		<pubDate>Fri, 21 Jan 2011 14:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-789</guid>
		<description><![CDATA[[...] recent post on his Startup Boy blog was featured on the Startup Digest reading list, and for good reason &#8212; it&#8217;s spot on. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] recent post on his Startup Boy blog was featured on the Startup Digest reading list, and for good reason &#8212; it&#8217;s spot on. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tech IT Easy &#187; 8 Things I learned about Entrepreneurship in 2010</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-786</link>
		<dc:creator><![CDATA[Tech IT Easy &#187; 8 Things I learned about Entrepreneurship in 2010]]></dc:creator>
		<pubDate>Mon, 17 Jan 2011 20:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-786</guid>
		<description><![CDATA[[...] hours or 4 quality hours: There was a post today about how working 80 hours is BS. I agree! That said, one important facet about entrepreneurial productivity is to stay accountable [...]]]></description>
		<content:encoded><![CDATA[<p>[...] hours or 4 quality hours: There was a post today about how working 80 hours is BS. I agree! That said, one important facet about entrepreneurial productivity is to stay accountable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-783</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Mon, 17 Jan 2011 03:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-783</guid>
		<description><![CDATA[Is &quot;work harder&quot; the correct answer to your proposed natural human tendency to idle about a bit?

What about something like &quot;take an extra day off a week&quot; ?  Put only the productive hours in at work and have a better quality of life.

Maybe?]]></description>
		<content:encoded><![CDATA[<p>Is &#8220;work harder&#8221; the correct answer to your proposed natural human tendency to idle about a bit?</p>
<p>What about something like &#8220;take an extra day off a week&#8221; ?  Put only the productive hours in at work and have a better quality of life.</p>
<p>Maybe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niket</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-782</link>
		<dc:creator><![CDATA[Niket]]></dc:creator>
		<pubDate>Mon, 17 Jan 2011 01:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-782</guid>
		<description><![CDATA[Totally true. 

Would you then say that employees can use this argument for more flexibility in their schedules? 

For me,I&#039;d say that idling is part of the job. I find myself thinking about problems I&#039;ve been trying to solve while doing the most mundane tasks (showering, walking, etc.). It&#039;s like I&#039;m always working on some problem whether it&#039;s in my direct conscious or not. 

Sometimes, when I used to work in an office, I&#039;d have a harder time coming up with solutions just because of the pressure to look like you are working. My best moments we&#039;re simply crunching through an issue with a colleague at a coffee shop, but I always felt like these &quot;breaks&quot; were frowned upon.

I don&#039;t really want to work in a place for 80 hours anyways, but I am more than happy to work hard to provide deliverables that take &quot;80 hours of work.&quot;]]></description>
		<content:encoded><![CDATA[<p>Totally true. </p>
<p>Would you then say that employees can use this argument for more flexibility in their schedules? </p>
<p>For me,I&#8217;d say that idling is part of the job. I find myself thinking about problems I&#8217;ve been trying to solve while doing the most mundane tasks (showering, walking, etc.). It&#8217;s like I&#8217;m always working on some problem whether it&#8217;s in my direct conscious or not. </p>
<p>Sometimes, when I used to work in an office, I&#8217;d have a harder time coming up with solutions just because of the pressure to look like you are working. My best moments we&#8217;re simply crunching through an issue with a colleague at a coffee shop, but I always felt like these &#8220;breaks&#8221; were frowned upon.</p>
<p>I don&#8217;t really want to work in a place for 80 hours anyways, but I am more than happy to work hard to provide deliverables that take &#8220;80 hours of work.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Professionalizing the Management Science of Entrepreneurship</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-298</link>
		<dc:creator><![CDATA[Professionalizing the Management Science of Entrepreneurship]]></dc:creator>
		<pubDate>Thu, 07 Jan 2010 12:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-298</guid>
		<description><![CDATA[[...] values for themselves? Or are they just more successful at creating value for investors? Or is the 80-hour work week a myth that doesn&#8217;t increase the odds of success over a 50-hour work [...]]]></description>
		<content:encoded><![CDATA[<p>[...] values for themselves? Or are they just more successful at creating value for investors? Or is the 80-hour work week a myth that doesn&#8217;t increase the odds of success over a 50-hour work [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Startup Boy is back &#45; Venture Hacks</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-261</link>
		<dc:creator><![CDATA[Startup Boy is back &#45; Venture Hacks]]></dc:creator>
		<pubDate>Mon, 09 Nov 2009 16:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-261</guid>
		<description><![CDATA[[...] personal blog, Startup Boy, is back. His posts, like The 80-hour Myth and VC Bundling, were an inspiration to me when I first moved to Silicon Valley. His latest post, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] personal blog, Startup Boy, is back. His posts, like The 80-hour Myth and VC Bundling, were an inspiration to me when I first moved to Silicon Valley. His latest post, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Sampson</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-27</link>
		<dc:creator><![CDATA[Curt Sampson]]></dc:creator>
		<pubDate>Wed, 25 Jul 2007 06:26:42 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-27</guid>
		<description><![CDATA[As someone who&#039;s &quot;drunk the XP kool-aid,&quot; as certain acquaintances of my like to say, I find your point about &quot;introduc[ing] peer pressure&quot; interesting. I completely agree, it&#039;s just that I call it &quot;fun.&quot; Perhaps I&#039;m just a social creature.As far as the programming stuff goes, I find that when I&#039;m pairing with another good programmer, I&#039;m burned out after six hours or so. (Mind you, six *very* productive hours.) It&#039;s hard to figure out what to do after that. Maybe have a meeting or something....cjs@cynic.net
]]></description>
		<content:encoded><![CDATA[<p>As someone who&#8217;s &quot;drunk the XP kool-aid,&quot; as certain acquaintances of my like to say, I find your point about &quot;introduc[ing] peer pressure&quot; interesting. I completely agree, it&#8217;s just that I call it &quot;fun.&quot; Perhaps I&#8217;m just a social creature.As far as the programming stuff goes, I find that when I&#8217;m pairing with another good programmer, I&#8217;m burned out after six hours or so. (Mind you, six *very* productive hours.) It&#8217;s hard to figure out what to do after that. Maybe have a meeting or <a href="mailto:something....cjs@cynic.net">something&#8230;.cjs@cynic.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-26</link>
		<dc:creator><![CDATA[mike]]></dc:creator>
		<pubDate>Mon, 16 Jul 2007 21:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-26</guid>
		<description><![CDATA[here&#039;s a corollary scenario I&#039;ve seen over and over:1. the team is perpetually sprinting to the next looming product deadline2. most of the team works until 8 or 10pm. this seems good3. so let&#039;s start bringing in dinners for the guys. Keep em happy and keep em here late.4. Pretty soon they realize that they get free dinner every night and know they&#039;ll be here until 10, so they roll into the office around noon6. next thing you know, people settle into 50 hours AND get a free dinner.
]]></description>
		<content:encoded><![CDATA[<p>here&#8217;s a corollary scenario I&#8217;ve seen over and over:1. the team is perpetually sprinting to the next looming product deadline2. most of the team works until 8 or 10pm. this seems good3. so let&#8217;s start bringing in dinners for the guys. Keep em happy and keep em here late.4. Pretty soon they realize that they get free dinner every night and know they&#8217;ll be here until 10, so they roll into the office around noon6. next thing you know, people settle into 50 hours AND get a free dinner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Wright</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-25</link>
		<dc:creator><![CDATA[Tony Wright]]></dc:creator>
		<pubDate>Mon, 16 Jul 2007 20:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-25</guid>
		<description><![CDATA[Great post.  I&#039;ve been wading through the Four Hour Work Week (which is hard, because it feels like a damn sale pitch), and it has a similar message.There&#039;s no easy measure for output or output quality (for most jobs).  One of the things I&#039;ve wanted to know for a long time is exactly how much time I spend on various apps and sites (I had a sneaking suspicion that I did a lot of things that made me feel busy, but weren&#039;t particular productive).  Over the last 6 months, some friends and I have whipped up a tool that measures how you spend your computer time and my results were pretty damn horrifying.If we ever find our way out of private beta, you can be horrified, too!  :-)
]]></description>
		<content:encoded><![CDATA[<p>Great post.  I&#8217;ve been wading through the Four Hour Work Week (which is hard, because it feels like a damn sale pitch), and it has a similar message.There&#8217;s no easy measure for output or output quality (for most jobs).  One of the things I&#8217;ve wanted to know for a long time is exactly how much time I spend on various apps and sites (I had a sneaking suspicion that I did a lot of things that made me feel busy, but weren&#8217;t particular productive).  Over the last 6 months, some friends and I have whipped up a tool that measures how you spend your computer time and my results were pretty damn horrifying.If we ever find our way out of private beta, you can be horrified, too!  <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shanti Braford</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-24</link>
		<dc:creator><![CDATA[Shanti Braford]]></dc:creator>
		<pubDate>Mon, 16 Jul 2007 19:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-24</guid>
		<description><![CDATA[I love seeing posts like this.I recently joined a startup where somewhat long hours are the norm.  Leaving before 8pm many nights feels like you are being a slacker.When my energy is drained &amp; I _know_ my productivity is low (if pushed, often-generating too many bugs in the code for  it to be useful), I often feel like taking off early and making it up some other time.What could be ideal for companies is a graphical display (or some indicator / brief meetings / etc) that indicates the output / production of everyone on the team.Of course, people usually know in the general ballpark how much everyone is working.I&#039;m just thinking of the scenario of someone who might only have 40 hours of his/her butt in the seat, but deliver 2x output.  That person should be rewarded, not pushed, of course.For coders, working code and/or tests checked into a Subversion repository is a pretty good indication that you&#039;ve actually been productive.
]]></description>
		<content:encoded><![CDATA[<p>I love seeing posts like this.I recently joined a startup where somewhat long hours are the norm.  Leaving before 8pm many nights feels like you are being a slacker.When my energy is drained &amp; I _know_ my productivity is low (if pushed, often-generating too many bugs in the code for  it to be useful), I often feel like taking off early and making it up some other time.What could be ideal for companies is a graphical display (or some indicator / brief meetings / etc) that indicates the output / production of everyone on the team.Of course, people usually know in the general ballpark how much everyone is working.I&#8217;m just thinking of the scenario of someone who might only have 40 hours of his/her butt in the seat, but deliver 2x output.  That person should be rewarded, not pushed, of course.For coders, working code and/or tests checked into a Subversion repository is a pretty good indication that you&#8217;ve actually been productive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wx</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-23</link>
		<dc:creator><![CDATA[wx]]></dc:creator>
		<pubDate>Mon, 16 Jul 2007 12:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-23</guid>
		<description><![CDATA[&quot;Nothing damages a startup like a mediocre and reliable performer.&quot;What&#039;s so dangerous about a reliable mediocre output?
]]></description>
		<content:encoded><![CDATA[<p>&quot;Nothing damages a startup like a mediocre and reliable performer.&quot;What&#8217;s so dangerous about a reliable mediocre output?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nivi</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-22</link>
		<dc:creator><![CDATA[Nivi]]></dc:creator>
		<pubDate>Thu, 21 Sep 2006 05:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-22</guid>
		<description><![CDATA[Re: measuring outputs and productivity:“Efficiency is doing things right; effectiveness is doing the right things.” -- Peter DruckerThe anecdotal high failure rate of even venture-backed startups indicates that most startups are not doing the &quot;right things&quot;.  Most startups are instead wrongly focused on doing &quot;things right&quot;. Sad to see so much effort and talent wasted.
]]></description>
		<content:encoded><![CDATA[<p>Re: measuring outputs and productivity:“Efficiency is doing things right; effectiveness is doing the right things.” &#8212; Peter DruckerThe anecdotal high failure rate of even venture-backed startups indicates that most startups are not doing the &quot;right things&quot;.  Most startups are instead wrongly focused on doing &quot;things right&quot;. Sad to see so much effort and talent wasted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Naveen Garg</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-21</link>
		<dc:creator><![CDATA[Naveen Garg]]></dc:creator>
		<pubDate>Thu, 14 Sep 2006 00:29:06 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-21</guid>
		<description><![CDATA[Well if 80 hour work week is a myth, then there is a legend of a fight against the 80 hour work week by the American Medical Student Association.  Residents used to get screwed working not just 80 hours, but 120 hrs... the result was demoralizing and turning doctors into monsters...
]]></description>
		<content:encoded><![CDATA[<p>Well if 80 hour work week is a myth, then there is a legend of a fight against the 80 hour work week by the American Medical Student Association.  Residents used to get screwed working not just 80 hours, but 120 hrs&#8230; the result was demoralizing and turning doctors into monsters&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StartupBoy</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-20</link>
		<dc:creator><![CDATA[StartupBoy]]></dc:creator>
		<pubDate>Sun, 26 Feb 2006 09:15:45 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-20</guid>
		<description><![CDATA[Thanks Adam, glad you liked it. I appreciate the encouragement.
]]></description>
		<content:encoded><![CDATA[<p>Thanks Adam, glad you liked it. I appreciate the encouragement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Elend</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-19</link>
		<dc:creator><![CDATA[Adam Elend]]></dc:creator>
		<pubDate>Sat, 25 Feb 2006 22:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-19</guid>
		<description><![CDATA[Excellent and insightful post.  I reposted with the following preface on my blog, queesnboundseven.blogspot.com:&quot;I don&#039;t think I&#039;ve ever reposted a post from another blog in its entirety before, but I read the following on Startupboy.com and I was still thinking about it 24 hours later.I found this interesting because I agree with his perspective, and try to manage employees in the way he suggests. But at the same time, it&#039;s a philosophy I find hard to implement in my own work - I find too often that my instinct is to work harder, and to feel behind unless I am working constantly. Something I&#039;m trying to work on...&quot;
]]></description>
		<content:encoded><![CDATA[<p>Excellent and insightful post.  I reposted with the following preface on my blog, queesnboundseven.blogspot.com:&quot;I don&#8217;t think I&#8217;ve ever reposted a post from another blog in its entirety before, but I read the following on Startupboy.com and I was still thinking about it 24 hours later.I found this interesting because I agree with his perspective, and try to manage employees in the way he suggests. But at the same time, it&#8217;s a philosophy I find hard to implement in my own work &#8211; I find too often that my instinct is to work harder, and to feel behind unless I am working constantly. Something I&#8217;m trying to work on&#8230;&quot;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Listwon</title>
		<link>http://startupboy.com/2005/11/29/the-80-hour-myth/#comment-18</link>
		<dc:creator><![CDATA[Benjamin Listwon]]></dc:creator>
		<pubDate>Fri, 02 Dec 2005 19:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://startupboy.wordpress.com/2005/11/29/the-80-hour-myth/#comment-18</guid>
		<description><![CDATA[The interesting thing is that, for programmers or any internet workers, there is no consistent measure of &quot;work&quot; that one can use. Using my own experience (only because I know it), there are weeks where 60+ hours will be spent effing aroundand then there is one 2 or 3 hour burst of intense, very productive activity, while other weeks will be full of 40+ hours of mindless copy/paste activities or needless meetings. What is interesting about this is, even though the week where I only &quot;work&quot; for a few hours will have me up for 85% of the week, I find myself drained both physically and mentally when I spend a week doing busy work or in meetings.Keying off of your 5-point plan, I would also add that there can be no really effective productivity without an environment of like-minded, inherently curious people. It is very difficult to find the right mix, and to foster a culture of creativity without slipping dangerously into a lack of productivity. But when you have the right people, it is like a well tuned sports car; nothing will handle better, move faster and &quot;wow&quot; people more.Who are these people? Well, I have found that you need to find people who meet whatever definition you have for: - curious - creative - knowledgable - open-minded - introspectiveNote that none of the above are things like &quot;smart&quot; or &quot;talented&quot; because, to me at least, those kinds of attributes usually demonstrate an ability to retain fatcual minutia, and not the ability to be effective problem solvers. In the end, that is what you want. Not someone who knows every key binding in vim or emacs, but someone who will go find out how to use vim, because they need to edit a file to make their work, and everyone else&#039;s better.
]]></description>
		<content:encoded><![CDATA[<p>The interesting thing is that, for programmers or any internet workers, there is no consistent measure of &quot;work&quot; that one can use. Using my own experience (only because I know it), there are weeks where 60+ hours will be spent effing aroundand then there is one 2 or 3 hour burst of intense, very productive activity, while other weeks will be full of 40+ hours of mindless copy/paste activities or needless meetings. What is interesting about this is, even though the week where I only &quot;work&quot; for a few hours will have me up for 85% of the week, I find myself drained both physically and mentally when I spend a week doing busy work or in meetings.Keying off of your 5-point plan, I would also add that there can be no really effective productivity without an environment of like-minded, inherently curious people. It is very difficult to find the right mix, and to foster a culture of creativity without slipping dangerously into a lack of productivity. But when you have the right people, it is like a well tuned sports car; nothing will handle better, move faster and &quot;wow&quot; people more.Who are these people? Well, I have found that you need to find people who meet whatever definition you have for: &#8211; curious &#8211; creative &#8211; knowledgable &#8211; open-minded &#8211; introspectiveNote that none of the above are things like &quot;smart&quot; or &quot;talented&quot; because, to me at least, those kinds of attributes usually demonstrate an ability to retain fatcual minutia, and not the ability to be effective problem solvers. In the end, that is what you want. Not someone who knows every key binding in vim or emacs, but someone who will go find out how to use vim, because they need to edit a file to make their work, and everyone else&#8217;s better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

