As designers we may sometimes fall in the engineering mindset of solving multiple issues with the least elements possible. This is actually not a bad practice. You take into account all of the requirements, come up with a UI that satisfies the acceptance criteria, you even take into account the time that it's gonna take to fruition and try you best to satisfy the customers expectations.
If it sounds complicated, well, it's because it is. Trying to balance all of these factors is not easy breezy at all.
On this article we are going to talk about having to compromise…
I was presented with this nice dichotomy recently, and after having browsed around to get a glimpse of the online debate I must say that I can't take any sides on it.
Let me elaborate.
Consistency in a design system is what you would see in a system that is locked, one that doesn't evolve often and it is built and used with efficiency on mind. And by efficiency I mean doing things fast and be consistent with a specific brand, color palette, communication tone, and so on to the point of specific components and sometimes even predefined layouts.
One of the things that comes with experience in any profession is identifying flaws in things without having to think about “why” it’s flawed. Oftentimes this leads to solving those issues without following any established process. This is quite common in a startup scenario and small organizations.
Let’s take the example of somebody asking you to propose a new design for a specific app.
You start identifying issues that you have encountered through your professional experience, write them in your to-do list, and jump right into Sketch to create a new comp and turn it around in hours. …
As part of the growth of the design team within CEMEX we had made important progress in reaching a basic stage of maturity.
Our todo list kept getting shorter. We developed the software application style guide, created a design language around it, and then we created our symbol library.
The inner workings of the design team were streamlined.
Everything was running smoothly on the inside, but we started experiencing issues whenever we interacted with development folks within product teams.
Whenever we delivered a composition, some feature visuals or even an InVision prototype, the developed counterpart stood always short from the…
While working at Accenture, I was given the opportunity to lead Visual Design for the new version of the Enterprise Health Management Platform of the Department of Veterans Affairs.
Healthcare software has many intricacies that have to be taken care of. Patient Safety and HIPAA regulations make it pretty difficult to create a loose and open User Experience. Then, there's the fact that all government software has to be 508 compliant, which adds a new layer of complexity atop of the strict rules already present.
This is one of the most successful products i have ever design, cause it represented winning a re-compete contract for almost 300 million dollars for Accenture.
Here I walk you through the specifics of the project.
One of the most gratifying projects that I have made at CEMEX was the creation of a Sketch symbol library. A unique reference for creating visual compositions.
The fundamental problem we were having that triggered the creation of it was that the team members were copy/pasting from the Master Style Guide PDF and modifying those elements to adapt to the requirements of the current deliverable.
This was inefficient for many reasons, but mostly because there were many versions of those files going around the office and there was no centralized way of having them updated.
Our system had to evolve…
This is a chapter of the evolution of the design team at CEMEX to serve the entire company and create digital products for both employees and customers by adhering to the user experience process.
A design office is of course constituted by designers mostly, in our case, there are at least 10 specializing in diverse branches such as User Experience, Visual Design, Interaction Design and UX Development. It's a mix of very creative people who got ideas of their own, preferences, taste and diverse backgrounds. …
You might find interesting the correlation on gravity and mobile navigation. The thing is that some aspects of nature have to be taken in consideration when developing UI for mobile apps, and gravity is one of them. Well, not exactly gravity, but gravity's implications on how we hold our handhelds.
If you look closely on how you grab your mobile phone while using it with one hand only you will find out that there is a particular way to do it. Most of the pressure is at the center of your palm, with that one corner of the handheld sitting…
The implications of loading data via AJAX are crucial in the way we interact with the user. There was a time when we didn’t care about the feedback a website gave to us, essentially, presenting new content to the user translated to a page jump. We can still say is the most common behavior throughout the web, and thus, many designers and developers might not have such preoccupations (yes, I'm talking to you WordPress peeps).
When a page jump occurs, the browser takes care of letting the user know that exchange of data is taking place. It might not be…