Is the Enemy Us or Fate? (4 of 5)

via Flickr by ashapiro515

via Flickr by ashapiro515

Reasoning by Analogy

To reason by analogy; recognize a past experience is similar to the current situation, evaluate what did and didn’t work in the past situation, make a choice about what to do and definitely not do.  Certainly analogical reasoning differentiates the novice from the grizzled veteran PM, based on the sheer number of stored past experiences.

For example, if you are defining the scope of a computer server development project and have worked on similar projects, experience will tell you that the printed circuit (PC) boards will require multiple prototypes (“turns”) before a workable version is obtained.  Your experience is PC boards always have required multiple iterations, thus multiple turns should be scheduled.  On the other hand, your hardware developers may be telling you they expect to nail it on the first round.  Do you believe them or your experience?  They are telling you one and you’ve never see less than four.  This is where the analysis comes to play.

Use of analogies can be especially powerful when applied in an area unrelated to the past experience.  Many times this results in innovation. One technique to foster innovation is having team members with varied backgrounds, thus avoiding groupthink, but this is a team item which we will leave to another time.

A few words of caution are needed in use of analogies.  We tend to focus on similarities and downplay differences.  Sometimes we are reluctant to surface and validate the underlying assumption of the two situations.  We have to be wary of having a solution in search of a problem.

Up to this point we have discussed analogies as a positive contributor to the situation; a way to move forward.  What happens when our experience fails to provide an analogy?  The chances are you have encountered a novel situation where the pattern recognition doesn’t square with past experiences.

Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • email
  • LinkedIn
  • MySpace
  • Reddit
  • Slashdot
  • StumbleUpon
  • Technorati
  • Yahoo! Buzz

Technorati Tags: , , , ,

About the Author

Wayne Goulding

Like many of his colleagues Wayne is an “accidental project manager”, starting as a mechanical designer, advancing into engineering, passing into engineering planning, growing to lead global, high-tech, complex programs, advising senior management in program/project process development. Wayne’s decades of work have yielded a diverse experience set; his jobs included, designing of machine tools, designing for automated assembly, manufacturing engineer, managing a software application development project, managing customer relations, managing product release to market programs, leading a non-profit organization, managing telecom upgrade projects, managing customer call center projects, managing project portfolio process development; his career has journeyed through industry sectors in metal-working/assembly manufacturing, nuclear energy, computer manufacturing, automotive, telecommunications; his forms of employment have run the full gambit, from full-time employee, to contractor, to consultant; he has contributed directly to, IBM, Westinghouse, Intuit, PMI-Silicon Valley Chapter, Honda/Acura, SoftReach Services, plus others; thru customer interfacing jobs he has worked with numerous Fortune 500 corporations many at the executive level. Educationally, Wayne has degrees in Mechanical Engineering, Business Administration, and a certificate in Program/Project Management. He is a certified PMI Project Management Professional (PMP) and is past president of the PMI-Silicon Valley chapter. With all the above, and more, it is clear Wayne is not one to sit idle. He is constantly doing, learning or teaching. Philosophically he believes a person’s success is measured in project achievements, new perspectives gained, new people met and help given along the way. (www.waynegoulding.com) (The Business of Project Management - waynegoulding-blog.com)
Creative Commons License
Note: This work and all associated comments are licensed under a Creative Commons Attribution-Noncommercial 3.0 United States License.

Leave a Reply