Hacker News new | ask | show | jobs
by jiggawatts 907 days ago
> said that it couldn't be meaningfully bettered

There’s the problem!

I’ve had this experience many times — people will internalise their limitations and assume that their best is the best possible. Etc..

When a junior employee just casually proves them wrong, calling the emperor naked, that makes them feel inadequate and even ashamed.

I’ve been involved in many similar scenarios. Often there is a history of meetings, consultants, vendor techs, etc… trying to fix the problem and then a grudging acceptance and business workarounds. To suddenly reveal all of that as a lie is to undo established history. It’s like trying to close down the Vatican and tell all the priests to go home because you found a “neat proof” that there is no God. To say that you’ll experience some disbelief and resistance to your ideas is an understatement!

I had one of these moments where I got a nightly report batch job down from 3 hours to about 5 seconds. The customer turned red in the face, screamed at me, accused me of lying and stormed out of the meeting room.

Turns out that guy had to stay back each night to make sure the job ran successfully and so that he could sign the print out officially. He’d accepted the impact on his personal life, after many arguments about his work hours with his wife, etc…

To have all that sacrifice and suffering instantly made superfluous!? Ouch.

1 comments

    I’ve had this experience many times — people will
    internalise their limitations and assume that their 
    best is the best possible. Etc..
Man, yeah. I've never found a way to really do this well.

The closest I've come to a winning formula here is to

1. Build a relationship where you have given praise and positive feedback to the individual's other efforts, privately and publicly. To be 100% clear here I'm talking legitimate praise here, not butt-kissing.

2. Find a way for the "victim" to share in your achievement somehow. Help him save face. "Bob and I were looking at ways to optimize the batch job etc etc, and we found a way... etc etc." People who know you and "Bob" will understand who really did the work.

That said, I would say my success at this sort of thing has been pretty low (although I am on a positive winning streak of one positive outcome in a row...)

    He’d accepted the impact on his personal life, after 
    many arguments about his work hours with his wife, etc…
Oh jeez. The... the pathos here is overwhelming.
Generally I've found that there is no easy way to call someone's baby ugly. Sometimes it is best to just say it outright, other times you have to skirt around the issue, or just let them come to the conclusion themselves when you demonstrate a fix to an "unrelated" issue that just so happens to be relevant to their problem.

> Oh jeez. The... the pathos here is overwhelming.

A landmine I've stepped on multiple times is that this type of scenario is sometimes not tragic, but actually a form of soft corruption: after hours work gets overtime pay! "Fixing" these issues can cut into people's salaries very significantly, perhaps reducing their pay to less than half. They're obviously going to fight you every step of the way, without ever saying the real reason for why they're really opposed to your helpful suggestions.

Oh geez, that unhappy guy was getting OT pay? yeah that explains a lot!!

Great points all around