{"id":7867,"date":"2017-03-29T12:25:04","date_gmt":"2017-03-29T11:25:04","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=7867"},"modified":"2017-04-06T20:45:43","modified_gmt":"2017-04-06T19:45:43","slug":"design-principles-kiss-feature-creep","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/design-principles-kiss-feature-creep\/","title":{"rendered":"Design Principles: KISS the Feature\u00a0Creep"},"content":{"rendered":"

This will be the first post of series of articles I will be writing on design principles. The idea is to share my perspective on timeless design principles that can be applicable across many mediums and contexts. It is aimed mainly at new designers and designers like me who tend to forget this stuff, and need a refresher.<\/p>\n

I have to admit the headline is a bit misleading for the sake of being more interesting. Please forgive me!\u00a0:)<\/p>\n

Lets get started with the two design principles: Feature creep and KISS.<\/p>\n

\"15nT12edJ4P0VQtqKSG_Yeg\"<\/a><\/p>\n

The danger of feature\u00a0creep<\/h2>\n

Most of the time continuous addition of new product features beyond the original scope usually results in cost and schedule overruns. If that happens, you\u2019ve let the feature creep sneak on you!<\/p>\n

Sometimes features are easy to add especially in software\/web development. You can think of feature creep as cancer for software applications. It accumulates too many features that end up crippling or even sometimes killing the end product.<\/p>\n


\n
\"Famous<\/a>

Famous example is Microsoft Word with all of its tool-bars visible.<\/p><\/div><\/center><\/p>\n

Feature creep appears when stakeholders start thinking they know what\u2019s best for the user. Yes! That\u2019s without actually communicating with the user.<\/p>\n

If anything, just remember. More is not better! Except sometimes.<\/strong><\/p>\n

Continuously adding features will add unnecessary complexity. Unnecessary complexity will add unnecessary costs (money and time).<\/p>\n

<\/div>
<\/svg><\/div>

\"Continuously adding features will add unnecessary complexity. Unnecessary complexity will add unnecessary costs.\"<\/p><\/span><\/blockquote>\n

How to deal with the feature\u00a0creep?<\/h2>\n

Watch out for small features that can easily sneak in and stay. Feature creep is a mean ninja! It is hard to detect, it blends so well with the environment and can hurt your product real bad.<\/p>\n

\"1L7APD8Xm9N-w0eiCe-e7sQ\"<\/a>

Feature creep can stab you in the\u00a0back<\/p><\/div><\/center><\/p>\n

<\/p>\n

When adding features, always test them with real users. Features must be linked to customers needs. Educate everyone around you about the feature creep.<\/p>\n

Read below about the KISS principle to keep the feature creep at bay.<\/p>\n

Traditional explanation of\u00a0KISS<\/h2>\n

The acronym KISS stands for Keep It Simple Stupid<\/strong>. Other variations are often used like Keep It Short & Simple, Keep It Stupid Simple and Keep It Simple Silly. The original phrasing of the principle Keep It Simple Stupid was popularized by Kelly Johnson<\/a>.<\/p>\n

\"Johnson designed aircraft for war which meant planes had to perform reliably and they had to be easy to fix in stressful field conditions. One of the principles he employed to do this was KISS.\"<\/span><\/p>\n

Simplicity should be a key goal in design. Simplicity means minimal amount of parts with minimal interactions between those parts.<\/p>\n

Fewer parts and interactions results in faster and cheaper way to build. Performance will be more reliable and will be easier to troubleshoot and maintain.<\/p>\n

The paradox in simplicity<\/h2>\n

Innovative designs are rarely simple! The process of iteration and prototyping is messy. Designs end up with inessential elements and interactions as they are developed. That\u2019s the feature creep mentioned in the first part of the article.<\/p>\n

\"The KISS principle becomes most useful once a design nears a working prototype. Iterations must become subtractive. Designer\u2019s focus needs to become narrower. Everything that has no significant purpose and does not solve the user\u2019s needs, has to be either removed or redesigned in a way that it will be available when it\u2019s needed.\"<\/span><\/p>\n

When you arrive at that stage of your design, ask yourself: what can be removed without hurting performance? Keep user testing your designs. Keep removing and simplifying. Apply KISS until you can\u2019t simplify any further.<\/p>\n

Simplifying is great as long as it doesn't hurt the performance and objective of the tool\/product you\u2019re designing.<\/p>\n

Simple is born from\u00a0complex<\/h2>\n

Imagine a standard pencil. It is a simple<\/strong> tool that enables you to leave your mark in this world. Everything in the pencil has its purpose and role and supports the needs of the user in the particular context.<\/p>\n

\"1sGwxxS2430R0UxgUuzIhBA\"<\/a>

Imagine a pencil in its all simplicity and complexity<\/p><\/div>\n

So what is the complex part?<\/p>\n

Just imagine, the process behind making that pencil and the design decisions that went into it. The way to assemble the wood and include the graphite mixture and the shape of the body so it doesn\u2019t roll off from the desk. Everything has its purpose and ultimately supports the user\u2019s goal. Beautiful and simple! But reaching that result was not simple at all!<\/p>\n

Here is a short video<\/a> of how pencils are made, if you are curious:<\/em><\/p>\n

O.K.\u00a0, enough pencils!<\/p>\n

Great UX design applies the same KISS principle. The end product needs to be simple<\/em> and go through all the complexity!<\/em> <\/strong>Clear your design so that everything in the product has a purpose and works toward satisfying the user\u2019s needs.<\/p>\n

Final thoughts<\/h2>\n

No matter how much design experience you have, Feature creep and KISS principles are universal and will serve you well in the future. When you iterate your designs look in both directions. Think of what to add and what to subtract.<\/p>\n

Always design to solve a problem for the user and improve things. Keep in mind, simple often is complex.\u00a0:)<\/p>\n

Remember the next feature you add could well be the feature that kills the product. Make sure you test it with your users. Keep your designs well balanced so you can achieve optimal level of functionality, cost and maintainability.<\/p>\n

Thanks for your time!<\/em><\/p>\n

This article was originally published on Anton's Medium page<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

This will be the first post of series of articles I will be writing on design principles. The idea is to share my perspective on timeless design principles that can be applicable across many mediums and contexts. It is aimed mainly at new designers and designers like me who tend to forget this stuff, and need a refresher. I have… Read More ￫<\/a><\/p>\n","protected":false},"author":117,"featured_media":7934,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-7867","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-viewpoint"],"acf":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\n\n\n\n\t\n