Is It a Technical Problem or a Developmental One?

Before hiring a coach, a consultant, or a facilitator, there is one question worth answering carefully, because it determines everything downstream: is the problem you are facing technical or developmental?

The distinction comes from Ronald Heifetz’s work on adaptive leadership and runs through Robert Kegan’s research on adult development. It sounds academic. It is anything but.

Technical problems

A technical problem is one where the solution is known, or knowable. You may not have the answer yet, but someone does, and once you have it, applying it is mostly a matter of execution.

Your team’s meeting structure is inefficient. Your feedback process is unclear. Nobody knows who owns which decision. These are real problems, and they are technical. You can fix them with better design: a decision rights framework, a new meeting cadence, a clearer org chart. An expert can hand you the answer, and if the team implements it, the problem goes away.

Technical problems are satisfying to solve. This is why so much organizational energy flows toward them, even when they are not the real problem.

Developmental problems

A developmental problem is different. The solution is not out there waiting to be found, because the problem lives in how people currently see, interpret, and respond. Solving it requires the people involved to grow, not just to learn.

Consider a partnership where feedback is theoretically welcome and practically absent. You can install a feedback process, and I have watched teams do exactly that. The process gets used for six weeks and then quietly dies. Why? Because the absence of feedback was never a process problem. It was protecting something: relationships, status, a fragile equilibrium among the partners. No template solves that. The partners have to develop a different relationship to conflict itself.

The tell of a developmental problem is this: you have already tried the technical fix, it worked briefly, and then the old pattern returned. If a problem keeps surviving good solutions, you are almost certainly looking at a developmental problem wearing a technical disguise.

Why the misdiagnosis is so common

Organizations misdiagnose in one direction almost exclusively. They treat developmental problems as technical ones. Rarely the reverse.

The reasons are understandable. Technical solutions are faster, cheaper, and less personally exposing. Nobody has to look at their own contribution to the pattern. You can buy a workshop, roll out a framework, and legitimately say you addressed the issue. Developmental work asks more: it asks leaders to examine the assumptions and self-protections that keep the current pattern in place. That is uncomfortable, and busy executives have an endless supply of reasons to defer discomfort.

But misdiagnosis is expensive. Every technical fix applied to a developmental problem costs money, time, and, most damagingly, credibility. Teams become cynical. “We did the communication training. Nothing changed.” Of course it did not. The training answered a question nobody was asking.

How to tell which one you have

A few diagnostic questions I use with clients:

Has this problem survived at least one competent attempt to fix it? If yes, suspect developmental.

Does solving it require anyone to change how they see themselves or each other, not just what they do? If yes, it is developmental.

Could a smart outsider hand you the answer? If yes, it is technical, and you should go get that answer. Not everything needs coaching.

Do people privately agree the fix will not work, even while publicly implementing it? That quiet knowing is a signal the real problem lives somewhere else.

Matching the work to the problem

Technical problems deserve technical solutions, and good ones. Developmental problems deserve developmental work: sustained, honest, usually supported by someone outside the system who can see what the system cannot see about itself.

The costliest move is not picking the wrong problem. It is picking the right problem and the wrong kind of work.

Michael Langer is an executive coach and team coach based in Brooklyn. He works with senior leaders and investment teams on the problems that survive good solutions.