Notified ≠ Understood: Why Your Platform Updates Never Reach the Teams That Need Them

English
This talk will be held in English. / Dieser Vortrag wird auf Englisch gehalten.

At 30 engineers, you walk over and explain why a dependency matters. At 300, you post in Slack, mention it at the all-hands, add a Confluence page — and assume the message landed. Then a team builds against a deprecated platform and everyone asks: “We told people.”

Drawing on experience leading large-scale platform programs and MBA research interviewing 20 directors, VPs, and C-suite leaders, this talk unpacks why broadcast fails where translation is needed.

You'll learn to spot sensemaking gaps, the middle-management trap, and communication debt — then map the paths your org actually depends on and fix the ones that matter.

  • Experience working in or leading teams within engineering organisations of 50+ people.
  • Familiarity with platform adoption challenges — rolling out IDPs, IaC tooling, or shared infrastructure across multiple teams.
  • No specific technical prerequisites; the talk focuses on organisational dynamics rather than specific tools.

  • Understand why "we told everyone" still fails — and why adding more channels makes it worse.
  • Recognise three patterns that strip context from critical updates: sensemaking gaps, the middle-management trap, and communication debt.
  • Map your organisation's load-bearing communication paths and identify single points of failure.
  • Apply practical changes to help managers translate platform decisions into team-level action.
Viktor Didenchuk Viktor Didenchuk is a Lead Technical Programme Manager in JPMorgan, leading engineering programs across hundreds of engineers. He founded Mindecs and grew it to 20 people, and worked on platform tooling at Scalr. He holds an MBA focused on systems thinking, with dissertation research on how senior tech leaders communicate through sustained disruption.
Viktor Didenchuk LinkedIn