About 60% of IT and Game Industry Professionals Report Challenges in Quality Control and Debugging; Top Issue is 'Lack of Testing Time' at Approximately 56%

■ What is the actual state of quality control in the IT and gaming industries?

Our lives are supported by various software, from smartphone apps and business systems to games. While convenient, a single bug can halt operations or damage user trust.

The people responsible for quality control and debugging (finding and fixing program bugs) support this quality. So, how do those working in the IT and gaming industries perceive their company's quality control system, and what challenges do they face?

Therefore, we conducted a joint survey with Q Ace on the 'Importance of Quality Control in the IT and Gaming Industries' targeting 30 men and women nationwide who responded in a preliminary survey that they have worked in the IT or gaming industry.

*When citing the content of this press release, please comply with the following:

- State that the source is 'a survey by NEXER Inc. and Q Ace Inc.'
- Place a link to Q Ace Inc. (https://q-ace.co.jp/)
- Place a link to the relevant article (https://q-ace.co.jp/column/it・ゲーム業界経験者の約6割が品質管理・デバッ/)

Survey Overview: 'Survey on the Importance of Quality Control in the IT and Gaming Industries'

Survey Method: Internet questionnaire

Survey Period: May 1, 2026 – May 7, 2026

Survey Target: Men and women nationwide who responded in a preliminary survey that they have worked in the IT or gaming industry

Valid Responses: 30 samples

Survey Questions:

Question 1: Was the quality control and debugging system at your workplace well-established?

Question 2: Please tell us the reason for your answer.

Question 3: How important was quality control and debugging considered within the company?

Question 4: Please tell us the reason for your answer.

Question 5: Have you ever outsourced quality control or debugging?

Question 6: Please tell us the reason for your answer.

Question 7: Do you have any challenges or concerns regarding quality control or debugging?

Question 8: What kind of challenges? (Multiple answers allowed)

Question 9: Please tell us specifically about the challenges.

*Note: Percentages are rounded to the first decimal place, so totals may not equal 100%.

■ 53.3% Responded that their Workplace's Quality Control/Debugging System was 'Well-Established'

First, we asked whether the quality control and debugging system at their workplace was well-established.

As a result, 'Somewhat well-established' was the most common response at 30.0%.

This was followed by 'Sufficiently well-established' at 23.3%, 'Slightly insufficient' at 23.3%, 'Insufficient' at 13.3%, and 'Don't know' at 10.0%.

Combining 'Sufficiently well-established' and 'Somewhat well-established' gives 53.3%, indicating that over half of the respondents felt the quality control and debugging system was well-established.

On the other hand, combining 'Slightly insufficient' and 'Insufficient' gives 36.6%, revealing that a significant portion felt uneasy about the system.

We asked for the reasons behind their answers. Here are some excerpts.

Responses from those who answered 'Sufficiently well-established' or 'Somewhat well-established':

- Because regular code reviews and tests are conducted during project progress. (Male, 30s)
- Because various tools were thoroughly vetted. (Male, 30s)
- It wasn't perfect because bugs occurred occasionally. (Female, 20s)

Responses from those who answered 'Slightly insufficient' or 'Insufficient':

- Because procedures are often not documented, leading to reliance on specific individuals and inconsistent quality. (Male, 30s)
- Because there aren't enough people. (Male, 40s)
- Because there is a shortage of staff. (Male, 50s)
- The quality data is clearly bad, but they constantly falsify it to reassure customers. It's sloppy, so I don't think the system is established at all. (Male, 40s)

Respondents who felt the system was 'well-established' cited mechanisms that ensure quality organizationally, such as regular code reviews, testing, and tool evaluation.

Conversely, those who felt it was 'insufficient' frequently mentioned issues like over-reliance on specific individuals and staff shortages. It appears that in some workplaces, procedures depend on individual experience and judgment without being documented, leading to quality inconsistencies.

■ 96.7% Responded that Quality Control and Debugging were Considered 'Important' at their Workplace

Next, we asked how important quality control and debugging were considered within the company.

As a result, 'Very important' was the most common response at 66.7%.

This was followed by 'Somewhat important' at 30.0% and 'Not important at all' at 3.3%.

Combining 'Very important' and 'Somewhat important' totals 96.7%, indicating that almost all respondents felt that quality control and debugging were treated as important tasks at their workplace.

We asked for the reasons why they were considered important. Here are some excerpts.

Reasons for being considered important:

- Because quality directly links to customer satisfaction and trust. (Male, 30s)
- Because mistakes are not allowed, it's a rule to do it properly. (Male, 50s)
- To continue receiving work orders. (Male, 50s)
- Because it causes failures. (Female, 20s)
- Because it is directly connected to the trust relationship with clients and is a fundamental prerequisite for doing business. (Male, 30s)

Many respondents who said it was 'considered important' cited its impact on customer satisfaction and trust.

Additionally, the comment 'to continue receiving work orders' suggests that quality control and debugging are seen not just as verification tasks, but as crucial activities for business continuity and building customer trust.

■ 36.7% Responded that They Have 'Outsourced' Quality Control or Debugging

Next, we asked whether they had experience outsourcing quality control or debugging.

As a result, 36.7% answered 'Yes', and 63.3% answered 'No'.

While about 37% have experience with outsourcing, it appears that many workplaces handle quality control and debugging in-house.

We asked for the reasons behind their answers. Here are some excerpts.

Responses from those who answered 'Yes':

- Due to a lack of in-house resources. (Male, 30s)
- Because the number of employees was too small. (Male, 40s)
- To reduce costs and incorporate a third-party perspective. (Male, 50s)

Responses from those who answered 'No':

- Because it was handled in-house. (Female, 20s)
- Because of high costs and the ability to manage it internally. (Male, 30s)
- Because they wouldn't take 100% responsibility. (Male, 50s)

Those who had outsourced cited reasons such as compensating for a lack of in-house resources or incorporating a third-party perspective to improve quality.

On the other hand, those who had not outsourced mentioned concerns about cost, the ability to handle it internally, and