Analytics for directors

When developing dashboards with managers and directors, one learns that good directors never stops. They are always in action: coordinating, traveling, in meetings, talking or presenting. They are clever and brilliant, but they have no time at all.  They have almost no time for looking graphics, but when they need it, it should be quick and clear.

That working experience lead us to following principles for building successful analytics:

  • One picture is better than 1000 words. Everybody knows the difference of looking at a table with numbers and seeing them on a graph. Examining a table requires scrolling down the records, memorizing data and comparing them, and this takes long time. But our eyes can grasp a graph at once. Where is the minimum? Where is the maximum? How is the data distributed? All that happens in fractions of seconds. And that’s the power of information visualization. An enormous power.
  • Intuitive design. No help page! If you need an help page you have already lost. Use intuitive symbols for controls and steering.
  • Develop for smartphones. Develop 1st for smartphones. Our directors need the graphics, now, while traveling! Remember, if you can develop for smartphones you can develop for big screens as well.
  • Touch screen is “touch” screen. And it is about 12-14 mm radius. Don’t develop for children.
  • Every Pixel Counts!  Minimize your elements. Don’t distract the user.  Each screen elements should be either for steering or to carry data information.  Before a release, take your time and make a clean-up round. Remove or simplify your graphics. Minimize text usage.
  • Taylor your graphs to your client. Qlikview and Tableau are not written for directors. They are written for DevOps. The assumption there is that the user (the DevOp), will be finally able, with the given tools, to produce a graphic for the real  business user, who will finally use this graphics.  We use a different approach: we know our director and his needs, and we want to make a taylored graph for him. And we don’t want third party software between the data and the screen. We want full control of the screen, because we want to give our users excellent results!
  • One graph at a time.  Or: less is more. Each screen page should present one result and no more. Graphs should be clear and easy to understand. Don’t be scared to take responsability and  ownership of your graphs.  Guide the users through your analysis, instead of leaving them alone with lot of numbers.