Developers: smart ways to deal with upper management May23 '07
Here are some smart ways for developers to deal with upper management in any medium to large company:
Always have what your boss wants when he/she asks for it. If you can't produce it, explain firmly why not. Do not be afraid to say no.
Don't get involved too quickly with any project - even ones your boss approves on a whim. Projects usually change shortly after the initial instructions.
For projects from others that your boss hasn't yet approved - don't even start.
Do things the way your boss asks - the first time. Don't get too creative, and don't make the project more than it really is, even if it means sacrificing organization within your development environment.
Don't try to over-organize anything. It will always get changed.
During slower times, don't be afraid (or feel guilty) to keep busy in other ways. When your boss needs something, they will come to you. It's their job to create tasks for you, not your job. If they're truly is no higher-end work for you, then they (upper management) will perhaps notice this, and do something about it. The point is - you can't control what comes (or what doesn't come) your way. Each day, just try to be productive in some manner.
In order to ensure work does keep coming your way, always be open and helpful to other co-worker's requests. This will make them feel they can come to you any time, and perhaps they will come to you when you are looking for work to do. If you shut people out, they will learn to avoid asking you for help. The more helpful and presentable you are, the more benefit you are to the company. Companies like people that are approachable, can multi-task, and handle many different things. They don't like people that lock themselves in their office, hoping to avoid all contact with others.
Treat other co-worker's requests with a grain of salt. You report to your boss, not others. Just because they think they need it, it may not benefit the overall goals of the company's development/IT department. It's the job of your boss to delegate that. Don't attempt to think you know what the company needs.
Don't speak in technical terms with your boss, unless they are truly into your field. If they ask what means you'll use to produce something, explain it in basic, non-technical terms. After all, they won't understand half the "tech stuff" you mention, so just save it for the right environment, such as discussions with other developers.
If your boss tries to suggest using a certain technology (in which you would have a more educated opinion on), just listen to their suggestion, and revise it later, on your own. It does you no good to shoot down ideas from your boss, or always try to prove you are smarter in that area.
Categories: Development 
, Tips , Workplace
Add Feedback (view all)
Leave feedback
is published and produced by Matt Thommes - an independent publishing enthusiast, mobile blogger, content creator, informative writer, web developer from Chicago.
Never one to conform, Matt intends to promote the effect the web has on our lives, in an effort to intensify, instruct, and clarify all that is happening around us.
Similar Entries
- GrandCentral eases caller management (55 recent visits)
- Query management software? (5 recent visits)
- Domain management software (4 recent visits)
- Firefox 3 smart address bar: wildcard search (2289 recent visits)
- iTunes Smart Playlists (171 recent visits)
- Smart vs. Lynch (1 recent visits)
Stats
5 unique visits since August 2008