{"id":507,"date":"2022-02-02T12:00:41","date_gmt":"2022-02-02T05:00:41","guid":{"rendered":"https:\/\/bnsd.binus.ac.id\/graphic-design\/?p=507"},"modified":"2022-02-02T12:00:41","modified_gmt":"2022-02-02T05:00:41","slug":"design-principles-behind-great-products","status":"publish","type":"post","link":"https:\/\/international.binus.ac.id\/graphic-design\/2022\/02\/02\/design-principles-behind-great-products\/","title":{"rendered":"Design Principles Behind Great Products"},"content":{"rendered":"
\n
\n
\n

The range of principles<\/h2>\n

If you try to google \u201cDesign Principles\u201d you most likely run into some basic rules of graphic design: proximity, balance, contrast, space, etc. Things that good designers usually familiar with, or, most likely, know inside out.<\/p>\n

The next huge part is principles of a rational design process. It\u2019s a set of concepts that makes you a true professional who\u2019s able to provide an excellent design with great efficiency. Applying these principles to the whole team sets a bar of standards that new employees should match or reach in the short term. Let\u2019s take a look at the\u00a0GOV.UK Design Principles<\/a>.<\/p>\n

\n
\n
\n
\n
\n
<\/div>\n

\"\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/figure>\n

The list seems reasonable, but what I think is that such things are an industrial standard by now. Everybody design with data, and everybody tries to understands context. I believe that if you choose design principles for your team, you should pick some that are groundbreaking and challenge your team to go further.<\/p>\n

Some teams put their principles online, and I regularly bump into some statements which sound like \u201cbe human\u201d or \u201cbe communicative.\u201d I hold a firm belief that such shit isn\u2019t worth to be hanging on a wall unless your team is full of insensitive silent jerks and you want to change that fact. Why did you hire them in the first place?<\/p>\n

\n
\n
\n
\n
\n
<\/div>\n

\"\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/figure>\n

So, what I was looking for, are\u00a0product design principles<\/strong>. And the Gov.UK provides at least one:<\/p>\n

\n

This is for everyone<\/em><\/strong>
\nAccessible design is good design. Everything we build should be as inclusive, legible and readable as possible. If we have to sacrifice elegance \u2014 so be it. We\u2019re building for needs, not audiences. We\u2019re designing for the whole country, not just the ones who are used to using the web. The people who most need our services are often the people who find them hardest to use. Let\u2019s think about those people from the start.<\/mark><\/p>\n<\/blockquote>\n

Design Principles of your product should tell you, your team and stakeholders which directions you should be going in the tough choices. They should focus on what distinct your product from others, how it feels and what is important for the business and your customers.<\/p>\n

You are probably aware of the Apple\u2019s Human Interface Guidelines or Google\u2019s material design guidelines. Design principles behind these systems try to unify different products under the platform and bring the shared feeling to them.<\/p>\n

If your product exists on various platforms, you should consider having a design system and some principles behind it, as well as the product design principles. You want to distance your product from others and unify the experience through different touchpoints, operating systems, and screens.<\/p>\n

There goes the same problem: some teams put obvious design principles for their product: clarity, simplicity, usability \u2014 but you can\u2019t create a good product without keeping such things in mind, and nowadays professionals stick with such principles by default.<\/p>\n

Wrapping up<\/h2>\n