‟You no longer have several years to develop things.
With Design Thinking you can concretise and visualise all the detailed thoughts and needs at a very early stage.”
has comprehensive experience with development of complex IT projects and is familiar with many of the methodologies and approaches which have been popular over the years. Around the turn of the year she has been running two Design Thinking processes with invokers – for widely differing projects: a public supply portal and an internal procurement portal.
“We had representatives of many different employee groups attending, and they all thought that it was really good. They are both pleased to become involved at such an early stage of the process, and they also respect people who are professionally strong and competent and have a comprehensive industry insight. Such as Martin and his team who are responsible for doing the interviews and facilitating the process. The process has really helped broaden the understanding of what we were actually needing.”
‟And it all looks really promising, especially in relation to, say, compliance. When we start with a Design Thinking workshop, it becomes easier to use the system than not to. In that case, we accomplish that people are actually using the finished system – and are using it as intended. This gives significant value even from the very first day.
When you are developing, you need to know that all users are in fact interested in doing it right! Many projects fail because even experienced developers have not been good enough at imagining the actual working situation. As long as you make sure that the easiest way to do things is to use the system, users will do that. Thanks to the concretisation and visualisation, and the mock-ups we are working with in the Design Thinking workshop, we all experience the actual usage situation, so the system can be developed properly from the start.
After all, the whole process inspires widespread user participation. Even at this early stage I see more than one bonus in it: For one thing, people's input is taken into account from the start, so that they feel both heard and seen. For another, they are able to better understand the challenges and obstacles that need to be balanced. You need to weigh the cost of getting everything at the same time. Make sure you include all the necessary bits to meet the needs. However, it is not always possible to meet all the wishes – and in this process, the reason is made visible. Which, in turn, will lead to understanding.”
‟The need for registration has only increased over the years, the complexity is increasing, but you no longer have several years to develop the systems. Design Thinking is good because it is condensed and help to ensure that you consider certain things in detail – before you start the development work. Such as how your solution should really look and feel. In specific and visible terms. This will also enable you to intercept any problems more efficiently and in due course. For it is really good at highlighting the possibilities and potential obstacles in relation to the needs. In this process, for instance, we realised that we were not properly supporting parts of the process. And that was clearly an eye-opener to us. So the error was intercepted before it even occurred.”
“The co-operation with invokers is a good experience – for leaders as well as employees. The invokers team were respected from the start because they demonstrate a strong technical knowledge and industry insight. Our functional needs were clearly and efficiently visualised. And when I compare Design Thinking to other models, e.g. Business Blueprint, and the plain written word – well, this is just so much more efficient.”