Automic Release Automation
Release Automation allows companies to automatically deploy their software packages on different kinds of environments. This is very helpful, saves a lot of time and ressources and has the advantage, that the quality of the rollout is on a high standard and doesn't vary. Nevertheless did we face lots of usability issues on this product (which was developed before my time) directly from customer's side. For the next upcoming release we wanted to take this feedback very serious and started with installing and using the software by ourself. And this was really hard, but now we had a feeling of how our customers feel... Our demand was "Allow first time users, without reading any documentation to fully deploy an application". Here is how we tried.
- Responsibilities: User Experience, User Interface Design, Prototyping and Testing, Customer contacts and Customer presentations
- Timeframe: May - August 2015
- Company: Automic, Release Automation
1. ON SITE ANALYSIS
We addressed all possible customers, but this time we failed. The time frame was too tight and we had an almost completely new team with no customer contacts so far. BUT we had an alternative - our Pre Sales Team. They knew quite good the situation on site and were power users themselves. Although they still had a good sense of what was wrong with the product.
So we started with a 3 Day Workshop
So we started with a 3 Day Workshop
2. WORKSHOP
So we started with a 3 Days workshop - Product Manager, UX Designer, Pre Sales and a Product Designer. The goal was to define what needs to be done to improve the UX of this product. We decided from the beginning, not to add additional features, but to really concentrate on a usable experience. We started with our Personas and their different roles in the context of Release Automation. When we achieved clarity about that, Story Telling helped us to get a feeling of our customer's needs and use cases. Out of the stories we created a first IN / OUT list, that gave us an impression of the whole project.
On Day 2 we continued with the creation of a Story Map.
On Day 2 we continued with the creation of a Story Map.
3. STORY MAPS
The story map we created was actually our base for the next 3 month. It covered everything we wanted to achieve and we also set this in a timely context, to see what was realistic. Again I can say, the creation process of such story maps is a huge benefit. Everyone gets the same view on what needs to be done, what is possible and - what is not possible and why.
The second big advantage is, that this map accompanies you through the whole project and everyone else, who steps by, can see what you are doing. So it is your and your collegues base and control
The second big advantage is, that this map accompanies you through the whole project and everyone else, who steps by, can see what you are doing. So it is your and your collegues base and control
4. PAPER PROTOTYPE
based on the results of the survey should be one thing after all: Fun. If I don't experience fun while bringing ideas to reality, maybe something is wrong. As soon as I accepted that failure is an effective way to proceed, I became a lot more productive.
I have to admit, I am an AXURE enthusiast and I always try to push the boundaries of this tool. The results you can achive there are awesome. See the prototype we presented at the World ATM congress 2012.
I have to admit, I am an AXURE enthusiast and I always try to push the boundaries of this tool. The results you can achive there are awesome. See the prototype we presented at the World ATM congress 2012.
4. TEST
Prototypes allow you to gather feedback in early stages from your potential users. Here you see a high level test-setup we presented at the Airpower in Zeltweg. It was a perfect location for our visitors - cameras mounted on the roof of the old tower, the presentation inside the old tower.
Testing, anaylzing the results, redesigning and starting from the beginning. It's always this iteration, therefore "Quantity leads to Quality" (Bill Buxton). When no users are available and a quick test is necessary, then an Expert Review is a very useful method. Invite your collegues to a formal review and collect as much feedback as possible.
Testing, anaylzing the results, redesigning and starting from the beginning. It's always this iteration, therefore "Quantity leads to Quality" (Bill Buxton). When no users are available and a quick test is necessary, then an Expert Review is a very useful method. Invite your collegues to a formal review and collect as much feedback as possible.
5. VISUAL DESIGN
Before we started, we were happy to finish our Automic Design Guidelines. This was only a first step, where we defined fonts, icons and the usage of colors but it helped us a lot to achieve a consistent appearance with all the other products.
The visual design was created by an external company before I arrived at Automic, so the idea was little improvement here and stick to the patterns. This is something that always causes discussions, especially with new employees ;)
The idea shall be stick to the patterns, but let room for improvements. A challenge for every Design responsible and for sure one of the core items to solve in every Design Team. If you don't get this done right, there are two possibilities.
a) You run in inconsistency and chaos between your products
b) You have a rigid Pattern and Design Library without the possibility to easily improve issues.
The visual design was created by an external company before I arrived at Automic, so the idea was little improvement here and stick to the patterns. This is something that always causes discussions, especially with new employees ;)
The idea shall be stick to the patterns, but let room for improvements. A challenge for every Design responsible and for sure one of the core items to solve in every Design Team. If you don't get this done right, there are two possibilities.
a) You run in inconsistency and chaos between your products
b) You have a rigid Pattern and Design Library without the possibility to easily improve issues.
6. DELIVERABLES
This shows the booth for Release Automation of the Automic World. It was really unbelieveable, to see first-time-users working with our new solution and getting it. Our demand "Allow first time users without reading any documentation, to fully deploy an application" was no longer an idea but became reality. The whole product got a huge focus, not only from customer but also from Automic side and was a real success. Thanks to all the guys who helped making this become a great product.
The moment when I see users first time trying out the implemented solution, we worked so hard on - and getting it, is one of the reasons being a Designer for me. There are few moments in my work life that are greater and fulfill me with more joy and pride.
The moment when I see users first time trying out the implemented solution, we worked so hard on - and getting it, is one of the reasons being a Designer for me. There are few moments in my work life that are greater and fulfill me with more joy and pride.
