Story

Product managers are usually confused that there are too many back-end platforms to work on: an online store back-end, an order management system, a provisioning system, a payment system, a digital-product distribution system, and a recharge and renew service system. Unfortunately, these systems are siloed so that product managers need to handle orders manually because of the inconsistency and unconnection among these systems, not to mention human errors. As a result, a systematic and integrated system (as seen the integrated back-end system below) is the best way to optimize the user experience in the sale process.

Integrated Back-end System for Management of Customer, Order, Inventory, Provisioning, and so on
The integrated back-end system

Process

  1. User interview: To observe user behaviors and to discuss the experience in using legacy systems.
  2. Legacy system study: To research the website structure, the database design, and the data structure.
  3. Analysis and design: To analyze user requirements and to prioritize tasks. To study a new payment gateway, Authorize.net, and related security issues. To design a consistent structure among these systems.
  4. Development and test: To use .NET Framework, Visual Studio, SQL Server, HTML, CSS, JavaScript, and JQuery. To conduct the user acceptance test. To launch the project. To get feedback from users for next version of the development.

Result

  1. Efficient and automatic order handling over the integrated back-end platform.
  2. Automatic notification. Stakeholders get an automatic notification without manual maintenance of various records. (as seen an expiration notification below)
  3. Inventory management. For example, serial numbers of digital products are distributed automatically after consumers pay online without manual distribution which causes man-made mistakes.
Service expiration notification by an email, by which you can link to the back-end system directly for more information
An automatic email notification