Merit 1. Maximize cost effectiveness by maximizing SaaS/software functions

Due to the difference in IT literacy between users and the difficulty of operating each software, it is not uncommon for newly introduced software to not be utilized. Also, in order to prevent usage that ignores the policy, I think that there are many companies that use it with some functions restricted.

In such a situation, the software introduced and developed cannot be fully utilized, and the investment is wasted.

By using DAP, resistance to new software can be minimized, so anyone can master new software at the same level regardless of "differences in IT literacy".

Merit 2. Cost reduction during software installation (Post)

Common processes after installing software include creating manuals, conducting seminars, and responding to inquiries at the support desk.
They prepare content according to each user's literacy and company policy, which takes time and effort. In addition, there are many cases where the support desk is outsourced, and in that case, costs will be incurred.

What is the effect on the above introduction costs? It is not uncommon for people to not see the manuals that they have worked so hard to read, or not to participate in the seminars. Also, in the early stages of implementation, the support desk is overwhelmed with similar inquiries, and that alone can consume resources.

DAP easily realizes a "manualless" world. As a result, you can significantly reduce the "costs" that were incurred during introduction, such as manual creation, training sessions, and function restrictions that were set individually. In addition, since it encourages users to use it autonomously, it improves their self-solving ability and leads to the "standardization" of inquiry content.

Merit 3. Eliminates the hassle of frequently updating manuals

When installing software, I think the general flow is to create a manual and spread it to inform users of its use. However, in the case of cloud services, since services and new functions are updated frequently, the problem is that manuals that have been prepared can quickly become outdated. Also, since the manual is updated every time the service is updated, the manual may exceed 100 pages. As a result, users cannot find the information they want in a limited amount of time.

DAP replaces conventional manual onboarding (human adaptation), such as manual creation and updating, with target software and user support on the software screen simply by installing it as a set. is easy to handle, and for users, it can be established (Product Led) simply by using the software as usual.

From the above three advantages, it can be said that digital adoption is a new post-implementation mechanism that creates mutual benefits for software administrators and users.

Effects of introducing a digital adoption platform

Manager's perspective

• It is difficult to look back after implementing the digital adoption platform
  In implementing DAP, the scope of the administrator's responsibility ranges from implementing guides to user onboarding. However, it is not possible to grasp whether the implemented guide is not skipped by the user and whether the DAP is producing the appropriate effect. Even if you try to check the above with the software you are using, the granularity of the log varies depending on the software, and it is often difficult to visualize the unified usage status. In order to properly utilize and invest in software, it is important to collect usage data by users and analyze it.
  In addition, as information to be visualized, not only quantitative data such as the number of active users, but also qualitative data such as user comments are used, and turning the PDCA cycle using DAP leads to efficient onboarding. It's the point.
• It takes time to implement due to the waterfall type introduction method
  Most of the normal DAP products are carefully designed at the time of implementation and are mostly waterfall type with coding.

As I mentioned at the beginning, DX has been progressing in recent years, and corporate business is changing rapidly. Under such circumstances, the waterfall cycle needs to be redesigned from scratch every time the specifications change, and it is necessary to improve the speed of digital adaptation.

user perspective

• Since the guide is displayed everywhere, it can be a hindrance to work
  A DAP guide will pop up to the user. Therefore, the user can intuitively operate it, which is effective for the establishment of the software.
  However, since this guide is set in various places where onboarding is required, the guide will be displayed everywhere, and it will have the opposite effect of being intrusive and not being able to see it.
  Therefore, it is necessary to set the guide so that it is displayed at the "minimum necessary and pinpoint", considering the timing of display and the target user attributes.