{"id":1336,"date":"2016-11-10T18:04:12","date_gmt":"2016-11-10T17:04:12","guid":{"rendered":"https:\/\/www.orionorigin.com\/?p=1336"},"modified":"2023-08-15T23:04:18","modified_gmt":"2023-08-15T22:04:18","slug":"plugin-wordpress-woocommerce-product-designer","status":"publish","type":"post","link":"https:\/\/www.orionorigin.com\/plugin-wordpress-woocommerce-product-designer\/","title":{"rendered":"The Hidden Mystery Behind Woocommerce Product Designer"},"content":{"rendered":"

Behind every business is an untold story. Behind every dream or project too is a story, which only the witnesses can re-count to the world. This is why we are taking you for a stroll down memory lane. To tell you everything about the Woocommerce Product Designer.<\/span><\/p>\n

Why was the Woocommerce Product Designer plugin created?<\/b><\/p>\n

When <\/span>Orion <\/i><\/b>was founded, it was more specialized in the modification of WordPress themes and in the creation of custom web applications for WordPress. One day a<\/span> customer requested for assistance on a project, which consisted of creating a web-to-print customizer which customers can use to design any product before the final order. This done he really appreciated the result and both ends were satisfied. <\/span><\/p>\n

Along the line we realized that the <\/span>demand<\/b> for this type of project on the market was very high. So we decided to do something about it. That is how we launched our first plugin ( the <\/span>Woocommerce Product Designer<\/b><\/a>) onto the market.<\/span><\/p>\n

Audience behavior towards the Woocommerce Product Designer plugin<\/b><\/p>\n

It was an immediate success. The audience was very impressed, but they had lots of suggestions, changes, this or that modification that they wanted on the plugin. So most of the time was spent modifying the plugin to satisfy the need of every customer.<\/span><\/p>\n

Problems faced by the support team<\/b><\/p>\n

1- No quality check:<\/b><\/p>\n

As soon as a client asked for modifications, we integrated them to the plugin. It made the clients happy, \u00a0but on the other hand those who bought the plugin and didn\u2019t understand the use of some integrated features therefore used some of the features wrongly. Unfortunately having said Yes, to every customer need, we ended up building a product that was not easy to use for beginners. Because the quantity of parameters and options included was huge, and nobody would like to waste time in reading a lengthy documentation.<\/span><\/p>\n

2- Poor time management: <\/b><\/p>\n

This led to an enormous quantity of support request related to those \u00a0features useful for few but confusing and useless for most. So we were submerged by questions from customers asking how to do this and that. By the time we solve one issue, two to three new tickets were already on the waiting list. Some clients had the same issue, and we had to solve the issue all over again before the official update.<\/span><\/p>\n

We hadn\u2019t learnt the difference between a bug and support. We didn\u2019t have the reflex to update the plugin every time an issue was resolved. It led to poor time and team management.<\/span><\/p>\n

3- Lack of strategy<\/b>: <\/span><\/p>\n

We were only three developers at that time handling the Woocommerce Product Designer plugin. We didn\u2019t have an advanced methodology to manage the issues concerning the plugin smoothly, which resulted in the fact that we spent more time on support than on improving the plugin itself.<\/span><\/p>\n

\"orion<\/p>\n

The decision to take it off the market<\/b><\/p>\n

Tired! \u00a0All the developers working on the plugin were tired of fixing the same issues over and over again, customizations requests, new features integration. We realized there was a lot of bugs in the plugin due to its complex nature. Handling support and integrating new features drained all of our energy, so we couldn\u2019t do any other thing. So the decision to take it off the market was considered.<\/span><\/p>\n

Why?<\/b><\/p>\n

1- To rest:<\/b><\/p>\n

Oh Yes! We became victims of our own success. So we needed to pause, take a step back and re-organise our work methodology. <\/span><\/p>\n

We had almost \u00a0200 tickets opened each month, it made us tired and exhausted, this in return negatively affected our productivity. <\/span><\/p>\n

2- To stop new clients from coming:<\/b><\/p>\n

Isn\u2019t that bold? Who the heck would have a business and say \u201c please i don\u2019t want more clients. Enough! \u201d. But sometimes you need to hit the nail right where it hurts the most. That\u2019s just what we did.<\/span><\/p>\n

3- To improve on the plugin:<\/b><\/p>\n

We went on a break to take time to fix all the bugs, test it, score the pertinence of every feature integrated, carve a method to manage support and trace a new path for the upcoming features.<\/span><\/p>\n

Audience reaction to the removal of Woocommerce Product Designer from the market:<\/b><\/p>\n

We received hundreds of emails of people who planned to buy the plugin and suddenly couldn\u2019t find it to buy. The disappointment from potential customers was huge. So during the period the plugin was offline, we gave it out for free to those who wanted it, but without giving them the support.<\/span><\/p>\n

Why was the come-back early?<\/b><\/p>\n

Every two days we received requests concerning the Woocommerce Product Designer plugin. \u201cWhen is it going to be back online?\u201d, \u201cCan we have the date it will be back online?\u201d ,\u201dAre there alternatives to get the plugin?\u201d. So we took time to improve the plugin, fixed all the bugs , tested every feature compatibility and now we have a more <\/span>stable version<\/b> online. <\/span><\/p>\n

So it\u2019s now effective and working. <\/span><\/p>\n

Conclusion<\/b><\/p>\n

Today we have learnt our lesson. We now have a procedure that allows us to collect customers feedback and feature requests. Periodically the whole team meets to decide on the \u00a0new features to integrate. We also have a group of beta testers that test the code for eventual bugs.<\/span><\/p>\n

The amount of bugs to fix has reduced drastically. Support is fluid now, compared to those days. More improvement is expected in the coming days. <\/span><\/p>\n

Useful tip<\/b>: A good scoring system model that can help you define the importance of a feature before adding it your plugin is in this article<\/a><\/span>.<\/span><\/p>\n

We hope this exercise answers all your questions and demands on the Woocommerce Product Designer Plugin.<\/span><\/p>\n

Don\u2019t forget to drop your comments. \ud83d\ude42 \u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Behind every business is an untold story. Behind every dream or project too is a story, which only the witnesses can re-count to the world. This is why we are taking you for a stroll down memory lane. To tell you everything about the Woocommerce Product Designer. Why was the Woocommerce Product Designer plugin created? […]<\/p>\n","protected":false},"author":1,"featured_media":153,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[417],"tags":[36,81,17],"class_list":["post-1336","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-designer","tag-woocommerce","tag-woocommerce-product-designer","tag-wordpress"],"acf":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/posts\/1336","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/comments?post=1336"}],"version-history":[{"count":4,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/posts\/1336\/revisions"}],"predecessor-version":[{"id":159374,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/posts\/1336\/revisions\/159374"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/media\/153"}],"wp:attachment":[{"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/media?parent=1336"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/categories?post=1336"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.orionorigin.com\/service\/wp\/v2\/tags?post=1336"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}