Most teams design the full dashboard and bolt on a shrug for day one. That is backwards: the empty state is the only screen every single user sees, and it is the one deciding whether they come back.
Here is how to invert the order without slowing the build — draw the empty state first, treat it as onboarding rather than an apology, and let it tell you which of the dashboard’s forty widgets anybody actually needs.