<?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[Pragmatic Data Scientists - Medium]]></title>
        <description><![CDATA[Pragmatic Data Scientists is a publication that aims to bring insights, tips, and guidance, to the data science field. - Medium]]></description>
        <link>https://medium.com/pragmatic-data-scientists?source=rss----a85444f66147---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Pragmatic Data Scientists - Medium</title>
            <link>https://medium.com/pragmatic-data-scientists?source=rss----a85444f66147---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:53:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/pragmatic-data-scientists" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Black Swan events and the myth of predictability: A chat with Sid and YZ]]></title>
            <link>https://medium.com/pragmatic-data-scientists/black-swan-events-and-the-myth-of-predictability-a-chat-with-sid-and-yz-de692a51ae0f?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/de692a51ae0f</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[black-swan-events]]></category>
            <category><![CDATA[intuition]]></category>
            <dc:creator><![CDATA[Jack Virag]]></dc:creator>
            <pubDate>Thu, 26 Oct 2023 18:32:00 GMT</pubDate>
            <atom:updated>2023-10-26T18:32:00.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="a black swan with green swirls and flames around it" src="https://cdn-images-1.medium.com/max/1024/1*ODAJ0yoVOSdHqqSGRqUreQ.png" /></figure><p>In a recent YouTube discussion between Sid and YZ, the duo delved deep into the complexities and intricacies of decision-making in data-driven environments.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpTMZObpWeSk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpTMZObpWeSk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpTMZObpWeSk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c5f53cd6d4c14e450c09d7bc6b9483ce/href">https://medium.com/media/c5f53cd6d4c14e450c09d7bc6b9483ce/href</a></iframe><h4>Sid’s recent MBA insights:</h4><p>Fresh from completing his MBA at USC, Sid highlighted some prevalent misconceptions about data-driven decision-making.</p><p>He remarks that the over-reliance on historical data to predict the future often leads to costly mistakes, especially in the realm of finance.</p><h3>The Thanksgiving turkey paradox:</h3><p>Sid introduced a compelling concept he discovered in Nassim Taleb’s “The Black Swan”—the Thanksgiving turkeyParadox.</p><p>In short, a turkey, raised for Thanksgiving, believes humans care for it, seeing as its life is comfortable and it’s well-fed. This perception strengthens daily until, suddenly and unexpectedly, it is slaughtered for the holiday feast.</p><p>This story illustrates the dangers of making assumptions based on limited historical data.</p><h4>Real-life Black Swan events:</h4><p>Black Swan events, as Sid explains, are unpredictable and extreme events that can cause significant impact.</p><p>Examples include terrorist attacks, the financial crisis of 2007, or even the rise of disruptive technologies like the internet in the late ’90s. These events often catch people and businesses off guard, especially if decisions are made based solely on historical data.</p><h3>The mediocristan vs. extremistan:</h3><p>Sid also introduced two contrasting realms of problems as discussed in “The Black Swan.” The <em>Mediocristan World</em> is where extreme outliers don’t significantly impact the mean, like heights or weights. On the other hand, <em>Extremistan</em> represents problems where outliers, like the wealth of billionaires, can drastically skew results.</p><h3>Investing and the power of extreme days:</h3><p>Sid presented a revealing study by the Bank of America, which analyzed the returns of the S&amp;P 500 from 1930 to 2020. The study showcased the outsized impact of a few extreme days in the stock market on overall returns.</p><p>Missing the ten best days each decade could plummet returns from 17,000% to a mere 28%.</p><h4>The takeaway: Diversification and accepting unpredictability</h4><p>Sid’s and YZ’s discussion underscored the importance of diversification in investments, decision-making, and life in general.</p><p>Rather than putting all efforts into predicting that elusive 1% event, it might be wiser to spread out one’s bets. This way, one can ride the wave of unpredictability and possibly benefit from those rare, high-impact tail events.</p><p>This conversation between Sid and YZ is a gentle reminder of the inherent uncertainties in life. Instead of getting caught up in the chase to predict the unpredictable, perhaps it’s more fruitful to diversify, be adaptive, and learn from the ever-evolving tapestry of experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de692a51ae0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/black-swan-events-and-the-myth-of-predictability-a-chat-with-sid-and-yz-de692a51ae0f">Black Swan events and the myth of predictability: A chat with Sid and YZ</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is aha moment wrong?]]></title>
            <link>https://medium.com/pragmatic-data-scientists/why-is-aha-moment-wrong-ed96ae493a01?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed96ae493a01</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Yuzheng Sun]]></dc:creator>
            <pubDate>Wed, 04 Oct 2023 23:36:28 GMT</pubDate>
            <atom:updated>2023-10-05T20:30:30.629Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gcjQzpE5eYOhm8CJFMKkig.png" /></figure><p>In the realm of product growth, the concept of ‘Aha Moments’ has gained significant traction. Inspired by notable examples from Facebook and Dropbox, professionals have come to identify these moments as the pivotal junctures in a user’s journey with a product. It’s the instant they comprehend the product’s value proposition. For instance, Facebook’s aha moment occurs when users connect with more than seven friends, making them realize its potential as a connectivity tool.</p><p>Aha moments are appealing because they represent a harmonious blend of quantitative and qualitative insights into user behavior. These events can be delineated and monitored on dashboards, allowing teams to channel resources into amplifying these moments. However, a critical oversight exists in this approach.</p><h3>The Issue with Aha Moments</h3><p>The common belief is that aha moments catalyze users to transition from being passive to active. This assumption justifies the vast resources dedicated to promoting such moments. The presumption is simple: expose users to these moments, and they’ll shift from passivity to activity.</p><p>But, more often than not, this isn’t the case. Active users experience these aha moments primarily because they’re already engaged. For instance, individuals predisposed to using Facebook will inevitably connect with friends quicker. This correlation extends to monetization. Users who exhibit certain behaviors might seem more inclined to become paid users. In reality, those with a higher intent to pay often demonstrate these purchase indicators from the outset.</p><p>Therefore, resources invested in fostering these moments might not yield the anticipated ROI. Essentially, businesses might merely be targeting users already predisposed to engagement, inundating them with notifications, marketing tactics, and incentives. This doesn’t genuinely add substantial value to the business.</p><h3>The Inherent Flaws</h3><p>Two inherent problems make this mistake nearly unavoidable:</p><ol><li><strong>They are users’ choice:</strong> These moments are essentially user behaviors, stemming from user choices laden with latent variables. One dominant latent variable is the user’s inherent inclination to be active. Hence, high-intent users will naturally gravitate towards these moments, while their low-intent counterparts might not.</li><li><strong>High Correlation with Desired Outcomes:</strong> A strong correlation usually exists between aha moments and the desired user activity. Given that these moments arise from active user choices, an endogeneity issue arises, making it challenging to establish a definitive causal relationship.</li></ol><h3>Rethinking the Approach</h3><p>Given this knowledge, how should businesses proceed?</p><ol><li><strong>Use Aha Moments as the proxies they are</strong>: Accept aha moments for what they truly are — indicators of user intent. They can serve as early signals of a user’s potential activity or inclination towards monetization. When viewed as indicators or predictors, these moments retain their utility. For instance, they can be employed to train machine learning models, allowing them to achieve scale sooner.</li><li><strong>Establishing Causality</strong>: If the goal is to establish a causal relationship, then the treatment needs to be exogenous. This requires placing certain features or experiences under the purview of the business, rather than leaving them to user discretion. One could randomly assign users to specific features or incentive programs, then compare long-term performance metrics with those lacking access. This methodology underpins AB testing and online experimentation.</li></ol><h3>In Conclusion</h3><p>When evaluating aha moments:</p><ul><li>Recognize that if they’re based on user choice, causality can’t be definitively established.</li><li>View them as indicators or predictors and leverage them accordingly.</li><li>To draw causal connections, ensure the treatment is exogenous.</li></ul><p>As the digital landscape evolves, it’s crucial for stakeholders to understand the true nature of aha moments. They might not be the game-changers they’re perceived to be, but when approached with a discerning eye, they can still offer valuable insights.</p><p>For further discussions or queries, please reach out. — <em>Pragmatic Data Scientists</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed96ae493a01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/why-is-aha-moment-wrong-ed96ae493a01">Why is aha moment wrong?</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[THE clear definition of Retention, and why yours is ambiguous]]></title>
            <link>https://medium.com/pragmatic-data-scientists/the-clear-definition-of-retention-and-why-yours-is-ambiguous-3b7512629093?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/3b7512629093</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Yuzheng Sun]]></dc:creator>
            <pubDate>Wed, 04 Oct 2023 19:41:53 GMT</pubDate>
            <atom:updated>2023-10-26T18:03:39.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D0e3FCicT3_WDHc1t2Y3kw.png" /></figure><h3>TLDR</h3><p>Retention is a concept where junior Data Scientists think they know, but senior Data Scientists become more and more careful with it. Why?</p><ul><li>Each retention has three durations — starting, ending, and the gap. Without a clear definition, you will have mistakes and waste a lot of time in alignment</li><li>We provide a complete definition, a unified framework, and a succinct version for common use</li><li>We provide examples for how to apply this definition</li></ul><h3>A hypothetical example</h3><p>Suppose your colleague asked you: <em>“What’s the weekly retention for active users of ChatGPT?”</em></p><p>The question is actually impossible to answer, because for different “cohorts” of users that started on different dates, each “cohort” can have different retentions, and their retentions change over time. Your colleague needs to be more exact in her ask.</p><p>You asked your colleague to be more exact, by giving you the start date and the end date. She returns:</p><p>“<em>For users who first became active on ChatGPT </em><strong><em>during 9/1–9/8</em></strong><em>, what’s their weekly retention </em><strong><em>on 9/15</em></strong><em>?”</em></p><p>This seemed clear, and you went and fetched a query.</p><p>But did you know that there may be four “correct” ways to interpret her ask?:</p><ol><li>For each daily cohort of 9/1 to 9/8, calculate the % of users who are weekly active till 9/15, then weighted average across cohorts</li><li>For each daily cohort of 9/1 to 9/8, (calculate the % of users who are daily active for 7 days prior to 9/15, take the sum) then weighted average across cohorts</li><li>For the weekly cohort of 9/1 to 9/8, calculate the % of users who are weekly active till 9/15</li><li>For the weekly cohort of 9/1 to 9/8, calculate the % of users who are daily active for 7 days prior to 9/15, take the sum</li></ol><p>You can have more ambiguities if you are not sure if the ending date should be 9/8, 9/15, or 9/22. Let’s not go there yet.</p><p>This kind of ambiguity is doomed to happen because there are <strong>three durations</strong> in any retention definition:</p><ol><li><strong>Starting duration</strong> — Users did some activities here to be included in the denominator</li><li><strong>Ending duration</strong>, and — Users who are in the denominator, did some activities here, to be included in the numerator</li><li><strong>The Gap in between</strong> — Retention is only meaningful when we give some time for users to churn</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SyZm2rKRnuY1T4ew5iBm7A.png" /></figure><p>We can’t just say “weekly” and use “common sense” to figure out which duration “weekly” is correspond to, because these definitions are all valid and can serve different purposes.</p><h3>More knowledge can lead to more ambiguity</h3><p>We see ambiguous definitions of retentions like this everywhere often because people don’t know the other possibilities. They thought their definition is the only way, when in fact, it is only a special case without good notation. It is natural that inexperienced data scientists being confident in their definition of retention, while more experienced data scientists became much more careful.</p><p>This ambiguity became obvious to me during my Facebook career. Back then Facebook was doing Commerce across Marketplace, Facebook Shops, and Instagram Shopping. We started to collaborate and try to compare our metrics. Turns out everyone has their own definition of retention, and we had to spend a lot of time to align on our definitions. If I remember correctly, in 2020, there was an internal post from a high level DS at Facebook, just to address this issue and have a uniform definition across the company. If Facebook, with all of its DS talents, had the problem until 2020, chances are, you do as well.</p><p>This post will help you solve this problem by breaking it down the the most fundamental elements, then reassemble. And it will be very clear. Every time you see a different definition of retention, you will be able to put your finger on where the difference arises and reconcile.</p><h3>How to define it clearly</h3><p>Retention is one word that contains four elements:</p><p><strong># of (Users with Action A during T0, and did Action B during T1) / # of Users with Action A during T0</strong></p><p>We need to be clear on:</p><ul><li><strong>T0, the starting duration</strong>: This is a duration of initial activities. It is often a day, but can often be a weekly, especially when you have a day-of-week effect, or a small sample size.</li><li><strong>T1, the ending duration</strong>: This is your observation window. Again, can be day or week.</li></ul><p>Remember that both T0 and T1 have two parameters — the length of the duration, and the date of the duration. From T0 and T1, we get:</p><ul><li><strong>T1 — T0, the “Gap”</strong>: Gap should be <strong>(end of T1 — end of T0)</strong>. This is where a lot of discrepancies in definitions happen as well. We should use end of durations, to avoid data truncation issues. I’ll explain later in the future post of this series.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gHp0tGyHm2LZYOh4pF2b8Q.png" /></figure><p>In addition, we often implicitly ignored:</p><ul><li>Action A: The initial activity, such as register, download, or <strong>active</strong>.</li><li>Action B: The returning activity, such as <strong>active</strong>, pay, or some meaningful usage.</li><li>Subset relationship: The numerator is a subset of the denominator</li></ul><p><strong>This definition gives you a single data point</strong></p><p>It is natural to think about retention and start thinking about J curve or triangle charts. We will talk about them later. But we need to have a clear definition of points, before we can define a curve well. The above definition is for a single data point. You can draw the J-curve by fixing the T0 and have different gaps.</p><h3>A more succinct version for “active retention”</h3><p>The most common application of retention is for Action A = First Time Active, and Action B = Active. Often, we are interested in T0 = daily, and T1 either = Daily or Weekly. We can create a succinct special case for this definition: <strong><em>DAU or WAU, @GAP</em>.</strong> Where</p><ul><li>D is daily, W is weekly, which correspond to the length of T1</li><li>Active User(AU) corresponds to the user’s status at T1</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AumTkqb6yCrQMyFqa4ldbQ.png" /></figure><p>So for example, if we use WAU@D14</p><ul><li>T1 is from D8 to D14</li><li>A user who is only active @D9 is considered a WAU@D14</li><li>A user who is only active @D6 is considered not a WAU@D14</li></ul><p>In practice, we need to specify T0 as well. The complete sentence is — For the X # of users who did action A between T0_start and T0_end, their WAU @GAP is XXX.</p><p><strong>Two pro tips:</strong></p><ul><li><strong>Retention vs. Stickiness:</strong> Note that Action A is first time active. If we remove “first time” and have Action A = Active, this becomes a common “stickiness” measurement. Under this definition, stickiness is only a special case of retention</li><li><strong>T1 ends on D13 intead of D14:</strong> You may want to consider using D0 as T0, and use D7 to D13 as T1, for two benefits:<br>- You fetch data on D14. If you define T1 as D7-D13, your data will be available.<br>- Suppose D14 is a Friday, your D0 will also be a Friday. So you are looking at Friday cohort on Friday. Anecdotally, some retention metrics spike at 7 day intervals so this is important to capture.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckVyS25WMGKDzSCbWrFzWw.png" /></figure><h3>Apply the definition</h3><p>Applying the definition, let’s define the above ambiguous example again.</p><p>Suppose our colleague asks us her question because she wants to get a sense of how many users keep using ChatGPT at least once per week, after 2 weeks of first activity. Because there is a day-of-week effect in terms of when a user is registered, she also wants a weekly average of starting date.</p><p>Then we should</p><ol><li>Use WAU @ D14.</li><li>For T0s, use 7 daily cohorts across a week and average across them</li></ol><p>With our definition, <em># of (Users with Action A during T0, that did Action B during T1) / # of Users with Action A during T0</em>, it is clear:</p><ul><li>We have 7 different T0s:<br>- Length is daily<br>- (Beginning and )Ending dates are 9/1/2023–9/7/2023</li><li>Gap: 14 days</li><li>We have 7 different T1s:<br>- Length is weekly<br>- Ending dates are 9/14/2023–9/20/2023<br>- For the cohort that starts on 9/1, the ending date is 9/14; for the cohort that starts on 9/7, the ending date is 9/20</li><li>Action A: First Time Active, subject to the product team’s definition. I’ll talk about this later.</li><li>Action B: Active</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ysqysk7sKLK4zr95I1VAxg.png" /></figure><p>We get 7 numbers and do a weighted (based on denominator) average. For example, the first number is:</p><p>(The number of users who first became active on 9/1/2023, and were active during 9/8/2023–9/14/2023) / (The number of user who first became active on 9/1/2023)</p><p>It may take a while at the beginning. But using this definition will force you and your colleagues to think clearly on what exact retentions you want to study. After a while it will be natural and you will have a better understanding of your users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b7512629093" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/the-clear-definition-of-retention-and-why-yours-is-ambiguous-3b7512629093">THE clear definition of Retention, and why yours is ambiguous</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make solid SEO content (and overcome that writer’s block)]]></title>
            <link>https://medium.com/pragmatic-data-scientists/how-to-make-solid-seo-content-and-overcome-that-writers-block-1258daf570d5?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/1258daf570d5</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[seo-content-writing]]></category>
            <category><![CDATA[content-marketing]]></category>
            <dc:creator><![CDATA[Jack Virag]]></dc:creator>
            <pubDate>Tue, 29 Aug 2023 21:44:18 GMT</pubDate>
            <atom:updated>2023-08-29T21:44:18.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CwjC2f2ZIRm1m0UtBAFonQ.png" /></figure><p>👋Hello, Jack here from PDS. Since “many” people have asked about starting their own content, here are the <strong>biggest takeaways from my +8-year content and SEO career</strong>.</p><p>Most importantly, <em>this isn’t an ultimate guide.</em> The internet is full of marketing and SEO help. This is<strong> the bootstrap guide</strong>, full of things you probably won’t hear elsewhere, designed to help you as much as possible with no gatekeeping.</p><figure><img alt="A Linkedin post by Jack Virag that says “What’s the difference between a new marketer and an experienced one? A new marketer knows all the rules, an experienced one knows all the exceptions.”" src="https://cdn-images-1.medium.com/max/789/1*02lvmnMMx-Sw437a1yCruw.png" /></figure><h3>Who are you talking to?</h3><p>One of the most important things authors need to determine is who their target audience is. Since your audience will be very specific to your industry, I won’t be too prescriptive.</p><p>Generally speaking, your blog posts will speak to one of two target audiences:</p><h4>Ideal buyers</h4><p>For a company like Statsig, this is data scientists, engineers, product managers, and other experimenters under whichever job title they occupy.</p><p>For you, as a marketer, you’ll need to develop your own list of personas. Remember to go deeper than just job titles. A good persona includes:</p><ul><li>What problems do they solve?</li><li>What tools do they use?</li><li>What frustrates them?</li><li>What type of content/resources do they prefer?</li><li>Etc</li></ul><p>They say <strong>the key to making a sale is to appear as a “trusted advisor”</strong> to prospective buyers. Remember, your salespeople will do the selling. Your content program is to gain visibility, spread the word, solve problems, and foster trust. 💪</p><h4>“The growth audience”</h4><p>The cynical takeaway is that search engines are an audience. That’s not true, despite marketers always saying things like “oh I wrote this post for Google.”</p><p>The growth audience is comprised of <strong>people at the top of the marketing funnel</strong>. They haven’t heard of your company, but you want them to find you through search engines, referral links, etc.</p><p>Even if they’re not a potential buyer, they might know one or become one someday. And their traffic helps your site perform better.</p><p>Growth content titles include things like “Top 3 rookie mistakes on feature flags,” or “The quick guide to calculating sample size.” They’re written to be scannable, entertaining, informative, and send solid on-page SEO signals to search engines. They’re also fun for human beings to read! 👽</p><h3>The knowledge spectrum</h3><p>&lt; No familiarity with your product — ///////////// — Active users of a product like yours &gt;</p><p>Your blog should have content for everyone on the knowledge spectrum, but <strong>individual blog posts don’t</strong>. This means each post should have a target demographic somewhere along the spectrum. Pick one, and write the post for them.</p><p>Also, beware of making too many “Ultimate Guide” Posts. Instead of one colossal blog post, you can make a handful with different target audiences possessing different levels of expertise, frustrations, needs, etc.</p><p><a href="https://www.semrush.com/blog/topic-clusters">A handful of blog posts around a topic</a> is almost always a better option than one giant blog post, because it sends better SEO signals, as well as providing different users an option tailored to them.</p><h3>Formatting</h3><p>You’ll need to have a style guide that you adhere to. Even if there isn’t one officially documented, you should be aware that every blog post should have:</p><ul><li>A title</li><li>A cover (or “hero”) image</li><li>A “hook sentence” (H4)</li><li>Cascading headings (H2 covers broad sections, H3 is for granular sections that are relevant to the H2)</li><li>At least 500 words (optimal is 1000+)</li><li>A handful of <a href="https://www.nutshell.com/blog/seo-content-writing#:~:text=your%20SEO%20content.-,External%20links,-External%20links%20are">external</a> and <a href="https://www.nutshell.com/blog/seo-content-writing#:~:text=text%20is%20random.-,Internal%20links,-Internal%20links%20work">internal</a> links</li></ul><p>Pro tip: The link anchor (the hyperlinked text itself) should be (close to) the keyword of the page you’re linking to</p><h3>Overcoming writer’s block</h3><h4>The skeleton method 💀🦴💀🦴💀🦴</h4><p>This is a simple process that works for me, and is worth considering if you find yourself stuck. It’s also great for structured SEO posts. I call it <strong>the skeleton method</strong>. ☠️</p><ul><li><em>Don’t start writing right away.</em> Write down all your talking points as bullet points. Just make one big list.</li><li>Put your list of talking points into an order that makes narrative sense.</li><li>Add headings where necessary. Think of it as “grouping” your talking points together. (FYI this also helps blog post skimmers)</li><li>One by one, delete and rewrite your talking points as complete sentences. As you type, you’ll find that more information emerges too.</li><li>If your skeleton was created in a notetaking app, you’ll need to c/p it into a word processor for this final step.</li></ul><figure><img alt="A notepad document showing headings and bulletpoints for a blog post in progress." src="https://cdn-images-1.medium.com/max/1024/1*OjHPfX3emhkQD_OQXYH8Pg.png" /></figure><p><em>^ An example blog post skeleton (in notepad) for a post about </em><a href="https://www.nutshell.com/blog/why-is-hubspot-so-expensive"><em>Hubspot being expensive</em></a></p><h4>Activating your storytelling brain</h4><p>Another tactic to overcome writer’s block is to <em>just talk to someone</em> about your topic.</p><p>You don’t even have to inform them that you’re writing a blog post. Conversationally discussing complicated ideas helps jumpstart your storytelling brain into processing the information.</p><p>Ideas and concepts are not words. They don’t naturally exist inside our brains as verbally conveyable information. Sometimes the transformation happens naturally during the writing process, but not always — and this is a common place to get stuck. A good discussion almost always fixes this.</p><h3>Basic writing style</h3><p>There is a rule of thumb for writing by which most skilled content writers abide. Aside from SEO signals, the readability of blog posts is a valid benchmark that all writers should be shooting for. Google claims that they don’t use time-on-page as a metric to determine a piece of content’s ranking, which is probably true, but that doesn’t mean that it’s not an important metric. In fact, click-through rates, shares, backlinks, etc., are valid enough indicators that algorithms don’t necessarily have to index users’ time-on-page in order to effectively estimate how good and engaging content is. Furthermore, Google recently launched a “quality content” upgrade that is meant to further incentivize sites against keyword-stuffing and other writing tactics that appeal to search engines over readers.</p><p>☝️ <strong>I know you skipped this.</strong> <em>Your readers would too.</em> Here’s the rule:</p><p>Counterintuitively to the writing styles taught in college, readers skip paragraphs that occupy <strong>more than three lines</strong> on the page. See below:</p><p>This is the first line of paragraph text.<br>This is the second line.<br>This is the third line.<br><em>And this is the line that causes people to skip the entire thing.</em></p><p>You don’t have to always adhere to this rule. Sometimes it’s unavoidable. Just <strong>don’t overestimate the attention of your reader.</strong> Even if they’re your biggest fan, human attention just doesn’t work like that.</p><ul><li><strong>Avoid using topic sentences and summary sentences in each paragraph.</strong></li><li>Think about using headings to isolate themes, so you don’t feel pressure to cram information into paragraphs. <em>Give yourself space!</em></li><li><em>“Write how you speak!</em>” Meaning that it’s okay to string together miniature paragraphs that build upon one another and follow a narrative, rather than having each paragraph encompass an isolated narrative.</li><li>When it doubt, just insert an arbitrary paragraph break. Seriously, you will find that this helps your story <em>flow. </em>Literally just break your paragraphs up!</li></ul><h3>Compelling titles</h3><p>Your page title should <strong>concisely reflect the content of the post.</strong> If there is a disparity, it sends bad vibes to Google.</p><p>Furthermore, your title should pique the reader’s curiosity, or otherwise make it clear why they should click and read your post. Pro tips in picking a title:</p><ul><li>Leverage the <a href="https://www.smtusa.com/blog/posts/using-psychology-to-make-content-marketing-more-effective.html#.YyTcD3bMLMY:~:text=our%20blog%20post.-,Information%20Gap,-Developed%20by%20behavioral">information gap</a> (it’s not clickbait if you’re not spammy about it)</li><li><strong>Keep the keyword close to the beginning of the title.</strong> This helps SEO as well as humans. (“[Release management] best practices” is better than “Best practices for [release management]”)</li><li>Avoid cliches like “ultimate guide” unless the article is like 5000 words.</li><li>Try to be a little bit novel. <strong>Your post title may appear among other search engine results.</strong></li></ul><h3>Finding your voice</h3><p>The best advice for creating good content&gt; Use <em>your own voice</em>, be yourself, and write as if you’re <strong>speaking to another human being</strong>.</p><p>Don’t try to be a thought leader, don’t try to use words outside your vocabulary, etc. Just express yourself. That’s what your readers want!</p><p>As a brand, you should take pride in being able to explain without using jargon. Speak plainly about somewhat complicated ideas, just like your audience might.</p><p>Instead of saying “leveraged and utilized supplemental resources,” we’d say “used a tool,” and so on.</p><p>Furthermore, using jargon of any kind (especially corporate jargon) is like gatekeeping — it shakes off the weakest connected readers/listeners. You should be using inclusive and simple (yet accurate) language to keep the barrier of engagement low.</p><p><em>“This works by using pre-experiment data to ‘explain’ some of the observed variance.”</em></p><ul><li>Craig Sexauer <a href="https://www.statsig.com/blog/cuped-on-statsig-d57f23122d0e">describing CUPED</a> simply and concisely</li></ul><h3>Keyword strategy, headings, and SEO stuff</h3><p>You shouldn’t overly focus on this when you’re writing your content. But here’s a summary:</p><ul><li>Every article should have <strong>1 keyword</strong> (sometimes called a “focus keyword/keyphrase”).</li><li>The keyword should appear <strong>about once per 200 words</strong>, and be distributed evenly across the blog post. This satisfies an algorithmic criteria called “keyword density.”</li><li>Your writing, if on-topic, will <strong>naturally cover what search engines consider to be “related keywords”</strong> in the paragraph text, so don’t worry too much about them. Just check the text once you’ve finished writing</li><li>The keyword should be in the title, as close to the beginning as possible.</li><li>The H3s should try to include keywords related to the H2s. Aim for ~66–75% again.</li><li>66–75% of H2s should include permutations of the keyword or related keywords.</li></ul><p>Example: <strong>Focus keyword</strong> (Belgian waffle), <strong>permutations</strong> (belgian waffle recipes, quick belgian waffles, belgian waffles vs regular waffles), <strong>related keywords</strong> (waffle iron, waffle ingredients, are waffles cheap?, what makes a waffle belgian?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlD9Y9rZ14XH8rUA0FVf4g.png" /></figure><p><em>Example SEO headings following keyword cascading best practices.</em></p><h3>Topic research</h3><p>Writing a solid piece of content—on any topic — will require a bit of research. Here are some tips:</p><ul><li>Start with a keyword that is adjacent to something you have content for, or rank for.</li><li><strong>Search the keyword and variations in Google.</strong> Record ranking results and their heading keywords.</li><li>Type as a question in Google and <strong>record related questions.</strong></li><li>Enter the recorded variations, heading keywords, and question queries into a keyword research tool (we use SEMrush).</li><li>Measure SEMrush’s estimated volume and competition for each keyword.</li><li>Use the results to craft your blog skeleton.</li></ul><p><strong>Note: </strong>A good skeleton doesn’t require keyword stuffing, and is the right mix between high volume and low competition (can do high comp when our domain authority is higher)</p><h4>“In conclusion”</h4><p>Just kidding! Generative AI almost always includes a summary sentence or heading that says “overall,” “in conclusion,” or “to summarize.” Make sure you delete that from your final draft.</p><p>That’s it, hope this article is helpful for people looking to start creating their own content. If you have questions, comments, or could use some help, don’t hesitate to reach out!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1258daf570d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/how-to-make-solid-seo-content-and-overcome-that-writers-block-1258daf570d5">How to make solid SEO content (and overcome that writer’s block)</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How startups can master the art of content creation]]></title>
            <link>https://medium.com/pragmatic-data-scientists/how-startups-can-master-the-art-of-content-creation-2d270075e53d?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/2d270075e53d</guid>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[marketing-tips]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[content]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Jack Virag]]></dc:creator>
            <pubDate>Fri, 25 Aug 2023 19:20:29 GMT</pubDate>
            <atom:updated>2023-08-25T19:20:53.969Z</atom:updated>
            <content:encoded><![CDATA[<h4>Takeaways from an interview with Jack Virag, Head of Content @ Statsig.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H6q6rYv19Pe_yqND6Bl8pg.png" /></figure><blockquote>“Every founder thinks, ‘let’s give this content thing a try,’ and they either hire a single marketer or manage freelancers — which isn’t a comprehensive content program.”</blockquote><p>Content marketing remains an elusive strategy for many startups, as founders grapple with how to invest in it and how to measure its effectiveness.</p><p>We sat down with Jack, an expert in the content creation field, to share insights on how startups can create a successful content strategy. Here are the top takeaways from our conversation:</p><h4>1. The Underestimation of Content Marketing in Startups</h4><p>Jack emphasized the common mistake of founders underinvesting in content marketing.</p><p>He observed that most new founders, unfamiliar with content marketing’s nuances, are hesitant to allocate significant resources to it.</p><p>“Every founder thinks, ‘let’s give this content thing a try,’ and they either hire a single marketer or manage freelancers — which isn’t a comprehensive content program,” Jack said.</p><h4>2. The Power of Content in the Marketing Funnel</h4><p>Discussing the bigger picture, Jack articulated content’s pivotal role throughout the marketing funnel.</p><p>Whether it’s drawing people in at the top of the funnel, piquing interest in the middle, or persuading a purchase at the funnel’s bottom, content holds immense sway. However, startups with limited reach must leverage events, social media, newsletters, and other distribution channels to enhance their content’s reach.</p><h4>3. The Bias Against Content Effectiveness</h4><p>Jack highlighted a prevailing bias: “Some might argue that a newsletter sent to a few subscribers generated more leads than content, making the newsletter superior. However, content might be the very reason people signed up for the newsletter.”</p><p>The tone and quality of your content not only influence brand perceptions but also the emotional connection users feel when they engage with your brand.</p><h4>4. Personalizing Brand Identity through Content</h4><p>Building on content’s emotional resonance, Jack emphasized its role in presenting a company’s human side.</p><p>“We want our users to recognize that we’re all human beings. From our data team to our console engineers, everyone contributes to our content program. This transparency provides users with a clear picture of who we really are,” Jack shared.</p><h4>5. Authenticity Matters</h4><p>Reflecting on Mark Zuckerberg’s public perception, YZ and Jack deliberated on the importance of authenticity.</p><p>YZ recalled, “Before joining Facebook, I had biases against Zuckerberg. But hearing him speak regularly changed my perspective.” Jack added humorously that while some perceive Zuckerberg as an “alien,” those who know him regard him as genuine.</p><h4>6. The Challenge of Evaluating Content Success</h4><p>When pondering over the ideal content creation process, Jack proposed an organic approach, placing quality over strict deadlines.</p><p>He also emphasized a content strategy that balances product-led growth with SEO. “It’s easy to design content for tangible products like sports equipment. However, for niche or new products, you must innovate, blending SEO with core product features,” Jack added.</p><h4>7. Quantifying the ROI of Content</h4><p>Addressing the perennial question of content’s ROI, Jack acknowledged the difficulty in communicating content’s qualitative benefits.</p><p>“It’s challenging to translate the emotional and trust-building aspects of content into concrete numbers,” Jack mused. Nevertheless, understanding these softer aspects and assessing whether your content truly delivers is crucial for a brand’s success.</p><h3>Moving Forward</h3><p>Mastering content marketing requires a mix of strategy, patience, and a keen focus on quality. As YZ aptly summarized, “It’s challenging to judge the ROI of content. However, with the right strategy and conviction, the benefits are immense.”</p><p>For startups and tech marketers alike, embracing content as more than just a marketing tool — but a bridge to connect, inform, and build trust with users.</p><p>—</p><p><em>Want more insights on content marketing and startup strategies? Stay tuned for more conversations with industry experts, or </em><a href="https://www.youtube.com/@pragmaticdata"><em>follow us on YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d270075e53d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/how-startups-can-master-the-art-of-content-creation-2d270075e53d">How startups can master the art of content creation</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surviving the high-stakes game of product sense interviews]]></title>
            <link>https://medium.com/pragmatic-data-scientists/surviving-the-high-stakes-game-of-product-sense-interviews-2d960e116e57?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/2d960e116e57</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Yuzheng Sun]]></dc:creator>
            <pubDate>Fri, 11 Aug 2023 23:28:44 GMT</pubDate>
            <atom:updated>2023-08-11T23:28:44.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*844pRhKAEoPApXYzYmyWrg.png" /></figure><p>Imagine stepping into a dark forest. Each pathway leads to different outcomes; some to treasure, others to dead ends. Your task is to choose your path wisely, armed only with your knowledge and intuition. In many ways, answering open-ended questions in product sense interviews feels exactly like this: a high-stakes game of exploration and decision-making.</p><p>Over countless mock interviews, I’ve watched many fellow explorers, armed with their technical prowess and eagerness to impress, rushing headfirst down these pathways. They scramble to find a definitive answer, the “treasure” at the end of the path. Unfortunately, they often find themselves at a dead end, realizing too late that they’ve missed the essence of the game. But fear not, for I’m here to guide you through this challenging yet rewarding forest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*wabDEFaR9Hinf6Kc.jpg" /></figure><h3>Principle 1: A two-way conversation</h3><p>Imagine that each time you step onto a new path, the forest whispers hints to you. The forest here is the interviewer, guiding you subtly toward your destination. To hear these whispers, you must be willing to engage in a two-way conversation, maintaining an optimal talk time ratio of approximately 2:1 or 3:1, with you talking the most. Don’t be the explorer who forges ahead without pausing to listen!</p><h3>Principle 2: Decipher the ‘what’ and ‘why’ before the ‘how’</h3><p>When a path splits in two, do you randomly choose a direction, or do you first try to understand why one path might be preferable over the other? Jumping headlong into problem-solving without grasping the problem is like choosing a path at random. Understand the ‘what’ and ‘why’ before you decide ‘how’ to proceed.</p><h3>Principle 3: The realm of trade-offs</h3><p>The forest doesn’t hold one single treasure, but multiple ones, each with its pros and cons. Similarly, open-ended questions have many answers, each with its own set of trade-offs. You’re not searching for the ‘right’ answer but assessing which solution fits best given the conditions.</p><p>Let’s journey through two hypothetical scenarios:</p><h3>Scenario 1: A gastronomic adventure</h3><p>You’ve been tasked with planning a dinner. The forest offers you various paths: a fancy restaurant here, a homely diner there. Before you rush to recommend the fanciest option, consider your party’s needs. What’s their budget? How many people are attending? What’s the purpose of the dinner?</p><h3>Scenario 2: The fake news conundrum</h3><p>As we approach the thorny problem of assessing the percentage of fake news on Facebook, many explorers may rush to define fake news and propose a detection method. However, the forest asks you a crucial question: why do you need to understand the ratio of fake news?</p><p>Tackling this problem requires a careful exploration of the paths ahead, taking into consideration your available resources, and adjusting your definition of fake news accordingly. Through an open dialogue with the forest (your interviewer), you can show your understanding of the issue at hand and your willingness to work collaboratively towards a solution.</p><p>Let’s illustrate how to approach this challenge. Begin by asking the forest about the purpose of the question, the available resources, and the accessible data. Then, propose a strategy like random sampling and manual tagging, considering resource constraints.</p><p>After presenting your initial plan, engage in a deeper discussion about implementing machine learning to further refine your strategy. This approach not only showcases your technical skills but also exhibits your strategic thinking and adaptability.</p><p>Surviving the forest of product sense interviews involves much more than presenting a definitive answer. It’s about communicating effectively, understanding the underlying business problem, and recognizing potential trade-offs. You’re an explorer, navigating through a rich and complex forest, not merely a treasure hunter seeking a single prize.</p><p>Have any thoughts or questions? Let’s start a conversation in the comments below. I’m always excited to learn from you and to make future posts even more beneficial for our collective journey. Happy exploring!</p><p><em>This post is an edited transcript of </em><a href="https://youtu.be/722vLIY5EJk"><em>a video on product sense interviews</em></a><em>, adapted for a blog format.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d960e116e57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/surviving-the-high-stakes-game-of-product-sense-interviews-2d960e116e57">Surviving the high-stakes game of product sense interviews</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From pedantic to pragmatic: Becoming a useful data scientist]]></title>
            <link>https://medium.com/pragmatic-data-scientists/from-pedantic-to-pragmatic-the-data-scientists-journey-68cf0b1785e?source=rss----a85444f66147---4</link>
            <guid isPermaLink="false">https://medium.com/p/68cf0b1785e</guid>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Jack Virag]]></dc:creator>
            <pubDate>Wed, 09 Aug 2023 22:07:58 GMT</pubDate>
            <atom:updated>2023-09-12T20:28:47.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JzDrE4vFp8Vwk0p7rLcYWA.png" /></figure><p><em>Written by </em><a href="https://medium.com/@yz_79011"><em>Yuzheng Sun</em></a></p><h4>I learned the word “pedantic” from my teammate Craig and instantly loved it.</h4><p>It’s a spot-on way to classify a certain type of data scientist: They’re painful to work with, they’re counterproductive, but they are dogmatically supreme, making them unchallengeable. The more they know, the extra painful they are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zpxWUeC4KiqwqB0CsDDqDQ.png" /></figure><p>We were all pedantic data scientists once — and we may still be. And while we certainly don’t want to behave this way, we can’t begin to help ourselves until we understand</p><ul><li>why we are like this</li><li>what’s the better way to behave</li></ul><p>Let’s start by answering the latter: Strive towards being a pragmatic data scientist. Pedantic data scientists are blockers, while pragmatic data scientists are seen as teammates.</p><h3>Ascertaining the value of a data scientist</h3><p>Throughout my career at different companies, there was always one constant question: <strong>How do we evaluate our business value as data scientists?</strong> I asked this question, discussed it, and got asked it many times. Nowadays, I actually find humor in it.</p><p>Let’s zoom out: Why do businesses exist? Businesses build things — whether material or intangible — that fulfill customer demand. Whoever assists in doing this creates value for the business. It’s that simple.</p><p>So why do we have doubts about finding our business value, especially as data scientists in large companies? It’s simple: There are too many roles and layers and concepts that it’s difficult to map your exact contributions towards the underlying goal. We don’t receive tangible feedback on our work from the market or from our customers. Instead, we have to rely on performance reviews to judge our value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sqqDmYOK8G5AGlghtXSwzQ.png" /></figure><p>Performance reviews are a whole topic by themselves, which I’ll save for another day. Just remember that they are proxies for your value at best: They are designed to measure and compare, but they are a microscopic representation of the end goal. <strong>The end goal has always been to help your business delight its customers.</strong></p><h3>Be confident in your value</h3><p>Data scientists are essential because we have the best tools to understand customers and businesses…It is our job, after all.</p><p>I’m not only talking about analyses, charts, models, and experiments, but more fundamentally, we have mental models and scientific frameworks. I’ll cover these topics one by one, with industry experts, in the future.</p><p>To serve this purpose well requires a pragmatic perspective. A pragmatic perspective means that we start with reality and use the most fitting tools to better understand our existing realities and baselines.</p><p>To better illustrate, below is a comparison between pedantic perspective and pragmatic perspective when facing various choices:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*DLR6CCgOhstutOE-ItZp4w.png" /></figure><p>It’s hard for pragmatic data scientists to fail, given our training, skills, and the questions we ask. For myself, my career role model is the mythical handyman who simply knows where the problem is by looking and knocking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VwmjLfKlvxfxQRsE-40msg.png" /></figure><p>I found that good pragmatic data scientists have the same technique because they have the right mental models to continuously sharpen their judgments — AKA intuitions, business acumen, or product sense.</p><p>Once we develop a good mental model with good judgments, our careers are almost on autopilot because we can just “feel” what’s wrong.</p><h3>Why do we choose to be pedantic?</h3><p>If being pragmatic data scientists is so great, who is stopping us? Spoilers: It’s ourselves, but we need to diagnose ourselves accurately in order to fix it.</p><p>I had the opportunity to do a series of data science career sessions with <a href="https://www.linkedin.com/in/robertomedri/">Roberto Medri</a>, one of the best pragmatic data scientists I have encountered. In one of the sessions, he asked the audience to participate in answering these two questions:</p><ol><li>Raise your hand if you know you shouldn’t be too technical in your presentations.</li><li>Raise your hand if you were too technical in your last presentation.</li></ol><p>You should’ve seen the crowd. We all raised our hands twice.</p><p>We all know that technical presentations lose our audience’s interest and trust, resulting in less impact and lost opportunities, yet we all do it. Why?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*n4KkA17RZ6TGEO3eRGH9RQ.png" /></figure><p>Roberto explained the mentality behind this contradictory behavior: We’re insecure.</p><p>We are afraid of being proven wrong — or worse, incompetent. So we build up our armor with domain expertise, things we know we can beat everyone on. In our heads, people can’t prove us wrong in debates. But in reality, these obscure analyses are often just useless.</p><h3>Becoming pragmatic</h3><p>Being pragmatic is a mindset, but being good at it requires a fair bit of training. Unfortunately, most of us spent many years in school, which actively taught us to be pedantic. There are really only a handful of random blog posts, videos, and interviews that teach us how to truly be pragmatic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*V4iH3v_M7ghjyjZaa6062A.png" /></figure><p>Our channel is dedicated to fixing this gap.</p><p>At <a href="https://statsig.com/">Statsig</a>, we firmly believe that our value is linearly correlated to the business value our customers can create with data. To that end, we continuously invest dedicated efforts to finding and reporting data science best practices — and we broadcast them for free.</p><p>We win when our customers win.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68cf0b1785e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pragmatic-data-scientists/from-pedantic-to-pragmatic-the-data-scientists-journey-68cf0b1785e">From pedantic to pragmatic: Becoming a useful data scientist</a> was originally published in <a href="https://medium.com/pragmatic-data-scientists">Pragmatic Data Scientists</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>