Winning Digital Customers

The episode contains a handful of genuinely operational ideas - the three-way customization framework (own it forever, yield to the package, or contribute to vendor roadmap), the perpetuity-cost framing for customization decisions, and the sequencing challenge created by uneven prior automation investment - but these are buried in lengthy throat-clearing, repeated questions, and standard transformation platitudes. Insight-per-minute is low.

“anytime you change a design or you change a package, either that package has to embed that design change in perpetuity and kind of make it part of their package, or you're kind of signing up for adjusting every time there's a rollout to make that, you know, part of a change you're going to have to own”

“organizations had already invested in a certain level of automation, uh, to address problems, their willingness to transition to a new common system or a new common approach approach was lower”

The perpetuity-cost framing for build-vs-configure decisions is a mild reframe worth noting, but the bulk of the content - cross-functional co-location, customer journey mapping, pilot-first rollout, client voice in the room - is standard digital transformation orthodoxy, and the episode even invokes Amazon's red chair as a reference point, a cliché in this space.

“it's realizing it's not the investment now...it's going to be Ten plus one in perpetuity”

“Amazon talks about the red chair that represents the client, et cetera. But it is really who in the room is representing the client's view”

Aaron Todd is a genuine practitioner - over a decade at a Fortune 500 institution across seven roles including strategy, ops, tech, and client service - not a speaker-circuit thought leader, and he speaks from direct implementation experience. However, he is MD-level rather than C-suite, and the conversation stays considerably shallower than his background would suggest is possible.

“over a decade at the bank, having held seven different roles across strategy, tech, operations, client service, the business”

“we actually brought clients in to speak to us and hearing what they were saying and then shared with them our views”

The episode names a specific platform (Microsoft Dynamics), a named individual process owner (Leila Sejczak), a specific venue and duration (six weeks in Pittsburgh), and a rough delay cost (3-4 weeks lost to COO transition), which is more concrete than many transformation episodes. However, there are zero hard performance metrics - no before/after resolution times, no dollar ROI, no query volumes - and 'thousands of users' is deliberately vague for an institution of this size.

“we co located this team for the vast majority of six weeks in Pittsburgh, wiped out a giant conference room, whiteboards on the wall on our innovation center”

“we had a very capable woman, Leila, uh, Sejczak, who joined us for that entire session”

The host does push for specifics on the six-week structure, output artifacts, and the build-vs-configure trade-off, and the follow-up on perpetuity costs produces the episode's most substantive moment. However, he asks the alignment question twice in nearly identical form, receives a nearly identical answer both times without noticing, leads the witness on several points, and never challenges the guest on the absence of concrete outcome metrics.

“when do we compromise and when do we hold to our design? And I'm curious what advice you have for people in that situation based on your opportunity to make a bunch of those decisions and see the outcome afterwards”

“did you find that everyone was pretty aligned...Or rather that...different people have different points of view and it's, it's tough to get everyone to really align”