A dot plot for tracking user behavior is a two-dimensional grid — rows for individual users, columns for time periods — where you place a dot every time a user completes a meaningful action on a given day. It sounds almost embarrassingly simple, but it surfaces patterns that aggregate metrics like DAUs and MAUs completely hide. If you're a founder trying to figure out whether people actually want what you built, a dot plot might be the most important dashboard you're not using.
What Is a Dot Plot and How Does It Work?
Think of a dot plot like a spreadsheet where every row is one user and every column is one day. Each time a user performs a key action — listening to a song, processing an invoice, sharing a photo — you drop a dot in that cell. That's it. No complex computation. No fancy SQL wizardry. Just a clean, visual record of who did what and when.
02:15
A hand-drawn dot plot showing individual users as rows and days as columns, with dots marking each day of engagement
Watch at 02:15 →
To add even more signal, you can mark the first day a user ever engaged with your product by drawing a ring around that day's dot. As your grid fills up, patterns start jumping out at you — patterns your brain would never extract from a line chart trending vaguely upward.
For example, imagine you're building a Spotify-like music app. You chart the event "listened to a song." After a week or two of data, you might notice that some users are active Monday through Friday but go dark on weekends, while others do the exact opposite. That's a behavioral insight you can act on — it tells you something real about who your users are and how your product fits into their lives.
How Do You Know If Users Actually Value Your Product?
This is the question that aggregate dashboards simply cannot answer. When all your users are lumped into a single metric, you get a number — not a story. A dot plot gives you the story.
Consider the Spotify example again. You might notice one user who joined a public playlist and then used the product for ten consecutive days. That's a signal. Maybe the playlist feature is what turns casual listeners into habitual ones. With a dot plot, you can spot that causal relationship and test it. With a DAU graph, you'd never even know to look.
You can also encode additional meaning into your dots. Use different symbols for different features — an "S" for search, a "P" for playlist joins. Shade cells to represent user states: iOS vs. Android, US vs. international, free vs. paid. Suddenly you're not just seeing that users engage — you're seeing how and why, and which product features are actually driving retention.
07:40
Side-by-side comparison of a DAU graph versus a dot plot built from the same user data — showing how much the DAU graph hides
Watch at 07:40 →
Why DAU and MAU Metrics Lie to Founders
Daily Active Users and Monthly Active Users have one fatal flaw: they flatten everyone into a single number. A user who opened your app once counts the same as a power user who ran 50 transactions. And if you have any growth at all — even slow, leaky growth — those graphs will trend upward even if your existing users are quietly quitting.
Here's a concrete illustration. Take a small cohort of users over two weeks and build both a DAU graph and a dot plot from the same data. The DAU graph might show a relatively stable 2-3 users per day with no dramatic swings. Looks fine, right? But the dot plot reveals the truth: several users onboarded and never came back, a few users only engage on weekdays, and engagement is generally thin and sporadic. The DAU graph told you "we're okay." The dot plot told you "we have a retention problem and probably an onboarding problem."
Aggregate metrics are useful for boardroom conversations. Dot plots are useful for actually fixing your product.
How to Track Individual Users Without Drowning in Logs
The knee-jerk solution when you want to understand individual users is to tail your server logs and watch every event roll by in real time. That works for maybe five users. After that, it's chaos.
11:20
The B2B churn example: a dot plot revealing that only 3 of 10 paid seats ever activated, with thin and sporadic usage across those 3
Watch at 11:20 →
Dot plots solve this scaling problem elegantly. At the small end — 10 to 50 users — your entire user base fits on one screen. You can see every user, every day, at a glance. At the large end, you sample. At Google Photos, with over a billion users, teams would print out dozens of dot plot pages, each representing a different segment: iOS users in France, web users in the US earning over $80K, and so on. Team members would sit with their assigned printout and look for patterns, then reconvene to share findings.
The key insight is that the human brain is extraordinarily good at detecting visual anomalies — but only when the data is presented visually. This is the same principle Max Levchin used at PayPal to fight fraud: they didn't know what fraud patterns looked like, so they visualized all their transactions and had humans stare at the screens until someone said, "That — that thing looks wrong." Dot plots harness the same instinct for product analytics.
And building one is fast. Modern AI coding tools can generate a basic dot plot from your event logs in about ten minutes. You just need to parse your logs into a 2D grid. No fancy infrastructure required.
Can Dot Plots Prevent B2B Churn Before It Happens?
Absolutely — and this might be where dot plots are most underappreciated. B2B founders often assume that as long as a contract is signed, they're safe until renewal. That's a dangerous assumption.
Here's a real example: a company sold an $80,000 annual contract for 10 seats to a name-brand customer. The customer onboarded, and the startup moved on. What they didn't see — because they weren't looking — was that only 3 of the 10 seats ever activated. Those 3 users engaged sporadically, rarely using the product more than twice a week. The internal champion who bought the product eventually left the company. The replacement looked at the contract, saw almost no adoption, and killed the renewal.
A dot plot would have surfaced all of this within the first two weeks. Low seat activation, thin usage density, and declining engagement are all visible at a glance. That's enough time to reach out, re-engage, run training sessions, or escalate to an executive sponsor — whatever it takes to save the contract.
In B2B SaaS, churn rarely happens suddenly. It accumulates quietly in underused seats and disengaged users. Dot plots make that accumulation visible in time to act.
What Events Should You Actually Put in Your Dot Plot?
This is where many founders go wrong. The temptation is to pick an event that generates a lot of dots — something like "opened the app" or "logged in" — because it makes the chart look healthy. Resist that temptation.
The event you track should represent genuine value being delivered to the user. Ask yourself: what does a user do in my product that means they got something real out of it today? For a music app, that's listening to a song. For an invoicing tool, that's processing an invoice. For a photo sharing app, that's sharing a photo.
Vanity events like logins create vanity dot plots. They'll make you feel good and tell you nothing useful.
Similarly, resist the urge to widen your time columns to weeks instead of days. Weekly columns smooth over the texture of behavior. You lose the weekday-vs-weekend pattern. You lose the "tried it once and disappeared" signal. You lose the streak of daily engagement that tells you a feature is sticking. Day-level granularity — or even sub-day for some products — is where the real insight lives.
Dot Plots vs. Cohort Retention Curves: Which Wins?
Neither — you need both, and they answer different questions.
Cohort retention curves tell you whether groups of users you acquire continue using your product over time. They're the best tool for answering "are people sticking around?" They give you a macro view of retention health across different acquisition periods.
Dot plots tell you how users are actually behaving day to day. They give you the texture and color behind the retention numbers. They help you ask the right questions, build the right features, and fix the right problems.
Think of cohort retention curves as your health checkup and dot plots as your MRI. The checkup tells you something is wrong. The MRI shows you exactly where and why. Used together, they give you a complete picture of your product's relationship with its users — and that's the foundation everything else is built on.
If you're an early-stage founder with fewer than a few hundred users, a dot plot could genuinely be your only dashboard. It requires no infrastructure, almost no engineering time, and it will teach you more about your product in a week than months of staring at aggregate graphs ever would.
