<?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 Ahmed Elsamadisi on Medium]]></title>
        <description><![CDATA[Stories by Ahmed Elsamadisi on Medium]]></description>
        <link>https://medium.com/@ahmedelsamadisi?source=rss-bb2bab566765------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EQjebnIxOMcNvwVc-XsMww.jpeg</url>
            <title>Stories by Ahmed Elsamadisi on Medium</title>
            <link>https://medium.com/@ahmedelsamadisi?source=rss-bb2bab566765------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:13:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ahmedelsamadisi/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[Using customer behavior to drive better product decisions]]></title>
            <link>https://medium.com/narrator-ai/using-customer-behavior-to-drive-better-product-decisions-75e44145fc79?source=rss-bb2bab566765------2</link>
            <guid isPermaLink="false">https://medium.com/p/75e44145fc79</guid>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ab-testing]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[questions]]></category>
            <dc:creator><![CDATA[Ahmed Elsamadisi]]></dc:creator>
            <pubDate>Tue, 15 Dec 2020 15:17:58 GMT</pubDate>
            <atom:updated>2020-12-15T16:10:00.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6zgWoQdk2ieliISkOgrnGg.jpeg" /></figure><h3>Understanding which customer behaviors lead to conversion is the fastest way to know which product changes to make.</h3><p>As a data person, I frequently get asked for help from product teams. Over the years, I spent quite a bit of time explaining the difference between good and bad questions.</p><p>Typically product teams want to improve something (say conversion). They’ll come to me for advice on what to measure —and nearly all the time they want to discover which<strong> product </strong>changes<strong> </strong>will have an impact<strong> </strong>on their metric.</p><p>“I want to know whether X matters so I’ll split my audience, test the product change, and see if it makes an impact”.</p><p>Notice that this question is from a product perspective: ‘did a product change have an impact?’, instead of a customer perspective: ‘which customer behavior leads to conversion?’</p><p>I know this sounds like such a small nuance, but it’s often the root cause why product teams launch features that don’t increase conversion.</p><p><strong>Here are some common questions from the product perspective:</strong></p><ul><li>I want to see if <strong>when we launch a class</strong> affects the number of people who sign up. We’ll launch the same class to half our audience at 4 pm and the other half at 5 pm. Then we’ll see how the different cohorts react.</li><li>I want to test <strong>which email messaging </strong>leads to more sales. I’ll split the audience in half, send each a different email, and see how many of them purchase.</li></ul><p>The problem with these that there is no causality. If we want to increase a customer metric (like conversion), we have to ask a question about customer behavior.</p><p>Let’s look at the first example to illustrate.</p><p>“I want to see if <strong>when we launch a class</strong> affects the number of people who sign up.</p><p>Launching a class doesn’t affect customers at all. Why not? Because nothing has happened to the customer. Do they know you launched a class? If you sent a notification did they see that notification? There’s no direct connection between ‘launching’ and user behavior.</p><p>If there’s no direct connection it’s not causal — in other words, if you ‘improve’ the time at which you launch a class time you will probably not increase conversion.</p><p>Let’s try something more direct: “How does the time of day of <strong>viewing a class </strong>affect the customer likelihood to sign up for that class?”</p><p>‘Viewed a class’ is definitely a customer action. And this is a far better question for two reasons</p><ol><li>we don’t need to run an A/B test at all to answer this question. We already have this data (because customers have already viewed classes at different times) and can start answering it immediately</li><li>if we conclude that the time to view a class matters, we now have a concrete action to take (try to get more customers to view a class at X time).</li></ol><p>The question of HOW to get customers to view classes at a more optimal time is a great product question, and its progress is very easy to measure.</p><p>The approach now is straightforward. Once you know the best time for customers to view a class, you can measure the change in the percent of customers viewing the class at this time.</p><ol><li>Create a metric by dividing customers into buckets based on the time they’ve viewed a class. (20% of customers viewed at 10:00 AM, 15% at 11:00 AM …)</li><li>Make some product changes to shift the percentage of customers in each bucket to the desired one.</li><li>As the percentages change, look at the overall conversion rate again. It should increase.</li></ol><p>What about the other question?</p><p>“I want to test which email messaging leads to more sales. I’ll split the audience in half, send each a different email, and see how many of them purchase.”</p><p>The customer doesn’t care about <strong>receiving</strong> an email. It could be marked as spam or bounce, or not be noticed in many other ways.</p><p>So what’s a good customer action?</p><p>“How does <strong>opening</strong> email A vs opening email B affect the likelihood to purchase within 30 minutes?”</p><p>One primary reason I get these types of questions is that product facing things are easier to control. You can’t control exactly when a customer views a class, but you can control when you launch it to the website.</p><h3>The entire point of product questions is to understand which product changes will increase conversion. By re-framing questions from the customer’s perspective, you’ll understand which customer behaviors matter. You’ll now be solving a much simpler problem: how can I change the product to affect a specific customer behavior?</h3><p>What can I do about it?</p><p>These mistakes are natural in a data-driven org. Part of the reason I co-founded Narrator was to counteract this — our data system is designed to only ask questions from the customer’s perspective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75e44145fc79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narrator-ai/using-customer-behavior-to-drive-better-product-decisions-75e44145fc79">Using customer behavior to drive better product decisions</a> was originally published in <a href="https://medium.com/narrator-ai">Narrator</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL Hack: How to join tables where the key is in a blob of text?]]></title>
            <link>https://medium.com/narrator-ai/sql-hack-how-to-join-tables-where-the-key-is-in-a-blob-of-text-4c74fcc2cb39?source=rss-bb2bab566765------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c74fcc2cb39</guid>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[hacks]]></category>
            <dc:creator><![CDATA[Ahmed Elsamadisi]]></dc:creator>
            <pubDate>Wed, 16 Sep 2020 18:28:27 GMT</pubDate>
            <atom:updated>2021-03-22T19:48:54.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MoJB44t81Y8EY_KQpmcTwg.png" /></figure><h3>SQL Hack: How to join tables when the key is buried in a blob of text</h3><h3>The Situation</h3><p>Text blobs are a pain, but they are commonly used with data from email platforms, Salesforce, or dynamic UTMs. In these cases, the JOIN key is probably hidden in a blob of text.</p><p>For example, say you want to join your users table using the user_id from the Salesforce notes column. But the notes data looks like this…</p><p><strong>Notes Column:<br></strong>Ahmed (user_id: 1f65e898-0f67-4d34-8ac3-ae223bb71a79) called us today</p><h3>First Attempt: Regex Parsing</h3><p>Initially, you can try to use regex to parse the user_id out of the value column. This is always annoying but can get close.</p><p>If it works, then a simple subquery and join should do the trick. However, like any free text column, the regex may not work perfectly.</p><p>Regex can be risky when the structure of the data changes:</p><p><strong>Notes Column:<br></strong>Ahmed (user: 1f65e898-0f67-4d34-8ac3-ae223bb71a79)<br>(r<em>eferences “user” not “user_id”)</em></p><p>When regex doesn’t work, use this hack…</p><h3>Solution: Use the &quot;ilike&quot; SQL hack</h3><p>Use an ilike to JOIN data by creating a dynamic key:</p><pre>SELECT <br>	...</pre><pre>FROM some_table a.    -- structured data</pre><pre>JOIN other_table b    -- data with the text blob<br>	ON ( a.column ilike &#39;%&#39; || b.other_column || &#39;%&#39;)</pre><p>This can be a handy trick if you’re in a pinch, but it can also be slow, so use it with caution. And watch out for unwanted duplication in your JOIN if the “ilike” matches more than once!</p><p>Good Luck!</p><p><em>Originally published at </em><a href="https://www.narrator.ai/blog/sql-hack-how-to-join-tables-when-the-key-is-buried-in-a-blob-of-text/"><em>https://www.narrator.ai/blog</em></a><em> on September 16, 2020</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c74fcc2cb39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narrator-ai/sql-hack-how-to-join-tables-where-the-key-is-in-a-blob-of-text-4c74fcc2cb39">SQL Hack: How to join tables where the key is in a blob of text?</a> was originally published in <a href="https://medium.com/narrator-ai">Narrator</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL Hack: How to get first value based on a time column without JOIN or Window Function?]]></title>
            <link>https://medium.com/narrator-ai/sql-hack-how-to-get-first-value-based-on-a-time-column-without-join-or-window-function-41eae3708c19?source=rss-bb2bab566765------2</link>
            <guid isPermaLink="false">https://medium.com/p/41eae3708c19</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Ahmed Elsamadisi]]></dc:creator>
            <pubDate>Wed, 09 Sep 2020 17:06:55 GMT</pubDate>
            <atom:updated>2020-09-09T17:06:55.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4ToBCSWJNA4A8EnrFk0VQ.png" /></figure><h3>SQL Hack: How to get first value based on time without a JOIN or a Window Function?</h3><p>This is my favorite trick in SQL!</p><p>If you are like me and have been working with data for a while, you have googled “how to get the first value without a join or window function” multiple times in your life. We often hate having to write complex queries to get a seemingly simple answer.</p><h3>For example, you want to answer questions like…</h3><ol><li>Give me the first coupon code the customer used</li><li>Give me the last page a customer visited</li><li>Give me the first invoice amount for the customer</li></ol><h3>Common ways of answering these questions</h3><ul><li>self JOIN on the MIN(timestamp)</li><li>use a ROW_NUMBER() window function</li><li>use FIRST_VALUE() window function</li></ul><p>…Yuck. These approaches are slow and messy. 😩</p><p><strong>Problems with these approaches…</strong></p><ul><li>SQL query gets really long with multiple sub-queries or CTEs (Common Table Expressions)</li><li>self JOINs and window functions are slow</li></ul><h3>The BETTER and FASTER WAY</h3><p>In my day job at <a href="http://www.narrator.ai/">Narrator</a>, I have to auto-generate complex queries, meaning that I have to get the first value of multiple columns at the same time.</p><p><strong>If the columns were timestamps then this would be EASY</strong></p><p>If you had a list of timestamps and you want the first one (based on the timestamp), this would not be a problem since you can just use MIN.</p><p>You can do a bunch of these in the same query SELECT and be done.</p><pre>SELECT</pre><pre>   [Group Columns],<br>   <br>   MIN( [Time Column]) as first_value,<br>   MAX( [Time Column]) as last_value</pre><pre>FROM table<br>GROUP by [Group Columns]</pre><p><strong>What if it’s not a timestamp?</strong></p><p>We still take the MIN (or MAX) of the timestamp column, but we do a neat trick to bring along the actual column value we want with it.</p><pre>SELECT</pre><pre>[Group Columns],</pre><pre>LTRIM(MIN(CONCAT([TIME COLUMN]),{value_column})), [TIME COLUMN]) AS first_value</pre><pre>FROM table<br>GROUP by [Group Columns]</pre><p>This takes advantage of MIN/MAX and GROUP BY so you don’t have to JOIN or use a window function! I think this is faster, simpler, and cleaner to read than other methods.</p><p><strong>Why does this work?</strong></p><p>We concatenate the timestamp with the value of the column we’re looking for. After the warehouse does a normal MIN / MAX on that string we can remove the timestamp, leaving us with the data we want.</p><p><strong>PROS</strong></p><ol><li>Fast!</li><li>Works inline (doesn’t require CTEs or self JOINs)</li><li>Works with GROUP BY</li></ol><p><strong>CONS</strong></p><ol><li>Kind of annoying to type</li></ol><h3>How it works</h3><p>Let’s assume you have an orders table and you want to find the timestamp of the first order based on category.</p><pre>SELECT <br>    <br>   category,<br>   min(completed_at) as first_order_at</pre><pre>FROM orders<br>group by </pre><p>Now, what if you want the name of that order?</p><p>Well, the trick is to Concat the name to the timestamp then compute the MIN then remove the timestamp.</p><p>The SQL:</p><pre>LTRIM(MIN(CONCAT(completed_at), name)),MIN(completed_at))</pre><p>1. Concatenate the timestamp and the column you want to find the first value for</p><p>CONCAT(completed_at, name)</p><p>This returns the following rows:</p><pre>2018-01-01T01:48:02The Best Name</pre><pre>2018-01-01T02:12:06Some Name</pre><p>2. Find the MIN of that string (the timestamp is at the beginning of the string so it will grab the <em>first</em> value)</p><p>MIN(CONCAT(completed_at, name))</p><p>This returns the following rows:</p><pre>2018-01-01T01:48:02The Best Name</pre><p>4. Remove the Timestamp from the result</p><pre>LTRIM(MIN(CONCAT(completed_at, name)), MIN(completed_at))</pre><p>This returns the following rows:</p><pre>The Best Name</pre><p>Note that LTRIM, when given a string as a second argument, will remove that string from the front of its first argument.</p><p>DONE!</p><p>To handle NULL values, use the query below</p><pre>NULLIF(LTRIM(MIN(CONCAT({time_column}), NVL({value_column},&#39;&#39;)), MIN({time_column}) ,&#39;&#39;)</pre><p>Here is the EXACT one I use (at <a href="https://www.narrator.ai/">Narrator</a>). It’s a bit uglier but a bit more efficient (saves an aggregation)</p><pre>NULLIF(SUBSTRING(MIN(CONCAT(DATE_TRUNC(&#39;second&#39;, {time_column}), NVL({value_column},&#39;&#39;))),20, 1000),&#39;&#39;)&quot;</pre><p>I hope you find this as helpful as I did! I have been doing data science for a while and love finding new hacks to make complex data tasks easier. These tricks really come in handy when dealing with event-based data (which is the structure of the data we use at the company I founded — <a href="http://narrator.ai/">Narrator.ai</a>).</p><p><strong>Do you have SQL tricks? Share them here! I’d love to hear them.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41eae3708c19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narrator-ai/sql-hack-how-to-get-first-value-based-on-a-time-column-without-join-or-window-function-41eae3708c19">SQL Hack: How to get first value based on a time column without JOIN or Window Function?</a> was originally published in <a href="https://medium.com/narrator-ai">Narrator</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 Signs you have a Data Modeling problem]]></title>
            <link>https://medium.com/narrator-ai/top-10-signs-you-have-a-data-modeling-problem-bf7a35d83122?source=rss-bb2bab566765------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf7a35d83122</guid>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Ahmed Elsamadisi]]></dc:creator>
            <pubDate>Tue, 08 Sep 2020 12:25:54 GMT</pubDate>
            <atom:updated>2021-03-22T22:20:58.422Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-eDr6-jHvmk-gFxDj5OHnw.png" /></figure><h3>Top 10 Signs You Have a Data Modeling Problem</h3><p><em>This post was originally published on </em><a href="https://www.narrator.ai/blog/top-10-signs-you-have-a-data-modeling-problem/"><em>Narrator.ai </em></a><em>on September 8, 2020</em></p><h3>1. Your warehouse is really slow</h3><p><strong>Situation</strong></p><blockquote>“I just hit Run Query. I am going to get a cup of coffee and hopefully it’s done when I get back.”<br> — Data Analyst</blockquote><p><strong>Problem</strong></p><ul><li>Every time a transformation runs in your warehouse, it drops and recreates every table, thus processing time only grows.</li><li>Table locks can add up, causing your table to need to be reprocessed before it can be used.</li></ul><h3>2. You have changed your BI tool multiple times</h3><p><strong>Situation</strong></p><blockquote>“We just invested in Looker and it will solve all of our problems. So far everything is really fast and matches, unlike Chartio which was slow and nothing matched.” <br>— BI Team</blockquote><p>6 months later…</p><blockquote>“I don’t know why Looker is super slow and none of the metrics match. I think Tableau Online solves this problem really well” — BI Team</blockquote><p><strong>Problem</strong></p><ul><li>Only a subset of data models make it into your BI tool when it’s first implemented. Then, as time goes on, you require more data models as your business evolves, and soon you’ve recreated all the issues that you experienced with your last BI tool. It’s slow and there are inconsistencies in metrics.</li><li>BI tools have to query your warehouse and cache the results of those queries. If a BI tool is accessing a query with multiple tables, but some of those tables still need to update, then it will cache the wrong results. This will also give you inconsistent metrics across dashboards.</li></ul><h3>3. Your transformations are more than 30 lines</h3><p><strong>Situation</strong></p><blockquote>“I just need to add sales_location to this table but the SQL (and python, sometimes) to generate it is literally 1200 lines. I will just create a new table with a cleaner query.&quot;<br> — Data Engineer</blockquote><p><strong>Problem</strong></p><ul><li>Each query needs to bridge multiple sources — and because foreign keys are often missing — you write insane sub queries to try to get a clean join. This leads to queries that are really long and complicated.</li><li>With complexity comes lack of understanding and so when something needs to change, your team will elect to either: (1) rewrite the data model with only what they need or (2) wrap the entire query in a CTE (Common Table Expression) and add to the query, increasing the length of the query and its complexity.</li></ul><h3>4. Reporting takes too long to set up</h3><p><strong>Situation</strong></p><blockquote>“I just spent my whole day debugging the sales_data table and I’m pretty sure the query is actually wrong.&quot; <br> — Data Analyst</blockquote><blockquote>“Oh yeah, you should use sales_data_v2.” <br> — Data Engineer</blockquote><blockquote>“What? Why do we still have sales_data then?&quot; <br> — Data Analyst</blockquote><blockquote>“Some dashboard depends on it and we can’t deprecate it because it is used by executives”<br> — Data Engineer</blockquote><p><strong>Problem</strong></p><ul><li>Every reporting request requires a long process to find the right data, validate it, and then assemble the visualization.</li><li>Finding, validating, and assembling the data is what takes forever. Your BI Engineer or Analyst has to parse 1000+ line SQL queries and run sanity checks to compare your aggregations with widely used dashboards.</li><li>As your data models evolve, you often don’t delete older data models because some executive (or stubborn person) at your company depends on it for a dashboard and you’re nervous about migrating it. This leads to weeks of wasted work of re-debugging a table that someone already knew was wrong.</li></ul><h3>5. Data engineering has an endless backlog</h3><p><strong>Situation</strong></p><blockquote>“We are currently blocked by Data Engineering.” <br>— Analytics Team</blockquote><p><strong>Problem</strong></p><ul><li>As more requests come in each Data Engineer has to make a very complex decision: build a new data model or update an old model. Creating a new model adds another model to maintain for life. Updating a model means queries get insanely long or introduces a bug that leads to broken dashboards or numbers not matching.</li></ul><h3>6. Dashboards have numbers that don’t match</h3><p><strong>Situation</strong></p><blockquote>“Why does the Sales Dashboard say we have 12,034 sales but when I calculate the sum of sales in Sales by Ad Source dashboard, I see 13,193. The data is wrong.” <br>— Marketing Team</blockquote><p><strong>Problem</strong></p><ul><li>Dashboards visualize your data models. If numbers don’t match in a dashboard, it’s an issue with your data model. If you have multiple data models with similar data then you’ll end up with two dashboards using two different data models but computing the same metrics.</li><li>This leads to two sources of truth for one metric.</li></ul><h3>7. No one knows where to find the data they need</h3><p><strong>Situation</strong></p><blockquote>“Why don’t you use the data dictionary?”<br> — Data Engineer</blockquote><blockquote>“It’s out of date so I just look at the transformation SQL” <br>— Data Analyst.</blockquote><p><strong>Problem</strong></p><ul><li>Data Dictionaries are practically impossible to maintain so they go out of date the moment they are deployed. Automated Data Dictionaries usually just tell you the column names and types, but not the assumptions made.</li><li>As soon as one table’s documentation is out of date, the data team will know that they cannot depend on the documentation so they will go back to the method they can trust — parsing the complex SQL transformations.</li></ul><h3>8. The data team is not trusted</h3><p><strong>Situation</strong></p><blockquote>“The data is always wrong” <br>— Stakeholder</blockquote><p><strong>Problem</strong></p><ul><li>With complex data models, even simple data tasks are complicated, risky, and error-prone. Stakeholders only see the data integrity issues when asking “simple” questions and stop believing in the team’s ability to answer more questions.</li><li>Data integrity issues lead to a mistrust in the data team.</li></ul><h3>9. Other teams are buying their own data tools to do their own analyses</h3><p><strong>Situation</strong></p><blockquote>“We set up Heap so we could do our own analytics.” <br>— Website Team</blockquote><p><strong>Problem</strong></p><ul><li>Engineering teams are constantly told that they don’t need data analysts or to do analyses. They’ve been told that these point and click tools can replace the need for data teams. THIS IS NOT TRUE!</li><li>Data teams now have to do twice the work: re-do the analysis and then educate the team on why the numbers they pulled are different than the numbers the data team got.</li></ul><h3>10. You’re constantly explaining why “simple” questions are more complex than they seem</h3><p><strong>Situation</strong></p><blockquote>“Well, figuring out how many people called us from the website is really hard.” <br>— Data Analyst</blockquote><blockquote>“Why? People come to the site then call us. I just want to know the % of people. Why is this complicated?”<br> — Stakeholder</blockquote><p><strong>Problem</strong></p><ul><li>Simple questions become very complex when they bridge data systems because foreign keys are usually not available.</li><li>Even if we could relate the data, there are many dimensions to each question, so a data analyst needs to consider all the edge cases before answering. Each edge case takes hours to test and, as a stakeholder, it is hard to see the rigor that goes into answering a simple question.</li></ul><p>My talk about answering data questions goes into a bit more depth about this: <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwjS7PaPsMPrAhUDVt8KHXs5CTkQwqsBMAF6BAgLEAQ&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGWPzsVOThWA&amp;usg=AOvVaw3vqXxsQnor8dh5qLhAXi5q">How to Answer Data Questions Without Being Miserable</a></p><h3>So you have a data modeling problem. Where should you go from here?</h3><p>It is not your fault! You’re probably using a <a href="https://medium.com/narrator-ai/star-schema-is-set-up-for-failure-f5e0bdfba189">Star Schema</a> and that is the status quo “best practice” so you think these problems are simply the nature of the beast. We have good news for you — they’re not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C6fBvMQBjKlq0V0S6NRNiQ.jpeg" /></figure><p>There is a better way.</p><p>Check out Narrator: After suffering through these same problems, we came up with a data model that reflects today’s reality. It is a single, 11-column data model that can be used to assemble any table.</p><p>See for yourself: <a href="https://www.narrator.ai/">Narrator.ai</a></p><p><strong>What are other problems you’ve experienced working with data? Could they be caused by bad data modeling?</strong></p><p>Comment with your problems and we can help you identify the problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf7a35d83122" width="1" height="1" alt=""><hr><p><a href="https://medium.com/narrator-ai/top-10-signs-you-have-a-data-modeling-problem-bf7a35d83122">Top 10 Signs you have a Data Modeling problem</a> was originally published in <a href="https://medium.com/narrator-ai">Narrator</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>