In Managing the Professional Service Firm, David Maister mentions an old saying about doctors who are more fascinated by diseases than by the people who have them.

It reminded me of a recent call. We were planning the first month of my analytics consulting engagement. The team liked what they were seeing. We looked at dashboard examples, worked through the roadmap — everything was going smoothly until someone interrupted me:

“We can build dashboards ourselves. What we’re really missing is someone who can think through the architecture.”

That made me pause. These days, pretty much anyone can put a dashboard together. There’s Claude Dashboards, there are ready-made subscription tools. But this team was stuck on something else: how to design the analytics system as a whole.

Which user actions should they track? How should data move between systems? How would they check its accuracy? Where would it all come together? And who would own each part?

We went back to the first month and reworked the plan. The focus shifted to architecture, working with stakeholders, and development. I explained who I would need and why: an internal coordinator, a developer for technical work, and ideally someone to handle data collection and keep it up to date. Those roles could overlap, but an outside consultant couldn’t replace the entire team.

The bigger point was this: a capable team doesn’t need someone churning out reports. It needs a system it can eventually run itself.

Now picture a familiar setup. A founder decides they need help with analytics and hires a contractor. The contractor delivers dozens of beautiful dashboards. The founder spends a day trying to make sense of them, then makes a few decisions.

A week later, a new problem comes up. And the poor founder gets buried in another batch of dashboards.

We become fascinated by dashboards, just like the doctors in Maister’s example become fascinated by diseases. Meanwhile, the founder doesn’t need another round of tests. They need to understand what’s happening and what to do next.

So if someone offers you a stack of reports as the solution, first ask: who is responsible for the data behind them, and which decisions are those reports supposed to help you make?

Want a stronger data analyst role or a raise? Grab the FREE Product Analyst Playbook and get the exact roadmap to your next offer.