Force of Habit: How Stephen Strasburg and Tommy John Surgery Relate to Business Leaders

I recently read an article in ESPN the Magazine (04/02/2012) about Washington Nationals Pitcher, Stephen Strasburg, among others who have had Tommy John surgery.  The surgery was required due to a tear in the elbow.  The author, Lindsay Berra, investigated what causes so many injuries and how it has impacted the game of baseball in terms of games lost by injured pitchers as well as the monetary loss of pitchers sitting on the shelf unable to play the game.

Most of us can think of at least one other pitcher, besides Tommy John, who has had the surgery: Kerry Wood, A.J. Burnett, C.J. Wilson, and Christ Carpenter are some recent pitchers mentioned in the article.  It has become so common, and the surgery so successful, that when the injury occurs teams count on those pitchers to return to full strength in about 18 months’ time.  They do not typically worry about how much money they are wasting, and better yet, how they could work to prevent these injuries.

Why do they typically occur?  The two common factors mentioned by Berra are overuse of a pitchers arm, and poor form in their pitching stride.  “To throw a baseball properly, a pitcher must get into the right position at the right time with the right succession of movements, like dominoes falling.”  Greg Maddux is a provided example of someone who utilized technology to prolong their career.  Nolan Ryan even mentions using anything available to improve his motions to prolong his career.  Both pitchers had long, largly injury free, hall of fame worthy careers that lasted into their 40’s.

Lindsay Berra goes on to discuss how there are pitching coaches still stuck in their outdated thoughts of how they coach a pitcher.  In the major leagues the thought is, if it isn’t broken and the pitcher is winning games, don’t fix it.  Berra mentions that some of these coaches seem to refuse to accept technology as a tool for improving a pitchers form.

Technology exists that can record a pitchers motions and a trained specialist can review that motion and provide recommended solutions for the pitcher to correct those unnatural motions.  There are better ways and coaches still refuse to adapt to use them, even though they can save them time and money on the use of a pitcher.

What does this have to do with business?  A lot actually.  This is a perfect example of a common occurrence in the business world.  How many bosses, or even clients, have you worked with whose thought process seems so archaic?  How many projects have you been on that were perceived to be running smoothly with positive results only to see unexpected problems occur that derailed the project?  These are the bosses that refuse to change due to the force of existing habits, the comfort of what they already know.

Risk management can be a major issue often overlooked.  There is not always a proper assessment of potential risks, such as failed technology or unfortunate budget cuts.  Perhaps the risk is the customer demands a change to a project’s requirements but your development organization does not have a process or plan in place for such sudden circumstances.  Maybe there is new technology out there that could help you to do your job much better, but your boss or client does not want to fund new equipment.  Maybe you were unknowingly provided the wrong piece of technology for the job and you later discover, only after the project has run off course, that there was something more suitable that could have prevented the whole disaster.

There are several scenarios I could write about, but the point is that it can be frustrating to work on a project that only after problems occur do you realize there were better options.  Pitchers want to pitch so they won’t stop to question their coach, just as project employees won’t always question their boss’ tactics if things are currently running smoothly.

Baseball, like so many project organizations, could benefit from being more proactive.  The solution to continue with the old school way is only a short term fix.  The end result could potentially end a baseball career or a project.  A proactive and continued effort from the start could save the team or a company millions of dollars, as well as the lost time to injury or project risks.

Pitchers and coaches could use technology to improve the pitchers form, what could a project team do?  Project teams could reexamine the development model they are using; perhaps the old stove pipe model could finally be laid to rest.  This could lead to the use of process improvement efforts where current processes are reviewed and improved along with proper policing to ensure process is followed.

Pitchers who welcomed change, like Greg Maddux and Nolan Ryan (lets mention 42 year old Mariano Rivera and 49 year old Jamie Moyer as well), found ways to remain effective and successful for a long period of time and their names will stand the test of time in the baseball annals.  We could include Tommy John as well for being the namesake of the surgery that prolonged his career.

Managers who are progressive and welcome change, whom are not afraid of failure, and resist the temptation to slip into a comfort zone, are the leaders who will remain relevant for longer periods of time in the always changing world of technology and project development.

Past innovators like Benjamin Franklin, Thomas Edison, John D. Rockefeller, Conrad Hilton, Henry Ford, Ray Kroc, and the late Steve Jobs, to current leaders like Bill Gates, Oprah Winfrey, Richard Branson, Phil Knight, and Jeff Bezos.  They all took risks and accepted change in their culture without knowing the true outcome until it happened.

While they may be outside the scope of what you strive for, if you want to avoid the blow to the elbow and remain relevant, as well as show you can save your project time and money, avoid the comfort zone.  Avoid the force of habit.

About these ads

Developing a software maintenance strategy? Some tips on where to start.

There are several places where you can find information on developing a software maintenance strategy.

Two common software process models are ITIL and CMMI.  ITIL is a set of best practices for IT services.  If your organization provides IT services, including providing a service desk, ITIL helps to provide practices to help them develop their strategy (ITIL, 2012).  CMMI is a process improvement framework that can be used for both development and maintenance organizations.  CMMI’s goals are to identify strengths and weaknesses and to turn those weak process areas into strengths (SEI, 2012).  Determining your approach comes from what the goals of the client are for their product.  ITIL and CMMI can help.

For a set of standards, you can look to ISO.  ISO/IEC 14764:2006 provides details for the management of software maintenance applications, including for planning, execution and control, review and evaluation, and closure of the maintenance process (ISO, 2011).  It can work for managing one or more maintenance projects.

IBM created a report on best practices for software maintenance for operating data warehouses.  The importance of a study like this is with the increase in Cloud computing.  Cloud related products would have to increase the size or quantity of data warehouses as a client moves to use contractors to store their data and applications (IBM, 2005).  If you are such a contractor, this is a good resource to help develop a strategy.  This can also be helpful for other application types that conduct maintenance with an impact on several applications or services.

References

ITIL. (2012). What is ITIL? Retrieved from: http://www.itil-officialsite.com/AboutITIL/WhatisITIL.asp.

Carnegie Mellon’s Software Engineering Institute. (2012). CMMI Overview. Retrieved from: http://www.sei.cmu.edu/cmmi/.

International Organization for Standardization. (2011). ISO/IEC 14764:2006. Retrieved from: http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39064.

IBM. (2005). Data Warehouse Software Maintenance Strategy.  Retrieved from: ftp://ftp.software.ibm.com/software/data/pubs/papers/dw-maint-strategy.pdf.

What is a project?

The following are some characteristics that define what a project should be.  I enjoy going back and reading this and comparing it to so called projects I have worked on.  Those projects that seem to have no planning, no goals, are under budgeted, and seem to run on and on with no end in sight.

  • A project is undertaken to create something, such as a product, service, or result (PMI, 2008).  There has to be something that shows a finished result.  It can result in a small component of another item, be a creation of the capability to perform a service, or be the finished document of a research project.
  • A project is temporary, having a definite beginning and end (PMI, 2008).  This is ideal, but we know some projects can run on, but to the best of a team’s abilities there is a defined beginning and a product with an end in sight.  It can be defined as a long or short project, but it is defined.  They can run a week, they can run for several years, but there must be a beginning and an end (Microsoft.com, 2012).
  • A project is an endeavor.  People need to do work with equipment on tasks that have an intention to them.  Nothing happens spontaneously.
  • A project has objectives that must be met to be completed (PMI, 2008).  To reach the endpoint, objectives must be met.  If objectives are not met a project can be terminated.
  • A project can be repeated, having repeated tasks (PMI, 2008).  As long as there is a unique element such as time and location, the fundamental uniqueness of the project work can be repeated, such as the construction of similar office buildings.   The project team, materials, and base design can be the same, but there may be some unique designs, circumstances, and contractors used.
  • A project can involve a single person, a single organizational unit, or multiple organizational units (PMI, 2008).  There
  • A project is an endeavor.  People need to do work with equipment on planned tasks that have an intention to them.  Nothing happens spontaneously (Microsoft.com, 2012).
  • A project has a plan.  The plan details the direction and purpose of the project, known as the scope.  It also details many of the details listed above, such as the objectives, estimated costs and schedule, tasks, materials, and estimated size of the project team.
  • A project is not an ongoing work effort, such as following an organization’s existing procedures (PMI, 2008).  Ongoing operations have no established end date and could run indefinitely, such as accounting and human resources (Microsoft.com, 2012).

Examples of projects include creating the mirror for the Hubble Space Telescope (component of another item), creating a new marketing display at Macy’s (business function that supports production), or building a house (outcome).  Projects exist at home, such as cooking a dinner, planting a garden, or repainting a room.

References

Project Management Institute (2008). A guide to the project management body of knowledge (PMBOK guide), Ch 1 & 2. Newtown Square, PA: Project Management Institute, Inc.

Microsoft.com. (2012). A short course in project management. Retrieved from: http://office.microsoft.com/en-us/project-help/a-short-course-in-project-management-HA010235482.aspx.

Follow

Get every new post delivered to your Inbox.

Join 37 other followers

%d bloggers like this: