A podcast where data experts solve real-world operational challenges submitted by listeners. Each episode tackles a fresh problem, delivering actionable solutions, key insights, and implementation steps to help data professionals overcome barriers and create business value. <br/><br/><a href="https://impactoperations.substack.com/s/data-breakthroughs?utm_medium=podcast">impactoperations.substack.com</a>
Data Breakthroughs: Solving Real-World Data Challenges
Claim This Podcastby Lior Barak - Cooking Data
14 episodes
Updated Daily
Accepts GuestsHas SponsorsLocation 🇩🇪
18
Podcast Authority
BetaPoorBased on show quality, social media presence, reviews, charts, and more
Quality37
Social0
YouTube0
Engagement0
Podcast Overview
A podcast where data experts solve real-world operational challenges submitted by listeners. Each episode tackles a fresh problem, delivering actionable solutions, key insights, and implementation steps to help data professionals overcome barriers and create business value. <br/><br/><a href="https://impactoperations.substack.com/s/data-breakthroughs?utm_medium=podcast">impactoperations.substack.com</a>
Language
🇺🇲
Publishing Since
4/25/2025
Unlock The Full Podcast Authority Score Report
See how your podcast performs across key metrics
18
Podcast Authority
BetaPoorBased on show quality, social media presence, reviews, charts, and more
Quality37
Social0
YouTube0
Engagement0
7
Excellent Areas
1
Good Performance
11
Growth Opportunities
excellent
Publishing Consistency
Every 3 days
Performing excellently!
good
iTunes Tags
6.5/10
Recommendations available
Unlock the full report to see detailed tips
poor
Episode Thumbnails
Recommendations available
Unlock the full report to see detailed tips
+16 More Metrics
Unlock comprehensive insights including:
- • YouTube presence analysis
- • Social media reach metrics
- • RSS compliance scoring
- • Podcast 2.0 features
- • Technical standards
What's Included in Your Full Report
Detailed Analytics
- Complete breakdown of all 19 authority metrics
- Personalized recommendations for each metric
- Industry benchmarks and comparisons
- Technical RSS feed analysis and compliance scoring
Growth Strategies
- Step-by-step action plans for improvement
- Quick wins to boost your score immediately
- Pro tips from successful podcasters
Get your free podcast insights report
See how your show performs across every key metric
Instant delivery
No spam
Attract Better Guests
High authority scores make your podcast more attractive to industry leaders and influencers who want to appear on credible shows.
Secure Sponsorships
Sponsors look for podcasts with proven authority and engagement. Your score demonstrates your podcast's value to potential partners.
Grow Your Audience
Understanding your strengths and weaknesses helps you make data-driven decisions to expand your listener base effectively.
2 verified contact emails on file for Data Breakthroughs: Solving Real-World Data Challenges
Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.
Recent Episodes
December 17, 2025
Episode 11: When “Just Connect It” Takes Four Months
<p>Episode Summary</p><p>I’m incredibly excited to have Ilya back for the Season 1 finale. He was my very first guest in the <a target="_blank" href="https://cookingdata.substack.com/p/data-breakthroughs-solving-pipeline">pilot episode</a>, and honestly, he helped me figure out this format - what works, what doesn’t, how to make the collaborative problem-solving feel authentic. So it felt only right to close this season by bringing him back full circle.</p><p>In this finale, we tackle a frustratingly common scenario: a marketing stakeholder needs data from a new platform for critical quarterly forecasting, but the data team estimates four months to build the connector. Meanwhile, two hours disappear every morning into manual CSV downloads, cleanups, and copy-paste operations, a process that’s already caused a 50% error in pipeline analysis.</p><p>What seems like a technical integration problem quickly reveals itself as something much deeper: an organizational breakdown in ownership, communication, and mutual understanding between business stakeholders and data teams. And true to form, Ilya immediately zeroes in on the people side of things.</p><p><strong>Problem Category</strong>: Data Integration & ETL<strong>Runtime</strong>: 40 minutes</p><p>The Problem</p><p><strong>Submitted by</strong>: Anonymous Marketing Professional<strong>Industry Context</strong>: Company with established data infrastructure and quarterly business planning cycles</p><p>Problem Framework</p><p><strong>Issue</strong>: Need data from the new marketing automation platform for quarterly forecasting, but building a connector will take four months, according to the data team. Currently manually downloading CSV files daily.</p><p><strong>Trigger</strong>: Quarterly planning cycle starts in 8 weeks. Currently spending 120 minutes every morning downloading, cleaning, and manually importing marketing data files. Last week, a copy-paste error threw off pipeline analysis by 50% - only caught because the numbers seemed unrealistic.</p><p><strong>Tension</strong>: The data team focuses on building robust, enterprise-grade connectors that take months to develop properly. While understanding their approach, there’s an immediate business need that can’t wait for the perfect solution. The manual process is unsustainable and risky, but the data is critical for business planning.</p><p><strong>Boundaries</strong>:</p><p>* Cannot change the quarterly planning timeline (set by business cycle)</p><p>* The marketing platform was selected by leadership and cannot be changed</p><p>* The data team has limited capacity and other priorities</p><p>* A budget exists for reasonable interim solutions</p><p>* Must maintain data quality standards for forecasting accuracy</p><p><strong>Tech Stack</strong>: New marketing automation platform with CSV export capability, central data warehouse for forecasting (specific tools not disclosed)</p><p><strong>Clarity Statement</strong>: Need an interim solution to get marketing platform data into the data warehouse reliably within the next 8 weeks, without waiting for the full enterprise connector that will take 4 months.</p><p>Our Guest</p><p><strong>Ilya</strong>Fractional Head of Data & Data Leadership Consultant</p><p>Ilya brings over 15 years of data experience, having led data functions at companies like Ada Health (symptom checker app), and various startups and scale-ups across Berlin and Munich. Originally from Moscow with a background in computational mathematics, he moved to Germany in 2002 and transitioned from database research to hands-on data engineering and leadership roles. After the biotech winter impacted Ada Health, Ilya pivoted to fractional and interim data leadership, helping companies build data platforms and teams across different domains and stages.</p><p><strong>Special Note</strong>: Ilya was our very first guest in the pilot episode and returns to close out Season 1, bringing his people-first philosophy full circle.</p><p><strong>Connect with Ilya</strong>:</p><p>* LinkedIn: <a target="_blank" href="https://www.linkedin.com/in/bkmy43/">https://www.linkedin.com/in/bkmy43/</a></p><p>* YouTube: <a target="_blank" href="https://www.youtube.com/@lab4.berlin">https://www.youtube.com/@lab4.berlin </a>(Data leadership discussions while smoking pipes - yes, really, and it’s worth checking out)</p><p>* Website: <a target="_blank" href="https://www.lab4.berlin/">https://www.lab4.berlin/</a></p><p>The Breakthrough Discussion</p><p>Initial Reactions</p><p>Ilya and I immediately recognized this as a people problem disguised as a technical problem. As Ilya put it: “From most failing projects and situations like this, I rarely saw the root cause was technology or tools.”</p><p>The four-month estimate raised red flags for both of us. As Ilya observed, connecting to an API of an existing marketing tool shouldn’t take four months - what’s likely happening is that “building a connector” actually means the entire pipeline: getting the data, integrating it into the company data model, and delivering it through BI tools with proper business logic.</p><p>The Real Problem</p><p>Through the reflection break and collaborative discussion, we identified the core issues:</p><p>* <strong>Communication Breakdown</strong>: The data team likely down-prioritized this request because other initiatives have a higher business impact, but they haven’t articulated this clearly. The stakeholder hears “four months” without understanding what’s blocking it.</p><p>* <strong>Ownership Confusion</strong>: It’s unclear who owns the decision about prioritization and tradeoffs. Without clear ownership, every request becomes a negotiation rather than a strategic decision.</p><p>* <strong>Missing Context</strong>: The data team probably doesn’t understand the business impact of the delay (corrupted forecasts, wasted ad spend, strategic planning delays). The stakeholder doesn’t understand what the data team is actually building and why it takes time.</p><p>* <strong>Us vs Them Dynamic</strong>: The situation has devolved into adversarial positioning - “the data team won’t help me” versus “stakeholders want everything immediately” - rather than collaborative problem-solving.</p><p>The Solution Approach</p><p>Rather than a single technical fix, our discussion produced a multi-layered solution:</p><p><strong>Immediate Relief (Week 1-2)</strong>: Ask one of the engineers to build a simple Python script or similar automation. This doesn’t need to be production-grade infrastructure - just something that reliably pulls the CSV, does basic transformation, and loads it into the warehouse. This can be a 2-3 day task rather than a 4-month project.</p><p><strong>Transparency & Context (Week 2-3)</strong>: Create a visible initiative backlog overview showing everything the data team is working on. When someone says “it will take four months,” they should be able to show exactly what’s blocking it and why those other priorities matter more. This isn’t about justifying delays - it’s about enabling informed decisions.</p><p><strong>Rational Decision Framework (Week 3-4)</strong>: Develop a structured way to articulate both the cost of building solutions and the business impact of delays. Put numbers on the table: What does two hours of manual work daily cost? What’s the risk value of potential forecast errors? What’s the opportunity cost of the data team working on this versus their current priorities?</p><p><strong>Strategic Alignment (Ongoing)</strong>: Establish clear ownership and a prioritization process that considers both technical complexity and business impact. This isn’t about the data team gatekeeping or stakeholders demanding - it’s about having a framework where tradeoffs are visible and decisions are rational.</p><p>Key Takeaways</p><p>3 Critical Insights</p><p>* <strong>This is an Organizational Problem, Not a Technical One</strong>: The four-month timeline isn’t about technical complexity - it’s about priorities, communication, and organizational dynamics. The actual technical work of connecting to an API could be done much faster if approached as a quick automation rather than an enterprise-grade infrastructure.</p><p>* <strong>The “Us vs Them” Dynamic Is Killing Efficiency</strong>: When stakeholders and data teams position themselves as adversaries rather than collaborators, every interaction becomes a negotiation. The marketing person sees the data team as obstructionist; the data team sees stakeholders as demanding and unrealistic. Neither side wins in this dynamic, and the business suffers.</p><p>* <strong>Ownership Clarity Is Essential</strong>: Without clear ownership of prioritization decisions, every data request becomes contested territory. Someone needs to own the decision about whether a four-month wait is acceptable given the business impact, and that person needs visibility into both the technical constraints and business consequences.</p><p>4 Action Items</p><p><strong>For the Problem Submitter</strong> (and anyone in similar situations):</p><p>* <strong>Request a Quick Automation Script (This Week)</strong> - Ask a data engineer to build a simple Python script or similar automation that pulls the CSV, does basic transformation, and loads it into your warehouse. Make it clear this doesn’t need to be production-grade infrastructure - just something reliable enough to bridge the gap. Timeline: 2-3 days of engineering time.</p><p>* <strong>Create Initiative Backlog Visibility (Week 2)</strong> - Work with the data team to create a visible overview of all current initiatives. When told something will take four months, you should understand what’s blocking it and why those priorities were chosen. This isn’t about challenging their decisions - it’s about having context for informed discussion.</p><p>* <strong>Articulate Cost and Impact With Numbers (Week 3)</strong> - Document the actual business impact: two hours daily of manual work (cost it out by salary), risk of forecast errors (quantify the potential impact), strategic planning delays (what decisions are being made without this data?). Similarly, ask the data team to articulate what they’d need to deprioritize to tackle this sooner.</p><p>* <strong>Establish Ongoing Prioritization Framework (Week 4+)</strong> - Work with leadership to create a clear process for prioritizing data work that considers both technical complexity and business impact. Identify who owns these decisions and ensure they have visibility into both technical constraints and business consequences. This prevents future “four months” surprises.</p><p>Episode Highlights</p><p>* <strong>02:00</strong> - Problem reveal: Four months for a marketing platform connector</p><p>* <strong>06:30</strong> - Ilya’s immediate diagnosis: “This is a people problem, not a technical one”</p><p>* <strong>14:45</strong> - Post-reflection discussion: Unpacking the communication breakdown</p><p>* <strong>24:30</strong> - The ownership question: Who actually decides priorities?</p><p>* <strong>31:00</strong> - Quick wins vs long-term solutions: The Python script approach</p><p>* <strong>36:05</strong> - Did we break through? An honest assessment</p><p>The Honest Assessment</p><p>At the end of the episode, Ilya and I agreed: <strong>This wasn’t a breakthrough moment.</strong></p><p>As Ilya candidly put it: “If I had a silver bullet, a process, or an idea how to solve it in a company, I would probably not be here. I’d be a millionaire.”</p><p>This pattern - stakeholder requests taking months, manual workarounds creating risk, “us versus them” dynamics - happens constantly across companies of all sizes. It’s not easily solved because it’s deeply rooted in organizational structure, culture, and human nature.</p><p>What our episode provided wasn’t a magic solution but a structured framework for thinking about these conflicts:</p><p>* Separating immediate tactical relief from long-term strategic solutions</p><p>* Making tradeoffs visible rather than hidden</p><p>* Moving from adversarial positioning to collaborative problem-solving</p><p>* Establishing clear ownership and rational decision processes</p><p>The problem that was submitted - the manual CSV downloads - can likely be solved with a quick automation. But the deeper problem - the organizational dynamics that created a four-month timeline - requires more fundamental changes that depend heavily on company culture, team size, and leadership support.</p><p>Resources & Concepts Mentioned</p><p>* <strong>Python Automation Scripts</strong>: Simple scripts using libraries like pandas for CSV processing and database connectors (psycopg2, mysql-connector, etc.) for warehouse loading</p><p>* <strong>Backlog Transparency Tools</strong>: Project management platforms (Jira, Linear, etc.) configured for stakeholder visibility</p><p>* <strong>Prioritization Frameworks</strong>: Cost of delay, weighted shortest job first, RICE scoring (Reach, Impact, Confidence, Effort)</p><p>* <strong>Interim vs Enterprise Solutions</strong>: The concept of “good enough for now” automation versus production-grade infrastructure</p><p>Continue the Conversation</p><p>Submit Your Data Problem or Become a Guest</p><p>Visit our show website: </p><p>https://data-breakthroughs-podcast.cookingdata.blog/</p><p>Here you can:</p><p>* Submit your data challenge for a future episode</p><p>* Apply to be a guest</p><p>* See the latest episodes</p><p>* Explore past problems and solutions</p><p>Share Your Alternative Solution</p><p>Have you dealt with similar stakeholder-data team conflicts? How did you resolve them?</p><p>* Use <strong>#DataBreakthrough</strong> on social media</p><p>* Reply to this newsletter with your approach</p><p>Implementation Follow-up</p><p>If you try any of these approaches and they work (or don’t work), I’d love to hear about it. Real implementation stories help the entire community learn.</p><p>Season 1 Reflection</p><p>This episode marks the end of Data Breakthroughs Season 1. I started with Ilya in the pilot episode, and it felt only right to close the season with him returning. Throughout the season, I’ve seen a consistent theme: most data problems are actually people problems. Whether it’s pipeline reliability, customer definition alignment, ML deployment challenges, or dashboard governance, the technical aspects are rarely the core issue.</p><p>Thank you for being part of this first season. Your problem submissions, guest applications, and community engagement have made this possible.</p><p>About Data Breakthroughs</p><p>Data Breakthroughs brings together data practitioners to solve real operational challenges through collaborative problem-solving. Each episode features authentic, unscripted brainstorming sessions where neither the guest nor I sees the problem beforehand, creating genuine, real-time problem-solving moments.</p><p><strong>Host</strong>: Lior Barak</p><p>Credits</p><p><strong>Host & Producer</strong>: Lior Barak<strong>Guest</strong>: Ilya, Fractional Head of Data<strong>Music</strong>: “Calisson” courtesy of Riverside<strong>Season</strong>: 1, Episode 11 (Season Finale)</p><p><strong>Season 2 Preview</strong>: Coming late February 2026 with enhanced problem submission requirements, extended reflection breaks, and continued commitment to authentic, unscripted data problem-solving. Season 3 recording begins in April 2026 for a June 2026 release.</p><p>Disclaimer</p><p>This podcast is for inspiration and educational purposes. The solutions and approaches discussed are general frameworks meant to spark ideas and collaboration. Always adapt recommendations to your specific organizational context, constraints, and requirements. Not every problem has a breakthrough solution, and sometimes the most valuable outcome is understanding the complexity better.</p><p>Thanks for being part of Season 1. See you in late February 2026 for Season 2!</p> <br/><br/>Get full access to Cooking Data guided by Lior at <a href="https://cookingdata.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4">cookingdata.substack.com/subscribe</a>
December 10, 2025
Episode 10: When Data Meets Decades of Experience
<p><strong>Data Breakthroughs - Episode 10: When Data Meets Decades of Experience</strong></p><p>Real-world data problem solving in action! Tiankai Feng (Director of Data & AI Strategy at ThoughtWorks, author of "Humanizing Data Strategy" and "Humanizing AI Strategy") and host Lior Barak tackle a manufacturing company where plant managers with 20+ years of experience resist a modern data platform.</p><p><strong>Problem Category</strong>: Organizational Data Strategy / Change Management<strong>Runtime</strong>: 32 minutes</p><p><strong>The Challenge</strong>: A family-owned manufacturer invested heavily in data infrastructure, but plant managers still make decisions based on "what happened last time" and gut instincts, creating a divide between analytics teams and operations.</p><p><strong>The Solution</strong>: Transform data from replacement threat to support tool through co-creation, clear communication about expertise-data synergy, and defining decision-making rules with proper incentives.</p><p><strong>Key Takeaways</strong>:</p><p>Expertise vs. data is always a tension field - communicate how they work hand-in-hand, not against each other</p><p>People don't use things they didn't help create - co-creation is essential for adoption</p><p>Success metrics must reflect both short-term and long-term value to align incentives properly</p><p><strong>Guest</strong>: Tiankai Feng, Director of Data & AI Strategy at ThoughtWorks Author of "Humanizing Data Strategy" and "Humanizing AI Strategy" Connect: <a target="_blank" href="https://www.linkedin.com/in/tiankaifeng/">https://www.linkedin.com/in/tiankaifeng/</a></p><p><strong>Get Involved</strong>: Submit your data problem or Become a guest: <a target="_blank" href="https://data-breakthroughs-podcast.cookingdata.blog/">https://data-breakthroughs-podcast.cookingdata.blog/</a></p><p>Join the conversation: #DataBreakthrough</p><p><strong>Full show notes</strong>: <a target="_blank" href="https://data-breakthroughs-podcast.cookingdata.blog/">https://data-breakthroughs-podcast.cookingdata.blog/</a></p><p>Disclaimer: This podcast is for inspiration and educational purposes. Solutions discussed are general approaches - adapt them to your specific context and constraints.</p><p>Music: "Calisson" courtesy of Riverside</p> <br/><br/>Get full access to Cooking Data guided by Lior at <a href="https://cookingdata.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4">cookingdata.substack.com/subscribe</a>
November 26, 2025
Episode 09: When Analytics Becomes a Dashboard Factory
<p><strong>Data Breakthroughs - Episode 09: When Analytics Becomes a Dashboard Factory</strong></p><p>Real-world data problem solving in action! Eva Schreyer (Head of Data & Analytics at Neugelb/Commerzbank) and host Lior Barak tackle a community-submitted challenge about analytics overload for the first time during recording.</p><p><strong>Problem Category</strong>: Business Intelligence & Dashboarding / Organizational Data Strategy<strong>Runtime</strong>: 37 minutes</p><p><strong>The Challenge</strong>: A product team drowns in 40+ charts per report while struggling to make data-driven decisions, creating a disconnect between analytics investment and business value.</p><p><strong>The Solution</strong>: Transform from dashboard factory to strategic partner through executive alignment, monetizing requests, and prioritizing deep-dive analyses over generic reporting.</p><p><strong>Key Takeaways</strong>:</p><p>Too much data doesn't mean good decisions-relevance matters more than volume</p><p>Making stakeholders understand the cost of requests (in time/effort) dramatically improves prioritization</p><p>Ask "what will you do differently when this metric changes?" to identify truly actionable insights</p><p><strong>Guest</strong>: Eva Schreyer, Head of Data & Analytics at Neugelb (Commerzbank) Connect: <a target="_blank" href="https://www.linkedin.com/in/eva-schreyer/">https://www.linkedin.com/in/eva-schreyer/</a></p><p><strong>Get Involved</strong>: Submit your data problem: <a target="_blank" href="https://data-breakthroughs-podcast.cookingdata.blog/">https://data-breakthroughs-podcast.cookingdata.blog/</a> Become a guest: <a target="_blank" href="https://data-breakthroughs-podcast.cookingdata.blog/">https://data-breakthroughs-podcast.cookingdata.blog/</a> Join the conversation: #DataBreakthrough</p><p><strong>Full show notes & visual diagrams</strong>: <a target="_blank" href="https://data-breakthroughs-podcast.cookingdata.blog/">https://data-breakthroughs-podcast.cookingdata.blog/</a></p><p>Disclaimer: This podcast is for inspiration and educational purposes. Solutions discussed are general approaches - adapt them to your specific context and constraints.</p><p>Music: "Calisson" courtesy of Riverside</p> <br/><br/>Get full access to Cooking Data guided by Lior at <a href="https://cookingdata.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4">cookingdata.substack.com/subscribe</a>
14 total episodes available
Recent guests on Data Breakthroughs: Solving Real-World Data Challenges
Guests from recent episodes — sign up to see every guest that has ever appeared on this show.
Ilya Vladimirskiy
Guest
Deep-dive analytics for Data Breakthroughs: Solving Real-World Data Challenges
Frequently asked questions
Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.
- What is Data Breakthroughs: Solving Real-World Data Challenges?
- How often does this podcast release new episodes?
This podcast updates daily.
- Where can I listen to this podcast?
This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
- Does this podcast accept guests?
Yes, this podcast regularly features guests.
Legal Disclaimer
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.