Scan for diagnosis and solutions

 

ErgoS is able to examine software on effectivity, efficiency, and convenience in a short period of time.

 

Quick scan

The quick scan is rapid because we use knowledge of the users effectively. The opinion of the users is not our focus. However, their practical experience with the production setting is.

Plan of action usually contains the following:

  1. Meeting to get acquainted.
  2. Formulate an offer.
  3. Optional review of documentation, such as manuals or screen prints.
  4. Preliminary discussion with the production management.
  5. Discussions (while observing) with two or more employees.
  6. Reporting.
  7. Final presentation.

Depending on the size of the project, item 1, 2, and 3 can be combined into one visit of one hour.

Items 4 and 5 are often combined into one visit of half a day.

 

Improvement programs

Prior to the assessment, it is important to think about practical feasible improvement programs. The assessment should aim at the issues that sooner or later can be improved.

Improvement programs on various levels are:

  • New and improved design. During the development of the new software, specification and supervision should ensure that the established problems are not built in again.
  • Improvements. The established problems are repaired by making the supplier/developer apply the intended improvements.
  • Selection. When purchasing the potential software, it can be assessed and selected on usability.
  • Configuration and system management. The software configuration (system configuration, user configuration, macro's etc.) is used to maximise usability.
  • Procedure and use. Users are informed and instructed to adjust and use their software in a healthier way.
  • Other hardware. Sometimes other hardware offers the best result; this often concerns the monitor.

Continuation is possible to achieve feasible solutions. Please consult Design and consultancy.

 

Het is belangrijk om voorafgaand aan de beoordeling na te denken over praktisch haalbare verbetertrajecten. De beoordeling moet zich namelijk richten op punten die vroeg of laat verbeterd kunnen worden.



Verbetertrajecten op diverse niveaus zijn:
  • Opnieuw en beter ontwerpen. Bij ontwikkeling van nieuwe software zodanig specificeren en begeleiden dat de geconstateerde problemen niet opnieuw worden 'ingebouwd'.
  • Verbeteringen aanbrengen. De geconstateerde problemen verhelpen door de leverancier/ontwikkelaar de beoogde verbeteringen aan te laten brengen.
  • Selectie. Bij aankoop de potentiële software beoordelen en selecteren op bruikbaarheid.
  • Configuratie en systeembeheer. De software-configuratie (systeeminstellingen, gebruikersinstelling, macro's e.d.) benutten voor een zo groot mogelijke bruikbaarheid.
  • Werkwijze en gebruik. Gebruikers voorlichten en instrueren om software op een gezondere manier in te stellen en te gebruiken.
  • Andere hardware. Soms biedt andere hardware uitkomst; dit betreft dan vaak het beeldscherm.