[BPUSS Case Study] How to Prevent the Formalization of QA?

Added to bookmarks
Bookmarks list

Bookmark has been removed
Bookmarks list

You can't add any more bookmarks

By registering as a member, you can increase the number of bookmarks you can save and organize them with labels.
Free membership registration

last updated：Dec 26, 2022

ドゥエピオン

Official site

[Currently distributing case materials for download] There are no usable answers in the QA list! Introducing a case where the entire team can update the QA.

We would like to introduce a case study on problem-solving using the internal inquiry efficiency system "BPUSS" at Duepion. If QA updates are not made, it becomes difficult to find usable QAs, leading to situations where the QA list is not used, resulting in mistakes and an influx of inquiries to the leader. To address this, we enable staff to register and publish the questions they ask the leader as "My QA" in our product, allowing the entire team to update the QA collectively. 【Case Overview】 ■Issue - Without updates, the QA list is not utilized, leading to mistakes and a concentration of inquiries to the leader. ■Solution - By registering and publishing the questions asked as "My QA" in our product, the entire team can collectively update the QA. ★You can view the adoption case materials for our service by clicking the "PDF Download" link below.