{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Fops-i-did-it-again.simplecast.com%2Fepisodes%2Fprovider-directory-G_tWUUnh","width":444,"version":"1.0","type":"rich","title":"Provider Directory: I will destroy your roadmap with Misha Nasrollahzadeh + Grant Veldhuis","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/60e2b59f-ca09-4dc7-8d7c-c565a7f46186/f3e9d615-8e91-4660-85e3-4719f672dc02/s2_intro_boilerplate_square.jpg","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/28bbbbb1-deab-4401-8830-8b83eeec45ab\" height=\"200\" width=\"100%\" title=\"Provider Directory: I will destroy your roadmap with Misha Nasrollahzadeh + Grant Veldhuis\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"Strap in, young product manager or engineer (or vibe coder!). You have been tasked with the provider directory project. You have scoped it with your engineers, and you think you can get this done in a quarter. And so dutifully you make it your OKR. I'm here to tell you that this is going to be your next year. Certainly not your next quarter. And you should probably listen to this episode so that you know all the things that we have learned the hard way and can sidestep it. \n\nProvider directory is a bunch of data and feature and product raccoons all in a trench coat. What makes building one so hard is that you get trapped trying to build each raccoon. The way out is to be clear-eyed about all the different components that get lumped under the provider directory umbrella, be specific and choosy about which ones you actually need to serve your members, and be ruthless about not building any of the others.\n"}