I think it more "a person capable of empathising with the users". Knowing the internals of how the baseball industry operates isn't relevent here. The relevent experience is being familiar with how the viewers interact with baseball.
Having said that, it seems like this applies mostly to frontend people writing the consumer facing portions. There are plenty of jobs where your users are other people in the company, or partner companies. In those cases, understanding the bussiness tends to be far more important than understanding the user experience.
For parking garages, the relevent experience would be someone has used them a lot. Or at least someone who is familiar with driving a car.
>In those cases, understanding the bussiness tends to be far more important than understanding the user experience.
Never understood the take that internal systems need a good UX because they very much do. Having been a consumer of ass-backwards designed software components, bad UX (apis, functions, other stuff) will inevitably propagate through the product and will rear their ugly head somewhere. Not to speak about "friction" and development velocity and so on.
Why yes, implementing this feature will cost you something like 2 hours. Not implementing it will either cost someone 4 hours to do it themselves or two hours over and over again to code around the lack of it. Please don't waste other people's time.
Having said that, it seems like this applies mostly to frontend people writing the consumer facing portions. There are plenty of jobs where your users are other people in the company, or partner companies. In those cases, understanding the bussiness tends to be far more important than understanding the user experience.
For parking garages, the relevent experience would be someone has used them a lot. Or at least someone who is familiar with driving a car.