Related We don't have any performance management method in our company. How can I get feedback from my boss and coworkers?

Performance management is often a black art. You have people that the company needs the most, but because they take forever to do that slam bang thing like GOOD CODE and GOOD PRODUCT (or so it seems to take too much time), an irritated manager wants to let that person go. THIS IS A SIGN THAT THIS MANAGER MUST BE FIRED.

  1. Performance management is often a black art. You have people that the company needs the most, but because they take forever to do that slam bang thing like GOOD CODE and GOOD PRODUCT (or so it seems to take too much time), an irritated manager wants to let that person go. THIS IS A SIGN THAT THIS MANAGER MUST BE FIRED.
  2. The next step in setting up policies that work is to check out how many times one or more team members ask QA for qualification of a problem that he or she saw in code being tested. If QA hasn’t been seeing anything like this, MAYDAY. Someone’s afraid to say that there’s trouble in a project and is scared for their job, and so won’t point out possible trouble. You DO have a Quality Assurance team, don’t you?
  3. Communication issues can kill a project or poison a team, often to the point of no return. You HAVE to have clear channels amongst team members and those who manage them. No one should be made to feel that their input is worthless, especially when it’s a junior who has an idea that could be a make or break for the code in question —- and has shown, by his or her work, that they can be doing the right thing when it comes to code and problem solving.
  4. From what I saw in your question, someone’s not quite sure that work has or hasn’t been done right or that the team’s needing to meet or is meeting reasonable goals. If requirements definition wasn’t clear early on in the current task or someone’s changed one or more requirements in midtask for everyone, this is the time to carefully clear the air. I hope it’s not too late for that for you or the team to do just that.
  5. One thing that might help you to start the process of getting feedback from your coworkers is to show a bit of code and ask their opinion of it or ask if they need any help, especially if it looks like a milestone is coming up. If code reviews show that there’s a problem, one thing that you do NOT do is yell at people because that problem showed up or was showing a major flaw or flaws in the system or code that no one had seen before. If a manager sees trouble but does not positively act in accord with what’s needed, maybe everyone should talk about it in a way that is not going to be called insubordination. There is nothing so humiliating as a big bug not being caught by a code review or trial proof of correctness and showing up at integration test. You DO have code reviews and proof of correctness of code in your shop, don’t you?
  6. Last, but not least, use any soft skills that you have to find out how things are working out with your boss and other team members —— and remember that sometimes you could be just as at fault as they are.