Help Your Engineers Accomplish More By Getting Them ´In The Zone´

The other day during a stand up meeting, one of our engineers, Ben, shared that he had a breakthrough after implementing a problem-solving technique we had been discussing loosely. The technique involved stepping away from the problem, fixing a different bug, then coming back to the original problem. When Ben did this, the solution magically appeared, and he solved his original problem within minutes. He’d previously spent days thinking about it—with no breakthrough.

We have all had those “aha” moments in which we are suddenly struck by inspiration. What is it about these moments that allows us to clearly see the answer to something that has vexed us for so long?

The answer isn’t simple. But it is knowable.

Ben told me, “It doesn’t make sense why the solution suddenly came to me, but it did.” I wondered if other engineers had the same experience, so I asked around the office (virtually because we’re all at home due to COVID-19). Most engineers agreed: they had done this in the past, didn’t know why it worked, and most critically, hadn’t systematized a way to repeat it.

That last piece is important. Engineering types want repeatable procedures to execute against. And they need to know why those procedures work. They don’t like magic. They like disciplined and orderly processes that produce results. (That’s a good thing, by the way. We don’t want our airplane engineers throwing ideas around to see what sticks. That’s why the discipline of engineering exists in the first place!)

So, with that in mind, here is what I believe is the most critical and underdeveloped skill in engineering: the ability to understand and control one’s feelings and emotions. We solve problems most effectively when our mood is just right. Too much pressure, and the brain shuts down. Too little pressure, and the brain wanders. This is about being in the zone and under pressure; think Tiger Woods and a 50-foot putt. Engineers have the same zone, just a different playing field.

We solve problems most effectively when our mood is just right. Too much pressure, and the brain shuts down. Too little pressure, and the brain wanders.

Think about it this way: when you are under extreme duress, you are likely to move to the classic flight-or-fight mode. That decision is made by your primitive brain—the part of us that is hardwired for survival. On the other end of the spectrum, when you are in your most blissful state, the thought of doing things that require extreme precision or analytics is equally difficult. There’s a sweet spot in the feelings spectrum for solving problems, and that is where we need to be to optimally solve a problem.

So, how does stepping away to solve a simpler problem allow us to solve more complex problems? How do ideas “magically” come to us? This happens because our minds are greased for answers once we get an easy problem solved. When we solve a problem, at least for the engineering mind, we get a rush. Success releases dopamine and other neurotransmitters that propel us forward. That, in turn, sets the stage for solving other problems. Suddenly, our brains are more grooved for problem-solving. Our mood is no longer overwhelming our analytical brain. And then, other answers appear. Not because of magic, but because the undercurrent of feelings that was distracting us has been put in alignment to allow the answer to become clear.

How can business leaders create an environment that allows engineers to access this success?

Start by taking ownership and acknowledging it is up to you to effectively and proactively set the mood at work. Every day, engineers are tasked with solving complex problems that require non-linear thinking. The world around them tells them to push forward with brute force until they break through, but what they really need is to intentionally disconnect from the problem.

To help foster an environment for productivity, try implementing some of the following:

Bake the concept of “slow down to speed up” into your organization. Make time for breaks and encourage thoughtful distancing from work.
Encourage beneath-the-surface, emotional conversations. Help your engineers identify and address their underlying emotions.
Don’t sabotage workflow with interruptions. Once your people are in the zone, do everything you can to help them stay there.

By creating an environment that encourages breaks and emotionally intelligent conversations, you can teach your engineers how to have a healthy and productive mindset. In time, this will help them solve problems more effectively.

The next time one of your engineers comes to you with a problem, instead of telling them how to solve it, ask them how they feel about it, and what they could do to change their mood. Then challenge them to do so, give them the space, and see if they don’t come back inspired. I know it works for me, and I hope it works for you too.

This content piece has been prepared solely for informational purposes. The content piece does not constitute an offer to sell or the solicitation of an offer to purchase any security. The information in this content piece is not presented with a view to providing investment advice with respect to any security, or making any claim as to the past, current or future performance thereof, and Mainsail Management Company, LLC (“Mainsail” or “Mainsail Partners”) expressly disclaims the use of this content piece for such purposes.

The information herein is based on the author’s opinions and views and there can be no assurance other third-party analyses would reach the same conclusions as those provided herein. The information herein is not and may not be relied on in any manner as, legal, tax, business or investment advice.

Third-party images, logos, and references included herein are provided for illustrative purposes only. Inclusion of such images, logos, and references does not imply affiliation with or endorsement for or by such firms or businesses.

Certain information contained in this content piece has been obtained from published and non‐published sources prepared by other parties, which in certain cases have not been updated through the date hereof. While such information is believed to be reliable for the purposes of this content piece, neither Mainsail nor the author assume any responsibility for the accuracy or completeness of such information and such information has not been independently verified by either of them. The content piece will not be updated or otherwise revised to reflect information that subsequently becomes available, or circumstances existing or changes occurring after the date hereof, or for any other reason.

Certain information contained herein constitutes “forward-looking statements,” which can be identified by the use of terms such as “may,” “will,” “should,” “could,” “would,” “predicts,” “potential,” “continue,” “expects,” “anticipates,” “projects,” “future,” “targets,” “intends,” “plans,” “believes,” “estimates” (or the negatives thereof) or other variations thereon or comparable terminology. Forward looking statements are subject to a number of risks and uncertainties, which are beyond the control of Mainsail. Actual results, performance, prospects or opportunities could differ materially from those expressed in or implied by the forward-looking statements. Additional risks of which Mainsail is not currently aware also could cause actual results to differ. In light of these risks, uncertainties and assumptions, you should not place undue reliance on any forward-looking statements. The forward-looking events discussed in this content piece may not occur. Mainsail undertakes no obligation to update or revise any forward-looking statements, whether as a result of new information, future events or otherwise.

No representation, warranty or undertaking, express or implied, is given as to the accuracy or completeness of the information or opinions contained in the enclosed materials by Mainsail and no liability is accepted by such persons for the accuracy or completeness of any such information or opinions. For additional important disclosures, please click here.