Tag: misunderstandings

  • Well-being in tech – Who really cares?

    Well-being in tech – Who really cares?

    As a freelance consultant for more than 15 years I skip from company to company of different sizes in different industries. For the last two years I have been very close to the IT-tech industry. I love to work with the “Nerds” and “Geeks” and I like the atmosphere on the devopsdays I have attended. But I am really confused about one important problem, which never ever occurred to me in this big mass before than it does in the tech industry: problems with health, psychosomatic disorders and mental illnesses.

    Whenever I talk with some of the tech folk, sooner or later hints of these problems appear and with asking the right questions, lots of people start talking about their problems in the past. They talk about back problems, a lot of headaches and neck tensions. At first glance this seem to be very clear because of bad body posture combined with a lack of physical activity and perhaps bad nutrition. But the roots for these problems can also be psychosomatically. These are by the way just the “light problems”.

    So many people told me about their burnouts, depression and other mental illnesses; they have also told me about being “out of job” for a year or more! And they have talked about the need for liters of coffee to get through the day, caffeine pills, energy-drinks and cigarettes! At devopsdays Amsterdam @botchagalupe talked about some talented and enthusiastic young techs and their Karo jisatsu – their suicide from overwork!

    My job in companies is to coach employees and leaders on topics like communication, team culture and leadership. And with these topics the question of well-being is always involved. So when I started with my first clients in the IT industry I did a lot of research and I found some studies about health problems in Germany. These studies said that tech people do not often stay at home because of common colds or something like that. But it told that there are above average problems in matters of nervousness, insomnia, stomach problems, mood swings, depressions and burnout. And there is an extremely outstanding usage of anti-depressants and other psychotropic drugs.

    There are other studies about pharmacological neuroenhancement and brain doping – the consumption of drugs to increase the “brain power” without medical necessity – which are frightening to me.

    What really puzzles me about this is, that all the people talk about colleagues with some kind of these problems or about their own experiences; that they know about it – and then they go on and “do business as usual” – nothing happens!

    Like a neon sign there is one big question in my head: Who really cares about well-being in tech?

    But why are there that many health problems in the IT-industry? On the one hand it is because of the nature of IT: faster and better is the credo of IT-projects. Continuous or daily delivery put a lot of pressure on the employees. Management systems like Scrum or Kanban and methodologies like Devops try to meet the requirements of the market. But are the single individuals really fit for it? What is done to enable the employees to meet these systems or methodologies on eye-level so that they feel well with it?

    Special management systems and methodologies need special skills – technical skills as well as soft skills. The companies´ focus is a lot on technical skill education, but mostly they don´t care about strengthening the soft skills! Employees are left alone with issues of bad communication, misunderstandings in the team, leadership full of pressure and – caused by this all: bad emotions and feelings!

    Now let´s have a look at the people working in the IT industry! One big skill, you really need to work successfully in IT is the ability to concentrate and focus on one special issue, to submerge into one task and fade out the rest around you. I experience this at home once a while, because my companion in life is a software architect and CEO. Being in a demanding project his head is working 24/7 and it seems as if nothing else could reach him. The ability to fade out everything which is not important for the project is on the one hand a gift but on the other hand it could be a really dangerous demon if even the physical and mental needs of oneself are faded out! This will perhaps be okay for a period of three months or so. But reality could be that project is followed by project and the period is no period any longer; it is the norm! People start with too much coffee every single day, caffeine pills or energy drinks or even worse with brain doping! Being tired or headaches often are signals, the body is sending us in case to stop us. But with ignoring the signals and working against them with some kind of drugs, situations will get worse! A downward spiral is started.

    What kind of life is it, if we do not care for our own well-being?

    The next point is, that the IT and tech-industry is still mostly a men´s world – sorry ladies, hope that will change some day! And even in modern times, in a men´s world you do not talk about emotions, excessive demands and mental illnesses, because lot of people believe that these are signs of weakness! So the risk is very real that people try to hide their problems until it is too late.

    So, who has to care for the well-being? WE ALL DO!

    At first everyone has to take care of their own individual well-being and pay attention to what our bodies are telling us! If we don´t care for ourselves, how will we be able to take care for others?

    Then there are colleagues, who should have a closer look at each other and talk about emotions and problems. Communication is a very important key for the well-being and the recognition of health and mental problems.

    Last but not least there are the leaders who play, to my opinion, a vital role in this issue. They are responsible for the success as well as for the employees. But what will happen to the success if the employees are insane or out of job for a long time?

    A paradigm shift is the only way! You all know about the problem! So please start to take care of yourself and of others! This will boost yourself personally and the team´s and company´s success!

  • Communication: Who is to blame for misunderstandings?

    Communication: Who is to blame for misunderstandings?

    Communication is everywhere and it is far more than only the spoken word and its origin meaning. Communication is one of the most complex and also complicated topics in human relationships: most of the time very thrilling, sometimes frightening but always important!

    As we all grew up with communication, you might think, we should be used to communicating very well. But daily life shows us that misunderstanding is the companion of communication. We all know from our own experience how hard it is to clear up such misunderstandings and how much precious time is wasted on them!

    The more people with different personalities are trying to communicate with each other, the higher the probability of misunderstandings.

    To take a closer look at all those cross-functional teams like devops or agile scrum teams you will recognize at once that there are lots of individual issues because of misunderstandings in every team. Each single issue on its own is disrupting daily work, something we all know from personal experience. Now try to imagine how much of a team´s efficiency is taken away by the sum of all issues caused by bad communication and misunderstandings! It is unimaginable!

    Communication is the link between all stakeholders: it determines the atmosphere in a team, the relationship between all parts, the understanding as well as the knowledge and information transfer. It influences the project times, the employees´ identification with the company or their work, individual responsibility and how to deal with mistakes. This list could go on and on.

    Time in IT projects is one of the limiting factors. To save time and avoid mistakes, new tools are be developed again and again. Companies invest money in these tools; sometimes tools are integrated in the teams, sometimes the teams are arranged around the tools or systems. But the very human part – the communication – which is important for every team, no matter which tools or which systems are used, is seldom the focus of IT education! You can changes methodologies, systems and tools, but if you do not get beyond bad communication, you won´t reach the full potentials of all those efforts. No matter if you have already chosen your tools or systems or if you are still searching for the right way for your team, you should always think about the communication within your team. Instead of always asking what the ROI of communication courses will be, you should better ask what the ROI of all those tools and systems could be with optimized communication!

    Before optimizing the communication you first have to find the bugs in the individual and in the team communication and eliminate them. Due to the inherent complexity, the support of an expert is sometimes useful. Just as not all people using computers are IT experts, not all people are experts in communication – even though they are communicating the whole time, sometimes even by saying nothing. Some are more gifted than others, some are able to learn by studying on their own and others need a little more time and support. Changing communication mostly means to change personal habits and this is always an extremely challenging requirement. Particularly for “brain-workers” like developers or other people from IT, it is very helpful to have some background information in combination with practical applications given by experts. First little steps of debugging the communication will soon be honored by success.

    “First do it right, than do it fast!”, is a developers wisdom. Concerning the communication this wisdom could be changed into: “First debug your communication, then optimize it!”

    Coming back to the question in the headline, it is not important to blame anybody for a bad communication. Everybody is responsible for it and instead of searching for the guilty one, you should start working on it. Be brave, start debugging you communication!