Seven features that are common to people who are overvalued


ByTojosan

There are people who work in a group say that evaluation is high but people can not do much work. This person is overestimated from the surroundings, but how is the evaluation that this imaginary "can do the work" is built? The author of a software engineer who has done many projects with many colleagues has summarized on his blog as seven ways to get overvalued.

The 7 Habits of Highly Overrated People | DaedTech
http://www.daedtech.com/the-7-habits-of-highly-overrated-people

◆ 1: Take excessive communication

ByAnne beaumont

If you want to be thought of as doing a productive job without doing useful work, you can do a lot of phone calls, send e-mails and make notes. Many people mistake these work as productive work. If people sending only one or two e-mails a day send mails that explain the details of what is happening in the project they are working on, the surrounding people vaguely "I will always think that I'm a busy guy." And if we talk about work colleagues around, the evaluation from around will change to nature.

Communication taking may be productive behavior, but there are no mention of projects in excessive progress report etc. of those who receive overvaluation.

◆ 2: Blowing a boss-breeze and becoming critical

ByRiccardo Francesconi

By taking excessive communication, you can establish a fictitious evaluation that is different from yourself ability, but from that point you can give instructions to the people around you and become a critic, you can accumulate it more . For example, "We are a bit late than the schedule so if you help Jim with the task of creating a report with Barbara, you will be saved" but if you give directions to the wind. This is because it is much easier to make that flow on your own than to take instructions from others. Also, since most people avoid conflicts and tend to be worried about other people's circumstances, even if they are in an unauthorized position to actually issue instructions, it seems that instructions are rarely passed.

It is a good way to raise fictitious evaluation by criticizing the surroundings with these taste remarks. "How hard is the gym, Barbara, what's going on with the report? Do I have to do it myself?" To say to members, "I feel uncomfortable that the project is not progressing well It will show "I feel ashamed" that I am not promoting work to other members, so my job will start going smoothly.

◆ 3: Advertise yourself carelessly

ByMTSOfan

When sending a lot of situation report e-mails, it is also important to always walk around and tell people how much work they are doing. "I would like to spend time with my family at home rather than doing such a mail until 10 pm ... well ... such a thing is impossible," but if you make a remark, it seems like you are always working for a long time Become. "Before 10 o'clock PM" is just a decoration, so it does not mean that you have to work until that time every day to be recognized around.

If you are subject to criticism, just list all the status report emails of the project you sent last month and show it to the critics OK. Speaking of the time you sent five or six mails, the critic will surrender and will convince you that your performance is perfect.

◆ 4: Make the discussion obscure

ByMichael Coghlan

People who are unable to find good points in their own work performance can always derail the discussion at any time. If you are a software engineer, when you are criticized for work, you should combine your philosophical part of "programming" and "art of software engineering" your own troubles.

This technique is effective not only for distracting criticism but also can stop that decision, such as when the project is trying to change direction which she does not like.

◆ 5: Make good use of time

ByAndrés Nieto Porras

If you have to write some code, you can withdraw from there by postponing or abandoning the project. Furthermore, it is more perfect if you blame your role against someone else. A great way to do that is to make a big communication gap.

Suppose you are working with a building and that the building will come home at 6 pm everyday. At 6:01 pm, I will send an e-mail to the building saying "I'd like to start a job but that code is necessary for Bill", OK is OK, and every day the building starts working 9 AM In the hour, 15 hours elapse until reply comes. Even if a mail reply came luckily, if I reply by opening and opening for a period of one or two hours, even if you did not wait for a few hours to reply to e-mails, it seems like they are working from around It seems that it is due to a building with important information and it seems to be waiting for hours. Even if I fail in my work, it seems that my work did not progress well due to the building.

◆ 6: to make an excuse before time

ByButupa

I heard that he was conducting a project several years ago, he seems to come across an excuse prepared beforehand.

One morning, I heard that the members of the project I was working on at the time sent a message in order to show the progress of work. However, someone said that they responded "Please look at their mails sent last night." When I checked the mail, there was "There is a clock in trouble, so I can not proceed with work, please give me advice." After interacting a little, he said that the clock he said was understood to be the clock on the task bar of the PC. Then, when asking why the work can not proceed if the personal computer's clock is broken, "Since uploading over a long period is part of the task, if the clock is broken down, some time is affected by time stamps There may be, but I do not know how to fix the clock because I am not familiar with the OS I'm using. "

This is an excuse to be irritated, but he said that he could not afford to blame another. The point of this parable is that the author has already done an excuse (an email to the effect that the clock is broken) earlier than asking the progress of work by email. The reason why I was able to send this e-mail is because it was because I was thinking about an excuse first.

◆ 7: Achievement is recognized in a way that can not be refuted

ByGrand Canyon National Park

If you do the work of surely checking the code written in the project every time, it will be called to the lunch conference. Once you get called to this lunch, no one will doubt your trust in you. But to do this you must be exquisite and ingenious. That is because people who wrote the code can immediately notice the improvement of adding 3 margins.

Also, advice voluntarily to people, to preach leadership and psychology is also a good way to raise a fictitious evaluation. Whether you are a leader or not, when you finish the project and do a discussion meeting, I remember those advices and stories unwillingly.

I think how to accumulate only overvaluation using the techniques so far, but in the case of a person who always feels underestimated that it is underestimated from the usual way, even if a little overlooked to show myself a little People who are being evaluated "There seems to be points to emulate to appeal.

in Note, Posted by logu_ii