• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
  • Skip to footer
  • Home
  • About Mel Bost
  • About the Book

Mel Bost - PMO Expert

PMO Expert

  • PMO
    • PMO Leadership
    • PMO Maturity
    • PMO Benchmarking
    • PMO Execution
  • Risk Management
  • SMART Goals
  • Project Information
    • Project Lessons Learned
    • Project Business Requirements
    • Project Communications
    • Project Community
    • Project Environment
    • Project Manager Qualities
  • Knowledge Management
  • Practices
    • Next Practices
    • Best Practices

What is “Leverage” and How Can Project Managers Use It To Their Advantage?

August 15, 2014 by Mel Bost Leave a Comment

Greek mathematician and inventor Archimedes said “Give me a place to stand, and with a lever I will move the whole world.”

As a project manager, you have probably used the term “lever” in the engineering or physics context to describe a device that can be used to gain a “mechanical advantage” in a given scenario.  It means that you can apply force, in varying amounts, to perform useful work.

Likewise, “leverage,” a commonly used word derived from the word “lever,” means the application of any number of concepts to achieve some advantage in a given scenario for the person or group that is skilled in the application of the concept.

Some forms of leverage might be an individual or group’s position in an organization, a specialized knowledge, a unique piece of information, or a robust technology, etc.

A good example of technology as a “leveraging” variable arose a few weeks back in a New York Yankees baseball game with the Detroit Tigers.  With Yankee Mark Teixeira on third base, the batter hit a ground ball to the infield that resulted in a throw from first base to home to stop a run from scoring.  Teixeira slid into home plate and touched the base with his left hand while the Detroit catcher was almost simultaneously taking the throw from first base and applying the tag to Teixeira.

The home plate umpire called Teixeira out, but Yankees Manager Joe Girardi disagreed.  He challenged the call while his Yankee bench coach called the press box to get some other camera views of the play.  Under challenge, the home plate umpire and umpiring crew chief consulted with the instant replay staff, whose use of camera technology has become an accepted practice in Major League Baseball.

The challenge by Girardi was upheld, and the home plate umpire’s call was reversed.

Girardi had used technology to leverage the situation.

Prior to instant replay technology and challenge, the play would have resulted in an out for the Yankees, and no run scored.

Think of areas in your project management experience where you or a project team member, stakeholder ,or third party has used position, knowledge, information, or technology to “leverage” a situation.  How might you have prepared yourself or your team to “leverage” your outcomes and your project objectives?

Those of you who are familiar with my recent book, Lessons Learned:  Taking Project Management to a New Level in a Continuous Process Improvement Framework, know that I have also applied “leverage” in an organizational dynamics connotation to describe how project lessons learned can be derived from seeing single projects as “events,” but recognizing that a more “leveraging” connotation for project groups can be identified. This can help you make lasting changes in project or business processes by identifying “patterns of behavior” among a group of projects subject to the same project environment.

“Leverage,” in this case, is insight about how project teams behave, how they organize themselves, what management principles and objectives they choose to follow, and what they value as being the “truth” for their direction.

If you as a project manager have not considered “leverage” in your day-to-day work process, give this some thought.

You might turn out to be the “lever” that Archimedes referred to who can move the whole world.

Thanks for reading my 100th Blog Post!

Filed Under: Best Practices, Project Lessons Learned

Reader Interactions

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search The Site

About Mel Bost

Mel Bost is a project management consultant specializing in project closeout and lessons learned, as well as process improvement, best practices, and benchmarking. For the past several years, he has been teaching “Project Management for Research” to postgraduate students at Arizona State University, as well as developing new approaches to the research process. Read More

Project Management Lessons Learned: A Continuous Process Improvement Framework

The NERS department congratulates C. Melvin Bost, Jr., on the publication of his new book.

Categories

Footer

Recent Posts

  • To My Project Community Readers:  Please Support the Fastest Path to Zero Initiative
  • The Role of Cognitive Sciences in Project Management and PMO Performance
  • A Tribute to Louis Tice: What He Contributed to my Thoughts about Project Management
  • How Can Project Managers Use the “Scientific Method” to Finesse Projects?
  • When is Project Management Much More Than Just Cost, Schedule, Scope and Quality?
  • The Importance of Perception in Capturing and Documenting Project Lessons Learned

Read the Book

Search the Site

© 2023 · Mel Bost, PMO Expert · Customized by Element Associates