Characteristics of SaaS
SaaS software release operation how to plan reasonably, first of all, we should make clear the characteristics of the whole SaaS software, SaaS software as a whole to provide product features is very much, even if only for a vertical field. And the same SaaS, for different enterprises, it is often used in depth and personalized configuration, which means that the complexity of our whole SaaS system will be relatively high.
Service complexity leads to UI complexity
And with the development of SaaS and complexity of the whole business is rising, so often our entire SaaS function point will be more, because the function point more, often in order to allow the user to quickly to find these features, a lot of times we often is not a simple UI design, is a relatively complex UI design.
However, due to the complexity of rule presentation in the whole interaction and UI design, we often need to operate the following aspects for users before the release of the new version:
Training KA users
First, before launch, we may invite the CIO, IT manager or the enterprise KOL of a typical customer to the SaaS training center. SaaS service providers to do some targeted training, to help enterprise core personnel can quickly master the new version of the function and learn to use.
Product technical operation
Secondly, for many UI revisions, data upgrades or performance upgrades, we need to give users a very clear reminder in advance on the whole software. For example, we often have banner or horselight operation prompts on PC or mobile terminals.
Release operational experience
The SaaS service informs the user of what upgrades will be made at what time and at what time, as well as any service instability that may occur during the upgrade process.
However, for some very core modules, we always keep two versions in the upgrade process, one is the old version and the other is the new version, so as to ensure that the new version will minimize the interference to the whole business of users. User when encounter some problems, he can quickly switch to the old version, in our experience, we are doing some big function in the process of revision, even if we put some function after the upgrade of all delivered to the user, we are also in the function design stage to do a lot of user research, also made a lot of detailed scientific data design, However, in the end, before the feedback and requirements of the majority of paying customers, we mainly retained the functions and features of the old version, and customers felt that the old version was more accustomed and effective.
, of course, how to go into this new version, user often also need a very powerful mechanism of gray level transition, all tenants of enterprise, we will first for these enterprise groups, such as we were divided into svip enterprise group, VIP enterprise group, paid enterprise groups, the standard enterprise groups, small micro enterprise group and free enterprise, for all enterprises, We will offer a very flexible gray cycle ability, ensure that small micro enterprises to free enterprise, free from the enterprise to pay, are gradually able to upgrade to the new version, including for some, they want to stay longer in older versions, we in order to meet this requirement, gray level need to be flexible enough to release.
Multi-sectoral collaboration of SaaS
So for the entire SaaS software release rhythm, often require the sales department, the department of customer success, the product design department, operating department collaboration between cooperate, often SaaS software operations cannot use technology to solve all the problems, need all departments to do this kind of collaboration, finally ensure that the user can be in touch to understand the new version before the new version, Understanding the use of the new version can complete an upgrade of enterprise digitization, and in the whole process, let the user experience to minimize interference.