The Pitfalls of Project Status Reporting
All too frequently, executives are caught by surprise when projects -- especially complex IT projects -- run into trouble. But complex projects do not fail overnight; they fail one day at a time, and generally only after numerous warning signs. The authors have been involved in 14 academic studies a...
Gespeichert in:
| Hauptverfasser: | , , , |
|---|---|
| Körperschaft: | |
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
[Erscheinungsort nicht ermittelbar]
MIT Sloan Management Review
2014
|
| Ausgabe: | 1st edition. |
| Schlagworte: | |
| Online-Zugang: | lizenzpflichtig |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
MARC
| LEADER | 00000cam a22000002 4500 | ||
|---|---|---|---|
| 001 | ZDB-30-ORH-047383216 | ||
| 003 | DE-627-1 | ||
| 005 | 20240228121103.0 | ||
| 007 | cr uuu---uuuuu | ||
| 008 | 191023s2014 xx |||||o 00| ||eng c | ||
| 035 | |a (DE-627-1)047383216 | ||
| 035 | |a (DE-599)KEP047383216 | ||
| 035 | |a (ORHE)53863MIT55317 | ||
| 035 | |a (DE-627-1)047383216 | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rda | ||
| 041 | |a eng | ||
| 100 | 1 | |a Thompson, Ronald |e VerfasserIn |4 aut | |
| 245 | 1 | 4 | |a The Pitfalls of Project Status Reporting |c Thompson, Ronald |
| 250 | |a 1st edition. | ||
| 264 | 1 | |a [Erscheinungsort nicht ermittelbar] |b MIT Sloan Management Review |c 2014 | |
| 300 | |a 1 online resource (8 p.) | ||
| 336 | |a Text |b txt |2 rdacontent | ||
| 337 | |a Computermedien |b c |2 rdamedia | ||
| 338 | |a Online-Ressource |b cr |2 rdacarrier | ||
| 520 | |a All too frequently, executives are caught by surprise when projects -- especially complex IT projects -- run into trouble. But complex projects do not fail overnight; they fail one day at a time, and generally only after numerous warning signs. The authors have been involved in 14 academic studies about the ways in which individuals report (and misreport) the status of IT projects and how the recipients of those reports respond to the information they receive. The authors' research suggests that understanding the underlying dynamics of project status reporting can help limit the chances of nasty surprises. In particular, they identify five "inconvenient truths" about project status reporting: 1. Executives can't rely on project staff and other employees to accurately report project status information and to speak up when they see problems. Many employees have a tendency to put a positive spin on anything they report to senior management. When the organizational climate is not receptive to bad news, truthful reporting can be inhibited 2. A variety of reasons can cause people to misreport about project status. Executives tend to attribute misreporting to poor ethical behavior on the employee's part. In fact, employees misreport for a variety of reasons; individual traits, work climate and cultural norms all can play a role. 3. An aggressive audit team can't counter the effects of project status misreporting and withholding of information by project staff. Executives may conclude that the best way to address the problem of misreporting is to rely on auditors to make sure that project status reports are accurate. However, once auditors are added to the mix, negative organizational dynamics can lead to a dysfunctional cycle that results in even less openness. 4. Putting a senior executive in charge of a project may increase misreporting. Although having a senior executive as a project sponsor often proves wise politically and can help in securing resources for a project, the involvement of senior leaders does not make it any easier to track project status. 5. Executives often ignore bad news if they do receive it. A number of the authors' studies found situations where employees went to share their concerns about a project with powerful decision makers who had the ability to change the course of the project (or stop it), but were unsuccessful. The authors propose solutions to reduce the risk of being blindsided by any of these inconvenient truths.... | ||
| 650 | 0 | |a Project management | |
| 650 | 4 | |a Gestion de projet | |
| 650 | 4 | |a Project management | |
| 700 | 1 | |a Iacovou, Charalambos |e VerfasserIn |4 aut | |
| 700 | 1 | |a Smith, H. |e VerfasserIn |4 aut | |
| 700 | 1 | |a Keil, Mark |e VerfasserIn |4 aut | |
| 710 | 2 | |a Safari, an O'Reilly Media Company. |e MitwirkendeR |4 ctb | |
| 856 | 4 | 0 | |l TUM01 |p ZDB-30-ORH |q TUM_PDA_ORH |u https://learning.oreilly.com/library/view/-/53863MIT55317/?ar |m X:ORHE |x Aggregator |z lizenzpflichtig |3 Volltext |
| 912 | |a ZDB-30-ORH | ||
| 912 | |a ZDB-30-ORH | ||
| 951 | |a BO | ||
| 912 | |a ZDB-30-ORH | ||
| 049 | |a DE-91 | ||
Datensatz im Suchindex
| DE-BY-TUM_katkey | ZDB-30-ORH-047383216 |
|---|---|
| _version_ | 1818767353206276096 |
| adam_text | |
| any_adam_object | |
| author | Thompson, Ronald Iacovou, Charalambos Smith, H. Keil, Mark |
| author_corporate | Safari, an O'Reilly Media Company |
| author_corporate_role | ctb |
| author_facet | Thompson, Ronald Iacovou, Charalambos Smith, H. Keil, Mark Safari, an O'Reilly Media Company |
| author_role | aut aut aut aut |
| author_sort | Thompson, Ronald |
| author_variant | r t rt c i ci h s hs m k mk |
| building | Verbundindex |
| bvnumber | localTUM |
| collection | ZDB-30-ORH |
| ctrlnum | (DE-627-1)047383216 (DE-599)KEP047383216 (ORHE)53863MIT55317 |
| edition | 1st edition. |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>03810cam a22003972 4500</leader><controlfield tag="001">ZDB-30-ORH-047383216</controlfield><controlfield tag="003">DE-627-1</controlfield><controlfield tag="005">20240228121103.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">191023s2014 xx |||||o 00| ||eng c</controlfield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)047383216</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)KEP047383216</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ORHE)53863MIT55317</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)047383216</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Thompson, Ronald</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="4"><subfield code="a">The Pitfalls of Project Status Reporting</subfield><subfield code="c">Thompson, Ronald</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">1st edition.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">[Erscheinungsort nicht ermittelbar]</subfield><subfield code="b">MIT Sloan Management Review</subfield><subfield code="c">2014</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 online resource (8 p.)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">All too frequently, executives are caught by surprise when projects -- especially complex IT projects -- run into trouble. But complex projects do not fail overnight; they fail one day at a time, and generally only after numerous warning signs. The authors have been involved in 14 academic studies about the ways in which individuals report (and misreport) the status of IT projects and how the recipients of those reports respond to the information they receive. The authors' research suggests that understanding the underlying dynamics of project status reporting can help limit the chances of nasty surprises. In particular, they identify five "inconvenient truths" about project status reporting: 1. Executives can't rely on project staff and other employees to accurately report project status information and to speak up when they see problems. Many employees have a tendency to put a positive spin on anything they report to senior management. When the organizational climate is not receptive to bad news, truthful reporting can be inhibited 2. A variety of reasons can cause people to misreport about project status. Executives tend to attribute misreporting to poor ethical behavior on the employee's part. In fact, employees misreport for a variety of reasons; individual traits, work climate and cultural norms all can play a role. 3. An aggressive audit team can't counter the effects of project status misreporting and withholding of information by project staff. Executives may conclude that the best way to address the problem of misreporting is to rely on auditors to make sure that project status reports are accurate. However, once auditors are added to the mix, negative organizational dynamics can lead to a dysfunctional cycle that results in even less openness. 4. Putting a senior executive in charge of a project may increase misreporting. Although having a senior executive as a project sponsor often proves wise politically and can help in securing resources for a project, the involvement of senior leaders does not make it any easier to track project status. 5. Executives often ignore bad news if they do receive it. A number of the authors' studies found situations where employees went to share their concerns about a project with powerful decision makers who had the ability to change the course of the project (or stop it), but were unsuccessful. The authors propose solutions to reduce the risk of being blindsided by any of these inconvenient truths....</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Project management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Gestion de projet</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Project management</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Iacovou, Charalambos</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Smith, H.</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Keil, Mark</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="710" ind1="2" ind2=" "><subfield code="a">Safari, an O'Reilly Media Company.</subfield><subfield code="e">MitwirkendeR</subfield><subfield code="4">ctb</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="l">TUM01</subfield><subfield code="p">ZDB-30-ORH</subfield><subfield code="q">TUM_PDA_ORH</subfield><subfield code="u">https://learning.oreilly.com/library/view/-/53863MIT55317/?ar</subfield><subfield code="m">X:ORHE</subfield><subfield code="x">Aggregator</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">BO</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield></record></collection> |
| id | ZDB-30-ORH-047383216 |
| illustrated | Not Illustrated |
| indexdate | 2024-12-18T08:48:32Z |
| institution | BVB |
| language | English |
| open_access_boolean | |
| owner | DE-91 DE-BY-TUM |
| owner_facet | DE-91 DE-BY-TUM |
| physical | 1 online resource (8 p.) |
| psigel | ZDB-30-ORH |
| publishDate | 2014 |
| publishDateSearch | 2014 |
| publishDateSort | 2014 |
| publisher | MIT Sloan Management Review |
| record_format | marc |
| spelling | Thompson, Ronald VerfasserIn aut The Pitfalls of Project Status Reporting Thompson, Ronald 1st edition. [Erscheinungsort nicht ermittelbar] MIT Sloan Management Review 2014 1 online resource (8 p.) Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier All too frequently, executives are caught by surprise when projects -- especially complex IT projects -- run into trouble. But complex projects do not fail overnight; they fail one day at a time, and generally only after numerous warning signs. The authors have been involved in 14 academic studies about the ways in which individuals report (and misreport) the status of IT projects and how the recipients of those reports respond to the information they receive. The authors' research suggests that understanding the underlying dynamics of project status reporting can help limit the chances of nasty surprises. In particular, they identify five "inconvenient truths" about project status reporting: 1. Executives can't rely on project staff and other employees to accurately report project status information and to speak up when they see problems. Many employees have a tendency to put a positive spin on anything they report to senior management. When the organizational climate is not receptive to bad news, truthful reporting can be inhibited 2. A variety of reasons can cause people to misreport about project status. Executives tend to attribute misreporting to poor ethical behavior on the employee's part. In fact, employees misreport for a variety of reasons; individual traits, work climate and cultural norms all can play a role. 3. An aggressive audit team can't counter the effects of project status misreporting and withholding of information by project staff. Executives may conclude that the best way to address the problem of misreporting is to rely on auditors to make sure that project status reports are accurate. However, once auditors are added to the mix, negative organizational dynamics can lead to a dysfunctional cycle that results in even less openness. 4. Putting a senior executive in charge of a project may increase misreporting. Although having a senior executive as a project sponsor often proves wise politically and can help in securing resources for a project, the involvement of senior leaders does not make it any easier to track project status. 5. Executives often ignore bad news if they do receive it. A number of the authors' studies found situations where employees went to share their concerns about a project with powerful decision makers who had the ability to change the course of the project (or stop it), but were unsuccessful. The authors propose solutions to reduce the risk of being blindsided by any of these inconvenient truths.... Project management Gestion de projet Iacovou, Charalambos VerfasserIn aut Smith, H. VerfasserIn aut Keil, Mark VerfasserIn aut Safari, an O'Reilly Media Company. MitwirkendeR ctb TUM01 ZDB-30-ORH TUM_PDA_ORH https://learning.oreilly.com/library/view/-/53863MIT55317/?ar X:ORHE Aggregator lizenzpflichtig Volltext |
| spellingShingle | Thompson, Ronald Iacovou, Charalambos Smith, H. Keil, Mark The Pitfalls of Project Status Reporting Project management Gestion de projet |
| title | The Pitfalls of Project Status Reporting |
| title_auth | The Pitfalls of Project Status Reporting |
| title_exact_search | The Pitfalls of Project Status Reporting |
| title_full | The Pitfalls of Project Status Reporting Thompson, Ronald |
| title_fullStr | The Pitfalls of Project Status Reporting Thompson, Ronald |
| title_full_unstemmed | The Pitfalls of Project Status Reporting Thompson, Ronald |
| title_short | The Pitfalls of Project Status Reporting |
| title_sort | pitfalls of project status reporting |
| topic | Project management Gestion de projet |
| topic_facet | Project management Gestion de projet |
| url | https://learning.oreilly.com/library/view/-/53863MIT55317/?ar |
| work_keys_str_mv | AT thompsonronald thepitfallsofprojectstatusreporting AT iacovoucharalambos thepitfallsofprojectstatusreporting AT smithh thepitfallsofprojectstatusreporting AT keilmark thepitfallsofprojectstatusreporting AT safarianoreillymediacompany thepitfallsofprojectstatusreporting AT thompsonronald pitfallsofprojectstatusreporting AT iacovoucharalambos pitfallsofprojectstatusreporting AT smithh pitfallsofprojectstatusreporting AT keilmark pitfallsofprojectstatusreporting AT safarianoreillymediacompany pitfallsofprojectstatusreporting |