{"id":1833,"date":"2009-12-17T12:12:26","date_gmt":"2009-12-17T11:12:26","guid":{"rendered":"http:\/\/progmanager.wordpress.com\/?p=901"},"modified":"2009-12-17T12:12:26","modified_gmt":"2009-12-17T11:12:26","slug":"managing-for-autonomy","status":"publish","type":"post","link":"http:\/\/realisedevelopment.net\/index.php\/2009\/12\/17\/managing-for-autonomy\/","title":{"rendered":"Managing for Autonomy"},"content":{"rendered":"
\n
If we want engagement, and the mediocrity busting\u00a0results it produces, we have to make sure\u00a0people have autonomy over the four most\u00a0important aspects of their work:<\/div>\n
\n
    \n
  1. Task \u2013 What they do<\/li>\n
  2. Time \u2013 When they do it<\/li>\n
  3. Technique \u2013 How they do it<\/li>\n
  4. Team \u2013 Whom they do it with.<\/li>\n<\/ol>\n<\/div>\n
    After a decade of truly spectacular\u00a0underachievement, what we need now is less\u00a0management and more freedom \u2013 fewer individual\u00a0automatons and more autonomous individuals.<\/div>\n<\/blockquote>\n
    Daniel H. Pink<\/div>\n
    Want\u00a0to learn how to manage for autonomy? \u00a0Get in\u00a0touch.<\/div>\n