The Dev is in the Details

The episode contains substantial, non-obvious insights about digital transformation leadership - particularly the distinction between bottom-up and top-down change initiatives, the criticality of local context, and the necessity of articulating 'what's in it for me' at individual contributor levels. However, there is notable repetition of core themes (fear-based resistance, local vs. global tensions, three-bucket business case framing) that pads the runtime. The guest offers genuinely useful frameworks but revisits them multiple times rather than progressing to novel territory.

“Whoever is implementing a technology just for the sake of a technology, that's the best path for a failure.”

“Digital transformation rarely fails because of technology. It fails when leadership avoids clarity, accountability, and hard decisions.”

The episode avoids clichéd transformation advice and grounds reasoning in real operational constraints - the 65-market example with identical tech producing wildly different outcomes is genuinely instructive. However, core ideas (change management, stakeholder engagement, business case framing) are not novel; the originality lies in the specificity of application to FMCG B2B rather than in conceptual innovation. The three-bucket business case (growth, hard productivity, time release) is a useful reframing but not groundbreaking.

“At that moment, we had around 65 markets live when I was there, and actually only half of them were having good results...and we had markets which should be super digitalized, like UK, and were struggling.”

“We are always trying to show three separate buckets. First, we look at the growth. The second bucket is productivities, but a hard productivities which are non-debatable, for example, a savings on a paper or a printout.”

Kamil is a credible practitioner with 20 years of hands-on FMCG experience across four major multinationals (P&G, Colgate-Palmolive, Philip Morris, PepsiCo) and direct responsibility for global B2B platform rollouts and local market transformations. He speaks from execution, not theory. His seniority and scope (managing 65-market deployments, leading Poland transformation from strategy through delivery) is substantial. Minor deduction because the episode doesn't deeply explore his failures or disagreements with prevailing wisdom.

“I have 20 years of experience in global FMCG companies: Procter & Gamble, Colgate Palm olive, Philip Morris International, and currently PepsiCo.”

“When I was running a global B2B platform...we had around 65 markets live when I was there.”

The episode includes concrete examples (image recognition in FMCG stores, the Philip Morris 65-market rollout, specific KPI challenges in Germany vs. Turkey, Żabka's 12,000-store network) and real metrics (20 years tenure, Poland transformation timeline, 400 trees saved through paperless initiative, 50% over-delivery rate on objectives). However, many claims lack supporting numbers: no breakdown of the failed markets' metrics, no quantified time release percentages for case studies, and limited financial data on business case outcomes. The business case discussion remains somewhat abstract despite framing.

“Let me give you a very concrete example, which is like number one blocker for B2B platforms for retailers in the FMCG sector...For the last 10 years, our main job is to visit the store and show the products are there, and our main point of the visit is to create an order with the retailer.”

“We made a brilliant program in PepsiCo, Poland, where we eliminated paper from any deliveries within Poland. We saved 400 trees just in 2025 out of this.”

The host asks sensible follow-up questions and attempts to drill into specifics (e.g., 'walk me through the time frame,' clarifying incentive structures). However, the conversation lacks sharp challenge or productive disagreement. When Kamil makes broad claims (e.g., '80% of digital transformations fail'), the host does not press on sources, nuance, or counterexamples. The host also allows Kamil to circle back to the same themes repeatedly without redirecting or asking him to concede limitations. The dialogue is friendly and clear but rarely pushes toward revealing tension or complexity.

“So playing around, you know, having some system because a global team said we need to implement it. If you hear something like that from a senior person, it's kind of a first indication that something might go wrong.”

“I just recently seen a Deloitte research which was in line with McKinsey research that around 80% of digital transformations fail. And I think this is one of the reasons, because it requires enormous agility.”