Why does management think that? Are developers aligned with the domain they have to work with? Are they delivering on the goals, vs. working sideways on pet projects / infrastructure?
If they are not (and not willing to / can't spare time to get familiar with the domain), the usual solution is to insert a Business Analyst (BA) between the customer and programmers. The BA should be familiar with the domain (or trusted by the client at least) and have programming experience to translate to the programmers.
A quick way I personally used to boost management morale and trust in team performance is to give a visual demo. You can't sell the work if it has boring output (reports, sheets of numbers). But you can spice it up with colorful stuff (diagrams, statistics, etc). Maybe even make it interactive so they can try. Could that apply in your case?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why does management think that? Are developers aligned with the domain they have to work with? Are they delivering on the goals, vs. working sideways on pet projects / infrastructure?
If they are not (and not willing to / can't spare time to get familiar with the domain), the usual solution is to insert a Business Analyst (BA) between the customer and programmers. The BA should be familiar with the domain (or trusted by the client at least) and have programming experience to translate to the programmers.
A quick way I personally used to boost management morale and trust in team performance is to give a visual demo. You can't sell the work if it has boring output (reports, sheets of numbers). But you can spice it up with colorful stuff (diagrams, statistics, etc). Maybe even make it interactive so they can try. Could that apply in your case?