Not only your external customers prefer a good UX and usability. Also internal applications and software need a good UX and usability. Especially for new software this is important for a sufficiently high acceptance. Also none a good UX and good usability provide for an enormous cost saving.<\/p>\n

Problems with UX in internal applications<\/h2>\n

You surely know this as well. If processes are to be changed internally or new software is introduced, there are always the voices that speak against it. Sentences like: “We have always done it this way.” or “We already tried that, it doesn’t work.” etc. It is always also a process where you have to take your colleagues and employees with you. This is the only way to avoid unpleasant discussions and to create a product that really helps.<\/p>\n

<\/p>\n

But not only the acceptance of the employees is often a problem, but also the understanding of the management and the staff that something new really has to be purchased. Development is always associated with costs. These can definitely pay off in the medium and long term, but there is still a huge risk. If your product does not solve the real problems, then nobody is helped. How such a thing can end in extreme cases, you can read here: spiegel.en<\/p>\n

Arguments for UX in internal applications<\/h2>\n

To create an acceptance also for your discipline and UX for the project, you need powerful arguments. The arguments at this point are the same that apply to UX in general.<\/p>\n

Cost savings<\/h3>\n

In the medium and long term UX saves money. Most of the time the initial effort will be a bit higher, but if it saves your company a lot of money in the end, it’s worth it. Through a good UX you can achieve that:<\/p>\n

\n
1. Make workarounds with Excel spreadsheets, for example, a thing of the past.<\/li>\n
2. Processes are designed to be effective and efficient and your software supports those very processes.<\/li>\n
3. The employees need no or only a little training to be able to use the software adequately.<\/li>\n
4. You avoid misdevelopments, because you can test the product iteratively with your users.<\/li>\n<\/ol>\n

   UX and agile approach<\/h3>\n

   Especially for internal applications, agile projects are preferable, since you have your customers directly on site and can expect regular feedback. UX and agile approach can go hand in hand very well and thus bring the product forward. Your colleagues will thank you for this iterative approach. Use the whole User Centered Design process to create an optimal UX for your colleagues.<\/p>\n

   <\/p>\n

   Benefits of UX for internal applications<\/h2>\n

   It should be easier to carry out the entire UCD process, especially for internal applications. Your colleagues are on site and work every day on the existing processes with the existing software. For user needs, reach out to your colleagues and especially ask about current workarounds, what’s wrong with the process, and what’s causing your colleagues to have to do more work. When exactly do they reach the point where they make mistakes or at least curse?. All these are indicators for improvements and optimizations.<\/p>\n

   Usaiblity testing should also be easier. Since recruiting can take place internally, you should normally have no problems finding test subjects. However, coordinate this with your project management. Now and then this can lead to problems between departments. Ask how you can best go about it.<\/p>\n

   Feedback in the review<\/h3>\n

   You can also use the SCRUM review after each sprint as a feedback round. Especially if your system is already live, you can get valuable feedback here. Invite your colleagues outside your project to participate. They use the system regularly and can tell you and your team exactly when things are going in the wrong direction. Take this feedback benevolently and consider with your team or also the feedback provider how this problem can be solved, if necessary. can be solved.<\/p>\n

   Documentation and processes<\/h2>\n

   <\/p>\n

   Even if you manage to put a great usability in your software, it is very important that you document everything. Document the process you optimized and show what problems existed before and how you solved them. Show that no important process step has been lost. Document all this clearly, so that every colleague can see that his opinion has also been incorporated into the product. Also to ggfs. To detect gaps, it is important that the process is documented in detail. However, such documentation is often also important to protect you ‘politically’.<\/p>\n

   When your software is ready, build a short term first level support with your team. Also you can invite to several appointments to give a short training session. Always remember, your colleagues may have been used to something different for years. School them briefly, even if this is not absolutely necessary. Your colleagues will thank you. Also, you and your team should communicate that there is some sort of support so that your colleagues can contact the team or you if something is still not working the way you thought it would.<\/p>\n

   Conclusion<\/h2>\n

   UX for internal applications is basically very similar to how it is towards your customers. Make sure that you involve your colleagues in the process to generate acceptance for your product and changes. Offer a support and a small introduction afterwards, your colleagues will thank you for it. Always remember to document the optimized processes in detail and present them transparently.<\/p>\n","protected":false},"excerpt":{"rendered":"

   Not only your external customers prefer a good UX and usability. Also internal applications and software need a good UX […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[135],"tags":[],"yoast_head":"\n