Return to Article

 

Things That Affect Your Company's Technical I.Q.

Note that the items affecting your company's technical I.Q.
involve the "people side" of technology application.





 LOWER




RAISE 

Reporting problems inaccurately, without solutions Accurately reporting problems with proposed solutions
Looking for someone to blame for problems, making people afraid to report problems or critical situations Encouraging people to confront problems, requesting solutions for problems and critical situations
Blindly riding your own "hobby horse", to the exclusion of other actions expected or requested of you Knowing your company, department and group or team objectives and how they relate to your own job
Pretending more knowledge than you really have Knowing both your technical strengths and weaknesses
Blindly insisting on maintaining the status quo Working out ways to improve things that need improving
Technical one-upsmanship or "I'm better than you" rivalry Working as part of a team with a objectives
Criticizing requests for help or assistance Helping someone to find the information they need
Finding fault with a competitor's ideas or products Learning from a competitor's ideas or products
Blaming employees for not knowing something Implementing on the job training and apprenticeships
Avoiding or neglecting seminars and conferences Supporting the many forms of continuing education
Not fairly distributing the assignment of duties, "hot" projects and educational opportunities among staff Actively caring about the job development of each person in your company, department or group
Ignoring the need for adequate reference materials Maintaining an updated technical library 
Capriciously setting fixed deadlines in an arbitrary or dictatorial manner Setting deadlines after in-depth consultation with the persons responsible for meeting them
Criticizing personal, group or departmental initiative Rewarding self-management and initiative
Rejecting all suggestions, criticizing all proposed change Encouraging suggestions and proposals for changes
Keeping company, department or group staff in the dark Publishing company, department and group objectives
Letting your level of technical expertise stagnate Advancing your own technical knowledge and skills
Giving up at the first failure or barrier Carrying on to accomplish what you set out to accomplish
Return to Article