5 ms·
I think the depends a lot on big company vs small company. At a small company, here are a few bullet points I find helpful/effective: 1. Lead by example: othe
by matt_the_bass 9y ago
I think the depends a lot on big company vs small company.
At a small company, here are a few bullet points I find helpful/effective:
1. Lead by example: others will follow you if they believe in you. Manager has be willing to do and seen to do any and all tasks that they delegate. This does not mean that the manager has to be the best one at it or do it the most. But they should do some of those tasks that no one really wants to do.
2. Be sure to acknowledge success of others. Do this both directly and indirectly. One great way is to tell person B how good a job person A did when in a place/situation that person A can hear. This could be in passing or explicitly complimenting them in a group. Don’t do this for every single task but do do it for both large and small tasks. People want to know that their work has been acknowledged and valued.
3. Ask questions of your team. Don’t be afraid to get opinions. Don’t be afraid to not know the answer. Do be clear if you change you mind/approach if you learn new facts. If someone helps you find the answer/path acknowledge (see #2)
4. Think before you speak.
5. Share the Why not just the What.
6. Be excited about your goals. Explain where to want to go and why. You are your teams link to upper management and customers. A good team member may be able to find the path better than you if they understand the destination.
7. Don’t overwork your team. This will enable you to call on them for they extra job/extra hours the few times it is really needed. (See #1)
These are by no means the only items. But certainly some items I’ve found useful.
Note, they do not apply only to programming. They do not apply only to engineering. I think they apply to all disciplines.