To properly see the difference between main and side issues is very important. The first most obvious solution is not always the right one. How do I determine the real problem?
A good help is to create user case scenarios (user journeys): If we solve this using method A, will all other scenarios still work properly? What will be the effort for the development team?
A good example was an assignment to create better radiator connection. Instead of only fixing the connection bugs, we ended up creating a wizard to guide the user to the process with simple visual feedback. In hindsight this sounds very logic, but that was not our first idea.
Responsive Photo Gallery Powered By Weblizar
It was time-consuming and difficult to draw radiators in the software and connect to a system. Knowledge was needed because of some technical limitations and bugs in the software.
We created a wizard that saved about 15 minutes of modeling for the engineer. A new idea coming from the feedback of customers, support and competitors.
And then there are always ideas and next steps to take: