Tableau Dashboard Mockup: How to Design Before You Connect Your Data

Tableau makes it easy to build dashboards fast — drag a dimension, drop a measure, and you have a chart in seconds. That speed is an asset, but it creates a trap: developers often start building before they’ve agreed on what to build.

The result is a dashboard that looks polished but answers the wrong question, or one that gets rebuilt three times because the stakeholder kept changing their mind.

A Tableau mockup breaks the cycle. Here’s how to use one.

What a Tableau mockup is (and isn’t)

A Tableau mockup is a static representation of a dashboard layout — which views will appear, where they sit, what filters exist, and which sheets are included — without any live data or Tableau logic.

It is not:

• A Tableau workbook with placeholder data
• A screenshot of a similar dashboard
• A sketch of what the final dashboard “might” look like

It’s a clear, shared spec that both the developer and stakeholder agree on before any connection, calculation, or formatting work begins.

Why not just start in Tableau?

Building a rough version in Tableau to show stakeholders sounds efficient but has drawbacks:

It anchors on implementation. Once a stakeholder sees real data in a chart, they start giving feedback on the data — wrong filters, unexpected values, edge cases. You spend the meeting debugging instead of designing.

It takes longer than a mockup. Connecting a data source, building enough views to show the layout, and assembling a dashboard takes hours. A mockup takes 15–30 minutes.

It signals false completion. Stakeholders often treat a working prototype as a near-finished product. Changes feel expensive, even when they’re not. Starting from a mockup resets those expectations.

Tableau’s layout constraints to keep in mind

Tableau dashboards have a few structural characteristics that affect how you mockup:

Fixed vs. automatic sizing. Tableau dashboards can be fixed size (common for embedded dashboards or presentation use) or automatic (scales to window). Fixed-size dashboards are usually 1200×700 or 1366×768. Automatic dashboards need layouts that work at multiple widths. Decide which you’re building before you mockup.

Tiled vs. floating objects. Tiled layout arranges views in a grid; floating allows precise positioning but is harder to maintain. Most production dashboards use tiled layouts with occasional floating elements for overlays or callout boxes. Sketch using a tiled mental model unless you have a specific reason not to.

Container types. Tableau uses horizontal and vertical containers to group views. Your mockup doesn’t need to represent containers explicitly, but grouping related charts visually will map naturally to containers when you build.

Dashboard actions. Filter actions, highlight actions, and URL actions determine how views interact. Note in your mockup if clicking a chart should filter another view — this affects layout (the filter target needs to be visible when the source is clicked).

Building the mockup

Step 1: List the views

Before touching any tool, write down the views (sheets) the dashboard needs. For each view:

• Chart type (bar, line, scatter, map, table, text)
• Primary dimension and measure
• Purpose (“shows trend over time” or “compares performance by region”)

A typical Tableau dashboard has 3–6 views. If you’re listing 10+, consider whether it should be multiple dashboards.

Step 2: Sketch the layout zones

On paper or in a mockup tool, block out the dashboard into zones:

• Header / KPI row — summary numbers, usually text tables or BANs (big-ass numbers)
• Main view — the largest chart, usually a trend line or geographic map
• Supporting views — 2–3 smaller charts that add context
• Filters — date range, dimension filters; usually at top or left

Tableau dashboards read left-to-right and top-to-bottom, same as any document. Put the most important information in the top-left.

Step 3: Mock it up digitally

Move your sketch into a digital tool so you can share it. Mockko’s canvas matches Tableau’s fixed-size defaults, and you can drop labeled chart placeholders to represent each view.

Label each placeholder with the view name and chart type: “Sales Trend — Line Chart” or “Top 10 Products — Bar Chart.” Add filter labels at the top.

Export as PNG or PDF, or share a link.

Step 4: Review and iterate

Share the mockup with your stakeholder before your review meeting and walk through it together. Use the session to answer:

• Is the right data visible at a glance?
• Are there views missing that you’d want?
• Should clicking any view filter the others?
• Is the sizing roughly right (does the main view deserve that much space)?

Make changes to the mockup until you have sign-off, then start building.

What to document alongside the mockup

A mockup alone isn’t a full spec. Note separately:

• Data source(s) and connection type
• Key calculated fields needed (if known)
• Dashboard actions (which views filter which)
• Performance requirements (does it need to load in under 5 seconds on live data?)
• Who has access and how it’s published

This documentation lives in a doc or ticket, not in the mockup itself. The mockup’s job is layout and structure — keep it focused.

---

Create a Tableau dashboard mockup in Mockko — free to start, no design skills required.