↪ Replying to @deeped
@deeped @fredrikwass @nilrod @sanasilb Rätt satsat! 💡 😃
Tagged: reply
↪ Replying to @wistikent
@wistikent @gunillaleffler @deeped @fredrikwass @asa_sandberg @uxpodcast @amybphd Vilket minne! Kul att det fastnade. Det var helt klart en av mina mest emotionella föreläsningar till dags dato. Glad att jag fick chansen.
@wistikent @gunillaleffler @deeped @fredrikwass @asa_sandberg @uxpodcast @amybphd Ditt avslut på dagen var exakt den reflektion och nedvarvning som publiken behövde. Nästan som att Deeped och Sarah designat hela grejen. 😊 De är grymma.
↪ Replying to @gunillaleffler
@gunillaleffler @wistikent @deeped @fredrikwass @asa_sandberg @uxpodcast @amybphd Just den här intervjun var ju tyvärr inte med Åsa, mer på samma ämnesområde. Deeped och Sarah spelade in ljudet från dagen; min preso finns också som blogginlägg: axbom.blog/digital-omtank…
↪ Replying to @JesperBylund
@JesperBylund On my mind are design choices where one makes it difficult to abandon shopping carts or services (easy to join, hard to leave), or where tools are forced upon a worker or citizen with no other choice available (time reporting system, or downloading an app to pay for parking).
↪ Replying to @unknown
@olaberg 'Freddy's coming for you' from the album Nightmare on Elm Street. ;)
↪ Replying to @wistikent
@wistikent @deeped @gunillaleffler @fredrikwass @asa_sandberg Ja, Åsa var jättebra! Undrar om yrkesrollen du tänkte på från början kanske var "behavioral psychologist" eller "behavioral engineer". Vi har ett avsnitt av @uxpodcast där vi intervjuar @amybphd som kanske är av intresse. uxpodcast.com/232-design-psy…
↪ Replying to @funnygodmother
@funnygodmother @RosenfeldMedia @amazon Yes!!
↪ Replying to @jonashyse
@jonashyse @natmiletic BASIC. My first book:
x.com/axbom/status/1…
↪ Replying to @TheNewThinkerr
@TheNewThinkerr LucidChart lucidchart.com
↪ Replying to @unknown
@gerrygaffney Wow, the future is here. But I can't read all of it 😬
↪ Replying to @lyreskog
@lyreskog Agree. Though I'm consciously trying to avoid that phrase in search of something more specific. This work by @nerdydivadesign was a wake-up call for me regarding how leisurely I use some terminology.
x.com/axbom/status/1…
↪ Replying to @wickedgeekie
@wickedgeekie Blog about it.
@wickedgeekie Thinking more about it, would it be possible to treat it as an actual case, where you reach exactly those aforementioned conclusions and offer a better way of posing the problem?
↪ Replying to @Tynell
@Tynell The logical fallacy of course being the idea that there was ever a problem to begin with ;)
↪ Replying to @unknown
@pedrobjorn Every day is a lesson in inequality.
↪ Replying to @JesperBylund
@JesperBylund Not necessarily. The minority in the cupcake example would really be the people with allergies. We don't test for allergies, we test for a winner of the options we put forward. Rather than declare a winner the best solution may be more choice.
x.com/axbom/status/1…
↪ Replying to @JesperBylund
@JesperBylund I do think the minority aspect is a feature of A/B-testing that should be called out. A/B-testing can (sometimes) be effective in boosting profits, but can be at the expense of select people being sidestepped - which the test will rarely show. So - yes - skewed, with real impact.
@JesperBylund And of course I'm also critical of the dogma. :)
@JesperBylund If you test blue and pink cupcakes against each other you may find more blue cupcakes eaten at the time, place and by the people you test them with. But if you don't talk to people you won't find out about allergies. And why a number of people still preferred the pink ones.
↪ Replying to @JesperBylund
@JesperBylund Not at all. I would argue it all depends on what you're trying to achieve, and what you believe the data is saying. Understanding the data is key, not a focus on declaring "winning" designs.
@JesperBylund You do need to complement statistical testing with focused qualitative research with a diversity in health, experience, status, ability, etceteras – if you are trying to achieve inclusive design.
↪ Replying to @yungtsai
@yungtsai @beantin @per_p @Windows Yeah it"s not perfect. I'd rather redesign the whole thing. My thinking was rhat Confirm is assertive (I"m confirming my selection of 'no'), whereas Accept is submissive (I"m accepting someone else's suggestion). But yes, even more clarity in this interface is needed.