Comments
When IT Pros Don't Cut The Mustard
Newest First  |  Oldest First  |  Threaded View
bquillen280
50%
50%
bquillen280,
User Rank: Strategist
5/14/2014 | 3:51:28 PM
Re: Trust but Verify, in Underperforming Project Team Members
Boy, I have to watch my typing!  Dogcat,  Thank you for your excellent response and additional comments, citing some of the challenges you have had.  It is never easy to manage a complex project, especially as an "outsider", is it?  Bennett
bquillen280
50%
50%
bquillen280,
User Rank: Strategist
5/14/2014 | 3:48:29 PM
Re: Trust but Verify, in Underperforming Project Team Members
Dogcat,  Thank you for yourexellnt response and additional comments, citing some of the challenges you have had.  It i never easy to manage a complex project, especially as an "outsider", is it?  Bennett
dogcat
50%
50%
dogcat,
User Rank: Guru
5/14/2014 | 11:35:34 AM
Trust but Verify, in Underperforming Project Team Members
I certainly must concur with most of this article; I too have worked as contractor project manager where you parachute into a difficult project. I have frequently thought about why companies bring in outside PMs, especially on large critical projects. I gues they may not have in-house PM capabilities, but why not develop them as in-house people will have orgainzational and political knowledge an outside PM must take time to master. Maybe it's easy to blame an outside PM if a doomed project fails. But, I was bothered by the "Trust but Verify" guidance. The Gipper, former president Reagan, used this in the Cold War context in dealing with the Soviet Union. Recently my boss used that on me when he repeatedly did not believe me when I reported information on an 'as-is' assessment. My source was a high ranking end user SME who had actually built the rogue systems in question. I refused to go back to this executive and ask the same question he had already answered multiple times. In this relationship, the SME and I had established a professionall level of trust. My boss set up a in person meeting with the SME, who then demonstrated on the desktop PC the rogue system he had developed, because the IT shop. my boss's boss, had refused to help the executive.

Verification is a standard process step(s) in mature systems engineering and should be done in routine way in all things. That's why we have PDR, CRDs, milestones, reviews, control gates, etc. These are not being done because of some 'trust' factor, but because as humans developing complex systems, we discipline ourselves, bosses too, in subjecting our work to critical review and ongoing assessment, thest check, verify, cycle. It has nothing to do with trust, and to introduce this cold war advesarial relationship term into a team is just another example of inmature, shaddy management practice.
dogcat
50%
50%
dogcat,
User Rank: Guru
5/14/2014 | 11:35:08 AM
Trust but Verify, in Underperforming Project Team Members
I certainly must concur with most of this article; I too have worked as contractor project manager where you parachute into a difficult project. I have frequently thought about why companies bring in outside PMs, especially on large critical projects. I gues they may not have in-house PM capabilities, but why not develop them as in-house people will have orgainzational and political knowledge an outside PM must take time to master. Maybe it's easy to blame an outside PM if a doomed project fails. But, I was bothered by the "Trust but Verify" guidance. The Gipper, former president Reagan, used this in the Cold War context in dealing with the Soviet Union. Recently my boss used that on me when he repeatedly did not believe me when I reported information on an 'as-is' assessment. My source was a high ranking end user SME who had actually built the rogue systems in question. I refused to go back to this executive and ask the same question he had already answered multiple times. In this relationship, the SME and I had established a professionall level of trust. My boss set up a in person meeting with the SME, who then demonstrated on the desktop PC the rogue system he had developed, because the IT shop. my boss's boss, had refused to help the executive.

Verification is a standard process step(s) in mature systems engineering and should be done in routine way in all things. That's why we have PDR, CRDs, milestones, reviews, control gates, etc. These are not being done because of some 'trust' factor, but because as humans developing complex systems, we discipline ourselves, bosses too, in subjecting our work to critical review and ongoing assessment, thest check, verify, cycle. It has nothing to do with trust, and to introduce this cold war advesarial relationship term into a team is just another example of inmature, shaddy management practice.
bquillen280
50%
50%
bquillen280,
User Rank: Strategist
5/14/2014 | 7:14:52 AM
Re: Mustard?
Thank you for your comments, but I think you need to check your idioms. There is of course the phrase: "pass muster", as in troops that need to pass muster. But, there is also the idiom: cannot "cut the mustard". So, the title is quite correct and to use a British phrase: "spot on"!
anon6345729928
50%
50%
anon6345729928,
User Rank: Apprentice
5/13/2014 | 10:49:08 PM
Mustard?
Uhm you really want to retitle this article. The term is "Cut the muster" or really "Cut muster"

 

See: http://grammarrule.blogspot.com/2006/11/english-grammar-rule-cut-muster-or.html

 

I dont think your grammar passes muster.. :)
bquillen280
50%
50%
bquillen280,
User Rank: Strategist
5/13/2014 | 2:51:10 PM
Re: Leave Of Absence
Yes; as a matter of fact, the individual took early retirement shortly thereafter.
RobPreston
50%
50%
RobPreston,
User Rank: Author
5/13/2014 | 2:33:58 PM
Leave Of Absence
I'm curious, Bennett: Whatever happened to that CIO who was placed on a leave of absence and replaced with a subordinate? Did he end up leaving the company shortly thereafter?
 


The Business of Going Digital
The Business of Going Digital
Digital business isn't about changing code; it's about changing what legacy sales, distribution, customer service, and product groups do in the new digital age. It's about bringing big data analytics, mobile, social, marketing automation, cloud computing, and the app economy together to launch new products and services. We're seeing new titles in this digital revolution, new responsibilities, new business models, and major shifts in technology spending.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest September 24, 2014
Start improving branch office support by tapping public and private cloud resources to boost performance, increase worker productivity, and cut costs.
Flash Poll
Video
Slideshows
Twitter Feed
InformationWeek Radio
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.