Lessons Learned

If it ain't about boats, it should go here.

Moderator: Soñadora

Lessons Learned

Postby Ajax » Fri May 18, 2018 8:37 am

Are there really any lessons learned, if anything less than 100% honesty is demanded?

I was provided with a blank spreadsheet and directed to fill it out with problems that were encountered, what the impact was, why they happened, and what some possible corrective actions might be.
That's very laudable, but at the bottom there was a caveat that screamed "DO NOT ASSIGN BLAME. WE ARE ALL ONE TEAM, STRIVING FOR IMPROVEMENT."

This has been "one of" the worst production experience I've had in 14 years on this project. There was one govt' employee, who held way too much authority with way too little knowledge, who singlehandedly caused between 60 and 90 days of NEEDLESS delay and waste of taxpayer money on this project. However, I'm not allowed to call attention to this, even in a constructive, respectful, politically correct manner.
As a result, I filled in the spreadsheet with some trivial, technical details that I encountered that really didn't impact things very much and sent it in to my corporate project overlords for integration with all the other comments.

In the body of my email, I stated my position on the experience in the same language used above, as well as saying that the form fails to honestly address our processes and the deteriorating relationship with our customer. The form is nothing more than a "feel good" exercise that doesn't address any root problems. I've reminded my superiors that I've served loyally and quietly here for 14 years and the fact that I would dare to speak out in this manner for the first time should be taken into account when considering the worth and gravity of my comments.

When I say "one of" my worst experiences, that is because I'm still currently working on my "actual worst" project right now.
Festina Lente
User avatar
Ajax
 
Posts: 7109
Joined: Wed Dec 12, 2012 10:23 am
Location: Edgewater, MD

Re: Lessons Learned

Postby VALIS » Fri May 18, 2018 10:27 am

Ajax, I don't know what you do, or what the situation is in your industry, but when I've been an employee with little control over management and business policy, when things got that screwed up I would usually quit and find a better situation. Of course that was easy when I was young and there were good opportunities.

Do you think the problems were limited to that particular project (it sounds like this isn't the case), or are they now intrinsic to the business model? When problems get "baked in" to the business, either due to management or the business environment, they seldom get better without a massive, and usually painful upheaval. Perhaps in your industry the competition is also saddled with the same problems, so the threat is not so much to your job, just your sanity.

And other times I would just put my head down, try to find some little aspect of the project I could be interested in, do my job, collect my paycheck, and then take my hard-earned vacation. And then quit.

Even when I've been in management, correcting a serious structural problem usually involves significant pain before it gets better (if it does -- sometime is's just pain.) This is why I like startups.
Paul Elliott
VALIS - Pacific Seacraft 44
Friday Harbor, WA
http://www.sailvalis.com -- http://www.navmonpc.com
User avatar
VALIS
 
Posts: 459
Joined: Tue Dec 11, 2012 1:18 pm

Re: Lessons Learned

Postby Ajax » Fri May 18, 2018 11:51 am

Hm...let me find my words.

This was a "task" on a $200m gov't project. 5 year contract with annual options to renew/not renew. This agency was never a Project Management Office until recently (4 years ago). We knew that there would be growing pains as they found their way, but they are failing to learn and they are deeply entrenching bad, bureaucratic habits. Our previous management office would tell us what they want, we would jointly develop the specifications, then the gov't would get the hell out of the way while we developed, tested, implemented and validated the new system or product. The new office intensely micromanages every facet.

My company, this team, has kept this contract for going on 25 years without a single, notable screw up. The new management office treats the whole company as if we were inept and dishonest.

So yeah, this isn't going to improve without a major upheaval.

I've actually had several interviews over the last few months. I've had several companies attempt to recruit me. I've turned them all down because the description of the work and the work environment is exactly the same as where I am now, except offering lesser benefits, less vacation and surrendering my seniority with the company. Same abuse, just different faces in different places.

The grass isn't any greener on the other side of any fences that I've checked. I loathe the gov't but I like my co-workers, I'm satisfied with the company, my pay, my benefits and (mostly) my work hours. I guess it's just a matter of outlasting the assholes at the project management office.
Festina Lente
User avatar
Ajax
 
Posts: 7109
Joined: Wed Dec 12, 2012 10:23 am
Location: Edgewater, MD

Re: Lessons Learned

Postby SemiSalt » Fri May 18, 2018 12:48 pm

How to fill the spreadsheet? Narrow focus, passive voice, and no proper names.

"The data acquisition module was late, causing cascading delays."
"Late changes required significant re-coding and concomitant delays"
And malt does more than Milton can
To justify God's ways to man. - A.E. Houseman - A Shropshire lad
User avatar
SemiSalt
 
Posts: 2346
Joined: Mon Mar 04, 2013 3:58 pm

Re: Lessons Learned

Postby Olaf Hart » Fri May 18, 2018 5:06 pm

When I had to give evidence at a Parliamentary inquiry, my lawyer advised me “ Never make a positive statement”

Translated from legalese that means don’t accuse anyone of doing something wrong.

I have found this is good advice in general.
Olaf Hart
 
Posts: 3820
Joined: Wed Dec 26, 2012 5:34 am
Location: D'Entrecasteau Channel


Return to Off Topic