UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

Why design principles shape stronger products

Jessie Chen
UX Collective
Published in
8 min readAug 23, 2016

Image credit

Our design team didn’t have any design principles and it was difficult to determine design success.

My job is to design and improve/redesign a legacy CRM system for real estate professionals. We often ran into design limitations because we didn’t have any principles to refer to. Our users have a love/hate relationship with the product. Some users think it’s a great lead generation tool that boosts their business and helps to manage their contacts. Some of them think it’s cumbersome, time-consuming to complete tasks, buggy and not user-friendly. There is so much to improve, but what are the restrictions?

New features vs. existing problems

We collaborate with our user research team to conduct user testing/interviews. It varies from testing existing features to redesigning a prototype. We gather user feedback and categorize them to define or confirm usability issues. We go through the cycle of user testing, design, and iterate. Yet, while we working hard improving the product, new features are often requested. This can be frustrating, especially on a page that already has usability issues. The more functions you add, the more complex it becomes.

Legacy design patterns

At work, we have our legacy design patterns. Thus, new designs are always tied into consistency. In theory, consistency is necessary because we don’t want to detract from what users are doing. Though at the same time, we want to move fast and reduce task clicks. But then we would have to sacrifice consistency. What should we do? How should we rank consistency and efficiency? Which is more important?

User needs vs. Design needs

Through user testing, we learned that user needs often don’t match design needs. Admit it, don’t we all have the tendency to design based on our hypothesis? We think we understand the user flow without further user research. The truth is that we aren’t always right. The lessons impart a human-oriented sense of “why?”. Why don’t users just get it? Why can’t they find such an obvious button? Why wouldn’t they want to use a function that we think is useful? Why don’t they like the existing features? So many why that confuses us.

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Responses (19)

Write a response

I find it useful to have design principles specific to an application or project. The design principles you mention could apply to just about any app. What would be the principles specifically for CRM? When I was working on Skype for HoloLens, we…

--

I feel like the phrase “design principles” is a little overloaded here. Students studying architecture, graphic design, art, industrial design, interior design etc. learning about these principles. These include principles such as “unity, isolation…

--

Clarity is all about the relationships between elements. Consider the relationships between items on the page and structure the page based on importance.

Clarity = relationships = context. Love this.

--