Data Connection

Hi! Sample way to introduce dynamic category breakdown in small multiple using BLANK() within field parameter ⚡️⚡️ ___________________ ➝ In some cases small multiples will be a great choice, in others - not. Depending on the context, data etc. if we still want to have an option to see the overal trend / value without breakdown, and on the other hand display certain items as breakdown, this kind of field parameter might be usefull. ➝ Great side of this approach is ability to display 'overal' view using entire chart space and not only a single small multiple part (which would depend on how we structure our small multiple grid). ➝ The downside (besides the fact that sometimes such small multiple breakdown will not provide a transparent message etc.) is lack of automatic adjustments of grids (number of field is fixed in formatting pane and it will not match the amount of available items in given filter context). Have you ever found similar switch valuable? What works best for your use-cases? 💡💡 Best regards! __________ Link to interactive dashboard where you can find the full library of my already published Power-BI related linkedin posts. https://lnkd.in/eCHg_r-z #analytics #data #ux #ui #powerbi #excel #datavisualization #report #dashboard #reports #design #reporting #visualization #microsoftpowerbi #business #uidesign #uxdesign #layoutdesign #layout #kpi #company #businessanalytics #bi #storytelling #finance #pbinativevisuals #PBIcorevisuals

Building on yesterday's post, I want to highlight how the structure of narrative reports differs from that of data stories. Reports are typically structured around a comprehensive set of key focus areas, especially recurring reports (weekly, monthly, quarterly, etc.). 👉 Regional sales report: North, east, west, south 👉 Marketing channels report: paid search, display, email, social media 👉 Operations report: production output, inventory, uptime/downtime, labor productivity A narrative report will highlight key observations within each section with additional context and interpretation. However, there’s no guarantee that each section will have something notable to share each new period. When there is a meaningful observation to share, the narrative report will surface them as potential “story threads.” These threads are just the "beginnings" of potential stories, which need further analysis to understand and explain what’s happening. A single narrative report could feature several of these story fragments that may or may not be related. A narrative report’s underlying structure will also not change to accommodate different storylines because that would lead to inconsistencies between recurring reports. In contrast, a data story singularly focuses on explaining a specific insight and uses a narrative arc to communicate it. A data story strives to tell the whole story rather than just bits and pieces. It is a diagnostic communication vehicle rather than a primarily descriptive one. As the diagram shows, each curated data scene in a data story advances the audience’s understanding and contributes to the overall narrative. Anything that doesn’t support the story is removed; otherwise, it will detract from the intended message. Structure is one of the main reasons why recurring reports shouldn’t be considered data stories. Every data story is based on a unique set of observations and insights. No two data stories will be the same. When reports and dashboards are designed to be repeatable and consistent, you can’t expect them to perform like stories, too. Both narrative reports and data stories are essential communication tools in an #analytics team’s toolbox and serve different purposes. I hope explaining their differences helps you recognize their strengths and unique roles. Again, I highly recommend checking out my article if you’d like to learn more about other differences between narrative reporting and data storytelling. Blog post: https://lnkd.in/gz2cFABV What are your thoughts on narrative reporting and data storytelling?