"You should add those things as foundational principles: the two-sided domain expertise and responsibilities, not tasks. It's not enough just to have knowledge or expertise of the industry. You have to know how to deliver results in it with the specific solution you're working in."
True domain expertise has two halves: deep knowledge of the customer's industry AND deep knowledge of how your product delivers results in that industry. Either half alone is insufficient.
Examples
The computer lab retirees at Utah State
My college job was running the computer lab at Utah State. Retirees enrolled in continuing education classes would come in to learn the basics. I showed them FaceTime to call their grandkids, and their minds were blown. The next day, the same retirees would come back expecting one-button Venmo transfers, automated tax filing, and credit card fraud monitoring, because the FaceTime demo had reset their entire mental model of what computers could do for them. The lesson: when your customer's mental model of the technology outpaces what is actually possible, you have to reset their expectations honestly, not let them keep climbing. Two-sided domain expertise is what makes that reset possible. You need to understand the customer's mental model (what they think the tool can do for them) AND the actual technology's boundaries (what your product can deliver), so you can bridge the gap with truth instead of riding a hype cycle into disappointment.
Related terms
Jeff Moss
Founder, Expansion Playbooks. A decade studying customer retention and expansion data from 75+ recurring revenue businesses.