{"id":2600,"date":"2008-12-01T16:40:35","date_gmt":"2008-12-01T20:40:35","guid":{"rendered":"http:\/\/calleam.com\/WTPF\/?p=2600"},"modified":"2015-01-08T18:29:00","modified_gmt":"2015-01-08T22:29:00","slug":"disconnect-failure","status":"publish","type":"post","link":"https:\/\/calleam.com\/WTPF\/?p=2600","title":{"rendered":"Disconnect Failure"},"content":{"rendered":"

The following entry is\u00a0part of the Pattern Library<\/a>. The Pattern Library records the common patterns of behaviours and events that have the potential to lead to project failure.<\/p>\n

\n

Pattern name : Disconnect Failure<\/strong><\/p>\n

In brief :
\n<\/strong>Project loses sight of its overall business objectives and ends up implementing a system that fails to meet the originally intended business objectives.<\/p>\n

Description :
\n<\/strong>Disconnect failures occur when the project’s intended business benefits fail to materialize because the project team were never clear on, or, lost sight of what it was they were trying to achieve.\u00a0 Disconnect failures occur in a number of ways and for a variety of reasons.\u00a0 Examples include;<\/p>\n

    \n
  1. The business objectives existed within the mind of the Project Sponsor but were never formally documented or communicated, as a result the project team lacked the reference point against which to align their efforts<\/li>\n
  2. The business objectives were defined, but once documented they were filed away and\u00a0never used as a reference point when making critical project decisions<\/li>\n
  3. Project\u00a0stakeholders have different objectives than that defined by the Project Sponsor and because of a lack of governance, stakeholders divert (either internationally or unintentionally) the project in a different direction<\/li>\n<\/ol>\n

    Because many organizations fail to track the business benefits of their technology investments, disconnect failures\u00a0are far more common than many organizations realise.\u00a0 The following study by the Economist Intelligence Unit<\/a> shows that a third of business process change projects fail to deliver their intended\u00a0benefits.\u00a0 This figure is likely a typical for many organizations.<\/p>\n

    Typical sequence of events :<\/strong><\/p>\n

      \n
    1. Business objectives are either never defined or expressed in vague terms<\/li>\n
    2. Lack of management oversight<\/li>\n
    3. Finishing the deliverables on time becomes the project’s focus rather than focusing on ensuring the originally planned business benefits are realized<\/li>\n<\/ol>\n

      Negative effects :<\/strong><\/p>\n

        \n
      1. Failure to realise intended business benefits<\/li>\n
      2. Lost opportunity cost<\/li>\n<\/ol>\n

        Related patterns<\/strong><\/p>\n

          \n
        1. Transitional failure<\/li>\n
        2. Alignment failure<\/a><\/li>\n
        3. Schedule pressure failure<\/a> (when under schedule pressure teams often focus on deliverables and schedule more than they do on business benefits)<\/li>\n<\/ol>\n

          Suggested Actions :<\/strong><\/p>\n

            \n
          1. Ensure appropriate oversight activities are included in the project and that the Project Sponsor is an active part of the project<\/li>\n
          2. Define objectives in clear and measurable ways<\/li>\n
          3. Include periodic “alignment” reviews to ensure the project is moving towards its intended goals<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

            The following entry is\u00a0part of the Pattern Library. The Pattern Library records the common patterns of behaviours and events that have the potential to lead to project failure. Pattern name : Disconnect Failure In brief : Project loses sight of its overall business objectives and ends up implementing a system that fails to meet the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[53,9],"class_list":["post-2600","post","type-post","status-publish","format-standard","hentry","category-pattern","tag-disconnect-failure","tag-pattern-in-failure"],"_links":{"self":[{"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=\/wp\/v2\/posts\/2600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2600"}],"version-history":[{"count":27,"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=\/wp\/v2\/posts\/2600\/revisions"}],"predecessor-version":[{"id":7463,"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=\/wp\/v2\/posts\/2600\/revisions\/7463"}],"wp:attachment":[{"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/calleam.com\/WTPF\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}