Effectiveness vs. Efficiency

Post written by Chris Spagnuolo. Follow Chris on Twitter 2 comments

I’ve been stuck in airports all day today between Denver and Charlotte but all has not been lost.  While waiting around for my flights, I’ve been reading The 4-Hour Workweek by Timothy Ferriss.  Although most of the book is dedicated to illustrating ways you can improve your work life and your personal life, one section of the book is focused on the difference between being effective and being efficient.  According to Ferriss, effectiveness is “doing the things that get you closer to your goals.”  Efficiency is “performing a given task (whether important or not) in the most economical manner possible.”  He asserts that “being efficient without regard to effectiveness is the default mode of the universe.”

We can learn a great deal from these brief statements, especially as it relates to implementing agile practices.  Although agile practices allow us to become very efficient, we must be sure to reap the true benefit of these practices by becoming extremely effective.  Scrum, by its very nature promotes effectiveness.  When we continually prioritize backlog items at the start of each iteration, we are increasing our effectiveness.  We are continually working on the most important items that get us closer to reaching our goal.    Backlog items that are unimportant or no longer relevant are eliminated, further increasing our effectiveness.  In addition, the inspect and adapt mantra of Scrum helps us become more effective (and efficient) as well.  By constantly reflecting on our practices and adapting them as necessary, we identify our inefficiencies and eliminate them.  By the same means we discover our strengths and exploit them to become even more efficient and effective.  Ferriss sums it up best by writing “What you do is infinitely more important than how you do it.  Efficiency is still important, but it is useless unless it is applied to the right things.”

© Copyright 2007, ChrisSpagnuolo.com GeoScrum! by Chris Spagnuolo is licensed under a Creative Commons Attribution 3.0 United States License.

Share on Facebook
Post to Google Buzz
Bookmark this on Yahoo Bookmark
Share on FriendFeed
Bookmark this on Digg
Share on reddit
Share on LinkedIn
Share on StumbleUpon
Bookmark this on Delicious

  1. Chris Spagnuolo's EdgeHopper said,

    [...] course, the underlying concern in both of these cases is keeping the QA’s and the devlopers effectively utilized during an iteration. Software quality always seems to boil down to a utilization/cost equation [...]

  2. Did we forget how to talk to each other? | said,

    [...] Twitter is cool. Wikis are neat. SharePoint is, hmmm, good? And email is email. These tools are all useful in helping us communicate with each other when we’re separated by great distances. They help us bridge the gap by providing fast, efficient means of communication. It doesn’t get more efficient than Twitter’s 140 character limit. But take a close look at these tools. They all share a common characteristic. They’re all based on written communication. While the written word may be very efficient for transferring information, it is not very effective at persuading people or making a real impact. And there is a tremendous difference between being efficient and being effective. [...]

Add A Comment


Creative Commons License
©2011 Edgehopper.com. Please don't copy me, it's bad karma.
Edgehopper by Chris Spagnuolo is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.