There is an old TV show called 'The Wire', and in it a con artist fleeces a mark.

The mark's friend tries to wake him up, whereupon the mark insists that the con artist has helped him.  The mark's friend tells him to 'wake up, he rain-made you!'

"What?"

"A guy says if you pay him, he can make it rain.  You pay him.  If and when it rains, he takes the credit.  If and when it doesn't, he finds reasons for you to pay him more."

This is a neat tv show moment, to be sure, but it is also a pattern that you will find everywhere in the corporate world.

A given product has a few devs, who do the work, a few bosses, who fire devs that suck, and a squad of rainmakers who mess around on their phones.  They are called Security Consultants, Architects, Scrum Masters... but what they all have in common is the same thing that an old saying recites about political doctrines.

They can never fail, only be failed.  Paying security guys doesn't stop you from getting hacked.  Paying <insert political trend> trainers doesn't stop you from getting sued.  There is, in fact, no world state that can ever indicate that paying one of these folks was a mistake.  Either their flag is checked, in which case all is well, or it is not, in which case they need more resources.

Lesswrongers will be familiar with the old concept of 'make your beliefs pay rent'.  It is terrifying how rare basic comprehension of this notion is in the organizations we depend upon.  People will accept unfalsifiable axioms as doctrine without the slightest qualm, and then you are gritting your teeth through another round of <insert buzzword> exercises.

They trade upon the credit earned by the few legitimate practitioners of their occupations, who genuinely do consult on security or master scrums.  It can be hard to tell the two apart, to grok whether your rainmaker is toting a cloud seeder or thoughts and prayers.

The only thing I've ever seen work was essentially formalizing the above.  Have everyone give 'failure statements' of the form "I will have failed if at time X Y measurable statement is true"  and look at the nature of the statements.  Productive people's will be about their contribution, rainmakers will talk about the weather.

New Comment
5 comments, sorted by Click to highlight new comments since: Today at 12:22 AM

I call these people "credit takers" and at some point I had a realization that I was one of them. Basically I was teaching some people programming, then some became successful and I felt good about it, but then remembered that their talent was noticeable from the start and my teaching might not have made much difference, I was just credit-taking.

It also happens to me when I got to solve a problem that many have and realize in retrospetct that it was a combination of luck, knowing the right people and skills that you don't know how to transfer, possibly because they are genetic traits. It must be frustrating to hear, after a question like "how have you conquered your social anxiety?", the condensed answer "mostly luck"

What did you do after having this realization?

Stopped teaching. Now if someone says "my kid needs something to do, can you teach him programming" my answer is "no". Those who want to program can come to me themselves and ask specific things.

On the other hand, it makes you think when you realized how much these kinds of social status booster have permeated every step of the hierarchical ladder of any large organization... and yet, somehow, things still  work out