Thanks Benn for another great article. It resonates well with me.
I really wish for two things; one that everyone in the room speaks in a simple and welcoming language, keywords and external references don't help - the fastest way to a solution. Second, DS folks should appreciate the value in investing time in leveling up with the customer, lingo and skills wise, for both better customer experience and better product/service/feature overall. After all the customer have experienced the "problem" for much longer
Agreed on the second point - I think there’s sometimes a tendency to assume data = expertise, and discount the expertise of other folks because they don’t speak the same language. (There probably is an actual language analogy there, where we make assumptions about people who don’t speak our native language fluently.)
Thanks Benn for another great article. It resonates well with me.
I really wish for two things; one that everyone in the room speaks in a simple and welcoming language, keywords and external references don't help - the fastest way to a solution. Second, DS folks should appreciate the value in investing time in leveling up with the customer, lingo and skills wise, for both better customer experience and better product/service/feature overall. After all the customer have experienced the "problem" for much longer
Agreed on the second point - I think there’s sometimes a tendency to assume data = expertise, and discount the expertise of other folks because they don’t speak the same language. (There probably is an actual language analogy there, where we make assumptions about people who don’t speak our native language fluently.)
On the jargon point, Randy Au again has a good post on that: https://counting.substack.com/p/ds-jargon-is-just-everyone-elses
Thanks for sharing Randy's blog post, great read and yes exactly what I had in mind.
Sometimes I feel that I've learned more data analysis from the collaborator than I actually gave back to them - gotta value domain expertise