Digital systems - individual
The checklist can be used to ensure that an individual system is designed with good usability, so that it supports users in their work and meets the demands of the business.
The checklist can be used to ensure that an individual system is designed with good usability, so that it supports users in their work and meets the demands of the business.
Questions
Questions
Questions
Questions
Document name | |
---|---|
Digital systems - individual | |
Area/location | Date |
Invalid Date | |
Approved by | Participants |
Description | The list is based on the following regulations |
The checklist can be used to ensure that an individual system is designed with good usability, so that it supports users in their work and meets the demands of the business. |
Question | Yes | No | N/A | Risk assessment: | Action | Responsible | Latest completion date | Control | ||
---|---|---|---|---|---|---|---|---|---|---|
Low | Medium | High | ||||||||
1. Is the system adapted to the needs of the business? |
|
|
|
| ||||||
2. Has the system been designed in cooperation (between employers and employees) with affected users? |
|
|
|
| ||||||
3. Does the system interact with other systems to support users? |
|
|
|
| ||||||
4. Is it necessary for users to create manual solutions? |
|
|
|
| ||||||
5. Do users need to adapt their work methods to the system? |
|
|
|
| ||||||
6. Is it easy and intuitive for users to share the information required to do their work? |
|
|
|
| ||||||
7. Can external users securely access information? |
|
|
|
|
Question | Yes | No | N/A | Risk assessment: | Action | Responsible | Latest completion date | Control | ||
---|---|---|---|---|---|---|---|---|---|---|
Low | Medium | High | ||||||||
1. Is the interface logically structured? |
|
|
|
| ||||||
2. Is it easy to find the information you are looking for? |
|
|
|
| ||||||
3. Is the interface designed for good readability? |
|
|
|
| ||||||
4. Does the interface work well for digital meetings? |
|
|
|
|
Question | Yes | No | N/A | Risk assessment: | Action | Responsible | Latest completion date | Control | ||
---|---|---|---|---|---|---|---|---|---|---|
Low | Medium | High | ||||||||
1. Is the system technically stable? |
|
|
|
| ||||||
2. Can updates be implemented without disrupting the work? |
|
|
|
| ||||||
3. Is the system sensitive to the connection speed (bandwidth)? |
|
|
|
|
Question | Yes | No | N/A | Risk assessment: | Action | Responsible | Latest completion date | Control | ||
---|---|---|---|---|---|---|---|---|---|---|
Low | Medium | High | ||||||||
1. Have affected users received sufficient training so that the system provides the intended benefit? |
|
|
|
| ||||||
2. Are there colleagues with a deeper knowledge of the system (so-called super users)? |
|
|
|
|
Other Here you can note risks that need to be addressed that are not included in the checklist |
---|
© Prevent – Arbetsmiljö i samverkan Svenskt Näringsliv, LO och PTK
More checklists can be found at www.prevent.se/checklistor