Can a Non-Tech Manager Effectively Oversee Tech Pros?

A manager is a worker with ambition who seized greater responsibility. But as the old saying goes, many manage to rise above their abilities, and attract reputations for uncertain guidance, indecision, and de-motivation.

It doesn’t have to be this way.

Putting the right person in the right job is the most important task that many companies screw up. A bad hire is bad enough, but the problem compounds when that bad hire is a manager—and the problem may scale up exponentially when you have an IT-oriented unit answering to a non-tech manager.

At some point, tech pros must interface with people who have relatively little idea how technology works. Yet “those people” run the business, and must understand and sign off on projects. They aren’t going away.

With all that in mind, can a non-tech manager effectively manage tech pros? Experts and consultants hold different opinions on that. No matter what the situation, though, hiring “the right manager” requires attention and effort.


Fernando Delgado is a consultant who makes his living as a coach for project managers, having worked at Yahoo and Google. Based on his experience, he is convinced that software engineers are best managed by other software engineers.

“In history… not a single product has ever shipped on time,” Delgado said. Any software project will hit unexpected roadblocks and snags along the way. Resolving those issues may require taking shortcuts or making tradeoffs. “Software engineers make the right trade-offs when faced with obstacles,” which makes software development unpredictable.

There is another soft factor to consider: the relationship between the manager and the managed. “Engineers want the trust and respect of whoever is leading them.” Delgado said.


An alternative viewpoint says it is possible for a non-tech manager to manage the technical. All it takes is a heavy reliance on soft skills, according to Scott Berkun, blogger and public speaker on creativity and business culture.

“A good manager provides clarity. They create clear goals that IT, or a programmer, or anyone in any role, can understand.” Berkun said via e-mail. “A good manager also invites feedback and listens well, inviting experts who work for them to give their perspective on proposed goals they set, to help managers recognize their potentially dangerous assumptions, and to revise their goals and requests to be better informed. “

A tech pro might not understand business goals or internal politics, which are more important in some situations, he added. Managers have to orchestrate a project, listen to the experts who report to them, and incorporate feedback—all of which are people skills, not technical ones.

It Depends

“I myself am not deeply technical, but I am tech-inclined,” said Kurt Van Etten, VP for product development at RedSeal, a cybersecurity analytics platform. His past experience serves as a bridge of sorts between the tech and managerial worlds: ‘You need a basic understanding of technology. You don’t need the expertise.”

A technical manager may know how a product works, only to have trouble conveying its importance to the board and CEO, Van Etten noted. When things get lost in that translation, issues arise.

Product managers can serve as the ideal mediator between the business and the technology, he added. People with a background in quantitative analysis work well in such positions, as they not only understand the user experience, but can talk to engineers: “It’s great if they come with an MBA.”

Management Is…

Managers must be analytical, communicative, have a good product sense and a vision. “The best product managers are capable of getting the team to be as productive as possible.” Delgado said. They do not expect perfection, instead looking for good-enough solutions that get past obstacles.

The best product managers show competence in a number of factors, but probably “spike” in one or two of them, Delgado continued: “Smart companies will place people in places they already spike to get the best return on team execution.”

It probably does not pay to spruce up skills that are already adequate, he added. “You can coach people to play to their strengths.”

Van Etten also keeps an eye out for soft skills. Can this person make a call on trade-offs? If the architect and the engineer both think they are right, and disagree on a course of action, how do you resolve it? “The key to soft skills is empathy,” he said. Listen to people and understand where they are coming from; explain why a decision was made, and why one factor mattered more than another. “Make sure you get contribution from everyone.”

Picking a winner in such circumstances is a problematic challenge. “All interview methods are highly subjective and prone to error: we all know this from the interviews we’ve experienced in our own careers,” Berkun said. “The best way to hire people is through experience—to actually work with someone on a small project where you can experience firsthand their abilities and qualities.”

A good interview focuses on the candidate, lets them talk or demonstrate their key abilities, and incorporates input from several different people on the team. It also delves into the necessary skills for the job at hand.

Management Is Not…

The sad reality is that bad management is commonplace. Still, there are methods that companies can use to ensure they do not cultivate bad managers.

“Bad management is common because management is both hard and subjective. Human nature is much harder to work with than the rules of engineering, science or grammar,” Berkun said. “There are different management styles, and types of workplace culture, and it’s rare that a manager is self-aware about both of those, much less knows how to improve them. “

A manager who believes their own success is dependent on the employee’s success is great for the employee; but if the manager believes his success depends on an employee’s failure, then the employee had better find another job inside the firm. “In a small company, a poor manager is a strong enough reason to search for a job elsewhere,” Delgado explained.

Bad managers can be weeded out, but that often takes a performance review that includes peer reviews from other managers, as well as feedback from employees who are protected from retaliation, Delgado continued. “Then you can get a system where a bad manager gets identified very quickly.” Such a system will also expose a manager who is good at managing up but terrible at managing down.

Typical companies will promote the best person or highest performer in a unit. “The best individual contributing is not the best manager,” Van Etten observed. “You see high performers put into a management role with no training… Of course they are going to fail.”

Management is about playing a different role, not being better or smarter than the staff, Van Etten continued. The solution is training someone in leadership. That means setting an example, sharing a vision and building trust with employees: “Followership is cultivated by leadership.”

“A good rule to reduce the creation of bad managers is to have a promotion path in each role that doesn’t require becoming a manager.” Berkun said. “If the only way to get a raise is to become a manager, workers who don’t really want to manage will be incentivized to do it anyway—they want more money, not the role of being a leader.”

It all comes down to listening, flexibility, and making informed decisions with the input from the staff. “Any conversation that involves considering different ideas can be seen as having friction, but that friction is a kind of energy, a heat that can be used to improve thinking, ” Berkun added. Whatever the trade-offs, there’s often more than one “good path” to take when it comes to effective management.

9 Responses to “Can a Non-Tech Manager Effectively Oversee Tech Pros?”

  1. Years ago, we had a development manager who was a former developer. He wasn’t a very good manager, though, and we let him go. After we let him go, someone else from within the company was suggested. He had a background in development but had spent most of his time as a manager. I was asked what I thought about it.

    My argument was that we had more than enough expertise in the group. We didn’t necessarily need another “smart person.” What we needed was someone to herd us and get us going in the right direction, manage resources inside and outside the group, etc. That said, we also wanted someone who could understand the terminology. We didn’t want to have to explain what the Kernel was and why it was important. We didn’t want to have to explain socket filters–he knows what a socket is and is smart enough to understand that a socket filter probably filters information on sockets.

    My phrase was that, for the Development Manager, we need “Little ‘d’, Big ‘M’.” Managers need to be able to manage. But it’s important that they understand what a developer is talking about without that developer having to explain everything “using words of less than two syllables.”

  2. One of the best managers I ever had was non-technical. What made him great was that he had a very clear vision of the finished product and never hesitated to passionately explain the vision in as much details as necessary to anyone who seemed to want or need the explanation.

    On the converse side, a technically-savvy manager has sometimes be untenable managing me: changing code without coordination, changing requirements because “it is a trivial change”, and meddling in my way of working.

  3. All I would say is choose your Managers and Team Leads with due diligence, especially those “capable of applying common sense and reasoning” would be good traits to look for, because those roles are immensely significant as they are the mediators between the workforce and the stake holders. If you put, in those positions, bad or non deserving people, then be ready to see the best of the talents you have, walking out the door, sooner or later because they’ll irritate the hell out of them with their stupidity and arrogance of being superiors. It’s worth leaving those positions vacant until you find a right fit. Mostly, the technical teams know how to manage their workload. All they need is clear requirements of the product they are going to build. Now you may ask them how many ways exist to meet the goal and pick the best suitable one.
    There shouldn’t be unsolicited technical meddling from the Managers unless they are involved in technical work day in and day out, lest they, being a techie years ago, end up in delusion of knowing more than their technical teams which leads to endless and useless time consuming debates.
    The bottleneck of all the problems could be at the TOP. So again, those positions are of immense significance and must be left vacant until a right fit is found. Meanwhile, pickup some interim managers with a clear message that they are not the managers but “interim” managers until the position is filled. My two cents. Thanks!

  4. The best managers I ever had was non-technical, and the absolutely worst manager I ever had was non-technical. It totally depends on the manager. A great manager knows what needs to be done, and sees that it gets done, while simultaneously respecting, and keeping the respect of, his people. A great manager works through the problems with his people, asking for input and looking for solutions as a team. A bad manager just says do it or else. A good manager looks for things that will allow him to reward his people and help them succeed. A bad manager will make note of every little mistake in order to punish his people and hold them back. It strictly depends on the personality and skills of the manager.

  5. Mike McHugh

    I understand the idea here but both the proposition and the argument are binary. What of the 50 shades of grey that exist between technical and not-technical?

    It’s like a self-fulfilling prophecy: in a situation where there is natural dissonance (based on technical knowledge, or lack thereof) between the manager and the managed, can they get along and support ‘management’?

    When it comes down to the wire, management is about getting it done. A manager does not need to engage in the activities of the managed, merely to obtain commitment to stated results, within a stated time frame, to a stated quality. It doesn’t have to be unpleasant. A non-technical manager should elicit from the managed the information and operational parameters that enable management to take place. And concepts of leadership and team spirit should easily overcome any dissonance that might be due to gaps in technical knowledge.

  6. From my experience India i worked with both these kind of managers, But managers who came from tech back ground understands what a developer trying to explain and they make the life better. The non-tech managers fail to evaluate people , only showcasers can survive. And they dont even know how to explain a problem to the client. And i was able to see managers from non-tech background is always insecured.

  7. The best person to lead a developer has BOTH management and technical skills. One or the other will not cut it. This is the actual rarity in “good leaders” that people talk about. It’s like having an interpreter who speaks multiple languages. If you can only understand one language, you’ll only be able to speak to people who speak that language. If you know more than one, you’ll be able to speak to more people. If you know management and have technical knowledge/skill, you’ll be able to speak to two different groups.

  8. John John John

    Can a non tech manager effectively oversee tech pros? Depends on what the culture of the team and how well people get along in the team. TLDR – no, a non tech manager can’t effectively oversee tech pros.

    I work in a team where one tech scammer persistently tries to pull wool over the eyes of the non tech management. Everything is everyone elses fault in the team. What took someone 1 hour to resolve she spent 2 weeks trying to figure out (not exaggerating) – after everything was settled, she would still gnaw at the ears of management how the 1 hour fix was the cause of all the problems to begin with. If you have such a cockroach in your team, having a non tech manager makes the situation worse. It’s a war of attrition, people who don’t play these stupid games will just give up and not bother about it so it becomes that the whiner who tries to tech scam the non tech IT manager will have the last word and usually does… God forbid you get one of these whining whinging tech scammers in your team. Mixed in with a non tech manager will spell disaster to the organisation.