<?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 Simon Temmerman on Medium]]></title>
        <description><![CDATA[Stories by Simon Temmerman on Medium]]></description>
        <link>https://medium.com/@simontemmerman?source=rss-dc0aae4286d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hM5grlS_P5x1EOikjVv7wg.jpeg</url>
            <title>Stories by Simon Temmerman on Medium</title>
            <link>https://medium.com/@simontemmerman?source=rss-dc0aae4286d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:01:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@simontemmerman/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[5 steps to improve your charts]]></title>
            <link>https://uxdesign.cc/5-steps-to-improve-your-charts-3c2a78b0c3a8?source=rss-dc0aae4286d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c2a78b0c3a8</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[charts]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Simon Temmerman]]></dc:creator>
            <pubDate>Mon, 10 Sep 2018 06:20:51 GMT</pubDate>
            <atom:updated>2018-09-12T17:06:52.519Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 steps to improve your charts (Act 2)</h3><h4>Turn your charts into stories people can actually read.</h4><p><em>In this series I would like to discuss data visualisations I come across in my work and improve upon it using a five step process:</em></p><ol><li>Context</li><li>Declutter</li><li>Align</li><li>Choose an more appropriate display medium</li><li>Highlight</li></ol><p><em>Every post will contain a before and after with my thought process in between. At the bottom a link will be provided to the online notebook for people interested in the code for the charts (created in </em><a href="https://d3js.org/"><em>d3</em></a><em>).</em></p><p><a href="https://uxdesign.cc/5-steps-to-improve-your-charts-716383325900"><em>Post 1 of this series</em></a></p><p>They ol’ double Y axis:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*kXCp4xIB0TqhMn5bBPOddw.png" /><figcaption>Starting point. <strong>Disclaimer: </strong>I’m not saying this is a bad visual, just that it could be improved.</figcaption></figure><p>Initial remarks:</p><ol><li>Double Y axis are often used in the dashboards I see. While not bad, they can be hard to interpret and make the chart more complex than necessary.</li><li>A common technique that tools employ is colouring the 2 Y axes so the bars and lines can be matched more easily with the correct axis. Next to not being super intuitive, color can be used more strategically.</li><li>The axis for bars has to start at zero. That’s because we compare the lengths of the bars pre-attentively. Not doing so results in a lie factor. While this principle is applied correctly here, it comes with a downside: changes in the headcount are hard to distinguish.</li><li>The budget line acts as a target. Because of the small deltas, it’s hard to make comparisons. The dots on the line make it even harder, they are not serving a purpose here.</li><li>No title or axis labels are present</li><li>Placing the legend at the bottom is not a good visual hierarchy, people will have to scan down before being able to identify the measures. A better strategy would be to label the axes or data points.</li></ol><p><strong>1 Context!</strong></p><p><em>A chart is meant to convey a story, something that will resonate with the people using it. Without context (</em><strong><em>Who </em></strong><em>will use it?, </em><strong><em>Why </em></strong><em>are they using it?) you can’t design your charts properly.</em></p><blockquote>See <a href="https://uxdesign.cc/dashboard-requirements-gathering-revised-90b2061a9385">my other post</a> on an effort to make this requirements gathering process easier</blockquote><p>For this particular chart, let’s assume we are a HR manager looking at the recruitment strategy. Do we meet our budgeted headcount? Do we need to focus more on retention or recruitment?</p><p>2 Declutter</p><p><em>Decluttering means removing all unnecessary elements from the chart. Everything we add to the chart will increase the cognitive load for our users, making the chart harder to interpret (think colors, labels, axis lines, legends, grid lines,…).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*fPit67jO8KUGixQWEudtjg.png" /><figcaption>Everything is de-emphasised now. A good guideline is to only highlight about 10–15% of the entire visual.</figcaption></figure><p><strong>Improvements</strong></p><ul><li>The left axes ticks are divided by thousands. I often find it more intuitive to reason in K’s than the whole number.</li><li>All axes are de-emphasised with a light grey color.</li><li>The legend is removed and put in the title (with no colours for the moment). This creates a better visual hierarchy.</li><li>The dots are removed from the lines. This makes the view easier on the eyes without losing anything.</li><li>The x axes labels are renamed to months and the year is put into the title. This allows for a more natural flow.</li><li>The axes are labeled</li><li>The budget line is broken up. The advantage is twofold: first of all it shows the differences in budget across months more clearly and as a consequence, makes it way easier to compare the bars to the budget lines. Secondly, people reading it will know intuitively it is a target without the need to specify that.</li></ul><p>3 Align</p><p><em>Properly aligning all items makes people perceive the chart as easier and thus more accessible to read. When done properly it can create a clear visual hierarchy, guiding the users eyes to where they need to be.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*Wr3tmM43W1lx31FidG5jqg.png" /><figcaption>The top left is the first place our eyes will look, seeing the title. Afterwards they will see the labels and then they can look at the chart data. Like this they have all the context they need to interpret the chart correctly.</figcaption></figure><p><strong>Improvements</strong></p><ul><li>We aligned the axis labels with the first tick on the axis.</li><li>We aligned the title to the left, creating a clear visual hierarchy.</li></ul><p>4 appropriate display medium</p><blockquote>I’m working on a guide to show what charts are useful in what situation. I’ll update the link here when it’s finished!</blockquote><p>As mentioned before, bars make it hard to see differences in the evolution because they have to start from zero. Dot plots do not have that problem:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*u2XqyTrO8_ptW8clCOXQjQ.png" /><figcaption>Notice the Y axis is not starting from zero now. We can compare the position of dots just as good as we can compare the length of bars.</figcaption></figure><p>This makes the delta’s clear and make comparisons easier. The line is still distracting (because of the overlap with the lines and dots) so let’s try a different display than 2 Y axis:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*cl0ATSAGjWhsn0J0BWms1g.png" /><figcaption>Broke up the single chart in two charts. This lets us focus on the two different measures. They share the x axes so they can be interpreted together.</figcaption></figure><p><strong>Improvements</strong></p><ul><li>Easier to compare headcount to the budget</li><li>Easy to see the evolution of turnover</li><li>Easier to spot correlations between the two (like in march there was a local peak in turnover and the headcount was an all time low)</li><li>Removed the axes lines as they are just a bit more clutter we don’t need</li></ul><p>5Highlight</p><p>We can now use color and text to highlight our message and guide the users eye:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*bhs_0EwuH33j1PtrY5Dkgw.png" /><figcaption>Highlighting only the part after June 2017 makes the rising turnover jump out together with the effect on the headcount.</figcaption></figure><p><strong>A link to the </strong><a href="https://beta.observablehq.com/@temmermans/turning-charts-into-stories-act-2"><strong>notebook can be found here</strong></a><strong>.</strong></p><p>See other improvements? Not agreeing with some of my remarks? Came across an interesting visual you’d like to see discussed in one of the next posts? Please share in the comments! 🤓</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c2a78b0c3a8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-steps-to-improve-your-charts-3c2a78b0c3a8">5 steps to improve your charts</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 steps to improve your charts]]></title>
            <link>https://uxdesign.cc/5-steps-to-improve-your-charts-716383325900?source=rss-dc0aae4286d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/716383325900</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[charts]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Simon Temmerman]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 10:11:02 GMT</pubDate>
            <atom:updated>2018-09-10T06:21:24.905Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 steps to improve your charts (Act 1)</h3><h4>Turn your charts into stories people can actually read.</h4><p><em>In this series I would like to discuss data visualisations I come across in my work and improve upon it using a five step process:</em></p><ol><li>Context</li><li>Declutter</li><li>Align</li><li>Choose an more appropriate display medium</li><li>Highlight</li></ol><p><em>Every post will contain a before and after with my thought process in between. At the bottom a link will be provided to the online notebook for people interested in the code for the charts (created in </em><a href="https://d3js.org/"><em>d3</em></a><em>).</em></p><p><a href="https://medium.com/@simontemmerman/5-steps-to-improve-your-charts-3c2a78b0c3a8"><em>Post 2 of this series</em></a></p><p>I recently bumped into a chart like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*ZRLeuEp47cfKZ-K4XABHrw.png" /><figcaption>Starting point. <strong>Disclaimer: </strong>I’m not saying this is a bad visual, just that it could be improved.</figcaption></figure><p>Initial remarks:</p><ol><li>This is often times called a <strong>spaghetti chart</strong>. Why? Because the lines are constantly overlapping. The lines that are overlapping are forming a different shape (like a ❌). Because this differs from the norm (a line) it will draw our attention. This is called a preattentive attribute. Because a lot of lines are overlapping, we don’t know where to look first.</li><li>Color could be used more strategically</li><li>Some clutter is making the chart more noisy than necessary</li><li>My eyes are constantly going back and forth between the legend and the lines.</li></ol><p><strong>1 Context!</strong></p><p><em>A chart is ment to convey a story, something that will resonate with the people using it. Without context (</em><strong><em>Who </em></strong><em>will use it?, </em><strong><em>Why </em></strong><em>are they using it?) you can’t design your charts properly.</em></p><blockquote>See <a href="https://uxdesign.cc/dashboard-requirements-gathering-revised-90b2061a9385">my other post</a> on an effort to make this requirements gathering process easier</blockquote><p>For this particular chart, let’s assume we want to invest in movies and we want to have a good look at the evolution in profits the different genres had. We have to easily compare them against each other.</p><p>2 Declutter</p><p><em>Decluttering means removing all unnecessary elements from the chart. Everything we add to the chart will increase the cognitive load for our users, making the chart harder to interpret (think colors, labels, axis lines, legends, grid lines,…).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*gzV_T2pNb5zUwgy8zyq2kw.png" /><figcaption>Everything is de-emphasised now. A good guideline is to only highlight about 10–15% of the entire visual.</figcaption></figure><p><strong>Improvements</strong></p><ul><li>We removed the legend and labeled the lines directly, no more back and forth between the legend and the data!</li><li>We de-emphasized the labels, titles and axis, making the data more prominent.</li><li>Formatted the y axis tick labels. We don’t need to see the whole number when it is up in the millions.</li></ul><p>3 Align</p><p><em>Properly aligning all items makes people perceive the chart as easier and thus more accessible to read. When done properly it can create a clear visual hierarchy, guiding the users eyes to where they need to be.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*osinFglC-M6G5n2Zlwhw8Q.png" /><figcaption>The top left is the first place our eyes will look, seeing the title. Afterwards they will see the labels and then they can look at the chart data. Like this they have all the context they need to interpret the chart correctly.</figcaption></figure><p><strong>Improvements</strong></p><ul><li>We aligned the axis labels with the first tick on the axis.</li><li>We aligned the title to the left, creating a clear visual hierarchy.</li><li>Turned the title into something a bit more engaging, making it more likely that people will inspect the chart further.</li></ul><p>4 Highlight</p><p><em>The chart is still hard to read. Highlighting can be done with colours or emphasised text to immediately draw the users attention. This can only be effective when used sparingly! Remember the 10–15% highlight rule 👍</em></p><p>Let’s assume here we are only interested in the family genre:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*MLBi9PBVZvsHNfpc3UGslQ.png" /><figcaption>Using color to to highlight the family genre, making it very easy to see the trend</figcaption></figure><p>The grey lines provide some context, but comparisons can’t be made yet.</p><p>5 appropriate display medium</p><blockquote>I’m working on a guide to show what charts are useful in what situation. I’ll update the link here when it’s finished!</blockquote><p>A mistake I see people make often is trying to squish everything into a single chart. This degrades the readability. A display that often helps with something like this is a <strong>small multiple. </strong>Adding a small legend below the title will bring us to the end of this chart refactor:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*vSdS5tlOZ4Yx10lYQIbZ1A.png" /><figcaption>End point. <strong>Pro tip:</strong> always make sure you use the same axis scaling in a small multiple. This will make it very easy to make comparisons, even over multiple charts.</figcaption></figure><p><strong>A link to the </strong><a href="https://beta.observablehq.com/@temmermans/turning-charts-into-stories-act-1"><strong>notebook can be found here</strong></a><strong>.</strong></p><p>See other improvements? Not agreeing with some of my remarks? Came across an interesting visual you’d like to see discussed in one of the next posts? Please share in the comments! 🤓</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=716383325900" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-steps-to-improve-your-charts-716383325900">5 steps to improve your charts</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning Charts Into Stories]]></title>
            <link>https://medium.com/series/turning-charts-into-stories-14940b38359a?source=rss-dc0aae4286d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/14940b38359a</guid>
            <dc:creator><![CDATA[Simon Temmerman]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 15:19:09 GMT</pubDate>
            <atom:updated>2018-09-03T15:19:09.073Z</atom:updated>
            <content:encoded><![CDATA[<p>In this series I would like to discuss one interesting data visualisation every week I came across in my work and improve upon it using a four step process:</p><ol><li>Context</li><li>Declutter</li><li>Align</li><li>Highlight</li></ol><p>Every post will contain a before and after with some of the key points as bullets. A link will be provided to the online notebook for people interested in a more detailed breakdown together with the code for the charts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*jWa-DVlvufuEJ85o8iG6jA.png" /></figure><ol><li>This is often times called a spaghetti chart. Because a lot of lines are overlapping, we don’t know where to look first.</li><li>Color could be used more strategically</li><li>Some clutter is making the chart more noisy than necessary</li><li>My eyes are constantly going back and forth between the legend and the lines.</li></ol><p><strong>A possible solution</strong> could be:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*ZIJayFebZNjAuRmCyYYt7g.png" /><figcaption><a href="https://beta.observablehq.com/@temmermans/turning-charts-into-stories-act-1">Read more</a></figcaption></figure><p>If you have a visualisation you would like me to discuss, drop me a line!</p><p>Let me know if you have ideas to improve this series!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*9cdY0YIiOr4OCpY72SYong.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14940b38359a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dashboard design & requirements: the struggle and the solution]]></title>
            <link>https://medium.com/delaware-pro/dashboard-requirements-gathering-revised-90b2061a9385?source=rss-dc0aae4286d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/90b2061a9385</guid>
            <category><![CDATA[cards]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[Simon Temmerman]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 17:24:55 GMT</pubDate>
            <atom:updated>2018-08-31T16:35:29.012Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Simon. I’m a front end enthusiast at <a href="https://www.delaware.pro/en-be">delaware</a>, working on all kinds of data &amp; analytics projects 📈.</p><p>Today I wanted to talk to you (yes, just you!) about the struggle of building dashboards and reports for the business community. Not the technical challenges that come with creating a data model or making sure your applications are intuitive and pleasing on the eyes but rather about how to get <strong>what’s inside a user’s head</strong> and translate that to clear <strong>requirements for data visualisation</strong>.</p><p>After you read this post and are in awe of the things I came up with I’d love to see all of your praise in the comments! (just kidding👼 <em>I’d love to hear your remarks so I can further improve</em>)</p><p>Ready? Get set. Let’s go 🚀.</p><p>Data visualisation is hard. Tools these days make it very easy to create bars, lines and pies and slap them on a page. So easy in fact, that the only thing clients seem to care about when planning a new analytics project is how many different charts the tool can produce. Afterwards it’s just a matter of making the tool available to your employees, right? So they can make shiny things? 💠 Sadly, no… A strategy like this will render the investment pointless. Too many things will be created that aren’t fully tapping into the potential of dashboarding and people will lose faith… and go back to everybody’s good friend excel.</p><p>Data visualisation is a lot more than picking a tool and creating charts. It’s about a thorough understanding of people and their needs (and appreciating the change a project like this brings for them). You need a good understanding of their <a href="https://en.wikipedia.org/wiki/Mental_model">mental model</a>. Your dashboards need to reflect that mental model and present it as a story they can read. One could almost argue we need careful planning and requirements gathering!</p><p>You know what else? Requirements gathering is hard. The hardest part.</p><p>I see it all the time: dashboards and reports are developed only to never be opened again. Is that because the people who should use are so reluctant to change? I don’t believe they are. I think it’s mostly due to not understanding the needs correctly (or not taking the time to try and understand them).</p><p><em>So just organise a workshop and ask them what they want! </em>🙄</p><p>It’s not that simple. Like Henry Ford said:</p><blockquote>If I asked people what they wanted, they would have said faster e̵x̵c̵e̵l̵ horses.</blockquote><p>People are really bad at predicting a future situation. What we are good at though is unpacking a problem when it is laid out visually in front of us. Drawing to the rescue! ✏️</p><blockquote><a href="https://www.invisionapp.com/blog/ux-design-sketching/">A problem visualised is a problem halved</a></blockquote><p>I noticed in workshops that starting to sketch was to daunting for a lot of people. So I needed an alternative. That’s when I thought of the possibility of using a <strong>card deck</strong>.</p><p>Why cards? Research has shown (Touch Neurology, 2011) that cards will clear your mind and improve your thinking process. It will help focus on the task at hand and gives the developer of the dashboard a good opportunity to really get to know the problems you are trying to solve.</p><p>For the cards I came up with the following structure, which I like in all my dashboards:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OhN_vpWwsFCh548wL3hIJg.png" /></figure><p>1 <strong>Scan the big picture</strong></p><p>That’s the job of the KPIs displayed on the most prominent place of the screen. For those I included KPI cards:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*7wOdDd-2NHnirZtqZ8hReg.png" /><figcaption>With on the front the possibility to write down a sample metric with title (titles are important, makes everyone in the workshop agree on what they are showing) and on the backside some more info. The charts that tell more about the metric are the link to step 2.</figcaption></figure><p>Note that you can write on the cards with a dry-marker and wipe them clean. I still wanted for people to write down notes and thoughts.</p><p><strong>2 Zoom in on important details</strong></p><p>One of two possibilities:</p><ul><li><strong>Filters</strong>: I don’t like filters on dashboards. As humans we are not equipped to make comparisons if we need to switch views all the time. We need the info all at once. However, it can be a good way to save screen space for information we do not need to see together.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*c_eZ7wAs3sw8aX5Jhyj3Lg.png" /><figcaption>Again with possibility to write down some sample values we need to filter on and some more notes (like what charts need to filter?)</figcaption></figure><ul><li><strong>Charts</strong>: when well designed, charts offer the possibility of instant insight. Which is what we are aiming for in a dashboard. I created a set of 40 charts (only the ones I believe belong on a dashboard, sorry area charts 😢) with explanation on how to interpret them and in what context they work best.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*wtf7QWOsOOlAk5tNS0yJrA.png" /><figcaption>The front shows an empty axis, to write what we want to show. Other cards also show legends when multiple colors are being used. The yellow boxes show the different categories this chart can be used in. Options are: Part to Whole, Deviation, Magnitude, Correlation, Change over time, Spatial, Distribution and Ranking.</figcaption></figure><p>For every chart participants also need to answer these two questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*CpuAATMWklF_oQabUMQRQw.png" /><figcaption>A dashboard is all about actionable insights. If the second question can’t be answered, the chart does not belong on a dashboard.</figcaption></figure><p>3 <strong>Link to supporting details</strong></p><p>This can be achieved by clicking or hovering over a chart. It can show some more details in a popup or redirect to another report. It can even link to an excel. Depending on the technology, filter values can also be passed around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/182/1*NPRWKJmNlEGk8QDZenlD_g.png" /><figcaption>A small card that can be added to a chart to define some functionality when someone interacts with the chart.</figcaption></figure><p>After trying this out, I noticed things got messy because the cards were flying all over the table 🛸 I then decided to make the <strong>cards magnetic and added a magnetic board</strong>. Added benefit is it mimics the constraints of the screen size. This makes people aware of the fact they can’t throw anything they want on the screen.</p><p><strong>Context, context, context</strong></p><p>An analytics project is more than visuals alone. What about data sources and IT infrastructure? That’s why I also created a board that I call the <strong>Lean Analytics Canvas </strong>(after the <a href="https://strategyzer.com/canvas/business-model-canvas">business model canvas</a>). It can provide vital context together with the mockups you create and is easy to iterate over.</p><p><em>This is something I’ll discuss in another post, I don’t want to make this one too long</em> 👶</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*IT9b2TUqplEbDp6XuIcslg.png" /><figcaption>Overview of the cards and boards</figcaption></figure><p>The intention of the cards is to define the requirements of a dashboard in a fun and engaging way for both the developer as the people who will use it. I believe taking an approach like this will result in better products that will actually be used.</p><p>What are your thoughts? Experienced anything similar? See potential for improvement? I’d love to hear it in the comments!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90b2061a9385" width="1" height="1" alt=""><hr><p><a href="https://medium.com/delaware-pro/dashboard-requirements-gathering-revised-90b2061a9385">Dashboard design &amp; requirements: the struggle and the solution💡</a> was originally published in <a href="https://medium.com/delaware-pro">delaware</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>