Continuous improvement: how does WeLoop use its own tool?

Victor Arfi,

While working on its WeLoop V2.0, WeLoop used itself during the technical acceptance. Being an “application improver tool” is great, using our own product to build our next version is much better.

1. Collecting feedback

Users have tested and analysed each feature (loops creation, interactions, notification email), wordings…

Once they have created their loops, several conversations were engaged to get more details about subjects. User experience has also been tested. Are interactions natural? Do they intuitively engage users? Is the platform easy-to-use? 

“It was unnecessary to send a mail with the list of all correctives and issues. We have made our feedback and discussed them with a simple click instead of creating numerous conversations. Quick and easy!” – Jessy L. – User & Graphist at WeLoop.

Finally, we also received help from our customers. Thanks to WeLoop within their Back-Office, they were able to share feedback about WeLoop itself. As a matter of fact we received 84 feedbacks in a short period of time in order to build the best version as possible.

2. Sorting and prioritizing feedback

With his WeLoop’s interface, our Product Manager oversaw all feedback related to WeLoop V.2.0. Displayed chronologically, he managed to separate “improvement feedback” from “corrective feedback” thanks to tags. First and foremost, he decided to feed the backlog (Jira) of our Dev Team with the “corrective feedback” first.

Then he looked at “improvement feedback” and relied on Reach Rate (% of people who have seen the feedback)  and Engage Rate (% of people who have interacted within a feedback) to prioritize his actions. Note that these two indicators are now live on WeLoop V.2.0 after adding several components of A.I.

“I won a lot of time creating and prioritizing the backlog. Now I can focus my time on other activities such as customer knowledge for example.” – Paseuth T. – Product Manager & CTO at WeLoop.

3. Developing correctives and improvements

On her side, the Product Team was focused on all improvements that needed to be made. Thanks to initial feedback directly integrated into their Jira, the whole team won a lot of time and accuracy.

“It was my first time using WeLoop within real Dev conditions! Unique channel of communication, fluid exchanges and engaged users are real game changers!” – Céline D. – Front-End Developer at WeLoop.

After the development and testing periods, the Product Manager notified and rewarded WeLoop’s users for their involvement. The circle is complete!

4. Delivery of the requested improvement

Not later than 10 days after, after some data migrations, WeLoop V.2.0 was live and used by our customers.
And the feedbacks were not long in coming! (We will write an article about this very soon.)

So, ready to discover this new version?

You want a Demo ? You need more information about WeLoop? Please contact us at: contact@weloop.io