Skip to main content

This is a general question that I've always struggled with.  How do people usually approach building dashboards, as far as what items to place in first (maps, charts, text, etc.), sizing the blocks, picking out the right size for the dashboard?  I feel like I spend so much time resizing blocks once I add a new sheet to the dashboard, or when I change the height of it, maybe it's just the way it is but I wanted to get other people's input on whether I'm making it unnecessarily difficult for myself.

5 answers
  1. Apr 23, 2019, 4:09 PM

    Adam,

    Your question is why I recommend floating as much as I do.  It creates a different analytical cycle - in that you're less tethered to the items that go in first being prominent and - especially for me - the distraction of items resizing and shifting vanishes.  Fair warning: there is a massive learning curve and the first 3 dashboards built in this transition are torturous.  And then....something clicks.

     

    You can see in the TDT how messy this can be, the iterations, the going back and forth, and the time to let it sit.  The analytical cycle continues heavily in dashboard composition and perhaps this is something that we don't discuss enough.  I think we perpetuate the myth that the analysis is in the charts and not the composition of the dashboard.  In reality, composing our findings into a sensible dashboard can be the hardest job.

     

    Here's what I recommend:

    1. Hit the float button.
    2. Write out a focused question, either as a title, on a sticky note, or within the dashboard.  The hard part here is a focused question.  So many people push for something that answers 'everything'.  Everything sets you up to fail.
    3. Throw charts on the dashboard to determine what answers this question.  One will provide a more high level 'good news/bad news' easy/fast answer.  This is your first chart.  Some call it the moneyshot. All other charts add nuance to your answer, either supporting it further or providing the caveats that need considered.
    4. Get it to a point that seems mostly finished and walk away for 24 hours if at all possible.  You need the break to see it. 
    5. Finish, tidy, align after the resting period.  You may also make different charts or change things entirely.

     

    The other long term item is to add a cycle where you sit with the end user.  Ideally, this comes before you ever build.  How does that person do the work?  Where do they go for information, what key numbers matter to the role, and what decisions are made?  Aim to make that easier and success will follow.

     

    Cheers.

0/9000