Business Intelligence for the Busy Bee

Every six months or so, an owner I’m working with sends me a screenshot of a dashboard they’ve been told they need. It’s usually some twenty-tab Power BI report or a Google Looker Studio thing that took an enthusiastic nephew an entire weekend to build. They send it because they’ve been staring at it for a month and they have no idea what it’s telling them. They send it because it makes them feel guilty.

I want to make a small case here that you should ignore the dashboard.

A real working business intelligence practice for an owner-operator is not a dashboard. It is three numbers. The numbers are different for every business, but the structure is the same: one number that tells you whether you have enough work coming in, one number that tells you whether the work you have is profitable, and one number that tells you whether the people you’ve already served are coming back. Those are the only three things you need to know on a Monday morning. Everything else is decoration.

The hard part — the part that takes thinking — is figuring out which three numbers actually answer those questions for your business. For a service business, “enough work” might be booked-hours next 14 days. For a retail business, it might be foot traffic. For an e-commerce shop, ad-spend-to-revenue. The “profitable” number is almost always margin per job or margin per product, and it’s almost always wrong in the books because something — labor, overhead, returns — isn’t being allocated correctly. The “coming back” number is the easiest to define and the hardest to actually measure: percentage of clients this month who’ve been here before.

Once you have those three numbers, the BI work isn’t building a dashboard. It’s building a habit. Every Monday, you look at them. They’re either green, yellow, or red. If anything’s red or trending red, you spend the rest of the week fixing it. If everything’s green, you trust it and go do the actual work. That’s it. That’s the entire methodology.

I’ll tell you the most counterintuitive thing about doing this for a living: the dashboards are mostly a coping mechanism. People build elaborate reports because the act of building them feels like progress. Owners stare at twenty-tab dashboards because they want to feel in control of their business, even though the dashboard is actively hiding the three things they should be looking at under sixty things they shouldn’t.

We do a thing at DataSmart called a working analytics setup — it sounds boring on purpose. The whole point is that it isn’t a fancy dashboard. It’s a weekly digest. Three numbers. Compared to last week, last month, last year. A short note from a real human about what’s drifting and why. If everything’s green that week, the email is one paragraph long. If something’s red, the email is longer, and there’s a recommended next move attached to it.

The owners who try this and stick with it usually have the same reaction after about a month. They stop opening the dashboard. They start opening the email. After three months, they realize they’d been making decisions on instinct for years, and the instinct was mostly right — but the times it was wrong were the expensive times, and the digest was catching them before they got expensive.

The dirty secret of small-business BI is that you don’t need more data. You need less data, watched more often, by someone whose attention is reliable. If that’s a service, fine. If that’s a Saturday-morning routine you hold yourself to, also fine. The format isn’t the point. The discipline is.

So next time someone sends you a dashboard with twenty tabs, take a breath and ask: which three numbers on this thing would tell me, at a glance, whether my business is healthy? If you can pick them out, that’s all you needed. If you can’t, the dashboard isn’t telling you anything — it’s just keeping you company.