-
On the other hand, there are professions where communication doesn't seem to be the main part of the job. Developers, for example, spend most of their time writing code.
-
According to research, some of them are so absorbed in working with the computer that they lose the skill of empathy.
-
However, to achieve an excellent result, a developer needs not to write more code, but to better understand the client's goals.
-
Andrey was used to receiving decomposed tasks and clear instructions from the project manager.
-
He did not try to dive into the details of the feature: why was it needed, which goals did the client want to achieve with it? Because of this
-
Andrey worked mechanically, writing code for separate tasks in the task tracker, without seeing the product roadmap as a whole or understanding how a specific feature was supposed to strengthen it.
-
But often the result did not fully meet the client's expectations, and
-
Andrey had to redo the same thing several times.
-
The manager may have decomposed the task incorrectly.
-
Or break it down so finely that the meaning was lost.
-
Or some requirements important to the client were lost during decomposition.
-
Andrey started using AI to write code. After all, Git contains millions of lines of code showing how to solve tasks in common languages. And code is just another dataset, that is, a source of knowledge for AI.
-
Andrey spends less time on typing work.
-
Now he has freed up time to dive into project details and understand the client's needs.
-
Now most of the working day
-
He meets with the client to better understand the goals and value of each new feature in the application.
-
He knows which metrics the feature should improve, how it should integrate into the current system, and how it will evolve in the future.
-
He thinks through the feature's logic more deeply and carefully. …Then he writes a detailed prompt, from which the AI generates almost production-ready code.
-
All Andrey has to do is test and refactor it.
-
As a result, the client accepts 90% of features on the first try because they fully meet the project's requirements and goals, while the rest are accepted with minor changes.
-
Thanks to this, the client's company brings the product to market faster and saves resources. The IT team also gets higher client satisfaction ratings and has become more profitable, because it hardly has to work under warranty, meaning it does not waste time rewriting or reworking things.
-
But at KT.Team, we have already started implementing this approach. And experience has shown that it works.