If the people asking you to solve a problem don't know what problem they want solved then there isn't much you can do except try to solve something and see if they complain.
You could argue that you should talk more with the stakeholders, but most of them don't have the skills required to accurately identify their own problems. Instead they need to see something running and then notice when things are missing, which is why we start building stuff without knowing what problem we ultimately are supposed to solve.
An business analyst appeared in the wild (..) as a consequence of stakeholders not knowing or having the necessary skills. BAs are experts in illiciting user requirements and transforming them into specifications and goals you can use to solve a problem.
Unless you know your goal you will never be able to deliver on your customer's expectations.
BA's work on business software which is typically written to help support processes and workflows that lean toward structure, definition, repeatability and so forth.
There's lots of software in the world (all creative software, for example) that doesn't share these attributes, and all the skills of a BA are useless.
The scope of software is larger than webdev and larger than business.
You could argue that you should talk more with the stakeholders, but most of them don't have the skills required to accurately identify their own problems. Instead they need to see something running and then notice when things are missing, which is why we start building stuff without knowing what problem we ultimately are supposed to solve.