Sunday, 14 March 2010 00:00

Chug, Chug, Vroom, and Expectancy Theory

Rate this item
(0 votes)

The Little Engine that Could

Or... I Think I Can

I have a book that sits in the bookshelf behind my desk and has been there for as long as I have had a desk—The Little Engine That Could, by Watty Piper. I have read it numerous times to each of my children and soon to my granddaughter, Kennedy. Each time I open it, the smell takes me back to my Dad's lap and a time when life was much easier. A time when my vocabulary was devoid of the word project. I am not sure if there is a direct connection between that word and life's simplicity, it is probably just an coincidence.

Positive Attitude

The book is about a project gone bad and the positive attitude it took to fix it. If you have not read it, the book metaphorically captures the essence of a failed project where the project's team members are left to find their own solution. The story is about an engine pulling a train load of food and toys over the mountain pass that has broken down. A little blue switching engine and the train's toys try to find an different engine to pull the train over the mountains. Other engines are too narcissistic, old, or tired. The engine that saves the project is the one that has a good attitude, the confidence to complete the job, and values the project's goal. The little blue engine is the benevolent leader who completes the project; the one that no one else believes can finish the job. This little leader has the "I think I can" attitude that makes dreams come to life. As with nearly all children's books, they are full of great business lessons; Derek Huether grasped the value of Green Eggs and Ham just last week.

Case Study: The Right Attitude

A client's Information Technology department was building a web-based tool. One of the features was integrating a third party tool. It would simply be a link on an internal web page to a provider's site. During the recovery audit interviews, one of the non-technical team members went on a tirade, wanting to remove the feature from the project. She wanted to manage the work as a separate project. Although the feature was isolated from the primary project it was very high risk due to the number of parties involved and the company's inexperience with third parties. Based on her inability to comprehend the issues, her involvement was minimized. Another person, although junior, was made the lead. He had the right attitude, was realistic about his capabilities, and took great pride at being assigned the responsibility. He rose to the occasion and lead the integration successfully.

Expectancy Theory

The little blue engine is great example of expectancy theory. If you think you can, your chances for success drastically increase. The theory, established by Victor Vroom (you thought I was going to bring in the Cat in the Hat, didn't you?), is based on three factors that motivate people—their attitude, their confidence in achieving the goal, and how the reward resonates with them. A project manager with the confidence and proper mind-set only needs to create the right reward and he or she can drive any team to complete a project successfully. Better yet, the attitude can infect the team with the same outlook, uncovering their leadership qualities. This observation is supported by Isaac, Zerbe & Pitt:

...leader interactions with followers permit the establishment of highly motivational working environments. In so doing, individuals acquire the means to transcend their traditional roles of supervisor, manager, or follower, and realize their potentials as leaders.

Motivation

The Little Engine That Could

I just takes motivation. Reflect on any project that has failed, the team's morale is dismal. There is little, if any, hope in achieving the project's goal, the team members fear losing their jobs, and no one sees a path to success. A proven method for improving moral is through relevant, timely, and accurate feedback. It helps promote their desirable behavior. Sonia Di Maulo (@ReadyToFeedback) has posted an article on team motivational basics that everyone should know.

I am a strong believer in trying new ways to break the dejected knuckle draggers. Listening, providing feedback, making decisions, building trust, and defending them; motivation takes work and imagination. I have never tried reading The Little Engine That Could or Green Eggs and Ham to perk the team up, I doubt it would get the desired effect. However, I have very successfully used a screaming flying monkey. Bringing out the little kid in us relieves the pressure and takes us back to the time before everything was a project.

So, remember, the next time you face the impossible, slowly repeat to yourself , "I think I can. I think I can. I think I can."

Read 7008 times

Related items

  • Process Mapping

    Process is at the core of any business. It makes work predictable, repeatable, and transferable. Without it we cannot scale our businesses. However, process can be a bane to making progress. Processes that work for a $10 million company have difficulties supporting a $30 million company. Trying to scale them to a $300 million company will not only fail but not address the issues that larger companies have that were never dreamt of in a smaller organization. Processes need to be discarded, revamped, and built—all of that without creating an overburdening bureaucracy.

    Anytime you need to go someplace, you first have to know where you are. Processes are never static and your company's current state is probably far from where you think it is. Hence, the first step is mapping out you company's current state followed by defining the future state. This is more than a logical map of the process; it must also include physical maps. Whether your process is solely to provide a service (say, website development) or physical (say, manufacturing) there are logistical issues that complicate the process flow. Without fully understanding those nuances, future state processes will not reach the desired efficiencies.

    For more information about process mapping fill out the form to the left and we will get in touch with you.

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • Tales of an Expert Witness: Sex, Lies, and Video Tape (Part II)

    Trust relationships, certifications, and standards sound like such a safe harbor. These sound like such great words in a proposal or statement of work. How could you possibly go wrong building a trusted relationship with a customer by committing to follow a standard? In fact, this can burn you… in court.

    No one ever starts a project with the goal of ending up in court. In fact, litigation may never cross your mind; after all, you have built a trusted partner relationship. Taking a few cautionary steps, however, will make your life easier if you end up in that ill-fated litigious position. Your best chances for success come long before you enter the courtroom—even before the project starts.

  • Comparing Organizational Change Management Models

    A few weeks ago, I set out to write a post on the comparison of various organizational change management (OCM) methodologies and realized that would be a disservice to my readers. It would simply drag you down the path of implementation while failing to focus you on building the foundation. The pressure was too much and I have relented to numerous requests on making that comparison. The caveat is that juxtaposing these models is not comparing different varieties of oranges or even apples and oranges; we are surely comparing the peel to the fruit they contain. Hence, comparing methodologies like Kotter's model (the peel), Prosci's ADKAR (the core), and General Electric's Change Acceleration Process (the whole fruit) need a different approach.

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

Sitemap