Simplicity

  • 3,006 views
Uploaded on

For the rest of the notes, visit my blog http://talirsux.wordpress.com/ …

For the rest of the notes, visit my blog http://talirsux.wordpress.com/

Simplicity can be divine. When done right.
When done right, you will find people using your product as if it were an extension of themselves.
They will be focused on what they can do with it, rather than on how to operate it.
You will find people understanding the main messages of your presentation or document, rather than drifting away.
When done right, simplicity is elegant, exciting and positive.

For the rest of the notes, visit my blog http://talirsux.wordpress.com/

More in: Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,006
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
62
Comments
2
Likes
5

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Simplicity can be divine. When done right.When done right, you will find people using your product as if it were an extension of themselves.They will be focused on what they can do with it, rather than on how to operate it.You will find people understanding the main messages of your presentation or document, rather than drifting away.When done right, simplicity is elegant, exciting and positive. Powerful.zen.
  • Simplicity can be divine. When done right.When done right, you will find people using your product as if it were an extension of themselves.They will be focused on what they can do with it, rather than on how to operate it.You will find people understanding the main messages of your presentation or document, rather than drifting away.When done right, simplicity is elegant, exciting and positive. Powerful.zen.
  • But it is not easy to achieve. It requires effort, dedication and sophistication.It gets worse.Once you have achieved simplicity, if you’ve done it right, it can be under appreciated. People seem to think the solution was obvious due to its simplicity. Effortless requires a lot of effort.
  • This guy branded his products by simplicity. He did pretty well.Notice the borrowed motto…
  • Within this sentence lay the 2 causes of complexity: many parts and the arrangement of the parts.Complexity. It has its pluses – but for today lets just call it evil. It’s simpler.
  • Complexity happens.No one intends to create complex systems or documents unless they are lawyers.No one says lets make this thing as complex as possible so nobody can understand it, read it, or use it.
  • The first enemy of simplicity is sheer amount. Amount of features.If you are writing a presentation it’s the amount of contents you feel you need to include in the presentation. Same for e-mail.All people guilty of featuritis please smile now…
  • Amount of hardware pieces, input devices, buttons, controls, cables. Many times happen due to constraints of time and resources.No time to invest in designing it better. We are already concentrating on other features.In the long run of course, this costs more to everyone.2007
  • Amount of UI elements, colors, sizes, fonts, text, animations
  • The second enemy of simplicity is how we put all the components together. Dependencies, conditions, order create one big mess.We can tell it is a mess because it is impossible to change. Each small change is linked to so many other things it becomes a nightmare.The type of components we use when we code - Components that we don’t understand (black boxes), that are dependant on each other, loops,
  • What does it mean? No simpler? It means that we have to explore and find out the essence
  • Simplicity is about subtracting the obvious, and adding the meaningful Maeda thoughtful reductionWhat is the main problem you would like to solve, base it on user needs & current frustrations – think of several ways to solve it.Design for the mainstream. Remove what can’t be implemented properly.The question that needs to be asked is “Why should we keep this”Thoughtful reduction, remove optionsSacrifice features that are used by only a small percentage of your customers or that you cannot implement properly
  • Today!
  • Advertising learned the lesson pretty quickly"אחד היסודות ליצירת פרסום אפקטיבי הוא היכולת לתמצת מסרים בדרך כזו, שתקל על הצרכן לקלוט ולהבין אותם. ..פרסום טוב מבוסס על מסר ברור וחד" אחוז השטח שתופסת הדמות/דמויות בפרסומת בכל עשור 1920 – 56% 1990 – 99%מספר הדמויות בכל עשור 1920 – 6 1990 – 1הכותרות נעלמו לחלוטין, אחוז הטקסט ירד מ – 38% ל – 13% משטח המודעה
  • Once the content of the components is clearwe can use several basic laws of organization to tell the user more about the relationship between the components.Every detail about our components bears meaning: the form, the size, the color, its placement, it’s relation to other components.If we use these attributes to convey relevant meaning – we directly affect the person’s understanding of the system.
  • Create hierarchy. Not everything is of equal importance. Show the person where to focus.
  • Organization makes a system of many appear fewer - MaedaOur mind is trained to better understand details when we give the meaning as a group. Chunking relieves us from seeing and deciphering each component on its own.Gestalt principlesClosure – we want to see simple closed forms.Continuity - we want to see continuous lines and curves (from smaller elements)Similarity (shape, color, size, orientation) they will be associated with each otherProximityIt is about the relationship between the parts and chunkingDesigning interaction – Jenifer Tidwell
  • Let’s have an Oprah moment. This closet is about to have a makeover.First of course is remove.
  • Next is the organize. What elements of organization were used here?Notice how similarity, color and orientation are used to group appropriate items. It makes us look at them as groups. We find them effortlessly.Setting all the clutches in a row we create continuity that is easier on the eyes.This organization will also ensure that we don’t miss out on a valuable item, just because we couldn’t see it in the mess.Sure, we had to put some effort in the organization, but it returns itself in the long run.
  • We need Focus.We cannot focus everywhere.
  • Here’s an example of an attempt to rescue a person who’s confronted with an unfamiliar set of remotes. The owner was away for the weekend and decided to help the friend who was coming to stay. She wrapped the remotes in paper to hide the redundant buttons and labeled the useful ones in plain language. Bad Design / Good Design Bill Moggridge 
  • Savings in time feel like simplicity.
  • Or no more than 3 taps. No more than 2 sentences.Dogma is a simple rule which has no exceptions. It requires a hard..ss boss which no one will defy.It works.It is hard on the workers.It needs to be accepted by all.
  • Rich Hickey - Without initial design for simplicity in the architecture of a system, the design of the system turns into an elephant that can’t be moved or changed.Complexity is derived from an architecture of pieces that are intertwined in each other making every change almost impossible.
  • I found these helpful…If you choose just one, be it Giles Colborne’s book which is simple and usable in itself

Transcript

  • 1. Design for SimplicityTali Rosen Shoham
  • 2. SIMPLICITYDivine
  • 3. “Simplicity is the ultimatesophistication”Leonardo da Vinci
  • 4. Steve Jobs
  • 5. COMPLEXITYSomething with many parts in an intricate arrangement
  • 6. 6
  • 7. 7Complicationof what wedesign
  • 8. 8featuritis is the ongoing expansion or addition of new features in aproduct…beyond the basic function of the product…can result in over-complicationThe engineers’ favorite featureThe UX’ers favorite featureThe marketing’s favorite featureThe Project Managers’ favorite featureThe customers’ favorite featureThe application engineers favorite featureThe services favorite featureEdge use cases (what if…)The competitors did it…Complicationof what wedesign
  • 9. 9Complicationof how wedesign
  • 10. 10Complicationof how wedesign
  • 11. 11Software engineers: this lecture is all about your toolkitComplicationof how wedesign
  • 12. 12Complexity’s little helpersFeelings What if Stakeholders Effort
  • 13. Strategies
  • 14. RemoveSimplicity is about subtracting the obvious, andadding the meaningful – J. Maeda
  • 15. “Things should be assimple as possible, butno simpler”Albert Einstein
  • 16. RemoveChoose acore, basedon usersneedsReduce theamount ofelementsPrioritize thechosenfeaturesFocus fromtheprojects’beginning
  • 17. 17Remove
  • 18. 18Remove
  • 19. OrganizeComponents bySize, Type, Color, Form, Labels & textLayout bySimilarity, Proximity, Closure,Continuity, WhiteSpace, Hierarchy, Grid, orientation
  • 20. 20OrganizeSize = Most important/Frequent/Critical
  • 21. 21OrganizeOrganization makes a system of many appear fewer -Maeda
  • 22. 22Organize
  • 23. 23Organize
  • 24. 24Organize
  • 25. Hide & Place elsewhereComplexity is still there.Hide it from view, or shift it to another platform
  • 26. 26Complicationof how wedesign
  • 27. ShortenLess is more
  • 28. 28Shorter time, shorter text, shorter document
  • 29. Dogma“No more than one button!”
  • 30. 30
  • 31. Test for ChangeHow easy is it to modify a component in your design?
  • 32. 32Design for simplicity = Design for change
  • 33. 33ResourcesSmart Designsoaphia.comBad Design / Good Design Bill MoggridgeSimplicity matters by Rich HickeyFeaturitishttp://www.webpagesthatsuck.com/Designing interaction – Jenifer TidwellOprahElephant
  • 34. Thank you