MonCatalogueFormations
B2B
For training organizations looking to increase their training sales on MonCompteFormation, MonCatalogueFormations is a training catalog management product that allows users to import, edit, format and export their catalog to MonCompteFormation.
In France, a public platform allows training organizations to publish their training offers delivering certifications recognized by the State. The problem is that this public platform is not very user-friendly for entering training offers, and training organizations sometimes offer many offers.
In addition, they struggle to format (HTML tags) the content of their offers (which can dissuade learners who wish to register). The State platform offers an "XML transfer" service to import training offers in one go, but training organizations lack the skills to format their offers in XML. Training organizations are therefore missing out on selling training because their catalog is far from optimal on the public platform. Competitive analysis: the other solutions have existed for at least 1 or 2 years. They offer: o This major feature 'XML Transfer' among others (ERP for training organizations). In this case, formatting is not offered. The data model of training offers is different from that of the public platform (the public platform is not necessarily intuitive) o Only this major particularity: often the price is high. In addition, import is difficult (the user journey focuses on exporting in XML format and the other steps of "customer work" are omitted).
1. Business Context
We started by creating the business model of our future company. We then broke down the training organization's work into functional (non-emotional) Jobs to be done and developed the value proposition map (we listed the customer's pain points and gains at each stage of the customer's work). Here's an excerpt from our customer Job:
Job Executor | Type of step | Step | Page |
|---|---|---|---|
Training Organization | 1. Define | Plans to import a large number of training courses onto the public platform | |
Training Organization | 2. Locate | Designs their training catalog | |
Training Organization | 3. Prepare | Prepares the Excel import file or the training courses in the application | |
Training Organization | 4. Confirm | Previews the import of their training courses | |
Training Organization | 5. Execute | Imports their training catalog | |
Training Organization | 6. Monitor | Checks the appearance of their catalog | |
Training Organization | 7. Modify | Refines the training catalog and its appearance | |
Training Organization | 8. Conclude | Exports the public platform XML file in the correct format |
Some pages are mapped here with the work steps (others are deliberately hidden).
The Product Owner mapped the tasks to be completed onto the main features that were prioritized, then broke them down into smaller features for estimation (the features are not set in stone at this stage). After estimation, the Product Owner defined the business terms, which serve as our glossary to delineate bounded contexts and the "business domain." The team was able to carry out the domain modeling, and we designed the domain with the help of the Product Owner's preliminary work and the business processes (event storming). Meanwhile, the target users and personas were defined. The Product Owner, who plays multiple roles in our project, drafted the conversations between the future users and our system, which naturally determined the task flows (sequence of pages). Once the pages were ordered and refined, they needed to be prototyped. At this stage, the Product Owner attached the business actions (partially defined during the domain modeling) to the pages. The tasks to be completed, conversations, and entities are also linked to the pages. At the same time, use cases (for product testing), functional requirements (which are subsets of the features), and business rules were specified. The developers were then able to take over, validating the defined domain and setting up the product (front/back end).
2. How did we proceed?
We have obtained several benefits from this first product implemented on Swoft:
Training organizations save a significant amount of time on catalog entry (for a catalog of 100 training courses, we import it in 25 minutes instead of the 800 minutes required for manual entry on the public platform). Additionally, training organizations can simulate the appearance of their catalog and reduce their verification time for formatting.
Training organizations have the ability to format their catalog for a large number of courses (formatting is done on our interface in just a few minutes for 100 training courses, while competitors cannot offer the same service).
Training organizations can access their catalog at any time and modify the data with just a few clicks (if an error were to appear in a hundred training courses, some could end up paying thousands of euros to XML consultants: https://www.codeur.com/projects/303953-fichier-xml-edof). Our UX method and data model make this possible.
Some of our clients have been able to increase their monthly revenue by 500%.
Regarding performance for end customers:
-
We maintain company and product documentation
-
We made sure to build an adequate solution to the defined problem
-
We have improved the collaboration between the sales team and the development team through the borrowed methods
-
The user experience is satisfactory (according to initial feedback and the time between importing and exporting the catalog)
-
We probably saved some development time by shifting some of the workload from developers to the business/product team and optimizing the specifications.
-
We were able to easily support junior profiles, whether on the product or developer side
