Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Kirby Montgomery says the first question about a good-looking engineering dashboard is who actually uses it and what decision it changes. He and Jim Milbury describe dashboards or cloud artifacts vibe-coded the night before diligence, hosted locally, and never shared with the C-suite or board.

Related Insights

The biggest failure of BI tools is analysis paralysis. The most effective AI data platforms solve this by distilling all company KPIs into a single daily email or Slack message that contains one clear, unambiguous action item for the team to execute.

A Palantir architect argues that standalone dashboards are a 'field of dreams' that nobody uses. Instead, metrics and KPIs should be byproducts embedded directly within operational applications, informing the user at the point of action and decision.

Collecting data is insufficient; its true value is in enabling difficult conversations about operational bottlenecks. Many teams understand data's importance in theory but fail the last-mile work of making it meaningful. Data must be structured to spark discussion and diagnosis, not just reporting.

Stakeholders often demand dashboards to feel "data-driven." However, these are rarely designed with a clear user purpose, resulting in a collection of impressive-looking data that is ultimately unactionable for the end-user who needs to make decisions.

Corporate dashboards are a 'first derivative of a fact,' not reality itself. Leaders who rely on them exclusively lose touch with the business, like an 'Undercover Boss' surprised by their own company. Stay grounded by talking to customers and using the product.

Marketers need complex, multi-point dashboards to make informed decisions. However, presenting this raw data to the C-suite causes confusion. The marketing team's job is to diagnose the complex data internally and then present a simplified, narrative-driven report to leadership that justifies strategy and investment.

Kirby Montgomery says monthly or quarterly monitoring must pair captured data with context, so non-technical investors understand why numbers moved. Code & Co. tells engineering teams it is not there for gotchas, but to translate their story; if the work is helpful, engineers lean in rather than game the metrics.

Traditional dashboards are obsolete because they create more questions than answers. The future is interactive, conversational AI that allows leaders to ask 'why' and get immediate answers and recommendations, eliminating follow-up meetings and Slack messages.

During the first six months post-acquisition, new reporting dashboards don't measure performance. Their primary value is exposing broken processes and inconsistent data definitions (e.g., what constitutes "pipeline"). Fixing this data plumbing is a prerequisite for meaningful analysis later.

The founder's initial "Results as a Service" model failed because finance leaders didn't want a "black box" solution, even if it worked. They needed a dashboard to see what was happening, maintain a sense of control, and appear serious. Pure outcomes aren't enough; visibility is crucial.