问题
Why do complaints keep rising while the product improves?
一方是否显著影响另一方？达到所投票数的四分之三即为定论。
已关闭 · 返回行动阶段
正以访客身份查看。输入用户名即可加入并参与。
问题在各小组之间分配，所以你拿到的是分给你们小组的那些——不是全部 180 个。
已定 177 / 180 0 个待你回答 为什么
没有人能回答几百个卡片对。每个卡片对交给一个小组；意见分裂的卡片对会再转给其他小组，所以它可能稍后出现在你的列表中，即使它起初在别处。已定数量包括所有小组的工作，所以它增长得比你自己的列表缩短得快。
上次计票：177 个已定 · 2 个上交跨组评审组 · 0 个有争议 · 1 个未达法定人数 — 每个评审组至少需要 max(2, 评审组人数的 75%) 张票；你们最小的评审组有 15 名成员.
Complaints about one feature spike after every release → 有影响？ → 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 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 | ✗ 否 | 讨论 |