This is a short spoken excerpt arguing that design systems should be treated like products: they need product-market fit work (customer interviews, defined feature sets) and staged releases (v1/alpha/beta) targeting real user needs rather than being built and passively hoped to be adopted.
You can make a product, but if it doesn't fit your market, people won't use it. Right. And so design systems are the same way if it's a product. And the way that they generally start is that people go, oh, let's just make a bunch of things for other people to use, and then they kind of cross their fingers and hope that somebody will use it. That's not the way that you assess market fit for any product. The way that you assess market fit is you probably are doing customer interviews before you have a product. You're probably defining a feature set that you know the customers are going to use, and then you're going to Release a version 1 or an alpha or a beta or something like that that then serves those particular needs.
