Japan, a developed country with a declining birthrate and aging population. Developing countries with rapidly growing populations.
To increase productivity, we support them with IT education services.
The results of our daily research and studies are summarized on one page as "MicroTech".
It can be part of a larger product or training for service creation. Only a small portion of the results are published, and a product is created within a few weeks or so.
Services,
partner collaboration, and more,
Please feel free to contact us.
As a general principle, we aim to develop specifications and designs that are less prone to failures. This minimizes the frequency and scope of failures. We do our best to avoid hasty releases and tight timelines, which can easily result in failures. In the unlikely event of a service failure, the detection system will raise an alert, and an emergency contact system will be set up to respond with the aim of restoring the service as quickly as possible. In addition, since malicious attacks by third parties are increasing, we are constantly monitoring our servers and defensive barriers to deal with such attacks.
The more services that have a large number of users, the more frequently they are upgraded and improved. Including small improvements, there are about 50 to 100 upgrades per year. Some improvements are easily noticed by users, while others range from program modifications to increase page display speed. The reason for the high number of upgrades is that all of them are planned and developed in-house.
If you discover a problem with the service you are using, please contact us immediately. When we receive a report of a defect, it is quickly disseminated to all project members in the company, and we begin the process of checking it out. Sometimes it is not a defect but a specification, but we will consider implementing it as a usability improvement idea.
Many of us are implementing an IT education system for the first time. First of all, please feel free to ask us what you want to do and whether we can do it. We will reply whether it is feasible with our service or not.
All information received from customers is taken into our proprietary management system. We then narrow down the people who can contact each account authority, so that only the minimum necessary information is required for the next operation. In addition, when information is no longer needed, such as at the end of a contract, it is quickly deleted and no effort is made to retain it. The security of the entire workflow is reconfirmed during ISMS audits and Privacy Mark audits.
When we launch a service, we have a consultant/producer/director/designer/engineer to plan, develop, and test the service. When the service enters the operation phase, customer support and inside sales join to coordinate client support and improvements.
The IT field is constantly emerging with new technologies. However, we believe that we need to be cautious about whether to incorporate them into the operation of our web services. For experimental products, we try out new technologies immediately, but for services that are operated on a large scale, the scope of impact is large, so we incorporate them after repeated testing to get comfortable with them.