The human behavior is unpredictable because we can’t analyze what people think even all the feelings involved in history. In fact, it seems a complex incognito everytime we add some variables.

When we create a dialog flow between human/machine the difficulties are the same (even bigger). We aren’t “interacting” with nobody and even when we write sometimes is hard to abstract this universe which we’re dealing and trying put yourselves in the user’s spot.

In this article I’ll show some discoveries working with AI, that’s why some key points in the analysis will be articles, today’s silence subject.

Silence

In my draw dialog flow (current working), at first user interaction, we can diagnosis the silence level of 60,3% (4 weeks period). This number brings me some questions:

• Why people don’t speak?
• Is it any difficulties?
• Aren’t the objective clear?
• Are make sense if you call to say nothing?
• What does the user want?

I kept these issues in my mind until did a test. I did analyze the user’s behavior outside of a controlled environment. I was encharged to conduct this activity and another designer was responsible to analyze human behavior.

After some interviews, we noticed a high number of users with doubts about how to interact with a robot. In fact, the same users were coming from a visual interface to a voice interface. And this was a shock for them. Asking what they should do… “Do I need to say? Is it a robot?”

And the results?

The result was a drop of 43% in silence at this point. It could be little at first, but it’s a significant user’s behavior change when we say something become didactic. In other words the quantity of silence at this flow step drops from 60,3% to 26,6%.

Sometimes we’re so focused on day to day, solving more complex problems that we forget basic heuristics, such as “prevent users fails”.

The first solution was tested and checked in voice interface (with happiness). But we have a long way to go ahead, to reduce even more the user’s silence.

The most valuable lesson learned here was: if you are drawing a solution, make users understand how to use your product. Sometimes we forget that people don’t read the manual, so that’s why your product must be friendly for the first time.

The post Do user know how to use your product? appeared first on Calegari.art.

What’s is UX?

User experience (UX) isn’t a picture, layout or wireframe… the experience just happens all the time. Basically is the user experience doing something, like going in a restaurant (book a table, waiting for the meal, tasting the food and paying).

The mission of a UX Designer is simply help the user to solve a problem, help him to finish his objective with your product in a better possible way (easily).

Amazon’s case

Greg Linden studies show that the performance really matters in a website, like  every 100ms delay in page load costs 1% of sales. So doesn’t matter if your page is beautiful if you don’t improve the performance.

Other point is the checkout form, in Amazon was detected that the users had some troubles to complete the registration process to checkout. So the solution was extremely simple, they cut off the registration. That improvment increased the sales in 45% giving US$300 millions to Amazon.

For final argument I can talk about the one click to buy button. That’s feature bring the facility to the user’s life, just ith a click you can buy anything reducing the time to spended in a page, working with the users anxiety. And this digital solution was so incridible, that now you can use a physical button. The thing is, you can put a Tide button in your wash machine and when the soap goes away, you simply click to buy more.

To conclude you can bring these three points of the Amazon’s case to make the paper of a UX Designer more tangible for your clients, co workers or just to explain to your parents.

Sources:
https://sites.google.com/site/glinden/home/stanforddatamining.2006-11-28.ppt
https://articles.uie.com/three_hund_million_button/
https://www.amazon.com/Tide-Dash-Button-products-ordered/dp/B0187TMRYM

The post UX Importance appeared first on Calegari.art.

The question is: Which tool should I pick?

For this, I brought two sites that will guide you to make your decisions, and bring some comparison with an effective simple and intuitive interfaces.

Here we can find a comparison tools table categorized by steps (of project), prices, platafform… and a link to users post new tools that are comming. The site also bring statistics data about the utilization of this tools. Check this

Showed like an interactive chart, we can change then axis according with our necessities and get the apps more accurate to our propourse. All of this with a friendly and intuitive way. Check this

The post UX Design Tools appeared first on Calegari.art.

Along my career sometimes I’ve faced a common problem: “Why is this website different from the proposal I’ve sent?”. Indeed the reason is simpler than I taught: “Because the devs aren’t designers”.

When we study UX (user experience) essencially we’re studying how to develop empathy to others, and in this case we should think the same. If we want a perfect pixel  layout we must know the limitations of the platfform and browsers that we’re working on. We also should be concearned about the people who’re developing our project. I mean, the priority for any developer is to keep everything working without glitches, in other words focus on code.

And that my friends were my starting point to learn HTML and CSS. It’s not a simple task, sometimes it’s a very complex and frustrating work, but all effort is worth it. The point is you don’t need to be an expert (because you’re a designer) but if you can learn some codes you can build it too, you can discuss technically aspects of your project with your coworkes and develop a new solution.

That kind of skills are totally necessary these days (in my opinion), because the world spins too fast and the age of “one task guy” is over. We need more multi-task professionals to do more.

So you can start watching some youtube videos, signing up e-learning platforms and (obviously) talking with a dev.

The post Why should I learn to code? appeared first on Calegari.art.