In our case, I've found our customers just aren't very good at imagining things that aren't in the user interface or actions that aren't implemented.
After all they're not developers, so likely aren't used to imagining user interfaces and interactions.
Regardless, the result is that if what we show them ain't pretty close to how it'll look and work, they won't get it and will have a hard time understanding how it will affect their workflow.
So we end up having to implement a fair part of the solution just to get some feedback that we can iterate on.
Since we have several decades of combined domain expertise inhouse, we're typically pretty good at guessing what the customer needs or wants and usually don't have to change much.
> Since we have several decades of combined domain expertise inhouse
Honestly this sounds pretty much like a luxury and as far as I can tell pretty rare. Maybe it's a country thing but in the UK many tech companies seem to have a "product team" with a collective memory of no more than a few months leading every decision. We don't have any BA's or anyone that can get requirements from customers. Seems to just be "here is the feature we decided you need" and then they wonder why the customer doesn't like it...
After all they're not developers, so likely aren't used to imagining user interfaces and interactions.
Regardless, the result is that if what we show them ain't pretty close to how it'll look and work, they won't get it and will have a hard time understanding how it will affect their workflow.
So we end up having to implement a fair part of the solution just to get some feedback that we can iterate on.
Since we have several decades of combined domain expertise inhouse, we're typically pretty good at guessing what the customer needs or wants and usually don't have to change much.