<?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[Husprey - Medium]]></title>
        <description><![CDATA[Husprey’s platform allows data and business teams to collaborate more effectively by using “data notebooks” — single-page documents that combine context, data, and insights. - Medium]]></description>
        <link>https://medium.com/husprey?source=rss----dbcd0d25d11---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Husprey - Medium</title>
            <link>https://medium.com/husprey?source=rss----dbcd0d25d11---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:46:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/husprey" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Husprey raises €3 million in funding to replace dashboards with data notebooks]]></title>
            <link>https://medium.com/husprey/husprey-raises-3-million-in-funding-to-replace-dashboards-with-data-notebooks-78275983fbeb?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/78275983fbeb</guid>
            <category><![CDATA[seed-investment]]></category>
            <category><![CDATA[data-notebooks]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Thibaut Collette]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 15:01:14 GMT</pubDate>
            <atom:updated>2022-12-06T15:00:59.017Z</atom:updated>
            <content:encoded><![CDATA[<h3>Husprey raises €3 million in funding to replace dashboards with data notebooks.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S-SsIACYrdr1Y-7HjoEL4g.jpeg" /></figure><p><em>Paris, Dec 6th, 2022.</em></p><p>Some of you have known us for many months. Some for a couple minutes.</p><p>In both cases, this blog post highlights what we believe, what we do, and why we raised funding so you can know us better.</p><p><em>This post is about Husprey as a data product. If you’re only interested in the fundraising details you can skip to the end.</em></p><p>In recent years, the rise of the so-called “Modern Data Stack” has brought significant changes to the data pipeline, from ingestion to usage. However, traditional dashboard solutions still dominate the “last mile” of analytics.</p><p>Data Engineering teams have a wide range of tools to choose from for the various tasks they have, from data extraction to transformation. On the other hand, data analysts are often limited to using dashboard solutions that are designed primarily to provide business users with a seamless experience.</p><p>As a result, analytics teams are often forced to use these tools even when they are not well-suited to the task at hand. In particular, in cases where analysts need to work on more complex questions, traditional dashboard solutions fall short.</p><p>Using dashboards for ad-hoc analyses work leads to tedious and error-prone processes involving copying and pasting data between BI tools and other applications such as Notion or Google Docs. This not only slows the analysis workflow down, but it also increases the likelihood of inconsistencies and errors in the final results.</p><h3>What we believe</h3><p>Our belief that Data Analysts should not be hidden behind dashboards is stronger than ever. We also believe that the best way to improve data-driven decision making is to enhance a company’s data culture.</p><p>While we do not expect business users to be able to write sql queries, we do expect them to improve their data literacy. This means not only being able to retrieve data points from dashboards, but also being able to ask better, more focused questions of their data analysts over time. The best way to achieve this is to experience and interact with expert-generated content.</p><p>We however data analysts to split their workstream into two parts. First, they should enable self-service and metric tracking for well-defined domains in dashboards. Second, they should continue to deliver high-value analyses, answering difficult business questions quickly and accurately.</p><p>Data notebooks are the best way to answer business questions, combining context, data, and insights in a single document. At Husprey, our goal is to empower analysts to create the best data notebooks and allow them to iterate as quickly as possible.</p><h3>What we do</h3><p>Data notebooks have been used by technical users for many years, but they have often been difficult to share with others. At Husprey, we build the platform data analysts need to share their work with their teammates and business users.</p><p>We focus on two key moments in the data analysis process to build our platform.</p><p>First, we focus on the moment when the data analyst begins working on a topic. Our goal is to shorten the iteration loop as much as possible. To achieve this, we offer:</p><ul><li>A great writing experience, both for context and for sql code;</li><li>A powerful data warehouse explorer, with a smart display of metadata, particularly through our integration with dbt;</li><li>A “local table” functionality that brings the best aspects of notebooks to SQL, allowing data analysts to break up long queries into smaller, more manageable pieces that can be easily reused and reviewed;</li><li>A simple interface for sharing takeaways, which allows data analysts to present their conclusions in a consistent and clear way.</li></ul><p><em>We are currently (as of Dec 2022) working on a new Query History feature, which will make it easy to search among all the queries that have been executed in a workspace. While this feature is expected to be available by the end of the year, you can sign up for early access </em><a href="/service/mailto:thibaut@husprey.com?subject=Query%20History%20beta"><em>here</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*akBdJK6Jr0rblJmKlksKXA.jpeg" /></figure><p>Secondly, our platform also facilitates collaboration between data analysts and business users. We make it easy for business users to connect with data analysts, leave comments and reactions, share links in Slack, and share public links with readers outside of their organization.</p><p><em>As we speak, we are testing out a brand new Notion integration. To join the beta, you can subscribe </em><a href="/service/mailto:thibaut@husprey.com?subject=Notion%20integration%20beta"><em>here</em></a><em>.</em></p><p>Again, we build our notebooks’ platform so data analysts can provide better answers to business users questions, quickly and accurately.</p><h3>Why we raised</h3><p>In the past few months, we have been working with several successful scale-ups in France, such as Ankorstore, Malt, and GoJob. We have also expanded our operations to other European countries, including Germany and the Netherlands, and more recently to the United States.</p><p>This continuous growth has validated both the market need for our product and our initial response to that need. As a result, we have decided to scale our operations and move faster.</p><p>We have been fortunate to have discussions with investors who we believe can help us achieve our vision. <a href="https://galion.exe.vc/">Galion.exe</a>’s impressive network of entrepreneurs will provide valuable opportunities for learning from peers, while <a href="https://www.axc.vc/">Axeleo Capital</a>’s expertise in B2B SaaS will help us avoid common mistakes and accelerate both our distribution and their operations.</p><p>Additionally, we are fortunate to have the support of experienced business angels who are providing expertise in areas such as sales, marketing, and product development.</p><p>Over the next few months, we will be expanding our team to support our growth and implement our vision. The funding we have received will be used to scale up our engineering and marketing teams, and to create dedicated success, data, and sales teams. If you are interested in joining our team, please check out our <a href="https://husprey.com/careers">Careers</a> page.</p><p>If our message resonates with you and your work, we invite you <a href="https://husprey.com/">to try Husprey</a> for yourself or to <a href="https://calendly.com/thibaut-husprey/intro-call">schedule a personalized demo</a>. We are always excited to meet with individuals and discuss how Husprey can help them with their data analysis needs.</p><p>We are deeply grateful to our early supporters and look forward to welcoming more people to the Husprey community in the future.</p><p>We are more convinced than ever about the destination and are building the team that will help us fly there. (See <a href="https://www.husprey.com/about#husprey-definition?utm_source=blog&amp;utm_source=post&amp;utm_campaign=seed_announcement">Husprey definition</a>)</p><p>Husprey</p><p>🦅</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78275983fbeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/husprey-raises-3-million-in-funding-to-replace-dashboards-with-data-notebooks-78275983fbeb">Husprey raises €3 million in funding to replace dashboards with data notebooks</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dashboards and ad-hoc analyses are different: split up your team and tailor your processes]]></title>
            <link>https://medium.com/husprey/dashboards-and-ad-hoc-analyses-are-different-split-up-your-team-and-tailor-your-processes-54a959f0986?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/54a959f0986</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[notebook]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Thibaut Collette]]></dc:creator>
            <pubDate>Tue, 01 Feb 2022 11:57:41 GMT</pubDate>
            <atom:updated>2022-02-02T11:32:23.432Z</atom:updated>
            <content:encoded><![CDATA[<p>Finding the right organization for a data team is complex. Should it be centralized, decentralized, federated, or custom made? The most common answer is “It depends”. (Links to great readings on the topic below)<em>. </em>Are there specific ratios to keep in mind while growing? <a href="https://substack.com/profile/6080775-mikkel-dengse">Mikkel Dengsøe</a> wrote a <a href="https://mikkeldengsoe.substack.com/p/data-to-engineers">great piece</a> about this question. When focusing on the data analytics sub-teams, choices are even harder due to their highly specific positioning at the frontier of business and data.</p><p>As the data pipeline matures (what I mean here is “As the Modern Data Stack eats up the world”), analytics teams iterate over their structure, create new roles (hello analytics engineers 👋) but still expect greater impact on business decisions. It, very often, means to keep improving at:</p><ul><li>Allowing self-serve data and dashboarding</li><li>Answering advanced Business questions</li><li>Enforcing data literacy</li></ul><p>While the first 2 goals are distinct, they are almost always operated in the same thread: within the same workflow, by the same people, and using the same tools. This slowly cripples your Analytics team velocity and discourages Business Users to ask (the right) questions.</p><p>To fix this slow infection, you’ll need to transform your team and processes so it can become multi-threaded. You separately tackle self-serve actions and advanced questions.</p><p>The good news: the infection doesn’t come unannounced.</p><p>On Slack, you start receiving more requests such as: “Sorry mate, I can’t remember where is the dashboard about the retention?” or “hey! I checked but didn’t find the product usage dashboard”. When business users start asking more of these, it basically means that <strong>there are too many dashboards</strong>. When looking for some data, they have too much of it and yet no insights.</p><p>You will start feeling overloaded, focusing with “no value-added” tasks while a sense of frustration among Business Users will grow. Because answering small requests takes up a significant portion of your time, answers to more complex questions or deep-dives will be delayed. Over time, the<strong> number of advanced Business questions asked to the Analytics team will start to go down</strong>.</p><p>But it’s never too late, to take back control. You need to transform your team and processes so it can become multi-threaded and more predictable.</p><h4>Split up your team</h4><p>Ideally, you would enforce multi-threading by creating 2 distinct sub-teams. One would be responsible for <strong>providing the best self-serve experience</strong>. The other one would be in charge of <strong>answering Business questions, build ad-hoc reports and deep-dives</strong>.</p><blockquote>Designing a dashboard and writing an analysis are two very independent tasks</blockquote><p>Designing a dashboard and writing an analysis are two very independent tasks. Some Data Analysts love to dig into the data, iterate over and over in order to find “the” insight. (Does it exist?). Many others would prefer to carefully design a dashboard that will help monitor the operations, and that will be accessed by an entire team on a daily basis. Those differences often match your team members’ personality traits and splitting up the team will help them focus on what they like the most and be happier at work.</p><p>As a good multi-threaded system, interference from one sub-team to another should be limited. If there is a higher demand, on one side, then the other team will continue to deliver as expected. This de-coupling will restore the trust from Business users as they see clearer timelines.</p><p><em>What if </em><strong><em>I am solo</em></strong><em> in my team? What if we </em><strong><em>can’t split again</em></strong><em> after splitting by departments? What if </em><strong><em>we prefer to do both</em></strong><em> deep-dives and self-serve? </em>Your split should still happen but it should be time based. Tasks and topics would then shift on a regular basis. To make sure you benefit the most from those changes, you should make sure you don’t change topics too often. From the feedback received in different teams, switching at an interval of less than a week is not recommend.</p><p><em>What ratio of </em><strong><em>self-serve analysts vs. deep-dive analysts</em></strong><em> should I have?</em> Well, once again, “it depends”. This ratio will basically evolve a lot depending on the quality of your Transform layer, on the company’s data literacy, the size of your team… However, you already have a self-serve to ad-hoc ratio. To start your transition into this “multi-threaded” analytics, aim at keeping it the same ratio while improving on creating different context for each thread. Start from here and iterate.</p><h4>Tailor your processes</h4><p>Traditional BI solutions offer great self-serve options from Looker to Tableau to Metabase (and many more). They all have their key differentiators: better dashboards, better chart capabilities, better discovery over non-prepped data, …</p><blockquote>Dashboards display only the data which most of the time actually brings in new questions.</blockquote><p>And yet their focus mostly stayed on providing the best self-serve experience. Dashboards are really good at making sure Business is going as expected, detecting failures or spikes. They display only the data which most of the time actually bring in new questions. Why do I see what I see in the data? How can I change this trend? Answering those questions requires digging and thinking — here enter ad-hocs and deep-dives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*-phDp3PxteROlv4-zC1e2g.jpeg" /><figcaption>Example of dashboard. Photo taken by <a href="https://unsplash.com/@lukechesser?utm_source=medium&amp;utm_medium=referral">Luke Chesser</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s take an example. In the Acquisition dashboard, the Marketing team just saw their Cost of Acquisition (CAC for those in the know) took a leap. Warning. They try to hack some conclusions on a spreadsheet but decide they need the help of their favorite Data Analyst. After some initial discussions to refine the underlying need and some real effort, our Data Analyst is able to deliver her conclusions. She sends a Slack message with a link to a Notion/Confluence doc with her conclusions, a bunch of copy pasted charts and a link to a dashboard.</p><p>While it seems fine, different issues emerge here.</p><p>A new tailored dashboard was added to your already long list of dashboards. As dashboards stay live, they should always contain up-to-date data and it won’t be long before someone pats on your shoulder and disgracefully informs you that “The dashboard is broken”. You’ll have to fix it. Congrats, you found what developers call “Technical debt”. As you continue to run more ad-hocs, you’ll start hearing more of those “CAC can be found in 3 dashboards. Which one should I look at?” requests. <strong>Ad-hoc analyses should create snapshots views, not live dashboards.</strong></p><p>But there is more.</p><p>Answering questions is an actual iterative process. A flow of assumption and conclusions. You go back and forth from raw data to formatted data to new visualizations to insights. This loop should be as short as possible. <strong>Feedback from Business Users</strong> should happen during these iterations,way before you produce your final deliverable. Otherwise, you’ll slide into a copy/paste chaos that you’ll regret later when updating all your charts in your final report. Also, t<strong>he iterative process has value by itself</strong> and you should keep the flow as a reference for future use (either for you or your newcomer) as it will improve your response time for the next analyses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qib7ZLwpDjH3h9qIRxp2nw.gif" /><figcaption>Preview of collaborative notebooks on Husprey</figcaption></figure><p><strong>Notebooks present themselves as the best way</strong> to share reports containing both the flow, the conclusions and the underlying data.</p><h4>Conclusion</h4><p>Analytics teams already spend time on various tasks but splitting up the team and tailoring the right processes/tools ensure happy Analytics team and happy Business Users.</p><p>Designing dashboards and answering advanced Business questions actually ask for different personality traits in your team members.</p><p>Dashboards are great for monitoring but create technical debt when used to serve ad-hoc purposes. Notebooks, on the other hand, mix the data and the brain juice of your Analytics team while speeding up the iterative flow.</p><p><strong>De-coupling self-serve and ad-hoc work will bring magic to your team!</strong></p><p>Thank you for reading. Please don’t hesitate to clap if you found this content valuable.</p><p>Cheers!</p><p>Thibaut<br><em>Co-founder at Husprey (https://husprey.com)</em></p><h4>Further Readings</h4><ul><li>Organizing Data Teams — Where to Make The Cut by <a href="https://svenbalnojan.medium.com/?source=post_page-----49969c5ec093-----------------------------------">Sven Balnojan</a> <a href="https://medium.com/@chartio/how-to-organize-your-data-team-77db2c2d027c">https://towardsdatascience.com/organizing-data-teams-where-to-make-the-cut-49969c5ec093</a></li><li>Data org structure examples by the awesome dbt team <a href="https://www.getdbt.com/data-teams/data-org-structure-examples/">https://www.getdbt.com/data-teams/data-org-structure-examples/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54a959f0986" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/dashboards-and-ad-hoc-analyses-are-different-split-up-your-team-and-tailor-your-processes-54a959f0986">Dashboards and ad-hoc analyses are different: split up your team and tailor your processes</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data notebooks — how useful around the holiday season?]]></title>
            <link>https://medium.com/husprey/data-notebooks-how-useful-around-the-holiday-season-ba84c4ce9610?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/ba84c4ce9610</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <dc:creator><![CDATA[Thibaut Collette]]></dc:creator>
            <pubDate>Fri, 26 Nov 2021 11:02:47 GMT</pubDate>
            <atom:updated>2021-11-26T12:35:23.128Z</atom:updated>
            <content:encoded><![CDATA[<h3>Data notebooks — how useful around the holiday season?</h3><p>I guess you are well aware today is “Black Friday” (for some retailers it looks like it even started weeks ago…) In this article, I share my vision of data notebooks, how they compare with dashboards, and how they can be useful to your analytics team. With the example of the holiday season.</p><p>For data teams, Black Friday usually marks the beginning of an intense period, with Cyber Monday, St. Nicholas, and Christmas following soon after.</p><p>In fact, for you data analyst, it even started a few weeks or months ago: <em>marketing</em> asks for recommendations on what acquisition channels to favor, <em>infrastructure</em> wants to know the expected traffic on your websites, <em>finance</em> is particularly concerned by payment frauds, <em>operations</em> knows that there will be a high rate of buyer’s remorse but needs a quantitative estimate to adjust their headcount, etc. Ah, also, they all need to specifically track the performance of these elements on dedicated dashboards 😳</p><p>And as soon as next week, you will evaluate the actions that the various teams have taken following (or not) the recommendations you have shared with them. How will you do this?</p><p>It’s tempting to make use of the dashboards you’ve set up earlier for tracking, take a few screenshots, and send all this by email. But is this the best solution?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zlhlCdTa26x19djryRvDQ.png" /><figcaption>Screenshot of a Dashboard in Metabase (https://metabase.com)</figcaption></figure><h3>Dashboards</h3><p>Dashboards are great to monitor a known set of metrics over time, get an overview over several KPIs at once, and grasp dynamics.</p><p>No doubt you need to set up dashboards for your stakeholders to get insights on what is happening on their day-to-day in their areas of interest.</p><p>Creating specific dashboards dedicated to an event or period makes sense as well, to get the picture from a particular perspective and quickly identify potential issues. Sorry but yes, I think your stakeholders are right to ask you for Black Friday dashboards!</p><p>However, the maintenance cost of dashboards is enormous: fixing broken queries or widgets, adding new filters, and improving UI are all extremely time-consuming tasks. It is even cited as paint point #1 by numerous data analysts we have met over the last year!</p><p>Creating dashboards for one-shot analyses seems insane, but spoiler alert there is an alternative. Read more.</p><p>Also, when it comes to evaluating past choices, tracking informed decisions, or building up related knowledge, dashboards fall short on several key elements.</p><p>First, they rarely (never?) embed the context: What has this particular dashboard been created for? What are the questions it is meant to answer? What are the underlying assumptions? Why these specific metrics or segments have been chosen?</p><p>And without context, no one can understand figures or trends.</p><p>It’s not a problem when a dashboard is well established, displaying well-known and shared KPIs (the context is then known to everyone), or if it is temporary (interested individuals just remember the recent context).</p><p>But this definitely cannot happen with a long-live yet infrequently used dashboard.</p><p>Now, if you don’t keep these dashboards alive, how can you keep their elements around to back your decisions and learnings? Looker or Tableau screenshots could help fill your email or report with fancy charts, but they would not make their conclusions much reliable, without any repeatability or traceability.</p><p>And to be honest, I bet you’re about to receive a DM from your CEO that says: “What bundles performed best? and that we should use for Christmas? Can you run a quick analysis?”[1].</p><p>This is when notebooks will prove their value the most.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uljRacHncbYK3VnTV4ABWg.png" /><figcaption>Screenshot of a notebook in Husprey (https://husprey.com)</figcaption></figure><h3>Notebooks</h3><p>By combining context, reasoning, interpretations, queries, and data themselves, notebooks are the perfect fit for anything that requires some sort of storytelling: investigations, explorations, post-mortem evaluations.</p><p>For instance, when you want to use the lessons learned from this Black Friday (being in 2 weeks about that CEO question 👆 , or next year to prepare Black Friday 2022): best bundles we created per demography; the impact of recent logistics issues; performance of specific acquisition channels vs. last year.</p><p>With a notebook-based collaborative tool, you can blend data and comments in a story format, following a logical train of thoughts and arguments. You highlight assumptions and limits, provide interpretation of the results. Those prove to be particularly useful when iterations need to include feedback from your Business teams.</p><p>It’s data for the human brain! What does the “I” mean in BI again?</p><p>Also, you can search all relevant content and conclusions, together with the data and context that lead to them. You are then able to make your own mind on the relevance of previous conclusions with respect to the present conditions.</p><p>And you actually leverage the knowledge accumulated by you and your team and improve in the long term.</p><blockquote>Over time, piling dashboards creates technical debt, writing notebooks builds up knowledge.</blockquote><h3>Conclusion</h3><p>Dashboards and data notebooks should not be considered mutually exclusive.</p><p>Dashboards are great for monitoring. Data notebooks are the way to go for reporting, and more generally for data storytelling.</p><p>Dashboards bring instant reactions when needed. Over time, piling dashboards creates technical debt, writing notebooks builds up knowledge.</p><p>And if I were to suggest 2 Black Friday’s resolutions for you to try this year:</p><ul><li>set a reminder to archive your Black Friday dashboards around December 20th (here is a <a href="https://www.google.com/calendar/render?action=TEMPLATE&amp;text=Archive+Black+Friday+dashboards&amp;dates=20211222T080000Z%2F20211222T090000Z">link</a> to set up a Google Calendar reminder)</li><li>write your Black Friday post mortem analyses in a notebook (here is a <a href="https://app.husprey.com/signup?invitation_id=medium-bf">link</a> to start writing them in Husprey)</li></ul><p>If you liked this post, please give it some claps to help us share the words!</p><p><strong>🎃 🦃 🎄<br>Happy holiday season to all!</strong></p><p>Cheers,<br>Thibaut</p><p><em>Who am I? My name is Thibaut and I cofounded Husprey. We build the best-in-class analyst workspace built around data notebooks. A single place for data collaboration within and outside the data team. Curious to know more or want to discuss? You can </em><a href="https://app.husprey.com/signup"><em>sign up</em></a><em> now or </em><a href="https://calendly.com/thibaut-husprey/intro-call"><em>book a call</em></a><em>. I would love to hear more about your team.</em></p><p>[1] They always think it’s “quick&amp;easy”, aren’t they? 🙄</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*L0nmL-S8mttCBBPHUGuqwg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba84c4ce9610" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/data-notebooks-how-useful-around-the-holiday-season-ba84c4ce9610">Data notebooks — how useful around the holiday season?</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analytics team — Wins you can implement today — Part II]]></title>
            <link>https://medium.com/husprey/analytics-team-wins-you-can-implement-today-part-ii-c0a95ea2d2f9?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/c0a95ea2d2f9</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Thibaut Collette]]></dc:creator>
            <pubDate>Mon, 15 Nov 2021 09:57:40 GMT</pubDate>
            <atom:updated>2021-11-15T09:57:40.144Z</atom:updated>
            <content:encoded><![CDATA[<h3>Analytics team — Wins you can implement today — Part II</h3><p><em>This is the second part of our “</em>Analytics team — Wins you can implement today<em>” series. Part I about communication tips is available </em><a href="https://medium.com/husprey/analytics-team-wins-you-can-implement-today-4f3bf6708714"><em>here</em></a><em>.</em></p><p>All data analytics teams have different issues: how to set up a clean data pipeline, how to maintain it, how to share dashboards (bonus points when there will be actually used), how to limit repetitive questions from being asked, how to pipe back the data to operational tools, …</p><p>But in the end (and as we could expect), all teams want to maximize their impact without growing the headcount exponentially. Tooling and technical skills are a very important part of the solution but the obvious one. Less obvious and still pretty often the bottleneck, <strong>communication </strong>and <strong>knowledge </strong>make sure your team has the expected impact.</p><p>If you’re in an analytics team (or if you are the analytics team!) and want to boost your impact, there is every chance that you should start by tackling communication and knowledge first. What do I mean? Here are some tips you can implement starting today!​</p><blockquote><em>Yes, you are good at data!<br>But this is not the end of the story.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*GgItYGoy_nVWQEq59oS46Q.gif" /></figure><h3>Part II — Share and leverage your team data knowledge</h3><p>After browsing, crunching, and exploiting your data, you gain valuable expertise and knowledge about them, which should definitely be shared within your team and your company (for your future self, your peers, upcoming newcomers, your business users). How valuable is it? First, let’s have a look at what kind of expertise you develop.</p><p>Obviously, you get accustomed (some would even say intimate) to your data. Here are some examples of apparently low-level, and yet critical!, elements you get overtime: Tips about the way to find specific properties or pieces of information — “No, you don’t need to join these 14 tables together, it is already pre-computed in this dedicated materialized view”; Specific events to be aware of — “We were unable to ship Product B in 2018Q1 due to component shortage, be careful when evaluating the acquisition performance of the campaigns run around these dates”.</p><p>You also develop knowledge around the way to prepare, plan and run specific analyses, either based on their topic (user retention, acquisition campaign performance, etc.), or based on the statistical tools they involve (clustering, survival analysis, etc.). You know what steps to go through, what decisions to usually take, what assumptions to reasonably make.</p><p>Yes, you are good at data!<br>But this is not the end of the story.</p><p>As a data team member, your goal is to irrigate your company with relevant data so that your business users can make the right decisions. This means raising the bar (in terms of cost, quality, delay) for everyone. Leveraging every ounce of knowledge and expertise you develop is key in this perspective.</p><p>While this sounds like a quite large and intimidating topic, it does not have to be complex. You do not need to implement a company-wide exhaustive data cataloging solution, associated with numerous internal MOOCs and Ted Talks!</p><p>Here is a selection of wins you can take today.</p><h4>Showcase some examples</h4><p><em>Difficulty 2/5 — Costs 1/5 — Impact 3/5</em></p><p>You are particularly proud of your last analysis on retention? Think it implements many best practices your team should follow and could serve as a template for the next ones?</p><p>Make it available for everyone! Decide on a shared location, and start building your data A-list, to be read by any newcomer in your team.</p><p><em>For ideas about where you can post, a Slack channel, or a bi-weekly newsletter might be good to start. Check the first part about communication </em><a href="https://medium.com/husprey/analytics-team-wins-you-can-implement-today-4f3bf6708714"><em>here</em></a><em> for more details.</em></p><h4>Run bi-annual data classes</h4><p><em>Difficulty 4/5 — Costs 3/5 — Impact 4/5</em></p><p>Data as a domain moves extremely fast. For you data analyst, it’s critical to stay at the edge of that field, but everyone else in the company cannot do that. Organize regular classes open to everyone (at least bi-annually). The goal of those classes is to show what the data team can do for them and help them adopt a data-oriented approach.</p><p>The difficulty here resides in the variety of profiles you may attract (but it’s crucial to welcome everyone). Carefully listen to your audience, understand what they are looking for, and help them grow.</p><p>With these classes, business users should better understand how to use and interpret data they already have access to, better express their needs when they come to you, and demystify the most recent trends — “No, we can’t answer everything by simply putting some AI on top of our database, but yes, last developments in natural language processing could be extremely useful to the marketing team, and we can work together to identify opportunities”.</p><blockquote>If you run data classes, prefer subjects around use cases that make sense for your audience, over generic training session on tools.</blockquote><p>Prefer subjects around use cases that make sense for your audience, over generic training session on tools; share your own experience:</p><ul><li>How to track the deployment of a new feature with our existing dashboards?</li><li>How to investigate a specific issue in SQL?</li><li>What we have done for Black Friday, and how it has been useful to the sales team</li></ul><p>No need to start big: sharing the learnings of a recent analysis might already be a good support for a first session. Also, announcing it publicly is a good way to engage you and your team in this virtuous circle.</p><h4>Get inspiration from others</h4><p><em>Difficulty 1/5 — Costs 2/5 — Impact 3/5</em></p><p>If you are in a tech company, chances are that there is some software development team around you. Guess what? Knowledge management and sharing is also a topic on their side!</p><p>Software development and data teams have a lot in common (and also big differences, we won’t enter the details here!). And while I don’t believe there can be a one-size-fits-all way of handling knowledge (because you want that knowledge to be actionable, it needs to be bound to your own ways of operating), there are definitely best practices that can be applied to both worlds — think about sharing code snippets, or maintaining technical documentation for instance.</p><p>Don’t stop here! Do the same with more distant teams that do build and manipulate knowledge a lot (and sometimes for much longer in your company). Think about R&amp;D, QA, Operations.</p><p>Get up from your chair and go talk to them (or give them a call if you are working remotely!)</p><p>In the information age, knowledge as a whole is a key asset for modern companies. It is even more important for a function and culture that is meant to penetrate each and every part of their activities: data. As a member of the data team, to fully achieve their potential, you have the responsibility to share and build upon your expertise.</p><p>Last but not least, it does not need to be a big company-level project, with even bigger change management processes. Short-term wins can be easily implemented, and already deliver value to everyone. The best way to build them durably is to seize every opportunity in your daily work, and iterate within short feedback loops.</p><p>Nothing new here, but worth remembering: start small, get feedback, iterate.</p><p><strong>Happy knowledge sharing!</strong></p><p>Cheers,</p><p>Thibaut</p><p><em>Who am I? My name is Thibaut and I cofounded Husprey. We build the best-in-class analyst workspace. A single place for data collaboration within and outside the data team. Curious to know more or want to discuss? You can </em><a href="https://app.husprey.com/signup"><em>sign up</em></a><em> now or </em><a href="https://calendly.com/thibaut-husprey/intro-call"><em>book a call</em></a><em>. I would love to hear more about your team.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*er53OfNErkvkFG2v0zKy-w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0a95ea2d2f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/analytics-team-wins-you-can-implement-today-part-ii-c0a95ea2d2f9">Analytics team — Wins you can implement today — Part II</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analytics team — Wins you can implement today]]></title>
            <link>https://medium.com/husprey/analytics-team-wins-you-can-implement-today-4f3bf6708714?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/4f3bf6708714</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Thibaut Collette]]></dc:creator>
            <pubDate>Mon, 20 Sep 2021 13:37:26 GMT</pubDate>
            <atom:updated>2021-09-20T13:37:26.397Z</atom:updated>
            <content:encoded><![CDATA[<h3>Analytics team — Wins you can implement today — Part I</h3><p>All data analytics teams have different issues: how to set up a clean data pipeline, how to maintain it, how to share dashboards (bonus points when there will be actually used), how to limit repetitive questions from being asked, how to pipe back the data to operational tools, …</p><p>But in the end (and as we could expect), all teams want to maximize their impact without growing the headcount exponentially. Tooling and technical skills are a very important part of the solution but the obvious one. Less obvious and still pretty often the bottleneck, <strong>communication </strong>and <strong>knowledge </strong>make sure your team has the expected impact.</p><p>If you’re in an analytics team (or if you are the analytics team!) and want to boost your impact, there is every chance that you should start by tackling communication and knowledge first. What do I mean? Here are some tips you can implement starting today!​</p><blockquote>Communication is rarely cited as a criterion for being a good analytics team member. I beg to differ!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*1rrlAf7pLnq0-CNLYrVeCg.gif" /></figure><h3>Part I — Communicate like a pro</h3><p>Communication is rarely cited as a criterion for being a good analytics team member. I beg to differ! It’s crucial to have good “2-way communication” skills. Understand what is being asked, being able to reformulate, and then clearly express progress status and results.</p><h4>Set up a Slack channel</h4><p><em>Difficulty 1/5 — Costs 1/5 — Impact 2/5</em></p><p>It’s not much (and some of you already implemented it). But if you haven’t it’s actually a perfect way to open up communication. Coworkers could then ask their questions whatever they are: request, data location, etc… It’s important for coworkers to know where they can ping you if they need help. For you, it means a single place to look for limiting shadow DMs or email requests.<br>Naming suggestion? <strong>#data-questions.</strong></p><h4>Send weekly emails about your priorities</h4><p><em>Difficulty 1/5 — Costs 2/5 — Impact 3/5</em></p><p>The goal here is to communicate your team’s priorities. When you don’t, people lose trust in the process. As soon as you start, people’s complaints will die down peacefully. They might challenge prioritization but then it will be an actual opportunity to explain how you prioritize different requests (the ones with the highest impact). A few bullets points with the ongoing and the next topics might be enough to start here. Nothing shiny.</p><p>(Not a fan of emails? You might start a generic <strong>#data</strong> Slack channel or a dedicated <strong>#data-priorities </strong>one)</p><h4>Find your relays</h4><p><em>Difficulty 3/5 — Costs 1/5 — Impact 4/5</em></p><p>Relays would be people in the operational teams that are more interested in solving their issues using data than the average. They are the ones who want to do more with their dashboards and who love to share with others. Most of the time you can identify some of them in different teams. <br>Treat them carefully.<br>You should build a relationship with them. For example, you can create a specific channel with them where you send advanced tips or try out new things before you send them to other people in the org. They will act as proxies and train people around them with operational tricks.</p><p>Ideally, set monthly meetings with them, get feedback from what is needed in their teams. It helps prioritize the needs.</p><p>—</p><p>Again, for those who know me,<em>​</em>​ you know how much I believe an Analytics team is actually very close to an internal Product team. What does it mean for us here? Prioritize based on your users&#39; (your coworkers) needs, communicate with your users, and find your hardcore users.</p><p><strong>Ah and start early and iterate.</strong></p><p>If you had to pick only one item from the list above, I would start a biweekly post containing a couple of interesting findings and the list of the next things to come. Initial positive feedback is expected in less than a month.</p><p>You want to know how you can boost data knowledge in your data team and in operational teams? Part II about knowledge will land next week.</p><p>Cheers,<br>Thibaut</p><p><em>Who am I? My name is Thibaut and I cofounded Husprey. We build the best-in-class analyst workspace. A single place for data collaboration within and outside the data team. Curious to know more or want to discuss? You can </em><a href="https://app.husprey.com/signup"><em>sign up</em></a><em> now or </em><a href="https://calendly.com/thibaut-husprey/intro-call"><em>book a call</em></a><em>. I would love to hear more about your team.</em></p><p>​</p><p>​</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f3bf6708714" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/analytics-team-wins-you-can-implement-today-4f3bf6708714">Analytics team — Wins you can implement today</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes a good data analytics question?]]></title>
            <link>https://medium.com/husprey/what-makes-a-good-data-analytics-question-6ed5decd1d48?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/6ed5decd1d48</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[data-analytics]]></category>
            <dc:creator><![CDATA[Thibaut Collette]]></dc:creator>
            <pubDate>Wed, 06 May 2020 07:46:49 GMT</pubDate>
            <atom:updated>2021-06-30T16:37:48.013Z</atom:updated>
            <content:encoded><![CDATA[<p>In our first <a href="https://medium.com/husprey/husprey-collaborative-home-for-data-analytics-teams-aef61c026fb2">blog post</a>, <a href="https://medium.com/u/b077ee87b53e">Joffrey Villard</a> exposed the 4 different steps of a data analytics process:</p><ul><li>❓Asking the data-related question</li><li>🕵️‍♂️ Gathering relevant data</li><li>💻 Analyzing data</li><li>📊 Delivering results</li></ul><p>Today, I wanted to take some time to share insights about the data analytics question itself. Why is it so hard to get it right? And actually, what makes a good data question?</p><h3>🤯 Why is it so hard to ask a good data analytics question?</h3><p>First of all, a non-technical user can ask data analysts help about a specific dashboard/KPI, or a product research or an operational issue being investigated. This list is actually never ending 😉. The scope of expected answers from one data question to another can vary drastically. Most of the time, to make things worse, answers are not unique <em>(answers contain their own bias — more on that on a later post)</em>.</p><p>Data literacy <a href="https://en.wikipedia.org/wiki/Data_literacy">[1]</a>, described as the ability to read, work with, analyze, and argue with data, is often a limiting factor for data usage in companies. Business users are not the ones to blame. Data tools usually are. From the beginning, they’ve preferred to focus on the engineering side and rarely provided specific UX to help <em>both</em> data novices <em>and</em> experts simultaneously.</p><p>Finally, interactions around data are a new kind of human communication, and as such they suffer from most of the common human communication issues: hidden/unspoken facts, unadvertised assumptions or distinct knowledge framework (between requesters and analysts).</p><h3>👍 What makes a good data question?</h3><p>A good data question will limit as much as possible the biases created by miscommunication.</p><p>When knowledge frameworks differ too much, because of background or experience, it’s important to say the extra words in order to limit the potentially wrong assumptions made by the counterpart.</p><p><strong>Concretely, it means that a description must support the question itself.</strong> From our experience, 4 main elements should appear in this description.</p><h4><strong>Context</strong></h4><p>The context is the why the question is asked. What was the process that required this question to be answered? With this context, analysts can make sure they frame the problem as expected. Also, it will allow them to leverage their history and provide a more relevant and complete answer.</p><p>Examples: “We want to assess our current Spain launch. We specifically would like to compare it with the launch in Italy last year.” / “Customer Support seems to receive a growing number of issues for our “Website” category. Can we get a quick assessment of the actual impact and if possible the reason of this change?” / “According to the last analysis, fraud on our API cost us 2M€ last year. What can be done data-side to minimize this loss?”</p><h4>Potential outcomes</h4><p>Alongside context, potential outcomes bring critical information to data analysts. How will this data be used? What decision can derive from the results? With those outcomes in mind data analysts can understand what is at stake and the criticality of the decision. Based on their experience, they can then wander in the data and provide the additional input that will help make an even better informed decision.</p><p>Examples: “This piece of data should finalize our investor deck” / “Goal is to make a decision about the new warehouse. Should we open it or not?” / “Based on the results, we will keep or remove the button on the product detail page”</p><h4>Recipients</h4><p>For a given context, the results of an analysis can be shared with audiences from different sizes or seniority: C-level, Finance or Marketing or Product teams, a single Team member, partners or 3rd-parties…<br>The same answer will be understood differently by people from different horizons. Once again, human communication at its finest. Listing the recipients of an analysis allows the analysts to put themselves in their readers’ shoes, and hence adapt their deliverables and messages (in terms of technical details, vocabulary, conclusions, etc.).</p><p>Examples: “This will be shared within the Finance team” / “We plan to communicate this information to our whole user base”</p><h4>Deliverables</h4><p>When someone comes and asks for a “simple extract”, it feels easy to specify file format. But no matter the type of analysis, requesters will always benefit from spelling out the expected deliverable. Those details also help analysts plan and allocate resources accordingly.</p><p>Examples: “Can we get the plain figure” / “I believe we can work together on a complete report” / “I would need this chart to include it in the sales deck”</p><p><strong>This to say, context is king 👑.</strong></p><p>When asking a data question, requester has to make sure the context is crystal clear. Data analysts should continue to ask follow-up questions, refining <strong>context, recipients, deliverables and outcomes. </strong>But the earlier those appear clear in the conversation the higher the chances to make every one happy, productive and to reduce biases.</p><h3>🥇 How do I make it happen in my company?</h3><p>Simple steps can help you start in the right direction:</p><ol><li>Publish a simple and yet already useful data request form either as a Google Form, a Typeform or a Slack webhook. <em>Ask in the comments or by email to receive our template.</em></li><li>Share internally a few case studies of previously done analysis. This can take between half a day and 3 days to complete but can get you off on the right foot and help Business Users know more about your teams’ work. (Important: include analysis from various complexity)</li></ol><p>And if you feel you learned something, please clap 👏 and share this article. It would mean the world to us.</p><p>Cheers ✌️</p><p>Thibaut —<em> Cofounder &amp; CEO @ </em><a href="https://husprey.com/"><em>Husprey</em></a></p><p>[1]: Data literacy, Wikipedia — <a href="https://en.wikipedia.org/wiki/Data_literacy">https://en.wikipedia.org/wiki/Data_literacy</a></p><p>[2]: How to ask an analyst a question, Mode Analytics (March 2015) — <a href="https://mode.com/blog/how-to-ask-an-analyst-a-question">https://mode.com/blog/how-to-ask-an-analyst-a-question</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*goBnpjDU2GYuz1JUZOOxYA.png" /><figcaption>Husprey logo</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ed5decd1d48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/what-makes-a-good-data-analytics-question-6ed5decd1d48">What makes a good data analytics question?</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Husprey — Collaborative home for data analytics teams]]></title>
            <link>https://medium.com/husprey/husprey-collaborative-home-for-data-analytics-teams-aef61c026fb2?source=rss----dbcd0d25d11---4</link>
            <guid isPermaLink="false">https://medium.com/p/aef61c026fb2</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[collaboration-tools]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Joffrey Villard]]></dc:creator>
            <pubDate>Mon, 23 Mar 2020 10:04:27 GMT</pubDate>
            <atom:updated>2020-03-23T10:04:27.579Z</atom:updated>
            <content:encoded><![CDATA[<h3>Husprey — Collaborative home for data analytics teams</h3><p>Welcome 👋</p><p>We’re very excited to start this journey with you!<br>In this first post, we explain why we decided to invest in this area and build the collaborative home for data analytics teams.</p><p><em>Feel free to clap, share comment and do not forget to join the waitlist at </em><a href="https://husprey.com/"><em>husprey.com</em></a><em>!</em></p><h3>The Data Analysis Process</h3><p>Based on our experience and many user interviews we’ve performed over the last months, here are our thoughts on the usual data analysis process and its common pitfalls.</p><h4>❓Asking a data-related question</h4><p>Business, Operations, Finance, Product and other teams all consume data to make relevant decisions in their area. If self-serve BI tools have been implemented and deployed, members of these teams can find answers to some of their data questions, but only when they are well defined and match information available in such tools.</p><p>In any other case, they need a <strong>data analyst</strong> to investigate their specific question.</p><blockquote>Let’s note here that such self-serve BI tools commonly claim they free data analysts from repetitive and low-value tasks. Indeed, most regular queries can be automated and data consumers can get results in some autonomy. However, they do not ease the overall data analysis workflow -only take care of execution steps-, and the more they get used, the more data analysts have to take care of their maintenance and support.</blockquote><p>Most of the time, data consumers have a high-level business- or operations-related question that first needs to be analyzed, split and translated into data-related ones. During this process, usual communication issues surface: differences in terms of professional culture, context awareness, vocabulary, general understanding of the company challenges, etc. can make this discussion tricky and lead to critical misunderstandings.</p><p>We believe it’s crucial to <strong>clearly write down what has been decided and operate afterwards in full transparency</strong> (in terms of prioritization, preparation tasks, findings, etc.). Keeping track of the preliminary discussions and underlying rationales participates in improving the traceability of key business decisions and in <strong>sharing knowledge across teams</strong>.</p><h4>🕵️‍♂️ Gathering relevant data</h4><p>When the requirements are made clear, the analyst gathers all the needed data. Most frequent questions then include:</p><ul><li>What data would I like to use at best?</li><li>What data can I use right now?</li><li>Are these data relevant / accurate / up-to-date?</li><li>What data did we use for similar analyses in the past?</li><li>What did we already use these data for?</li></ul><blockquote>To address these challenges, data catalogs and similar tools endeavor to map and document most of the data in the company. However, as they are global, address a governance topic and have to impact almost the whole company (from developers who write code that stores data, to analysts that use them, to sales who ask and read analyses report, to DPOs who supervise all data usage), their adoption is slow and they are of little help to the analysts for this step.</blockquote><p>We believe that keeping track of what data is actually used to perform a real, useful analysis is the best way to document the available data. <strong>A pragmatic approach to data management should be favored over a systematic (and unrealistic) one.</strong></p><h4>💻 Analyzing data</h4><p>As a third step, the data analyst uses her expertise in statistics, data mining and machine learning to carry out the actual analyses. Frequently, similar analyses have already been performed in the past, and the analyst could leverage any such past work if it were registered in a searchable repository. However, most archiving tasks are left to the lonely analysts, without clear guidance and anticipation (at best, we see dedicated folders with all source files on a shared drive).</p><p>We believe that these problems can be addressed by providing data analysts with <strong>dedicated tools that embed best practices</strong> from both statistics and programming worlds: restrictions and assumptions for particular statistical methods, usual techniques for a given problem; peer review, code versioning.</p><h4>📊 Delivering results</h4><p>Finally, the data analyst can gather all her results and deliver her findings in an appropriate way, depending on the purpose of the analyses, their audience and the nature of the underlying data -producing a one-off report, creating or updating a recurrent automated report or dashboard. Unfortunately, the traceability is rarely taken into account when delivering these results: they eventually reach some slides on which important decisions will be taken, with no simple mean to go back to the analysis itself or the source data.</p><p>We believe that the deliverables should be clearly linked to the results, the analysis itself, and the underlying data, so that <strong>the traceability of each data-driven decision is guaranteed.</strong></p><h3>Our Proposition</h3><p>At Husprey, we build <strong>the collaborative home for data analytics</strong>.</p><p>Based on a <strong>data-specific workflow</strong>, our SaaS application fosters <strong>collaboration</strong> with and within data teams.</p><p>We help business users to ask the questions the best way.</p><p>We help data analysts to bring speed and reliability to their process: search through what was done, reuse and spread knowledge.</p><p><em>Would like more details? Learn more (and register!) on our website: </em><a href="https://husprey.com/"><em>husprey.com</em></a></p><h4>A glimpse at our design mock-ups</h4><p><em>As a business user</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IFVonKxKpQZhU3-3.png" /></figure><p><em>As a data analyst</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SRpm9vsNelkQtVNl.png" /></figure><p><em>If you find it interesting don’t hesitate to clap for us and also share our first blog post ever. You can also email us or join our waitlist at </em><a href="http://husprey.com/"><em>husprey.com</em></a></p><figure><img alt="Husprey Logo" src="https://cdn-images-1.medium.com/max/1024/1*m6ljmvKrJn1otPxiHFoogQ.png" /><figcaption>Brand new Husprey logo. Thank you so much Amélie &amp; Zoé :D</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aef61c026fb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/husprey/husprey-collaborative-home-for-data-analytics-teams-aef61c026fb2">Husprey — Collaborative home for data analytics teams</a> was originally published in <a href="https://medium.com/husprey">Husprey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>