Concise dashboard solving a defined decision need, built in Tableau Desktop with a reproducible data pipeline and clear design rationale for accurate, fast insight consumption.
Link to Tableau Public or Server workbook; include a short GIF or PNG previews for quick scanning and note that interactive embeds belong on Pages or a site, while the README links to them.
Name the datasets, ownership, access method (file path or DB schema.table), date range, row count, refresh cadence, and any caveats like filters, exclusions, or known quality issues.
Summarize upstream prep (SQL/DBT/Prep joins, filters, calc fields) and in‑Tableau logic, noting extract usage (.hyper), refresh schedule, and critical formula snippets users should know.
List dashboards, their audience and purpose, key sheets that feed them, and any stories; give a one‑line “how to read” for each view to set expectations quickly.
Document global filters and parameters, reset behavior, and actions (highlight, filter, URL); note important tooltip definitions and how users drill or navigate between views.
Explain chart selection by question, color and accessibility decisions, typography and spacing, and layout/sizing strategy for desktop vs. mobile to justify visual clarity.
State live vs. extract rationale, performance recording findings, use of context filters, and known heavy queries or row‑volume limits that influence load times.
Describe reconciliation steps against source‑of‑truth, variance thresholds, edge cases tested (nulls/outliers/time zones), and stakeholder sign‑off dates for confidence.
Specify the project path on Tableau Public/Server, permissions, data source publishing strategy (published vs. embedded), and where to embed a live iframe if needed.
Steps to clone, place sample data, open .twbx/.twb, connect or refresh extracts, and verify row counts; list required drivers, fonts, or palettes to match the intended visuals.
Upcoming enhancements such as parameters, additional cohorts, new KPIs, row‑level security, or device‑specific layouts, with brief notes on priority and scope.
Licenses for data, attributions for icons/maps/palettes, and maintainer contact details or issue link for feedback and contributions.