Your Tableau Dashboard Needs Two or Three Views, Not Eight

1. Why two or three, and where that number comes from

Before the explanation: you have eight finished sheets and one dashboard. How many of them would you put on it?

Two or three. That's not a taste call, it's Tableau's published guidance: "In general, it's a good idea to limit the number of views you include in your dashboard to two or three."

The reason is about attention rather than about screen space. A dashboard is read, and a reader gives it one pass. Every view you add divides that pass. Four views means each one gets a quarter of the attention that one view would have had, and none of them gets long enough to land.

There's a second cost that's easier to miss. Adding a view doesn't just take attention from the others, it takes away the reader's sense of which one mattered. A dashboard with one clear view and two supporting ones tells the reader where to look. A dashboard with eight equal panels tells them to work it out themselves, which is the job you were supposed to do.

The number isn't sacred. Four views can work when three of them are small supporting numbers rather than full charts. But if your answer to "how many views" is six or more, the honest problem is usually the next section.

2. The filter that decides which sheets survive

Before the answer: two people ask for the same dashboard. One runs the sales team, one runs the warehouse. Should they get one dashboard or two?

Two. And this is the whole idea of the page, because trying to serve both with one dashboard is where crowding actually comes from.

Tableau puts the standard plainly: "The best visualizations have a clear purpose and work for their intended audience." Those two things travel together. A purpose without an audience is a topic, and an audience without a purpose is a mailing list.

So the filter is one sentence, and you write it before you drag anything onto the canvas.

This dashboard answers [one question] for [one named person or role].

Then take each finished sheet in turn and ask whether a reader needs it to answer that question. Not whether it's interesting, and not whether it took you two hours to build. Whether the question can be answered without it.

Say out loud what happens to a sheet that fails that test, before reading on. It doesn't get deleted. It goes onto a different dashboard, for the audience it was actually serving, or into the appendix of the deck. The sunk cost is the reason people keep views, and moving a view somewhere useful is what makes it possible to let go of.

Picture your own busiest dashboard for a moment. How many separate people would you name if you had to say who each view was for? If the answer is more than one, you have found the crowding.

3. Where each surviving view goes

Before the explanation: your dashboard has one headline view and two supporting ones. Which corner does the headline go in?

Upper left. Tableau's guidance is to place your "most important view so that it occupies or spans the upper-left corner," and the reason it gives is that "most viewers scan web content starting at the top left."

That's worth taking literally. The upper-left view is your headline whether or not you meant it to be, in the same way the first sentence of a paragraph is its topic sentence whether or not you wrote it that way. If a filter panel is sitting up there, your headline is a filter panel.

Three placements that follow from it:

One more move that costs nothing. Give the dashboard a title that states the finding rather than the subject. "Regional sales" names a topic. "The West is carrying two thirds of growth" names the answer, and a reader who only sees the title has still been told something true.

4. Fixed, automatic or range: picking a size

Before the options: you build a dashboard on a large monitor and email it to someone on a laptop. What do they see?

It depends entirely on one setting, and this is the decision that produces most of the "it looks wrong on my machine" messages. Here is the fork.

The question: what dimensions should the dashboard be?

Answer one, fixed. You choose exact dimensions and design at them. Everyone sees the identical layout, and nothing shifts. If their screen is smaller, they scroll or the whole thing scales down. Choosing this means you're saying you know the screen it will be read on.

Answer two, automatic. Tableau adapts the overall dimensions of the visualization based on screen size. Nothing gets cut off on a smaller display. The cost is that your careful placement flexes, so things you lined up may not stay lined up.

Answer three, range. You set a minimum and a maximum size. The dashboard flexes between them and stops flexing outside them. It's the middle option, and it exists because both of the others are absolute about something.

What decides it: whether you know the screen. A dashboard going onto a wall-mounted display or into a specific report has a known size, so fixed is right. A dashboard published to Tableau Public for strangers has an unknown size, so range or automatic is right.

Why it matters: a fixed dashboard designed at a large size and read on a laptop is the single most common reason a dashboard that looked finished arrives looking broken. It's not a rendering fault. It's an answer to this question that nobody remembered making.

In Tableau Desktop there's a fourth path worth knowing about: you can design specific device layouts, so a phone reader gets a different arrangement of the same views rather than a squeezed copy of the desktop one.

5. Details people miss

Before the list: someone adds a ninth view because a stakeholder asked for it. What's the honest answer to that request?

That it belongs on their dashboard, not this one. Requests are not the enemy. Putting every request on one canvas is.

Five more.

A number can be a view. Two or three views doesn't mean two or three charts. A single large number with a label is often the best headline a dashboard can have, and it costs almost no attention to read.

Sheets do not have to be used. A workbook can hold twelve sheets and put three on the dashboard. The other nine are working notes, and nobody has to see them.

Pick the encoding your reader can read accurately. Length and position along a scale are read more accurately than area or angle, which is why a bar chart beats a pie chart for comparing sizes. The chart choice guide walks through the whole set.

Sort the headline view. An unsorted bar chart makes the reader do the ranking. Sorting in Tableau is one click and it's an analytic act, not decoration.

Test it at the size it will be read. Not at the size you built it. If it's going in a slide deck, put it in a slide before you call it finished.