The Unrelenting Pursuit of Effectiveness
What we can learn from Peter Drucker
Peter Drucker does not get talked about a lot any more. A professor and prolific author, Drucker is arguably the greatest thinker about business, organizations and management of the last 100 years.*
He possessed a unique gift to see where our world was headed - away from the production of physical goods to knowledge work. With that farsighted view, he deeply considered its implications.
One of his earliest books, The Effective Executive was published in 1966. And despite its 59 years of age, its advice remains timeless.
Today - I wanted to share a few ideas of Drucker’s that I continue to ponder months after having read the book.
Anyone can be an executive - title does not matter. Here’s how Drucker described it - “if you are responsible for a contribution that materially affects the capacity of the organization to perform and to obtain results” you are an executive.
The most important task of any executive is to get the right things done. “Effectiveness is a habit.”
How you spend your time will determine your effectiveness. But you have to know where you are spending your time first. Once you do, you can determine how to improve. Keep a time log.
A commitment to contribution will further drive effectiveness. Must have a laser focus on actually making a difference rather than grandstanding, ego, etc.
Take full advantage of the unique strengths of each team member. Focus on their strengths, rather than bringing up their weaknesses.
Jobs should be demanding and big. Challenge is necessary to bring out each person’s strength.
If good people are failing in a job, despite having succeeded elsewhere, it is the job that is the problem, not the people. Redefine the role.
Do the first things first and one at a time. You must also then say no to most other things.
Limit your decision making. What are the decisions that must be made - the critical ones
Most problems are not unique - but symptoms of an overarching generic issue. Create policy/process/standards about the generic issue first.