구조 잡기 · Why do complaints keep rising while the product improves?

질문

Why do complaints keep rising while the product improves?

한쪽이 다른 쪽에 크게 영향을 줍니까? 던진 표의 4분의 3으로 정합니다.

게스트로 보는 중. 참여하려면 닉네임을 입력하세요.

질문은 그룹별로 나뉘어, 내 그룹이 받은 질문만 나옵니다. 전체 180개가 다 나오지는 않습니다.

이유

수백 개의 쌍을 혼자 답할 수는 없습니다. 각 쌍은 한 그룹에 갑니다. 의견이 갈린 쌍은 다른 그룹에 넘어가므로, 다른 곳에서 시작한 쌍이 나중에 내 목록에 나올 수 있습니다. 확정된 수에는 모든 그룹의 작업이 들어가므로, 내 목록이 줄어드는 것보다 빨리 늘어납니다.

확정 177 / 180 내가 답할 질문 0개

지난 집계: 결정 177 · 그룹 간 패널로 넘김 2 · 이견 있음 0 · 최소 인원 미달 1 — 패널마다 던진 표가 최소 max(2, 패널의 75%) 필요합니다. 가장 작은 패널의 멤버는 15명입니다.

닫기 ✕

Most complaints are about waiting, not about the answer → 영향을 주나? → The knowledge base is written by people who have never taken a call

아직 아무 말도 없습니다.

끝난 단계입니다. 쌍과 투표 기록은 위에 있습니다.논리 확인 ↗

Refund policy is different on the website, in the app and in the script	→	…	미결 넘김	논의하기
The phone line closes at five and the emails start at five past	→	…	미결 넘김	논의하기
The best agents leave within a year	→	The phone line closes at five and the emails start at five past	미결	논의하기
Most complaints are about waiting, not about the answer	→	Complaints are counted only when someone uses the word complaint	✓ 예	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	Complaints about one feature spike after every release	✓ 예	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	Complaints are counted only when someone uses the word complaint	✓ 예	논의하기
Most complaints are about waiting, not about the answer	→	A customer who complains twice gets the same first reply both times	✓ 예	논의하기
A customer who complains twice gets the same first reply both times	→	Most complaints are about waiting, not about the answer	✓ 예	논의하기
Refund policy is different on the website, in the app and in the script	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✓ 예	논의하기
Refund policy is different on the website, in the app and in the script	→	A customer who complains twice gets the same first reply both times	✓ 예	논의하기
A customer who complains twice gets the same first reply both times	→	Complaints are counted only when someone uses the word complaint	✓ 예	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	Refund policy is different on the website, in the app and in the script	✓ 예	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	Agents who take the time to fix a problem properly miss their numbers	✓ 예	논의하기
Survey requests go out before the problem is solved	→	The same question is answered a hundred times because the help page is wrong	✓ 예	논의하기
Survey requests go out before the problem is solved	→	Templates make every reply sound like nobody read the message	✓ 예	논의하기
Nobody from product reads the ticket tags	→	Survey requests go out before the problem is solved	✓ 예	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	Survey requests go out before the problem is solved	✓ 예	논의하기
Nobody from product reads the ticket tags	→	The best agents leave within a year	✓ 예	논의하기
Nobody from product reads the ticket tags	→	The same question is answered a hundred times because the help page is wrong	✓ 예	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	Complaints are counted only when someone uses the word complaint	✓ 추론됨	논의하기
Complaints are counted only when someone uses the word complaint	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
Refund policy is different on the website, in the app and in the script	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
…	→	Complaints are counted only when someone uses the word complaint	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Complaints are counted only when someone uses the word complaint	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	…	✗ 아니요	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Refund policy is different on the website, in the app and in the script	→	Complaints are counted only when someone uses the word complaint	✗ 아니요	논의하기
Most complaints are about waiting, not about the answer	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
Most complaints are about waiting, not about the answer	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
Most complaints are about waiting, not about the answer	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
…	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	Complaints are counted only when someone uses the word complaint	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	…	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
…	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	…	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
Refund policy is different on the website, in the app and in the script	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
…	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
…	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Most complaints are about waiting, not about the answer	→	…	✗ 아니요	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	…	✗ 아니요	논의하기
Most complaints are about waiting, not about the answer	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	…	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
…	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
Refund policy is different on the website, in the app and in the script	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
Refund policy is different on the website, in the app and in the script	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
Refund policy is different on the website, in the app and in the script	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
Complaints are counted only when someone uses the word complaint	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	A customer who complains twice gets the same first reply both times	✗ 아니요	논의하기
Angry customers are moved to the back of the queue by the priority rules	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
…	→	Most complaints are about waiting, not about the answer	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	…	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	Complaints about one feature spike after every release	✗ 아니요	논의하기
…	→	Agents who take the time to fix a problem properly miss their numbers	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Most complaints are about waiting, not about the answer	→	The knowledge base is written by people who have never taken a call	✗ 아니요	보는 중 ↑ · 닫기 ✕
Most complaints are about waiting, not about the answer	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
Complaints about one feature spike after every release	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	Angry customers are moved to the back of the queue by the priority rules	✗ 아니요	논의하기
Agents cannot issue a refund without a manager, and the manager is in meetings	→	Complaints are counted only when someone uses the word complaint	✗ 아니요	논의하기
…	→	Refund policy is different on the website, in the app and in the script	✗ 아니요	논의하기
The knowledge base is written by people who have never taken a call	→	…	✗ 아니요	논의하기
A customer who complains twice gets the same first reply both times	→	The knowledge base is written by people who have never taken a call	✗ 아니요	논의하기
Agents who take the time to fix a problem properly miss their numbers	→	Agents cannot issue a refund without a manager, and the manager is in meetings	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	The best agents leave within a year	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	The best agents leave within a year	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
The best agents leave within a year	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Nobody from product reads the ticket tags	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
…	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	…	✗ 아니요	논의하기
Nobody from product reads the ticket tags	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
…	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
The best agents leave within a year	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	…	✗ 아니요	논의하기
Nobody from product reads the ticket tags	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
The best agents leave within a year	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	The best agents leave within a year	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
The best agents leave within a year	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
…	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
Nobody from product reads the ticket tags	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	The best agents leave within a year	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
The best agents leave within a year	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	…	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
…	→	The best agents leave within a year	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	The best agents leave within a year	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	Survey requests go out before the problem is solved	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	…	✗ 아니요	논의하기
…	→	The same question is answered a hundred times because the help page is wrong	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	The best agents leave within a year	✗ 아니요	논의하기
Nobody from product reads the ticket tags	→	…	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
…	→	Nobody from product reads the ticket tags	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	…	✗ 아니요	논의하기
…	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
Survey requests go out before the problem is solved	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
The phone line closes at five and the emails start at five past	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
Managers see the dashboard, agents see the queue, nobody sees the customer	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기
Templates make every reply sound like nobody read the message	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
…	→	The phone line closes at five and the emails start at five past	✗ 아니요	논의하기
Customers repeat their problem to every person they are passed to	→	The best agents leave within a year	✗ 아니요	논의하기
The best agents leave within a year	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
The best agents leave within a year	→	Managers see the dashboard, agents see the queue, nobody sees the customer	✗ 아니요	논의하기
Nobody from product reads the ticket tags	→	Escalations go to a team that does not read the ticket history	✗ 아니요	논의하기
The best agents leave within a year	→	…	✗ 아니요	논의하기
Escalations go to a team that does not read the ticket history	→	…	✗ 아니요	논의하기
…	→	Templates make every reply sound like nobody read the message	✗ 아니요	논의하기
The same question is answered a hundred times because the help page is wrong	→	Customers repeat their problem to every person they are passed to	✗ 아니요	논의하기