Reading through this conversation worries me about adopting the product -- will it meet B2B needs, or will it do what it was conceived to?
This feels like a case where you could be more open minded to users' "job to be done" and less reliant on the "you can just..." trope from engineers over-familiar with a pet tech.
While I appreciate you got to "let's jump on a call", the "I'm not sure I understand" plays like engineering speak for "you're doing it wrong".
I've found, in general, users never do it wrong, rather, product owners fail to accept their product is not being used for the job they think.
Users have a need, users try to make a need-adjacent product fit the need -- but it doesn't. Teaching the users a lesson in using the product doesn't actually resolve the need.
(This is similar to the rare insight that requiring user training before using the product is a sign of both a poor user experience and a need/feature mismatch. The more marketed and "required" the training, the less well-suited the product.)
Didn't want to sound dismissive here, English isn't my first language so maybe I didn't express myself in the right way.
The let's jump on the call is genuinely to understand what the job to be done is, whether it's something we should cover or not and see if the problem is an education gap in our documentation or a product gap in our offering.
If we're not the right product to serve those specific needs we'd point to the best alternative we know of
This feels like a case where you could be more open minded to users' "job to be done" and less reliant on the "you can just..." trope from engineers over-familiar with a pet tech.
While I appreciate you got to "let's jump on a call", the "I'm not sure I understand" plays like engineering speak for "you're doing it wrong".
I've found, in general, users never do it wrong, rather, product owners fail to accept their product is not being used for the job they think.
Users have a need, users try to make a need-adjacent product fit the need -- but it doesn't. Teaching the users a lesson in using the product doesn't actually resolve the need.
(This is similar to the rare insight that requiring user training before using the product is a sign of both a poor user experience and a need/feature mismatch. The more marketed and "required" the training, the less well-suited the product.)