On types of problems and going straight into solving mode.
Today I felt like writing about the problem or problems? If you look online or ask ChatGPT to give you the main skills or task of a Product Manager, one of the main is to define the problem. The famous “Problem You’re Solving” is one of those 6 dimensions that the PM
must unlocked. The idea is to understand the specific challenge that one is solving for their users. I am a product manager so I think a lot about problems, all day long. In that journey of defining a problem is that most people go directly into solution mode. This is itself very “problematic” why? Because it takes time to understand the problem one is solving. One of the most common mistakes I see in the AEC industry that I don’t see so often in the Tech industry is that AEC goes immediately into trying to solve a problem instead really understanding what the specific problem is and what type of problem are they trying to solve. I feel that there are different types of problems…so the concept of defining the “problem you’re solving” it’s not so straight forward, first you need to understand the type of problem.
A problem, in the simplest definition would be an issue or challenge that needs to be addressed or solved. Generally, can be solved with a task, a goal or even a situation that after executed comes with a resolution. This would be small or large.
But then it’s when here comes the complicated bit, the ones that we just think are problems but might actually be “systemic problems” that inherent in a system or organization. These problems they are just not simple issues but mostly are cost by the way the system that they came up from is designed or operated, generally these problems are engrained and difficult to solve. In this case we cannot solved them just simply with a task, goal, or situation. For these ones to be solved it requires changes to the systems structure, culture, or policies.
Then we have “complex problems” those are a pain too, generally complex problems are just difficult to define and solved due to multiple variables, inter-dependencies and generally one needs to analyse every single outcome to come up with a solution for it.
I struggle to differentiate between systemic problems and complex problems, and I think that systemic problems are always complex. Because a system has relationships and interdependencies. But will stop there on the type of problem subject.
By this point, if you still follow this article, you will be thinking: why are you thinking so much about the type of problem and the problem? Well, the reason is, when you will go into solving this problem, it's fundamental to understands the types because otherwise is impossible to tackle the solution or even know if you can solve it. As I wrote in a previous article here, I believe the built environment industry, or the most common called AEC industry, is a system, and by itself the main problems are not simple ones, those are systemic and complex. So simple task solution will not cut it.
Also, most of the time, due to most people in the industry being problems solvers themselves, the industry leaders tend to immediately move into problem solving. The inertia is to look at the latest hype (blockchain, industrialized construction, digitalization...) and just go for it and claim it will fix it all. Do not misunderstand me, I do believe these solutions can have a positive impact in the AEC industry. But I believe many times companies and industry failed implementing one of these solutions and then, the entire industry goes into “that was not the right solution, let’s move to the next thing, or ditch that completely”. And the main thing is that before they didn't decide what problem were trying to fix in the first place with that hype solution.
In my view most of the times these technologies or hype trends come up because they do have positive impact in specific context but again, breakdown what we are trying to solve is critical. I also believe that the change in the AEC industry will come from within a change in the structure of it, a combination of solutions and most probably triggered by policies and renewal of processes. But I guess that is for another article.
“When solving problems, dig at the roots instead of just hacking at the leaves.”
― Anthony J. D'Angelo
Comments