{
  "id": 9548310,
  "title": "Building a Collaborative Platform Culture in a Bank",
  "url": "https://urgent.news/2026/09/24/building-a-collaborative-platform-culture-in-a-bank",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-24T11:09:00.000Z",
  "source": {
    "name": "InfoQ",
    "slug": "infoq",
    "url": "https://www.infoq.com/news/2026/09/collaborative-platform-culture/"
  },
  "original_language": "en",
  "account": "Marcy Paramonova and Stéphane Cusin discussed how to build a collaborative platform culture within a bank at KubeCon & CloudNativeCon Europe. They explained that a platform is not just infrastructure, but a collaboration system where communication and interaction occur. Paramonova emphasized that culture follows structure, meaning that a shared set of standards and practices is necessary to foster an engineering mindset among developers and product teams.\n\nThe platform team offered open support sessions where developers could collaborate and solve problems together, moving away from the traditional support model of ticket-based assistance. These sessions brought together various technical teams, encouraging cooperation and shared learning. They also introduced super user awards to recognize developers who contributed to improving the platform, which helped create a sense of value and appreciation for the team's efforts.\n\nParamonova highlighted the importance of an engineering mindset, which focuses on problem-solving, continuous learning, and sharing passion for tackling challenges. This mindset is essential for adapting to new technologies and technologies.\n\nThe speakers discussed how they designed systems that fostered the desired culture within the organization. They emphasized the importance of rituals and routines around collaboration, such as holding a weekly \"Genius Bar\" where developers could ask questions and receive immediate feedback. They also organized user insights sessions to share priorities, progress, and roadmaps with users, fostering transparency and shared ownership.\n\nAdditionally, the platform team adopted a lifecycle approach for each capability, tracking usage, value, and potential improvements. This visibility allowed the team to make informed decisions about retiring outdated features and migrating to newer capabilities, ensuring a smooth and efficient platform evolution.\n\nOverall, the key to creating a collaborative platform culture was to design systems and routines that naturally promote collaboration, feedback, and continuous improvement, rather than relying on external factors like individual requests or manual interventions.",
  "summary": "A platform is a collaboration system, not infrastructure. Culture follows structure: platform teams can build open support sessions, create super user awards for contributing developers, and establish shared open standards to grow an engineering mindset. Developers and product teams depend on a platform team, which in turn depends on application teams; to go forward, they need shared standards.…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}