Comments on: 6 Ways to Find Weak Signals http://www.ciodashboard.com/it-management/6-ways-uncover-weak-signals-it-projects/ IT Strategies for CIOs and IT leaders Tue, 31 Jan 2012 14:10:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Twelve early warning signs of IT project failure | O-I Newswire http://www.ciodashboard.com/it-management/6-ways-uncover-weak-signals-it-projects/comment-page-1/#comment-30391 Twelve early warning signs of IT project failure | O-I Newswire Fri, 20 Aug 2010 20:44:27 +0000 http://www.ciodashboard.com/?p=1332#comment-30391 [...] [...] [...] [...]

]]> By: Twelve early warning signs of IT project failure http://www.ciodashboard.com/it-management/6-ways-uncover-weak-signals-it-projects/comment-page-1/#comment-30367 Twelve early warning signs of IT project failure Fri, 20 Aug 2010 16:32:07 +0000 http://www.ciodashboard.com/?p=1332#comment-30367 [...] on precisely this topic, CIO advocateChris Curran, discusses several methods for detecting “weak signals” that indicate downstream problems: [...] [...] on precisely this topic, CIO advocateChris Curran, discusses several methods for detecting “weak signals” that indicate downstream problems: [...]

]]> By: The Best Project Management Techniques You’re Not Using — CIO Dashboard http://www.ciodashboard.com/it-management/6-ways-uncover-weak-signals-it-projects/comment-page-1/#comment-29270 The Best Project Management Techniques You’re Not Using — CIO Dashboard Fri, 13 Aug 2010 08:14:39 +0000 http://www.ciodashboard.com/?p=1332#comment-29270 [...] [...] [...] [...]

]]> By: Using Weak Signals to Detect Troubled Projects — CIO Dashboard http://www.ciodashboard.com/it-management/6-ways-uncover-weak-signals-it-projects/comment-page-1/#comment-29263 Using Weak Signals to Detect Troubled Projects — CIO Dashboard Fri, 13 Aug 2010 08:12:04 +0000 http://www.ciodashboard.com/?p=1332#comment-29263 [...] the next post, 6 Ways to Find Weak Signals, I explore some ideas for overcoming our biases by recognizing and processing weak signals that our [...] [...] the next post, 6 Ways to Find Weak Signals, I explore some ideas for overcoming our biases by recognizing and processing weak signals that our [...]

]]> By: cornercuttin http://www.ciodashboard.com/it-management/6-ways-uncover-weak-signals-it-projects/comment-page-1/#comment-4469 cornercuttin Mon, 26 Oct 2009 15:26:34 +0000 http://www.ciodashboard.com/?p=1332#comment-4469 weak signals are not often caught because no one has made it a priority to look for them. i think that, if top-level/executive management made it very clear that they will not accept a project manager who lies or misleads about project status, weak signals would be sought after continuously. in the end, even if weak signals are caught, documented and discussed, it doesn't amount to anything if no action is changed. if a project is lagging, will top-level management actually change the release data (what happens if this release date is contractually set?)? will management actually bring in more resources to solve the problems that are occupying to much time/resources within the project? i have been to status meetings and said that my project is doomed and hasn't budged in weeks/months due to the fact that 3rd party software hasn't been shipped/configured, due to the fact that i am putting out fires in other builds/software, or other reasons. i've seen others be as honest as i was. but nothing happened. management says to just keep working on what you have, knowing full well nothing will change by the next status update. recognizing weak signals is easy. actually force management to do their job, and have them manage stuff. project managers should [often] go around the team lead and talk to developers directly. department directors should skip their project managers and go to the developers directly. i would be interested to see you write an article about what to do once weak signals are captured and recognized. weak signals are not often caught because no one has made it a priority to look for them. i think that, if top-level/executive management made it very clear that they will not accept a project manager who lies or misleads about project status, weak signals would be sought after continuously.

in the end, even if weak signals are caught, documented and discussed, it doesn’t amount to anything if no action is changed. if a project is lagging, will top-level management actually change the release data (what happens if this release date is contractually set?)? will management actually bring in more resources to solve the problems that are occupying to much time/resources within the project?

i have been to status meetings and said that my project is doomed and hasn’t budged in weeks/months due to the fact that 3rd party software hasn’t been shipped/configured, due to the fact that i am putting out fires in other builds/software, or other reasons. i’ve seen others be as honest as i was. but nothing happened. management says to just keep working on what you have, knowing full well nothing will change by the next status update.

recognizing weak signals is easy. actually force management to do their job, and have them manage stuff. project managers should [often] go around the team lead and talk to developers directly. department directors should skip their project managers and go to the developers directly.

i would be interested to see you write an article about what to do once weak signals are captured and recognized.

]]>