large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

<a href="https://uxdesign.cc/designing-performance-load-a5ff8e3159d5?source=rss----138adf9c44c---4">uxdesign.cc &ndash; User Experience Design &mdash; Medium</a> | Anton Nikolov 
<h4>Should we always design to reduce performance load?</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a5N4vokpfnlmUnnJMou9zw.jpeg">Photo by <a href="https://unsplash.com/photos/3y1zF4hIPCg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hans-Peter Gauster</a> on <a href="https://unsplash.com/search/photos/stress?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>
The article is focused on the performance load in relation to what the user experiences, when using the product. The assumption is that the system/product is working within acceptable speeds and can bare the usage load.
So, performance load in the context of this post, means mental or physical effort that is required from the user when using products. Other terms that refers to the same are Cognitive load(mental/perceptual loa) and Kinematic load(force that causes motion e.g. physical effort for the human body).
I often hear fellow designers (including myself) who argument their decisions with phrases, which boil down to “ If we do this, we will reduce the cognitive/physical load and it will result in better UX.”
The question is, aren’t we oversimplifying it? Often making things too easy makes them boring. Boring things aren’t used that often, are they?
Of course, sometimes the outcome needs to be a boring feature/product that stays there and fulfill it’s purpose without the need for the user to act. This is fine but we shouldn’t always aim to achieve that.
The general rule is that the higher the performance load is, the more likely is that the user will need more time to execute the task and potentially make errors on the way. There is a <a href="https://uxplanet.org/design-principles-hicks-law-quick-decision-making-3dcc1b1a0632">previous post about Hick’s law</a>, which covers that.
We could argue that we should always aim to simplify the design to a state where the performance load is low.
For example if your users goal is to build a nice fit body.
<blockquote>Would you design the best looking EMS (<a href="https://www.wikiwand.com/en/Electrical_muscle_stimulation">Electrical muscle stimulation</a>) machine that will stimulate the users muscles with electrodes and make them contract on their own?</blockquote>
<blockquote>It’s simple, the user turns it on and lays on the couch eating popcorn and watching TV, while the body works it’s way toward it’s top shape. The perfect fitness machine, according to some old TV commercials.</blockquote>
<blockquote>Or would you design a machine with weights that will make the user sweat from exertion?</blockquote>
<blockquote>The user will need to go through high performance load both mental and physical before any results become visible after time. For this second approach, the <a href="https://uxdesign.cc/design-principle-ikea-effect-2d908b2de81">IKEA effect</a> could describe the benefit of making the user put effort and go through the higher performance load.</blockquote>
The answer is not binary, the options are not only to have high or low performance load. Could have been nice to be that simple.
I prefer to think of it as thermostat that should be tuned according to the context and the intended user, so your product can provide the right “temperature” for the user to feel comfortable.
Often, during the user journey the performance load needs to change from low to high.
Let’s take again a fitness machine as a metaphor for designing a user journey. The machine needs to be easy to understand from the first sight. It needs to direct the user how it should be operated and how to increase the weights. Once the user feels safe and knows the basics, the machine would provide a way to increase the performance load to a challenging level based on how advanced the user it. Of course, this example is a bit oversimplified compare to some digital products or more complex physical products.
However, the principle of transitioning the performance load from low to high can be used in many contexts from Gaming industry to Enterprise products, where different users have different level of proficiency.
Good design needs to account for these needs and be capable of providing the needed performance load at the right time.
<h3>Things to consider when designing for performance load</h3>
<h4>Context</h4>
Understand the context, in which the product will live and how your users will be using it.
Is it environment that ads to the cognitive load? How much performance load is there before you even introduce your product/design to that context?
Sometimes the environment where the user will be using the product is overwhelming with cognitive or physical stimulus. In that case, it could be better to reduce the performance load when designing the product.
Your product will be rarely used in isolation from the rest of the environment, so always keep the context in mind.
<h4>Time</h4>
Time is the most important resource each of us has and we as designers need to keep this in mind constantly. Strive to optimize the design and the performance load to take up the right amount of time from the user.
Is the task time sensitive? How sensitive? Is it about preventing an airstrike, turning off the stove or about responding to a personal message?
Usually, the more time sensitive is the task the more we need to reduce the performance load when designing.
<h4>User proficiency</h4>
Go and talk to different users. Get the feeling what is their proficiency level. Are they spending 8h a day in the context you’re designing for or they spend 15min a week? How much complexity can they handle?
The higher the proficiency is the more likely is that the user can take on higher performance load.
<h4>Feedback</h4>
Feedback is essential for any human being that lives. It is the base of how we operate and navigate the world including any given design.
Make sure your design includes ways to provide the proper amount of feedback to the user. From simple message that the file has been uploaded to complex report of what has happened in the past week. It all matters more than we usually think when designing.
The lack of proper feedback is frequently a pain point in any user journey.
User tests your products to figure out the right amount of feedback that the user needs. How much information should you serve back in any given touch point? Should you provide both physical and mental feedback?
Simple tactile feedback can take the user experience to a whole another level. Similar to how game console controllers are adding to the experience with vibration in the right moments.
The trick is to provide the right amount of feedback. It is easy to increase the performance load a lot if for example the tactile feedback is not used sparingly. Imagine, a console controller that does not stop buzzing all the time.
<h4>Communication and language</h4>
Often forgotten point by many designers. Communicating and using the user’s language to manage the performance load can be one of the cheapest and most efficient ways to improve the UX of the product.
A single unknown word in the interface. A warning message that can’t be seen due to non-compliance with accessibility guidelines. These can skyrocket the performance load.
Even when the design was made with the best of intentions to provide the best feedback and the right amount of cognitive load.
Think of what is the language your users are using. Use copywriters who can significantly help polish the copy of the product. Make sure to follow the official accessibility guidelines so the users can see, hear and interact as intended with the design.
<h3>Final thoughts</h3>
Consider the performance load aspect of your design as a dance that the user will perform with the product. Sometimes the need will be for a slow and calm dance that relaxes the user and provides satisfaction. Other times, it will need to be more energetic with higher intensity so the user can feel alive. These dances could happen on the same stage at different hours of the evening.
It is not a question of having performance load or not. It is about how much is needed in the different touch points of the user journey.
Thanks for being here and reading my thoughts!
Feel free to follow me and connect with me. 🙂
<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F50d69a%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=a5ff8e3159d5" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://uxdesign.cc/designing-performance-load-a5ff8e3159d5">Designing: Performance load</a> was originally published in <a href="https://uxdesign.cc">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Designing: Performance load

Designing: Performance load

Should we always design to reduce performance load?

Top Stories