sustainable-pace


How do I make the case for Sustainable Pace?


In a workplace where many people (including management) feel long hours is the way to demonstrate commitment, what are effective arguments that such practices are harmful, not just to the team members themselves, but to the project itself?
I am familiar with - and I believe - the common arguments: the risk of burnout, compromised quality, insufficient attention to keeping our skills up and our code malleable. But what arguments are most persuasive? What is the most persuasive way to deliver them?
Update Thanks, everyone, for all the great links to data - it's helpful, but what I'm really after is what arguments will be persuasive to people who are deeply invested in the crunch-mode ethic. I think I need more than data to shake loose their preconceived notions.
I had some success by comparing people to servers. If you had servers utilized at 125% sustained rate, with no redundancy, no disaster recovery and greater workload in the pipeline you'd be a fool not to plan to add capacity real soon. Trying to drive people under similar utilization and also without backup or redundancy is actually riskier because people are even more likely than machines to break down under those conditions.
Lots of good points to be made by continuing the analogy.
Have a look at The Mythical Man Month, Peopleware, and Slack. Then cite the hard work and real numbers of those more credible than yourself.
Use statistics.
It is really common sense. Alas not everyone has it.
There is no good way to bring it up, without being seen as a whistle blower. At some point people will start dropping like flies and productivity will grind to a halt.
There are many naval stories about bad captains.
See "Why Crunch Mode Doesn't Work: 6 Lessons", by Evan Robinson. It's a very quick, very persuasive read, and it includes citations to research over the last hundred years (!) if you want more detail.
In addition to seconding #Matthew's suggestion of The Mythical Man-Month, I would recommend 37Signals's REWORK. It has plenty of excellent arguments in favor of workplace sanity. I would advise reading and digesting the book as a way to internalize the rationales. Directly quoting the book to the kind of people you are trying to convince might not be as effective.
Also, if everything fails and your workplace continues to be a toxic, dysfunctional mess, reading REWORK might get you fired up to start your own company. It worked for me.

Related Links

How do I make the case for Sustainable Pace?

Categories

HOME
pdf
listview
pypi
oracle11g
c#-4.0
tinymce
sqlite-net-extensions
elm
dxl
fsm
blueprintjs
fancybox
indesign
usergrid
highlight.js
saxon
angular-ui
custom-wordpress-pages
zapier
xlsxwriter
css-animations
claims-based-identity
icloud-api
filezilla
strncpy
instant-messaging
perlin-noise
repo
uiswipegesturerecognizer
host
libraries
sqlite2
squib
texmaker
s
xml-documentation
python-webbrowser
csound
knpmenubundle
pillow
cudafy.net
or-tools
specrun
database-optimization
markojs
ready-api
pervasive-sql
rtbkit
msys
google-places
comobject
service-accounts
fluid-dynamics
p2
truevault
tablelayout
angularjs-ng-click
htmlcleaner
marmalade
bundles
transcoding
multiprocessor
inbox
quartz-graphics
file-locking
pushbackinputstream
mqx
clipper
bluepill
multipage
labwindows
qtkit
buildr
asyncfileupload
custom-backend
adk
vdsp
genshi
servicehost
iphone-web-app
paster
infrastructure
suppress
jquery-ui-droppable
simpletest
thread-local-storage

Resources

Encrypt Message



code
soft
python
ios
c
html
jquery
cloud
mobile