<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aurélien Vautier on Medium]]></title>
        <description><![CDATA[Stories by Aurélien Vautier on Medium]]></description>
        <link>https://medium.com/@aurelienvautier2?source=rss-433ff92faeb4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pWc1g4zQuTG9uKyr6gtBbw.png</url>
            <title>Stories by Aurélien Vautier on Medium</title>
            <link>https://medium.com/@aurelienvautier2?source=rss-433ff92faeb4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:43:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aurelienvautier2/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[When Dataviz Self-service backfire on readability]]></title>
            <link>https://medium.com/@aurelienvautier2/when-dataviz-self-service-backfire-on-readability-ac2430460a5f?source=rss-433ff92faeb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac2430460a5f</guid>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Aurélien Vautier]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 14:06:40 GMT</pubDate>
            <atom:updated>2024-06-06T14:06:40.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y3LtNi8k0pl7BSef.png" /></figure><p>Companies are creating more and more dashboards, unfortunately, in this frantic race, quantity inevitably takes priority over quality. A few years later, we find ourselves in debt with dashboards that are difficult to understand and need to be redesigned.</p><h3>When Dataviz Self-service backfire on readability</h3><p>Excessive use of self-service data can lead to information overload and decision paralysis, preventing employees from taking action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v51vFomwEB4DJe0B.png" /></figure><p>The ambition to deploy self-service to all means that the business has to learn new techniques and methods to acquire for lack of time, desire or knowledge gap.</p><h3>4 ways to improve readability</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*RRLBTZdl-2sVl06F.png" /></figure><p>When coaching Data Analysts or Dashboard Designers, one of the things I come across most often is information overload. The cause of the creation of these enormous dashboards is often a failure to diplomatically say ‘no’ to the demands of the business.</p><p>How can this be remedied?</p><ol><li>Hire a Data Product Managers who focus on requirements</li><li>Create a Data Design Process</li><li>Getting the business to understand and adopt Data Visualization and your company’s BI tool</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*Ax7ovPe4mmMPs1I4.png" /></figure><p>Dashboard text is often all the same size, but the way it is prioritized helps to guide the user’s eye to the most significant elements.</p><p>The most important KPI on the dashboard should be 22 px, while the Last refresh date should be 9 px.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*sfrLpy-96S6TBuxQ.png" /></figure><p>When it comes to fonts, less is more. Don’t look for originality, or even for any connection with your branding. Dashboards are first and foremost useful, not stylish.</p><p>A sans serif font with different weights will do the job just fine.</p><p>I’m particularly interested in these fonts: Roboto, Inter, Rubik, Karla…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*n46Y91tzhFGD-dyB.png" /></figure><p>A classic mistake is labels that are truncated or rotated vertically. We are sometimes tempted to rotate our texts to save space, but we must always bear in mind what is most important for the user: the <strong>readability </strong>and <strong>intuitiveness</strong> of the dashboard.</p><p><em>Originally published at </em><a href="https://www.datavizclarity.com/blog/when-dataviz-self-service-tools-backfire"><em>https://www.datavizclarity.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac2430460a5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exposing the Hidden Pitfalls of ‘Cockpits’ in Data Visualization]]></title>
            <link>https://medium.com/@aurelienvautier2/exposing-the-hidden-pitfalls-of-cockpits-in-data-visualization-f05184be0cf6?source=rss-433ff92faeb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f05184be0cf6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Aurélien Vautier]]></dc:creator>
            <pubDate>Mon, 19 Jun 2023 10:27:32 GMT</pubDate>
            <atom:updated>2023-06-21T07:54:17.888Z</atom:updated>
            <content:encoded><![CDATA[<p>The term cockpit is increasingly used in everyday life. It’s the new buzzword that, seemingly out of nowhere, is trying to sweep aside “Dashboards”, which themselves had already had to deal with “Reporting”.<br>What is a Cockpit ? What’s the difference with a dashboard ? What are the hypothetical impacts of building one ?<br>First, let’s dive in the etymology behind the word “Cockpit”.</p><h4><strong>Etymology :</strong></h4><blockquote>The original meaning was literally “pit where a cockfight happens,” and in the 1700s <em>cockpit</em> became the Royal Navy’s term for the area where a <em>coxswain</em>, or ship’s pilot, was stationed. <a href="http://www.vocabulary.com/">www.vocabulary.com</a></blockquote><h4>Within a data environment</h4><p>While not officially defined, “cockpit” typically represents a large collection of charts and indicators used for control and decision-making.</p><p>In the following five points, I will outline the reasons why I find this term problematic :</p><h4>1 — Encourages visual overloading</h4><p>The illustration below demonstrates how a cockpit becomes overwhelmed with numerous charts and KPIs, resulting in stakeholders becoming psychologically detached from a clear understanding of their activities.</p><p>The famous “Less is More” is no longer invited to the party.<br>More charts = More pixels = Less clarity</p><figure><img alt="More charts = More pixels = Less clarity" src="https://cdn-images-1.medium.com/max/1024/1*-SKOzQVruX-WAwc7BBKf6g.png" /></figure><h4>2 — Encourages excessive data sources and data volume</h4><p>One of the pitfalls often seen in teams using the wrong terminology (report, dashboard, cockpit, dataviz…) is that they haven’t yet adopted best practices for data modeling and data visualization.</p><p><strong>The request : “</strong>We need a cockpit that facilitates cross-functional monitoring of the company’s activities, and allows us to get into the details of any services we want”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P3H3dRkX2fB7kwcLqhX9Jw.png" /></figure><h4>3— Overemphasis on control and command</h4><p>A cockpit with its inherent emphasis on control can pose change management challenges. Moving from reports to dashboards often involves overcoming the obstacle of abandoning the sense of control usually represented by cell form and reports.</p><p>It would be easier to make users shift their mindsets from Excel to a Cockpit, compare to a Dashboard. A Cockpit often keeps this same sense of details, high granularity and the use of a multitude of charts. This is less the case for a dashboard where we aim to aggregate data, setup visual exploration and embrace a minimalist approach. The gap here is way more difficult to cross.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_LkBhjTdOlwMtPv84FE7Q.png" /></figure><h4>4 — Misalignment with user familiarity</h4><p>The term “cockpit” draws an analogy from aviation, which can be unfamiliar and even intimidating to many business intelligence users. Unlike pilots, who experience extensive training and have specialized knowledge of cockpit controls, business professionals from various backgrounds engage with data visualization interfaces. Using the term “cockpit” may create a disconnect and make users feel overwhelmed, hindering their ability to engage with and make the most of the data available to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pc7Z69psVX-PpoC3WjQ4LQ.png" /></figure><h4>5 — Time To Market</h4><p>The sooner your dashboard is available in the company, the sooner you can start generating ROI. Time to market directly impacts the product’s potential goal, allowing you to capitalize on new opportunities and drive business growth. A shorter Time To Market reduces the time between launch and initial feedback, enabling you to refine and evolve your product in the right direction.</p><p>Unfortunately, Cockpits are quite long to build because of the complexity related to several points : <br>- High number of datasets<br>- Lack of methodology for this kind of demand<br>- Lack of UX expertise in the datavisualization ecosystem <br>- Difficult to reconcile diverse requirements and opinions.<br>- High number of people involved<br>- Expectations and pressure are higher when it comes to cockpits (often dedicated to a broad population or top management).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRMuc1DnUNe9FZjCSmqFNQ.png" /></figure><h4>Conclusion :</h4><p>The naivety surrounding the use of the term “Cockpit” in business intelligence highlights the need to re-evaluate our terminological choices. By adopting a more suitable language, such as “dashboard”, we can improve clarity and promote effective data visualization practices.</p><p>Let’s reimagine our terminology, if necessary, to create more intuitive data visualization experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f05184be0cf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>