What does it mean to be responsible in practical terms?
I find myself in the evening at 9 o'clock at work, with an angry client in ICQ, who “urgently needs it,” and in an attempt to bring the code that another programmer was writing to work. It seems that today it will not work. The client is not shy in expressions, puts pressure on the feeling of guilt. Terribly embarrassing. From long sitting behind a computer eyes hurt. From the need to debug and rake someone else's govnokod - back. If your back hurts, then most likely you should be doing the work you hate right now. In my head - despair, anger. And hammering the thought:
I
I do not want
Responsible for others shoals
It was 2004. I opened the studio about a year ago, and the only thing I really wanted to do was to program. I did not want to be engaged in accounting, personnel, business activities, clients, negotiations. I just wanted to write code. Something like these guys .
')
Over time, something has changed. No, I still want to write code. But, for example, I realized that these were not foreign shoals . And what exactly I, as the director, ultimately answer for them. For hiring these people (it is them) and for agreeing to work with these clients. For the fact that this is how the tasks were distributed, and this is how the workflow was set. Yes for everything, in short.
Now it will be necessary to turn on the imagination: I will try to explain at what point the "responsibility" is included.
Here you sit, calmly go about your business (write code, for example). And a colleague from the neighboring department comes to you with a problem. You can advise something to him. Or you can send it to hell (you have to do your work). In the end, everyone has shitty days.
But at that moment, as you delve into his problem and take it upon yourself, a “chpok” is heard - and now this is your problem. Now to solve it is a matter of technique. But until the “chpok” has been heard, you will treat the problem as someone else’s, and you will hardly be sincere to solve it. By and large - without this "pip" you do not care if the problem will be solved: it will be someone else's problem . (By the way, a monkey sits on your back with the sound of “chpok” , if you know what I am talking about).
You can, of course, write a lot of clever words about delegation, etc., but this will not change two facts:
When viewed from the side, it is often seen that a person rested or digs in the wrong place. And he himself still does not understand that he rested. We need to come up and push, offer a workaround, decide something for him. But before you go - it is necessary that there is a “chpok” and you accept responsibility for solving the problem.
On good, responsibility should be delegated, along with the appropriate authority.
Well, for example, who should be responsible for:
Okay. Then the question arises: what in practical terms does it mean to “bear responsibility”?
What responsibility can there be?
I remembered offhand:
Something else can, but so far it does not occur to the head.
However, which of these “responsibilities” can be put into practice in the daily work of the studio? Not exactly criminal and administrative. Perhaps I would not use physical too often :-D. We somehow immediately neglected the religious cult.
The closest analogue is moral responsibility. This is the type when you prokosyachil, and you - reprimand. A kind of "punishment without punishment." In practice, this translates into that:
Watching my one and a half year old son, I noticed that he starts screaming and crying when:
This behavior seems to be almost natural: if there was a facac on the project - you need to find the culprit and very emotionally explain to him where he, the bitch, is wrong. This action removes the pain of the head, which he feels almost physically when something goes wrong on the project.
Despite the prevalence of the method (and the alternatives are not enough), its frequent use leads to a difficult moral situation in the team, and what the subordinates consider the manager to be a complete asshole. (And you need it?).
But there is a financial responsibility. Perfectly! But in most cases the fact is a farce. Well, it does not work properly. Few (extremely few) of the hired personnel are responsible for the implementation of the objectives of the project. In the worst case, the prize will be insufficient or fired.
Imagine for a moment that you are a project manager for the development of a U-Mobile. Like, make cool, get a lot of money. If you don't, you won't. And now the project has been launched, they have given you money. You calmly go to another company and ...
It turns out that there is a defect in the project, due to which you need to recall the entire series. Who is now financially responsible? Well, not exactly a manager - with him everything was fine.
Ok, in the construction industry in contracts, some real sanctions are prescribed, according to which you can really try financially or criminally to punish the guilty even after 30 years. It is clear that in fact it turns into a farce and search for a scapegoat.
The farce is as follows:
But this is a separate big topic about KPI, which should be considered in the same separate, large and terrible article.
Instead of output:
I do not want to settle for others
but it is my responsibility
I hired these people
How does responsibility arise?
you have a problem and - chpok!
she is yours
in a good way the manager should be responsible
but what is it like?
moral - get reprimanded
works? Yes!
material - applicable?
no, she is constantly avoided and delegated to the leadership
if anyone is able to give guarantees, it’s the business owner himself
I
I do not want
Responsible for others shoals
It was 2004. I opened the studio about a year ago, and the only thing I really wanted to do was to program. I did not want to be engaged in accounting, personnel, business activities, clients, negotiations. I just wanted to write code. Something like these guys .
')
Over time, something has changed. No, I still want to write code. But, for example, I realized that these were not foreign shoals . And what exactly I, as the director, ultimately answer for them. For hiring these people (it is them) and for agreeing to work with these clients. For the fact that this is how the tasks were distributed, and this is how the workflow was set. Yes for everything, in short.
Now it will be necessary to turn on the imagination: I will try to explain at what point the "responsibility" is included.
Here you sit, calmly go about your business (write code, for example). And a colleague from the neighboring department comes to you with a problem. You can advise something to him. Or you can send it to hell (you have to do your work). In the end, everyone has shitty days.
But at that moment, as you delve into his problem and take it upon yourself, a “chpok” is heard - and now this is your problem. Now to solve it is a matter of technique. But until the “chpok” has been heard, you will treat the problem as someone else’s, and you will hardly be sincere to solve it. By and large - without this "pip" you do not care if the problem will be solved: it will be someone else's problem . (By the way, a monkey sits on your back with the sound of “chpok” , if you know what I am talking about).
You can, of course, write a lot of clever words about delegation, etc., but this will not change two facts:
- Your employees will still carry you their problems;
- If they suddenly don’t have their problems for you, then they have big problems.
When viewed from the side, it is often seen that a person rested or digs in the wrong place. And he himself still does not understand that he rested. We need to come up and push, offer a workaround, decide something for him. But before you go - it is necessary that there is a “chpok” and you accept responsibility for solving the problem.
On good, responsibility should be delegated, along with the appropriate authority.
Well, for example, who should be responsible for:
- deadlines
- quality,
- budget,
- customer satisfaction on a particular project? Obviously, the project manager! (all obvious?)
Okay. Then the question arises: what in practical terms does it mean to “bear responsibility”?
What responsibility can there be?
I remembered offhand:
- Criminal
- Administrative.
- Physical (I mean corporal punishment for wrongdoing; slavery there ...).
- Religious (anathema there, for example).
- Moral (ooo! This is something like "religious").
- Material (fines, for example).
Something else can, but so far it does not occur to the head.
However, which of these “responsibilities” can be put into practice in the daily work of the studio? Not exactly criminal and administrative. Perhaps I would not use physical too often :-D. We somehow immediately neglected the religious cult.
The closest analogue is moral responsibility. This is the type when you prokosyachil, and you - reprimand. A kind of "punishment without punishment." In practice, this translates into that:
- You are loaded;
- Yelling at you;
- You load yourself;
- And all this at the same time.
Watching my one and a half year old son, I noticed that he starts screaming and crying when:
- something goes wrong, as he would like to;
- it hurts him physically.
This behavior seems to be almost natural: if there was a facac on the project - you need to find the culprit and very emotionally explain to him where he, the bitch, is wrong. This action removes the pain of the head, which he feels almost physically when something goes wrong on the project.
Despite the prevalence of the method (and the alternatives are not enough), its frequent use leads to a difficult moral situation in the team, and what the subordinates consider the manager to be a complete asshole. (And you need it?).
But there is a financial responsibility. Perfectly! But in most cases the fact is a farce. Well, it does not work properly. Few (extremely few) of the hired personnel are responsible for the implementation of the objectives of the project. In the worst case, the prize will be insufficient or fired.
Imagine for a moment that you are a project manager for the development of a U-Mobile. Like, make cool, get a lot of money. If you don't, you won't. And now the project has been launched, they have given you money. You calmly go to another company and ...
It turns out that there is a defect in the project, due to which you need to recall the entire series. Who is now financially responsible? Well, not exactly a manager - with him everything was fine.
Ok, in the construction industry in contracts, some real sanctions are prescribed, according to which you can really try financially or criminally to punish the guilty even after 30 years. It is clear that in fact it turns into a farce and search for a scapegoat.
The farce is as follows:
- Feeling a close fakap, top management can quickly quit, leaving behind a "legacy" that falls on the head of another poor fellow (while walking and telling how everything was fine with him).
- If you take into account not only managers, but also employees of creative professions (designers, programmers), then it is still more difficult with them. Material liability demotivates them.
But this is a separate big topic about KPI, which should be considered in the same separate, large and terrible article.
Instead of output:
I do not want to settle for others
but it is my responsibility
I hired these people
How does responsibility arise?
you have a problem and - chpok!
she is yours
in a good way the manager should be responsible
but what is it like?
moral - get reprimanded
works? Yes!
material - applicable?
no, she is constantly avoided and delegated to the leadership
if anyone is able to give guarantees, it’s the business owner himself
Source: https://habr.com/ru/post/148358/
All Articles