
#Uiuc engineering timetracker professional
Not only does it belong there, it is even a critical part of it, assuming of course that you have good arguments to make for your point and convey it in a respectful and professional manner. I disagree with the notion that passion or personal preference doesn't belong in a decision-making process. I am a co-founder (and CTO) of a small company myself and hence get to talk to the folks in my company quite regularly. Given the support for this answer I will likely get downvoted for this, but I disagree with this advice. It'll also remind you of (and force you to fully consider) the frequently hidden option that's often forgotten when presenting a new idea or direction, which is the status quo. It will make you appear more level-headed and capable of making decisions that are good for the business.

#Uiuc engineering timetracker how to
It'll get you thinking in terms of pros and cons and how to persuade other people by appealing to their point of view. Avoid picking favorite solutions and presenting them as the clear winner or only option. Try to replace the above phrases with "one option is to." and change your thinking to complete the thought in a way that makes sense. In the flow of a conversation, it may feel like you're merely emphasizing a point and bringing your (presumably solid) technical experience to the table, but to the listener it often makes your suggestions appear self-serving, poorly considered, and possibly irrational from the perspective of the business. How often do you say things like "we have to", "we need to", "we really should", "can we", or "I'd like to"? The problem with all of these statements, from the perspective of someone like your manager, is that they hint at a passion or personal preference that doesn't belong in a decision-making process or conversation.

Imagine yourself having a conversation with your manager or someone in a relatively similar position about a decision or suggestion you have. A piece of simple, concrete, implementable advice I read recently that I really like is "communicate in the language of options, not demands, imperatives, requests, or preferences."
