Developer Understanding Matter

Decoding the IT Language for Biz Leaders

In the “AI for Game Publishing” series, we explored how game business professionals can practically leverage AI, focusing on real-world use cases and strategic implications observed in the field.

However, when discussions with developers turn toward AI and technology, many business stakeholders eventually encounter a familiar phrase:

“That’s technically not feasible.”

At that point, a common question arises:

“The business intent is clear, and the value is obvious. So why is it impossible?”

There’s no need to worry.

This is rarely a problem of intelligence or capability. More often, it is a misunderstanding rooted in a difference of language.

This series aims to clarify the foundational concepts and key terminology of IT, cloud, and AI, and to provide practical guidance on how to communicate more effectively with development teams and engineers.

ℹ️ What “Technically Not Feasible” Really Means

In the game industry, few phrases are heard as often as “That’s technically not feasible.”

In most cases, this does not mean something is truly impossible.

What it usually implies is closer to:

“It’s difficult within the current system architecture,” or

“We need to carefully assess the cost and risk involved.”

Consider the following examples:

The business team suggests enlarging character visuals on the lobby screen, but developers respond that the UI engine structure makes it difficult.

The operation team asks to increase peak-time event exposure, while the server team warns of excessive database load.

The marketing team proposes personalized recommendation banners, only to hear that this exceeds the current API integration scope.

When discussions remain trapped in each side’s terminology, they often conclude with, “Let’s settle for a more realistic option.”

However, there is a critical difference between understanding technical constraints and accepting them without insight.

A good example is NCSOFT’s <Lineage W>, which was designed as a global one-build architecture, allowing players from different regions to interact on a single server, while simultaneously deploying distributed servers to minimize regional latency.

Similarly, Supercell designed its event APIs as independent components from the early stages, enabling real-time event deployment by region and language.

When technology and business share a common understanding from the outset, requests evolve from simple hand-offs into genuine collaboration.

ℹ️ From “Fun” to “Data”: A Shift in the Game Business Paradigm

In the past, a game’s success was largely driven by fun and marketing.

Today, data explains player behavior, cloud enables global scale, and AI delivers personalized experiences.

For example, Nexon’s <KartRider: Drift> leveraged cloud-based log analysis to understand regional access patterns across its global service. By automatically optimizing matchmaking servers, response latency was reduced by 30 percent, significantly lowering early user churn. Based on these insights, Nexon automatically optimized matchmaking servers, reducing response times by 30% and lowering early-stage user churn.

Even the same promotion can produce vastly different outcomes depending on who sees it and when. Identical items can generate multiple times the revenue simply by adjusting packaging and timing.

These precise decisions are all rooted in data-driven insight.

Without understanding this process, game operations inevitably revert to intuition.

That is why game business professionals must develop a foundational understanding of IT, cloud, and AI.

It is the starting point for designing truly data-driven strategies.

ℹ️ You Don’t Need to Code, but You Do Need the Language

The purpose of learning technology as a business professional is not to write code.

The real objective is to communicate at the same level of abstraction.

For instance:

A gaming PM suggests real-time leaderboard updates, and developers reply that real-time queries are costly and require a caching strategy.

A marketer proposes more frequent login bonus events, while developers warn that increased API calls may degrade server response times.

Without understanding concepts like queries, caching, or APIs, business teams may only perceive delays and push schedules harder.

With basic technical literacy, however, the conversation changes:

“Could adjusting the cache refresh cycle help?”

“Is it possible to batch API calls?”

At that moment, the discussion shifts from demand to collaboration—transforming business goals into technically viable solutions.

ℹ️ Why ‘Operations’ Matter More Than “Launch”

The true goal of any game is not launching itself, but sustainable operations and long-term player trust.

Cloud infrastructure plays a central role in this.

Through features like auto-scaling, servers can expand dynamically to handle demand spikes while maintaining consistent service quality worldwide.

For example, KRAFTON’s <PUBG: Battlegrounds> faced massive traffic surges immediately after its global launch yet handled them without service disruption thanks to cloud-based auto-scaling.

Ultimately, clouds are not just a technical choice. It is a business infrastructure designed to minimize operational risk—a survival strategy for modern game publishing.

ℹ️ AI as a Partner in ‘Execution,’ Data as a Partner in ‘Decision-Making’

AI is no longer a novelty feature.

It is deeply embedded across operations, marketing optimization, and player retention.

For example, Riot Games operates an AI-driven Behavior System that analyzes chat patterns, behavior logs, and reports in real time. This system automatically detects toxic behavior and enforces penalties through integrated reward and sanction mechanisms.

Similarly, Ubisoft’s <Tom Clancy’s Rainbow Six Siege> uses AI-powered Dynamic Matchmaking, which analyzes player history, server conditions, and regional traffic density to adjust matchmaking quality in real time. This reduces waiting times and maintains fair competitive environments.

AI excels at identifying patterns that humans may overlook, applying insights instantly, and supporting better decisions at scale.

Without understanding how AI works at a conceptual level, business leaders remain passive recipients of outcomes rather than active users of insight.

♻️ Closing Thoughts...

At its core, games are still about ‘fun.’

But the ability to sustain that fun increasingly depends on how well we understand technology

IT, cloud, and AI are no longer languages spoken only by developers or engineers.

They have become ‘strategic languages’ that every game business professional must understand.

In this series, we will continue to break down foundational IT concepts, cloud architectures, and how AI learns from data, explaining how these elements are reshaping real-world game businesses in practical terms.

In the next post, we will explore the question:

“Who is a programmer?”and take a closer look at how development teams think and work.

※ Disclaimer: This content reflects the author’s personal views and includes only publicly available examples. It does not represent the official position of any company mentioned