Are geeks innately cranky? Many have pontificated on the cultural difference between technical and non-technical folks but where does it come from? Could it come from the overly specific word choices, which pass for sarcasm in the scientific community? Could it come from social conventions such as the ritualized kvetch of like-minded professionals?
Here are some suggestions for non-technical folks and management to help them cultivate happy and productive environments for engineers and to get them off to a solid start.
1. Foster innovation and intellectual curiosity
Never consider a desire to experiment as a distraction from “real work”. Always value the contribution of the individual and their uniqueness. I’ve worked with developers who play multiple musical instruments, cook gourmet meals, and hold black belts in martial arts. All engineers have unique perspectives and opinions, so consider their input. They’ll feel appreciated. For example, if an engineer discovers a new technique or a refinement to an algorithm, encourage them to present at a conference or get it published. Set aside time for engineers to explore and do their own research.
2. Ensure autonomy
If your hiring process seeks out individuals with passion and creativity, don’t box them in once they get to work. No one wants to feel like a hired hand carrying out orders. Engineers can execute plans, so allow them to make the right technical decisions. If your organization has product people, always make sure the team functions harmoniously.
3. Give engineers growth options
Don’t lose the enthusiasm of a committed team member by preventing them from moving up in the organization because of the lack of opportunities. Provide sensible paths for advancement since management isn’t for everyone. For those who don’t want people working under them as a career goal, consider providing promotion pathways in science and technology along with research and development (R&D).
4. Prevent burnout
Building software is different from building cars or houses, so don’t measure an engineering team’s progress by the same standards as other groups. When an engineer hears someone say, “Well you know so much about this, this task X should only take you an hour,” it could easily make him or her (and their skill set) feel undervalued.
If you’re from a non-technical background, find out more about the task you’ve assigned and trust the engineer you’ve hired to execute your vision within the given deadline. A good engineer will know to how to make strategic decisions that are the best use of your time and money. More hours spent in the office doesn’t necessarily mean a better product. Learning to recognize quality over quantity of hours in someone’s work can make all the difference.