Self-service analytics tooling is evolving because the analytics function is changing.

The old model focused on making dashboards easier to build. The newer model shifts toward engineering-centric foundations, metric consistency, and scaling analytics across many teams without creating chaos.

At the same time, simplicity and interoperability have become central. Even with standardized metrics, self-service fails when the user experience is fragmented, assets are inconsistent, and users need workarounds to answer basic questions.

A streamlined, interoperable architecture reduces friction, builds trust, and makes self-service sustainable.

Key Points

• Self-service succeeds when the governed path is the easiest path, not when you simply add more tools.
• Optimize the stack around real user personas, not a generic “one size fits all” UX.
• Interoperability matters because users need an end-to-end flow from trusted data → consistent metrics → usable analysis.
• Standardized metrics help, but they only scale when the surrounding experience is coherent, discoverable, and reliable.

Conclusion

Self-service tooling is not a shopping list. It is a system that either reduces friction or creates more of it.

The goal of this step is to help you choose and design the building blocks that make self-service work at scale. That means aligning architecture, metric consistency, and user experience so different personas can answer questions without reinventing logic or creating parallel versions of the truth.

Slides