• Design Friction

    Frictionless Design Choices : Learning by Shipping

    • Frictionless and minimalism are related but not necessarily the same.
      • Minimalist design is about reducing the surface area of an experience.
      • Frictionless design is about reducing the energy required by an experience.

    It shouldn’t be much of a surprise, but a great deal of product bloat comes from adding the obvious feature or directly listening to customers, or by failing to stick with design patterns. Ironically, efforts to enhance products for today’s customers are often the very features that add friction, reduce minimalism, and lead to overall bloat.

    There’s an additional design challenge. The first people who use your product will likely be the most enthusiastic, often the most technical, and in general the most desirous of features that introduce friction. In other words you will get the most positive feedback by adding features that ultimately will result in a product with a lot more friction.

    As the scope of the app grows the needs of different user bases diverge and splinter

    #1 - Decide on a default rather than options.

    Configuration options are hell to maintain and test several years into a project. And remember, once you give - it’s very hard to take away.

    #2 - Create one path to a feature or task.

    The question shouldn’t be : would i ever want to get there from here, but is it okay not to get there from here; how painful is this blockage; and how often will it really ever happen

    #3 - Offer personalization rather than customization.

    It’s easy to let these lines blur into a deep gray section. Personalization allows expression, whereas Customizations means augmentation. Make them the exception not the norm, because they can quickly become a muscle reflex for indecision.

    #4 - Stick with changes you make.

    It’s basic band-aid psychology. Do it fully and wait for the sharp pain to soothe or deal with fear, anticipation, and continuous dull pain.

    #5 - Build features, not futzers.

    If there is a story or a theory behind it, you need that feature. If it has the makings of a super cool demo, it’s all fluff

    #6 - Guess correctly all the time.

    If you want it to be smart, it better be freakin’ genius - or at least have a great personality.

    The risk with every change is not simply failing to maintain minimalism, but introducing friction that becomes counterproductive to your goals.

    Therefore the real design challenge is not simply maintaining minimalism, but enhancing a product without adding more friction.

  • Dust off the resume - Customers are hiring

    Interesting framing method to inform design decisions.

    Designing Features Using Jobs To Be Done

    • Personas are imaginary customers defined by attributes that don’t acknowledge causality.
    • User Stories […] have three big problems:
      • They use Personas.
      • They couple implementation with motivations and outcomes.
      • They ignore context, situations, and anxieties.

    Designing successful products means observing how real people solve problems now, exploring the context of the situation they are in, and then understanding causality, anxieties and, motivations.

  • http://roninbrush.tumblr.com/post/120097115615/intro-to-a-video-presentation-created-in-after

  • Let’s get cooking!

    bbq

  • If looks made a diff

    JSX Looks Like An Abomination - JavaScript Scene - Medium

    • JSX is not limited to HTML. You can use it to create arbitrary object trees. Netflix uses that capability to mirror their web app architecture on a wide variety of devices using their own custom object model for TV rendering.
    • React Native uses it to render device-native UI elements.
    • React creates a single listener automatically, so you never have to think about event delegation again.

    Designers Don’t Mind JSX

    I don’t. Reminds me of xaml. A little off putting at first; but it grows on you; and it’s powerful.

    Inline Styles Are Good

    I agree.

    • Putting styles in a React component is more akin to putting styles in a web component than putting styles into raw HTML
    • you only have to update it in one place, and you don’t have to worry about selector scoping.
  • http://www.roninbrush.com/post/119515908305/strategist

  • Great reminder how our physiology shifts our experience based on the condition of our instruments. 

    Science explains how time spent outdoors colors your view of #thedress - LA Times

    • If our brains conclude that the image is lighted by a cool illuminant like a blue sky, we will ignore shorter wavelengths and determine that thedress is white and gold. However, if our brains decide that the image is being lighted by a warm illuminant like an incandescent light, we willdiscount longer wavelengths in the picture and will see the dress asblue and black.
    • Although they are not yet sure why that would be, their current hypothesis isthat women and older people are more likely to spend their awake timeduring the day, and therefore more likely to assume that their visualworld is contaminated by blue sky
    • “You have in your head an internal model of what the colors of the worldare, and that helps you resolve ambiguities,” Conway said. “The machinein your head says, ‘Well, given what we know historically, I’m going toassume it is this color, or that color.’ “
    • Someone who spends more time under artificial lighting may make a different assumption, he explained.
    • people are more likely to filter out blue tones than they are other colors
  • http://www.roninbrush.com/post/118690918025/timeline-graphic

  • http://www.roninbrush.com/post/118436690090/sketch-dont-cover-up-the-problem

subscribe via RSS