The last version of Internet Explorer, version 11, was released on October 17, 2013. This is a very long time ago when taking into account the rapid development of web technologies. These days it is often difficult and time consuming to get modern technologies to work well in this old browser. More and more frameworks are dropping support, and even Microsoft themselves has announced that they will fully drop support for IE in their own services in 2021.
Consequently, we have decided to not include support for IE in the Design Library website.
We strive to simplify what's complex.
Our design process contains of four different parts. It is not always a linear process; it depends on the work previously done and what phase you have in front of you.
The very first stage of the process consist of gathering a better understanding of the problem and the different pieces affecting this problem. The objective for this stage is to explore around the opportunities and in close collaboration with the business gather insights and research and let our customers react and give input to us.
Based on the findings and understanding that we got from the first stage we move forward to look at internal and external knowledge to deepen our understanding and start forming hypotheses on how we can meet the customer needs.
Instead of jumping the gun and move directly to solution mode, this part of the design process supports us in taking the time to further develop on the findings from stage one and elaborate on them.
Overlooking all the findings can lead to focusing on irrelevant data and problems, increasing the risk of failure in the design.
We explore around and test several solutions based on the hypotheses that we have from the previous step and evaluate the solutions against each other to find the one that we want to move forward with to development.
A big win from this part of the design process is to put different departments together. By having designers, engineers, developers or others that have expertise in the area working together, you speed up the problem-solving.
When we have a solution that we believe in and want to take further, we make a more finished design of it, taking into account usability, accessibility and clear copy. To ensure that the design is solving the customer needs and deliver the intended business value, we user test the solution with real end users.
As you might have guessed, we have a number of different methods to use when both ideating and evaluating solutions.
When the team move into the implementation phase, our role is to balance between supporting the ongoing development as well as exploring future features and opportunities.
We made it to the official sign-off to production and launching! The team can now sit down, relax, and they never have to worry about this ever again. Sounds pretty good right? Unfortunately, this is a common pitfall for a lot of companies.
It is in the optimization part of the design process where it really gets interesting, challenging, yes, but it is now that we have the real opportunity to create value for the business and our customers.
As fast as the world around us can change, our customers' needs can change even faster, and we must constantly become better at following up and trimming our solutions in order to continuously improve them.
The second we stop caring about what is in production, we miss the opportunity to learn more about what works and what doesn’t, which will make this design process more and more challenging to apply every time we need to start from the beginning. By iterating through A/B tests, modifying the copy, follow up on effect goals and perform usage test of released features we come closer to ensuring great user experience for our customers.
This is nothing that we do on our own, if we want to reach the sweet spot that we mentioned earlier we need to make it a team effort and get everyone involved to really care about putting the customer first.
All of this, and more, can also be found in our introduction to the design process video.