Vanity Dashboard

Vanity Dashboard is the polished executive view that shows only good news. Every chart is green. Every line trends up. The screen exists so leadership can capture it for slides and reports. It offers zero guidance on what to do next. The team ships it because no one gets fired for making everything look successful. The vanity version is the final boss of the five failure modes outlined in the anti dashboard paper. It combines the graveyard, the carousel, and the eye of Sauron into one flattering package that hides every real problem.

This is not a decision tool. A real dashboard forces the user to confront reality and take action. The vanity one lets the user feel informed while changing nothing. It is not one question answered well. It is every metric thrown at the wall to see what looks best in screenshots. It is not a priority list sorted by the product team. It is a collection of stats chosen by whoever wanted their favorite number featured. Stripe rejected this approach. Their home screen leads with revenue but pairs it immediately with the failed charges and disputes that require attention today. The vanity version would leave those disputes off the first screen so the picture stays pretty. Linear does the same by ranking issues by priority and SLA instead of showing a balanced scorecard of every possible engineering metric. These choices make the screen useful on day two and every day after.

Take the executive dashboard at a well known project management tool in 2024. The screen opens to a hero widget showing tasks completed this month with a twenty two percent increase. Next to it sits velocity trending up, team utilization in the green zone, and customer satisfaction at ninety four percent. The CEO loves it. The screenshot makes its way into the annual report and the next fundraising deck. Buried three tabs deep is the fact that new user onboarding time has doubled and activation has fallen off a cliff. No action link exists from the main numbers. The screen is a victory lap with no finish line. Cursor took a different route with its project pane. It answers where was I and what was I doing by showing the last prompt, the current file, and the editor front and center. No vanity metrics about how many lines of code were written or tokens consumed. The focus stays on the work. Cron follows suit by placing the next event at the top of the calendar view so the user knows exactly what comes next without any decorative charts competing for attention. Vercel does the same with its project view by showing the deploy timeline and URL as the only question that matters.

Ship a vanity dashboard when you need to impress people who never touch the product. Ship it when the board meeting matters more than the daily workflow. Ship it when the company culture punishes bad news and rewards green charts. Never ship one for teams that need to move fast. Never ship one when your retention depends on users finding value on their second or third visit. Never ship one if you have any interest in building habits around your tool. The vanity version trains users to ignore it. Once they learn the screen lies they stop looking. The anti dashboard trains them to check it daily because it tells the truth even when the truth is that things are broken. Superhuman rejected vanity when it built its triage first inbox designed to reach zero every day. GitHub did the same by making assigned pull requests the entire home view with nothing else above the fold.

The five rules of the anti dashboard exist to kill vanity at the root. Rule one demands one question per screen. Vanity tries to answer all of them and succeeds at none. Rule two requires the product to sort the priority list. Vanity leaves it unsorted or sorted by whatever flatters most. Rule three picks one time horizon that matches the question. Vanity offers every toggle and defaults to the one that looks best this quarter. Rule four ties every number to an action. Vanity stops at the number. Rule five hides the long tail. Vanity either shows everything or only the flattering tail. Hit these rules and the vanity evaporates. Miss them and you have built another screenshot machine. Notion Calendar follows them by placing the next event at the top of the day view and pushing every heat map and secondary stat below it.

Raycast proves a dashboard does not need to look like a grid of widgets at all. The search bar becomes the entire interface. No room for vanity when the user types their intent and the right command appears. Progressive disclosure done right supports this discipline. Show what matters now. Hide the rest until the user asks. Vanity inverts this by showing only what makes the company look good now and hiding what might make it look bad. The before screen in most audits is a twelve widget mess where every cell competes and nothing wins. The after collapses to one hero stat tied to a clear action, three priority rows, and a muted footer. The same data lives in both versions yet only the opinionated one gets used twice.

Run the seven question audit on any vanity dashboard and it fails every line. No clear single question. No primary action tied number. No product opinion in the sort order. No thoughtful default time horizon. No meaningful hiding of less important data. The empty state usually asks the user to customize their own view which is homework not product. A new user learns nothing useful about the actual state of the work. These failures compound until the dashboard becomes the thing everyone mocks in meetings but no one has permission to kill. Teams building in 2026 will face the same temptation. Fundraising decks still need charts. Boards still love green. The winning teams will resist anyway.

Vanity dashboards let teams pretend they are data driven while avoiding every hard decision the data demands.