DOP 274: What Is the XY Problem?

[@Jaabaa_Prime]

I've seen this issue too, so many times almost 30 years of software and architecture consulting🙂I had something similar a couple of months ago, Task: provide an API (X), using REST (Y), for a complex business model. After a couple of weeks I realized that the complexity of satisfying all the service clients with REST calls was going to be a huge undertaking. I told the project management that we are switching to GraphQL (new Y to solve X) and leave the "required data" to the calling services and not trying to implement an endpoint for each use case.

[@gpltaylor]

Most people are poor at thinking about a problem, and quickly start solutionizing. They don't know how to clarify a problem. For example, what's the purpose of the Three Char's to the file extension. What are they going to do with it. What's the goal. People (managers/Directors) think they should go to developers with a solution. However, 10 developers can solve a problem in a more robust way that also uphold all existing business logic if they are given a problem and not a solution. "maybe the problem is not the problem" has the root cause in lack of experience within the business, process, people and systems. It takes time to educate 10 developers, 2 product owners and 4 testers about a "problem", so giving them a solution, is quicker.. Or is it....