'Tis Better to be Effective Than Efficient

Effective Over Efficient


Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.

It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.

Effectiveness may just be the better target.

Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:

  • Build a shared understanding of the problem you are trying to solve
  • Establish clear guard rails for distributed decision making
  • Measure progress based on outcome, not output

Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.

You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective.


Three Steps for More Effective Projects

Problem Statement

Decision Filters

Measuring Business Value is not the Points

Excerpt from Beyond Requirements discussing Outcome over Output From B2T Training blog

Interview From Agile India 2017

For More Information

Beyond Requirements: Analysis with an Agile Mindset

Analysis Techniques for Product Owners

Do you like what you see here?

Subscribe to the KBPUpdate to get weekly notifications of new posts on the site and links to other resources across the internet that will help you determine the right things to deliver.

Would you like to see a sample of what you'll get?  Here are samples of past KBPUpdate issues .


Beyond Requirements


Learn More

Analysis Techniques for Product Owners


Learn More