2 Replies Latest reply on Feb 5, 2019 2:36 PM by Nicholas Edalgo

    Ideas for visualizing exception reporting

    Nicholas Edalgo

      Currently we're using a dashboard that has lots of mini-tables in it for exception reporting.  The goal is for the audience to see it and if their element pops on the report, they need to take action by remedying the issue.  Problem is, it's very bland with just tables.  Filters which are adjusted every cycle are used to display what pops on the report.


      Does anyone have a creative way they use to show exception reporting?  I'm trying to enhance aesthetics.  Right now it works, it's just ugly.

        • 1. Re: Ideas for visualizing exception reporting
          Jim Dehner

          Interesting -

          A lot depends on the audience - engineers are a lot different than sales guys


          You mention a lot of little tables - making it sound like a patchwork - and lots of filters


          you may want to consider leveraging set actions to add some action to the presentation

          there are 2 attached that I've used in presentations - one uses asymmetric symmetry to create a drill down

          the other uses set actions on a dashboard to identify products performing better/worse YTD see the scatter plot - - actions can be applied to geography or market segments


          Don't know how applicable to your specifics but it may give you some ideas



          If this posts assists in resolving the question, please mark it helpful or as the 'correct answer' if it resolves the question. This will help other users find the same answer/resolution.  Thank you.

          • 2. Re: Ideas for visualizing exception reporting
            Nicholas Edalgo

            Thanks for those examples.  In this instance it's just projects being displayed that are not in compliance for any of about 10 reasons.  So if a project is marked as 'completed' in this column but another column with the completed date is blank, the filtering causes it to pop on the report.  The 10 or so iterations of that all work independently and each has its own table with a list.  It's like a quality control exception list.


            So I could do a pull down, but then it's just replacing table stacking with items in a pull down that users would have to manually go through.  There may not be a better way to display this though.