Lean By Design

The episode contains a few genuinely useful framings - most notably that workarounds are a design failure not a behavior problem, and that technology selection should precede process mapping not follow a leadership question - but these insights are heavily diluted by extended analogies (dishwashers, magnet tiles, paint brushes, cogs) and self-promotional content about the hosts' book and assessment product, reducing effective idea density.

“working around the systems as opposed to working through the system. That's actually not a behavior problem. That is a design problem.”

“You should never look for a piece of technology that is specifically answering the question that leadership brought to you”

The reframe of system non-adoption as a workflow design failure rather than user behaviour is the episode's sharpest original claim, but the bulk of the content - champion/super-user models, community of practice, management buy-in, change management - is standard process-improvement orthodoxy recycled without fresh evidence or contrarian argument.

“That's actually not a behavior problem. That is a design problem.”

“It might only be just to answer a hunch. Does that need to be repeatable? Probably not.”

There is no external guest; the episode is two co-hosts who are operational consultants in biopharma, with one citing 10-plus years of Smartsheet use. They demonstrate practitioner experience but present largely as service vendors marketing their own assessment tool, not as operators who have scaled a function at a named organisation.

“Personally, I've been using Smartsheet for over 10 years”

“I'm in a situation now where the IT does not claim ownership of the system in any way. However, they are listed as owners across the entire uh space.”

Concrete evidence is nearly absent: no named client organisations, no dollar figures, no adoption rates, and no before/after metrics. The only substantive specificity is a brief reference to the pharma patent cliff and a passing high-throughput screening example, both left undeveloped.

“we had a client that was building a facility for that. And now folks are not placing bets on these long runways. They're trying to place bets on sure things because of a patent cliff that's about to happen across multiple large pharma.”

“I've seen this with high throughput screening. We have one analyst... the high throughput is in running the experimentation, but then when you go to process and analyze it, weeks, months”

As a two-host format with no external guest, there is no adversarial tension; the hosts consistently affirm each other's points and questions are framed as broad open prompts rather than sharp probes. The episode functions more as a co-authored monologue than a dialogue with genuine follow-up or productive disagreement.

“What have you seen work to sort of bring back some of that report, some of that support in a way that allows really a marriage of the systems that are being brought in and the way that you do the day-to-day work?”

“who do you think would be the most appropriate person to sponsor the workflow alignment activities”