Hard Hats & Data Chats

The episode contains a handful of genuinely useful practitioner heuristics - most notably the 'what are you doing in Excel after you export' reframe and the green/yellow data-freshness indicator - but roughly 4 minutes is pure personal filler and the remaining substance is largely standard change-management and data-hygiene advice repeated at a slow pace.

“If we can capture what are you doing in Excel after you export the data, that's how we can provide the best value because we can just give you those numbers directly.”

“we actually made just a little indicator. Um, it was just a green and yellow indicator. So if all the data had refreshed like we expected, we gave it a little green dot on the dashboard.”

The 'reframe the ask from rows-and-columns to business questions' angle is a solid practitioner heuristic, and the AI-readiness-through-clean-data argument is timely, but almost everything else - get executive buy-in early, clean duplicate records, iterate in phases - is recycled consulting orthodoxy with no contrarian edge.

“Don't tell me which columns and rows you're looking for in the report. Tell me what kind of questions you're trying to answer.”

“when we started working with Tableau many years ago, they were still in kind of startup mode as a company. And their thing that they like to say was land and expand”

Both participants are genuine practitioners - an ERP implementer and a BI consultant with real construction-vertical depth - but neither is a senior operator who has built or scaled a business; they are implementers and advisors, not decision-makers, and the show appears to be internally produced with no independent validation of track record.

“within construction, the different vertical markets, the different types of contractors, that can change drastically. Like, for example, a mechanical contractor, very labor-intense.”

“don't overcommit, don't sell so much work that you don't have the resources available and you have to start hiring temporary contractors, which eats up your marger quicker than anything.”

There are a handful of concrete, illustrative examples - customer hierarchy split across five entities, the DSO/DPO calculation, the green/yellow freshness indicator on a five-source dashboard - but there are zero hard outcome metrics, no named client companies, and no dollar figures or timelines to anchor the claims.

“lots of times you won't see the customer that you expect as the top customer because it's actually split into maybe five different companies, because they have different locations”

“You're trying to calculate DSO and DPO from the accounts receivable data.”

The opening four-plus minutes are dedicated entirely to bike races and Paris vacation planning, questions are consistently leading and affirming rather than probing, and there is no moment of genuine challenge or productive disagreement throughout the episode - it reads as two colleagues agreeing with each other at length.

“I'm going to be doing a gravel race in Steamboat Springs, Colorado next month. And I'm trying to decide if I'm going to fly and put my bike in a case or if I'm going to drive.”

“What are some of the other things that you might do when looking at KPIs and trying to identify that?”