Networking

Geralt takes some time off: How we implemented a process platform at CD PROJEKT RED – and why leave requests are little monsters of their own

In this session, you’ll learn:

• why a process that looks simple to the end user isn’t necessarily simple to design and automate;
• why gathering requirements at the start of the project wasn’t enough – and how the collaboration model between the business and technical teams evolved as a result;
• how to design a solution for an organization where team structures and dependencies are constantly changing;
• why your first process shouldn’t be judged only by whether it works today, but also by whether the technology, architecture, and delivery model can support the processes you plan to add next.

Leave and overtime requests are a great place to start with digitalization. They’re familiar, repeatable, and relevant to every employee. From the user’s perspective, it seems simple: fill in a few fields, submit for approval, and you’re done.

At CD PROJEKT RED, this process became the first step toward something bigger: building a platform that could support more business processes over time.

Creative projects such as video game development, however, come with their own set of challenges. Teams change frequently. Artists, writers, animators, and gameplay designers are regularly reassigned to new tasks – and, as a result, to new teams and coordinators. When it’s difficult to predict what people will be working on, or who they’ll be working with,
one, two, or six months from now, managing organizational structures becomes far from straightforward. Especially when more than 500 people are involved in developing The Witcher 4.

The first implementation showed us that behind the simple experience of submitting a leave request lies a whole range of moving parts that need to work together – from coordinating work to integrating with other systems.

In this session, we’ll share what we only discovered once we started building the new system, why some of our initial assumptions had to be revisited in practice, and how this first implementation shaped the way CD PROJEKT RED now approaches subsequent processes.

Jakub Sochacki

Business Systems Manager, CD PROJEKT RED

Michał Wawrzonkowski

Business Systems Coordinator, CD PROJEKT RED

Weronika Modzelewska-Ochman

Employment&Payroll Lead, CD PROJEKT RED

70 processes in 18 months. From paper to end-to-end automation.

In just 18 months, Bruk-Bet carried out a comprehensive digitalization of its processes, the kind of transformation that takes many organizations years. That pace wouldn't have been possible without a solid foundation: an architecture that followed directly from decisions made in infrastructure and software. A holistic approach to the transformation made room for the most important change of all, building understanding, engagement, and collaboration between IT and the business. The results are substantial: dozens of processes automated, infrastructure moved to the cloud in parallel, and systems deployed to support key areas of the business. Paweł Górka, IT Director at Bruk-Bet, will share his experience.

From the session, you will learn:

• why a well-functioning process automation layer makes it easier to implement domain-specific systems, while limiting costly customization
• how to organize internal competencies and partner collaboration so a small team can reliably deliver dozens of applications a year
• why moving infrastructure to the cloud became the catalyst for a much broader transformation
• how to manage organizational mindset to build IT engagement, business collaboration, and trust from the board

Paweł Górka

IT Director, Bruk-Bet

Launch Break and networking

Stop planning for certainty. Start building for change. 

For years, organizations designed their processes, systems, and operating models for stability. Today, the challenge is no longer change itself, but the speed at which it happens – across business, regulation, and technology. Competitive advantage increasingly depends on an organization’s ability to adapt continuously without losing control, quality, or momentum. The role of technology – and the way it is delivered – is changing too. IT can no longer operate simply as a provider of solutions, with the business acting as the customer. What you need is a model where both sides build competences together, shorten the distance from need to working solution, and create an environment where change can scale. Speakers from KRUK, ENEA, will share how they did it. 

What you'll take away from this panel: 

• how to identify business needs and turn them into real change faster, 
• how to reduce the communication barriers between business and technology teams, 
• when it makes sense to build your own Center of Excellence, and what role it can play in scaling transformation, 
• how to get business users involved in digitization, 
• how to move from isolated automations to a way of working that keeps the organization improving. 

Sebastian Gajecki

CIO, Enea Centrum

Adam Łodygowski

Chief Data & Technology Officer w Grupie KRUK

Networking

Networking

Get AI down to business: Configuring AI agents and automations in WEBCON

A hands-on workshop on configuring LLM-based automations and AI agents inside WEBCON. Step by step, with the landmines called out, you'll leave with the patterns, prompts, and governance checkpoints you need to start building AI into your own applications next week.

Adrian Baszak

Business Analyst

Networking

Get AI down to business: When OCR meets AI in document-heavy workflows

For everyone whose processes live on invoices, contracts, correspondence, and scanned paperwork. We'll show how AI supplements OCR to handle the cases that traditional extraction never could — and how to bring the document automations you've been putting off into production.

Mark Mulder

Senior Pre-Sales Consultant

Networking

The new Designer Studio — Experience what's next

A deep-dive, hands-on look at the next Designer Studio. See how building and evolving applications changes, what the new authoring experience feels like in practice, and what it means for the way your team works. The future of the tool you use every day — shown in detail, with the thinking behind each change.

Dawid Porowski

Product Manager

Lunch Break

Keep the lights on, keep the trains running — Monitoring and troubleshooting in WEBCON

Business-critical or supportive, every application needs someone watching it. This session covers how to set up observability across your WEBCON environment, what to monitor, how to spot trouble before users do, and how to react fast when something does go south. Practical patterns for the team on call.

Łukasz Chechelski

Senior Technical Consultant

Networking

Migrating Data into WEBCON: Choosing the Right Approach at Any Scale

WEBCON offers several ways for bring legacy data into the platform: Dictionary Import, Item Lists, the Public REST API, and User-Defined APIs. Each option has its own strengths and trade-offs. This session compares these approaches through two real-world migrations: a 21,000-row Excel migration completed in just three hours – from receiving the source file to a completed import – and a 600,000-file on-premises SharePoint migration spanning two site collections and 20 libraries, resulting in 35,000 workflow instances with attachments. The entire migration was completed in less than 72 hours. You'll leave with a practical framework for selecting the right migration approach based on your project's scale, architecture, and complexity.

Daniel Krüger

Senior Software Developer, DCCS

Networking