I’ve been thinking a lot recently about the purpose of a product and how to successfully fulfill it. When writing last year about “product market flex” (which is fluid) vs “product market fit” (which is static), I noted that there is sometimes a mismatch between your product’s capabilities and the maturity of the market.
I was treating “teaching users your product” as 1 big job, and in reality there are potentially 3 sub-jobs hiding behind it. When you teach your product, you actually teach 3 different dimensions: the interface, the domain, and the benefit.
















