{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Data Science Tech Brief By HackerNoon","title":"Why Partner Data Became My Toughest Engineering Problem","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/cf8c383c\"></iframe>","width":"100%","height":180,"duration":523,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/why-partner-data-became-my-toughest-engineering-problem.\nYour partner portal isn't broken; your definitions are. How fixing \"data lineage\" cut deal registration time from 4.5 days to under 2.\nCheck more stories related to data-science at: https://hackernoon.com/c/data-science.\n            You can also check exclusive content about #data-architecture, #systems-engineering, #rev-ops, #partner-ecosystem, #channel-sales, #gtm-strategies, #sales-operations, #deal-registration,  and more.\nThis story was written by: @aniruddhapratapsingh. Learn more about this writer by checking @aniruddhapratapsingh's about page,\n            and for more stories, please visit hackernoon.com.\nPartner systems slow down when data definitions drift. Real stability returns only when the model is cleaned up and workflows align around a single, consistent structure.","thumbnail_url":"https://img.transistorcdn.com/8VxAgS1Ll3FJEERcAdhFdqqXJMnE7OfD2RUvrjauLt0/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMjY4LzE2ODM1/ODI1ODUtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}