Why it’s important
Users expect to be able to use online services 24 hours a day, 365 days a year. If a service is unavailable or slow, it can mean those users aren’t able to get their work done. Minimize service downtime and have a plan to deal with it when it does happen. Know how users will be affected and ensure that service availability is communicated, users are supported, and that we learn from outages.
What to consider
- How do your users interact with your service?
- What is the planned availability of your service (i.e., 24/7 or business hours only)?
- Who are the service contacts or leads responsible for assisting end-users? For responding to a service outage?
- Do you want direct end-user support from the DoIT Help Desk? In which situations do you anticipate your end-users needing help?
Toolkit: Principles and practices worksheet
Capture info as you work through each of the principles.
Get in touch with the DoIT Interoperability Team to start your interoperability project.
Put this principle into action
- In the early stages, learn about your users — why, how, where and when they’ll interact with your service
- As you progress,
- Determine if your service will be available 24/7 or business hours only
- Decide who will help your end-users during onboarding, when they need technical assistance, when your service experiences an outage, etc.
- As the development of the service evolves, determine if you want the DoIT Help Desk to triage help calls. Work with the Help Desk to create documentation.
Dig deeper into this principle
DoIT’s Service Transition Team is here to help.
Please send feedback to the DoIT Interoperability Team. We welcome your input!