3 ms·
Its very different, few skill sets carry over from engineering, at first it seemed like I wasn't doing anything useful at all. The challenge is not going back
by ChuckMcM 9y ago
Its very different, few skill sets carry over from engineering, at first it seemed like I wasn't doing anything useful at all.
The challenge is not going back and doing technical work that someone on the team can do because it feels good to 'get something done', and it isn't possible to just edit some code in an engineer reporting to you and recompile them so that they work 20% faster than they did before.
There are a lot of bad managers. You'll hear all sorts of horror stories. But there isn't a book that explains good management, there are 100's of books and they are all different because how management makes sense to a person is unique to that person. When I first started managing I would read books that people recommended. Sometimes there was something useful, sometimes it was opaque. Some assumed you had no understanding of others emotions, others assumed that what others were feeling was as clear to you as if they had an emotional status monitor hanging over their head.
Three things emerged from the mess;
1) There are always two people in a manager/employee relationship and that pair is unique, and the tools need to be appropriate for that pair.
2) People who work for you, are notoriously bad at telling you that you suck. Try to cultivate relationships outside of your group that can give you a different perspective of how things are going.
3) At the end of the day respect, responsibility, and a clear understanding of what is expected is the most effective way to keep people happy and productive.
So to summarize, yes the new role was challenging and what was more, frustrating, in part because the tools I had learned for developing new engineering skills were not applicable. It isn't a job for everyone, this is for sure.