Friday, May 27, 2022

Scammish: Employee Engagement Survey Anonymity / Confidentiality and Why I Rather Not

Every year or some companies are twice a year, I have to fill an employee engagement survey. Every time I fill it in I cringe in the information that I have to share. I have been on teams of 5-10.

I Can Tell With Some Uncertainty From the Results

Most bosses will share the results. From the different graphs, I can usually tell which data point is which person. It does require that I am a bit familiar with each person. The easy data points are the people who have issues/problems. But not any issues/problems, these are typically the people who really, really, really want to help the group. Because most people will just lie on the survey.

I Tried But...

I have randomly been extra truthful on the survey. I even filled out the open ended response on extra this to say.

I also have routine meetings with all my bosses. If they did not, I set up the meeting. So they should already know my positions on certain topics. 

Even Ideally... Surveys Are Totally Useless

5+ companies, multiple more bosses (due to reorgs), they all have the same results... nothing. I was part of one group that actually did try harder. Still all "improvements" barely last the one call discussing the results.

Sure the boss may appear excited for the change, animated, hoo rah rah, booya, etc, I have only seen one get past the meeting . That one time lasted maybe half a year (but COVID happened... so........)

Survey Answer Is Always Perfect or Near Perfect With One Exception

If you are not confident in your workplace and you just want to stay in the the status quo, the the answer is ALWAYS, ALWAYS the happy answer. If the question is negative, then the answer is the negative of that negative.

For example, do you hate your work? Answer is fully disagree.
For example, do you love your work? Answer is full agree.

ALWAYS

Why? Because everyone else is. And if you disagree, the boss will know. And most bosses will cut you because it is easier to deal with than dealing with the real problem.

What if you have a good relationship with your boss? Then the answer would naturally be the same anyways.

What if the question is on the corporate level? Still the happy answer.

Exception?

You really hate your job and you really want to tell the company about it. But why would you want to help at the end? The answer is still the same.

Unless you really, really want to screw over your boss and you plan on never leaving. Because that sore spot will forever stay on his employee engagement score. But likely, he'll identify you anyways and get you fired. Then his score will go up the next year and it'll look like he did something............

Sooooo...... for me, if I were to analyze the results... I would expect everyone to either say they are happy or lie that they are happy. Anything less is more of a sign to what I consider my real answer...

REAL ANSWER for company if possible

Hire or promote good managers if you want to improve. Train managers? I have not seen a single manager ever change the way they manage their team. It seems to be a natural soft skill that people either have or don't have. Jerk managers will continue to be jerk managers. They may pretend for a short period of time. I am even tempted to say that even if you incentive the preferred behavior (if that is even possible), I think they still wouldn't change (or change back). Even for mediocre managers, lazy managers, hands-on managers, etc.

Maybe, maybe.... change the incentives on how teams should work. The biggest problem I see even for good managers is that the "real" demand is to deliver quickly with good enough QA that defects can go undetected. "Real" because the demand that managers deal with is usually different than what their managers say the demands are.

For example, lvl2 manager will say the demand is to upgrade the system to the next system but in reality is stressing lvl1 manager to manage current fires which is not related to upgrade. Lvl3 manager is telling lvl2 to modernize but escalating fires to lvl2. This is my dubiousness on modifying the incentives.

Tuesday, May 17, 2022

RANT: Why Scrum / Agile Does NOT Work for non-IT companies

My brain is just hurting right now. I can no longer take just how dumb people are in general. It just boggles my mind how little people just use their brains. And this is why I believe agile just cannot work in non-IT companies.

How to Make Agile Work

Just say you are doing agile. Use agile terminology. Use words like scrum, daily stand-up, retrospective / post mortem, acceptance criteria, etc. Say it with confidence, no one really knows what they mean. And those who do, just speak louder and interrupt them.

Breakdown three month waterfall processes into two week waterfall processes (but call them sprints). You cannot do a TRUE sprint because the other teams are not dedicating to the who agile process. If you need to show delivery, say that QA is taking too long. Deliver quickly with terrible quality. Make sure to blame others for the problems. Worst-case say there was too much scope creep.

Do daily stand-up call, a daily call that is supposed to be 15 minutes as 30 minutes. Don't worry what that means, just say it is a short status call. It is never short nor a status call. It will always go over 30 minutes because there is always someone who does not know how to summarize their status.

Want to be a scrum master? Just say you are one. No need for certification nor all the testing and training. Everyone I worked with who had one are absolutely clueless. Sure some try, but no one really understands. Why because none of them are engineers of any sort. They are just PMs that couldn't make it to be a PM. Or worse, they are engineers or analysts that couldn't make it.

If you want to do something your way, you HAVE to "act" dumber (or be yourself whichever is dumber) than the other person. There is no logic or reason that can persuade the other person especially if the person is actually smart. What persuades a logical person from even trying is to make them think that you are too dumb to be reasoned with. They may say something like "that will save you on step" and you should respond "I want to add a useless comment" but don't say useless... because you have to show the managers that you are doing something even if that something is nothing but you cannot say nothing... so nothing is something. Or, just agree but continue working as if you never had that conversation.

Even if you have the power to persuade people and get them to understand the process, DO NOT DO IT. You are just going to inflate the director's ego. He was just guessing stuff but now that he saw that it works, he will assume that it was all him and will take all credit. And because you were probably the biggest trouble-maker by making people complain that you are forcing them to do stuff, you'll likely get laid-off for being the most unproductive person.

Thursday, May 5, 2022

Work Life: Programmer vs Developer vs Engineer (Software / Non-Tech World) IMO

Outside of the tech companies, they are essentially the same thing. For companies that have a tech side but is wholly managed by the business side, majority of the managers and much less HR have absolutely no idea what the differences are.

The company will use whatever title to make the person happy. If the company does well and expand, then they will use whatever title that person had last. Even if the company merges with another both companies had no idea and basically use dice to decide which titles to use. 

In all my experience of a very small percentage of companies either directly or indirectly, this has always been the case. Even the titles of levels or jr/sr are quite arbitrary. Some companies have rules but most are based on years. Although they claim experience but there are too many contraries to the rule. To me, they appear to just use it to leverage the employees.