The value of the system starts from the day it is launched.
Handover, contact points, priority of improvements. How to connect to operations from the development stage.
Releasing the system is an important milestone. It is also the starting point for users to begin using it in their daily work.
Treat handover as part of the development process.
It's important to organize the information needed to continue using the system, not just the operation methods. When changing settings, confirm who is managing which account.
We prioritize ensuring that the right people can access the information they need, rather than focusing on the volume of documentation.
Decide on the first step when a problem occurs.
If contact information and scope of response are ambiguous, even small issues can take time to verify. We agree on the contact point, response time, roles of both parties, and the information needed for verification before release.
Link improvements to objectives.
Requests are not all of the same priority. We confirm who is affected and what is happening in the current situation, then set priorities.
Improvement is not just about adding new features. Reduce one input, change confusing displays, eliminate unnecessary tasks. While observing daily work, we choose the next step.
Build. Operate. Improve. represents the attitude of valuing the connections. The specific support content and scope of responsibility are agreed upon for each project.