Privacy and Cookies

For full functionality, this website places cookies on your computer. In addition, cookies are placed for tracking visitor behavior within Google Analytics. This information helps us improve our website. The cookies contain anonymous information and remain in your browser for a maximum of 2 years. Read more

Make your life easier. Talk to the users.

Software users are often involved late in the development process. This may be due to the speed of the project or monitoring the scope. Usually by then it is too late to go back to the drawing board and making changes at this stage is quite expensive. But how do you solve this?

Use it first.

Use it first.

You have maintained the speed, but the ultimate goal is, of course, the users' use of the software. If they encounter problems, this can lead to frustration or worse, the users use shadow IT instead of the newly developed software.

It is not the first time that end users do not fully share the enthusiasm for software design. However, software implementation is not just launching the software but primarily using it.

How can you prevent this? Talk to the users!

Do this at the start of a project. Not if you already have your entire software in the pipeline, but right from the start. After all, the users know what they need most. They can immediately indicate where the bottlenecks are or where they see improvement. What's great is that they can start testing immediately once you have a design or mock-up ready so that you can respond to the feedback you receive in time and not only when the entire piece of software has been realized.

Software implementation is not just launching the software, it is primarily using the software.

- Enigmatry

Related projects:

Involve users.

Talking alone is often not enough because everything looks good on paper. But if it is then converted into a program, it can be confusing. So, let the users use the software and see what they encounter, which things should be different, and whether the whole thing is intuitive enough. This gives direct feedback that you can take immediately, and you also open the conversation about workflows and priorities. So, several birds with one stone.

Healthcare workers indicate this.

Healthcare workers indicate this.

We recently made significant improvements in their work processes for the healthcare organization Pameijer. In particular, because of the direct feedback from the healthcare employees, we knew exactly where improvements and opportunities lay. When the new software was rolled out, users could get started right away because they knew exactly what the software should be used for.

Without listening to the healthcare employees' feedback and wishes, the software's development and rollout would have been a lot more difficult.

So make your life easier and involve your users in the development!

Read more about Pameijer here.