<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Liran Cohen on Medium]]></title>
        <description><![CDATA[Stories by Liran Cohen on Medium]]></description>
        <link>https://medium.com/@lirco?source=rss-dedd0093a82d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CAhyi_rA6QkT5kFHLnrFow.png</url>
            <title>Stories by Liran Cohen on Medium</title>
            <link>https://medium.com/@lirco?source=rss-dedd0093a82d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:46:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lirco/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Data Team’s Challenges]]></title>
            <link>https://lirco.medium.com/the-data-teams-challenges-f13962630ca2?source=rss-dedd0093a82d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f13962630ca2</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-developer]]></category>
            <category><![CDATA[data-development]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[data-analytics]]></category>
            <dc:creator><![CDATA[Liran Cohen]]></dc:creator>
            <pubDate>Thu, 18 Mar 2021 12:48:56 GMT</pubDate>
            <atom:updated>2021-03-21T15:18:21.654Z</atom:updated>
            <content:encoded><![CDATA[<h4>Breaking down what’s broken</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7oonnMrjgoiVPaZeejYFmg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@danielaiphoto?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daniela Izotenko</a> on <a href="https://medium.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>If you engage with analytics data at your organization, and especially if you are a member of a data team — this post is for you.</p><h4>Context — Who we are</h4><p>We are a group of data experts and software development managers on a mission - <em>to help data teams thrive</em>.<br>In order to make data great again, we decided not to jump right into solutions. We believe that partnering with data industry leaders and sharing the challenges - is the ultimate first step in order to make the change. Together.<br>If you’re interested in taking part of that change, read on!</p><h4>Putting it into context — The Common Data Analytics Pipeline</h4><p>Breaking it down, there are three main areas on a data pipeline</p><ol><li><strong>Raw data</strong><br>Thanks to low costs on cloud storage, companies now keep all the data they can get, at its raw format (stored on Data Lakes). <br>Raw data can be either structured or unstructured data of any kind, such as BI events with a predefined schema or json files storing some entity state, etc.</li><li><strong>Data transformations</strong><br>Running raw data through data processes (ETL/ELT) that clean, enrich and transform it, giving business context to the data (we will can the result of these transformations a “Data Warehouse”/”DWH”).</li><li><strong>Data analysis<br></strong>On top of the DWH, data teams build data products such as dashboards, and perform deep analysis, to deliver data driven insights</li></ol><h4>The Data Team — Key Concepts</h4><p>Data teams are the engine behind data driven organizations, enabling people in the organization make better decisions, based on data</p><p><strong>Key concepts in order to connect people with data<br></strong>We think of data teams as producers of data products inside their organizations. And a great data products, most basically needs to have the next features:</p><ul><li><strong>Short cycles</strong> to get data insights<br>Fast feedback for user engagement, in our case business parners who ask for analytical insights</li><li>Data should be <strong>reliable<br></strong>Data insights is worthless if it’s wrong / not reliable</li><li>Data products should be <strong>proactive</strong> <br>Ideally, data products should let us know what happens before we manually or by coincidence find it — probably too late</li></ul><h4>The Reality</h4><p>In reality, we are far from the speed and reliability we desire to achieve. <br>In many cases, it takes too long waiting for insights and data has frequent reliability issues.</p><p><strong>Long time to insight<br></strong>Industry researchers talk about 3 weeks on average waiting for analysis.<br>Data is locked behind super-busy data teams and data insights are inaccessible in many cases.</p><p><strong>Poor data reliability<br></strong>Resolving data integrity issues consume 50% of the data team’s time.<br>Too frequently we encounter data reliability issues, and most commonly these issues are being found too late and time costly to fix</p><h4>The Gaps We Need To Address</h4><p>The big question here is, as in many cases — why?</p><ul><li>Why does it take so long to get data insights?</li><li>Why do we frequently face data reliability issues?</li></ul><p>Breaking down the causes for poor data velocity and poor data reliability by looking at the pipeline, each area has challenges:</p><ol><li><strong>Input data breaks<br></strong>Raw data, and generally input tables, often change unexpectedly — and break predefined assumptions.<br>Changes revealed too late cause pipeline crashes, reliability issues and even data losses.</li><li><strong>Painful pipeline maintenance<br></strong>Manual data quality checks, assumptions that constantly break, logic errors and scalability issues result in long and painful cycles of development for data<em> </em>transformations</li><li><strong>Static dashboards<br></strong>Using dashboards as main data analysis tool, we commonly identify KPI changes long after they happen. And manually finding the root cause takes days</li></ol><h4>We Need Better Data Management Tools</h4><p>Analysis velocity and data reliability problems are all over the industry — Data teams all across the industry struggle with similar problems.<br>Struggling with these issues of velocity and reliability of data is the reality data teams and their clients are facing on a daily basis, and the vastness of such problems across the industry, point out that there is a huge gap — <br><strong>We are lacking the right tools for data management.</strong></p><h4><strong>You can make a change</strong></h4><p>Partner with us on the journey to help data teams thrive.</p><p>If you’re at the data ecosystem, and interested engaging with us, we’d love to hear from you and share challenges, thoughts and ideas.<br>You can contact me directly at lirco.data@gmail.com (would love to hear from you!) or comment here below :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f13962630ca2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>