<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Philipp Sackl-O’Neill on Medium]]></title>
        <description><![CDATA[Stories by Philipp Sackl-O’Neill on Medium]]></description>
        <link>https://medium.com/@phlsa?source=rss-c533e87035d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cY5u4Y4TE2jRXXO3.jpeg</url>
            <title>Stories by Philipp Sackl-O’Neill on Medium</title>
            <link>https://medium.com/@phlsa?source=rss-c533e87035d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:36:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@phlsa/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Snappy Gradients and Systemic Thinking–Weekly Links]]></title>
            <link>https://medium.com/push-ux/snappy-gradients-and-systemic-thinking-weekly-links-b8260caf8aef?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8260caf8aef</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ethnography]]></category>
            <category><![CDATA[interface-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Mon, 06 Sep 2021 06:55:50 GMT</pubDate>
            <atom:updated>2021-09-16T15:38:24.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Patent drawing for the Aero Snap interaction" src="https://cdn-images-1.medium.com/max/1024/1*DWv1QK3NmQlS2rLvZ3YcNA.png" /><figcaption>Patent drawing for the Aero Snap interaction, by <a href="https://shoef.myportfolio.com/">Stephen Hoefnagels</a></figcaption></figure><p><em>Every week, we compile a list of 5 great articles — one for every work day of the week. Want to suggest a post for this series? </em><a href="/service/mailto:philipp.sackl@push-conference.com"><em>Let us know!</em></a></p><h4>Monday: Oh Snap!</h4><p>Let’s start with some good, old-fashioned interaction design. And by old-fashioned, I mean something from 12 years ago, when Windows 7 came out. One of it’s coolest productivity features was Aero Snap, which let you arrange windows on the screen more quickly. In this deep dive article, <a href="https://shoef.myportfolio.com/">Stephan Hoefnagels</a> walks us through the thinking that went into this feature in great detail.</p><p>By the way: if you want a similar feature on the Mac, I can recommend the <a href="https://rectangleapp.com/">Rectangle</a> app.</p><p><a href="https://web.archive.org/web/20200211122709/https://docs.microsoft.com/en-us/archive/blogs/e7/designing-aero-snap">Designing Aero Snap</a></p><h4>Tuesday: Systems for People</h4><p>While design systems have grown out of asset libraries, they have since become full-blown workflow management systems. And as with any system used by humans, usability is an important factor in how effective they will be. In this post, current and former members of the Lyft UX team give us a nice overview of how all the components of their design system play together.</p><p><a href="https://medium.com/tap-to-dismiss/user-centered-design-system-resources-2df958d90749">User-centered Design System Resources</a></p><h4>Wednesday: Accessible From The Start</h4><p>If you ignore a problem for too long, it becomes much harder to fix. This isn’t just true for yesterday’s dishes that you still haven’t cleaned up, but also for accessibility in products. <a href="https://lishadai.medium.com/">Lisha Dai</a> shows us how easy it can be to design more accessible mobile apps and websites when thinking about different ways of usage from the beginning.</p><p><a href="https://blog.prototypr.io/answer-4-questions-to-make-your-first-accessibility-project-effortless-a797e2efeb68">Why you should think accessibility from the design phase?</a></p><h4>Thursday: Being There Without Being There</h4><p>Observing people in their day-to-day context is an extremely valuable aspect of user research — and it has become much harder to do since the pandemic started. This article by <a href="https://medium.com/@hosseinraspberry">Hossein Raspberry</a> takes a look at the tools at our disposal.</p><p><a href="https://uxstudioteam.com/ux-blog/digital-ethnography/">Pushing Ethnographic Research at the Times of Remote Work</a></p><h4>Friday: Smooth.</h4><p>Since we started this week with interaction design, it’s only fair to end it with a visual design topic: Gradients. If you were every using gradients in your UIs but they just didn’t look quite as cool as you wanted, this overview will give you some handy pointers on where to start tweaking.</p><p><a href="https://blog.prototypr.io/how-to-design-sexy-gradients-a897b42c245">How to Design Sexy Gradients</a></p><p>And with that, we wish you a great week ahead!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8260caf8aef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/push-ux/snappy-gradients-and-systemic-thinking-weekly-links-b8260caf8aef">Snappy Gradients and Systemic Thinking–Weekly Links</a> was originally published in <a href="https://medium.com/push-ux">PUSH UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Words, Shapes and People—Weekly Links]]></title>
            <link>https://medium.com/push-ux/words-shapes-and-people-weekly-links-f9ee25ac3a80?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9ee25ac3a80</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[uxtesting]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Wed, 01 Sep 2021 18:55:55 GMT</pubDate>
            <atom:updated>2021-09-01T18:56:16.655Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every week, we compile a list of 5 great articles — one for every work day of the week. Want to suggest a post for this series? </em><a href="/service/mailto:philipp.sackl@push-conference.com"><em>Let us know!</em></a></p><h4>Monday: No Second Chance for First Impressions</h4><p>Using a product for the first time can be revealing, but it is also by definition a one-time experience. As designers, we are often too knowledgeable in the systems we design to adequately judge the experience of someone who has never used them. That’s why user testing is so important for this phase and it is why case studies like the one <a href="https://medium.com/@huajunyue?source=post_page-----c444c105206e--------------------------------">Junyue Hua</a> did for the Xbox Series S are so eye-opening to read.</p><p><a href="https://bootcamp.uxdesign.cc/thoughts-on-the-xbox-series-s-user-experience-c444c105206e">Thoughts on the Xbox Series S’ user experience</a></p><h4>Tuesday: Look Mom, Both Hands!</h4><p>There are a thousand ways to use the web and some of them get more attention than others. One that is consistently at the bottom of the list is keyboard-only usage. The good news is: it is comparatively easy to put oneself into the shoes of a keyboard-only user. <a href="https://medium.com/@triemers12?source=post_page-----584872b3fda9--------------------------------">Tori Riemersma</a> shows how big the differences in experience can be by comparing two big online retailers.</p><p><a href="https://uxdesign.cc/amazon-and-nike-com-through-the-lense-of-a-keyboard-584872b3fda9">What do Amazon and Nike look like through the lens of a keyboard?</a></p><h4>Wednesday: Wise Words</h4><p>User interfaces are mostly text. While UX writing has emerged as a distinct discipline in the past decade, the psychological principles behind good UX writing have been the same for a long time. Kalina Tyrkiel showcases some of these principles in this handy overview.</p><p><a href="https://www.uxpin.com/studio/ux-design/the-psychology-of-ux-writing/">The Psychology of UX Writing</a></p><h4>Thursday: We shape our tools and then our tools shape us</h4><p>Similar to UX writing, the rise of design systems has accelerated sharply in the past years. Among other things, this transformation has shown that we can’t just make decisions about visual design when looking just at one use case. <a href="https://twitter.com/hihayk">Hayk An</a> has pushed this concept one step further with Shaper, a case study of a UI style manipulator.</p><p><a href="https://hihayk.github.io/shaper/">shaper - interface styles shaper</a></p><h4>Friday: Qualitative Testing</h4><p>Whoever you design for, however you write your UX copy and whatever tool you use to shape the UI, there is simply no substitute for qualitative testing. In this great overview, <a href="https://www.nngroup.com/articles/author/kate-moran/">Kate Moran</a> shines a light on all the aspects of qualitative testing.</p><p><a href="https://www.nngroup.com/articles/qual-usability-testing-study-guide/">Qualitative Usability Testing: Study Guide</a></p><p>And that’s a wrap! Have an excellent week and always be testing, shaping and writing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9ee25ac3a80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/push-ux/words-shapes-and-people-weekly-links-f9ee25ac3a80">Words, Shapes and People—Weekly Links</a> was originally published in <a href="https://medium.com/push-ux">PUSH UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design to Redesign — Weekly Links]]></title>
            <link>https://medium.com/push-ux/design-to-redesign-weekly-links-638c50f4e7c2?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/638c50f4e7c2</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[cognitive-psychology]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Mon, 23 Aug 2021 04:57:50 GMT</pubDate>
            <atom:updated>2021-09-16T15:39:56.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design to Redesign—Weekly Links</h3><p><em>Every week, we compile a list of 5 great articles — one for every work day of the week. Want to suggest a post for this series? </em><a href="/service/mailto:philipp.sackl@push-conference.com"><em>Let us know!</em></a></p><figure><img alt="Sketches of user interfaces on paper" src="https://cdn-images-1.medium.com/max/1024/1*5lLGYJXaxAKqdevef94-QQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@halacious">Halacious</a> on Unsplash</figcaption></figure><p>Let’s talk about redesigns. Most design work is actually redesign work. It’s changing and improving existing products. Sometimes that’s just adding another item to a menu, other times it’s a full-on revamp of an entire product.</p><h4>Monday: Angry Birds</h4><p>Unfortunately, change is often hard for our users. Twitter recently experienced this. When they rolled out their latest design refresh, they were quickly swarmed with critical tweets. In this article, Maria Panagiotidi digs into some of the reasons why people might dislike a redesign, regardless of the design itself.</p><p><a href="https://uxdesign.cc/why-do-people-hate-redesigns-64c2b009cc32">Why do people hate redesigns?</a></p><h4>Tuesday: Lowering the (Address) Bar</h4><p>But of course, not all redesigns are created equal. Another prominent and recent example is Apple’s redesign of Safari, which is currently in beta. This isn’t just a facelift. Apple changed some of the fundamental interaction paradigms of their browser. When attempting such a feat, it is important to know why you are doing a redesign and what you are optimizing for, as Jonas Downey points out in this witty analysis.</p><p><a href="https://jonas.do/writing/2021-08-08-safari-redesign/">Reviewing the Safari redesign in iOS 15</a></p><h4>Wednesday: Looking for Freedom</h4><p>In a way, a redesign makes users feel like they have lost some freedom, which — surprise! — is not a very nice feeling. The negative reaction to this perceived loss of freedom is called “reactance” and it can be triggered in many situations beyond redesigns. Cognitive Lode takes a deeper look at this phenomenon and ways to avoid it in this guide.</p><p><a href="https://coglode.com/research/reactance">Reactance - Why controlling peoples&#39; sense of freedom can trigger an angry motivation to regain it</a></p><h4>Thursday: All Aboard!</h4><p>One way to get users on board with your changes is, well, onboarding. In the past decade, designing for onboarding has become a distinct specialization within UX. What sets it apart (among other things) is that it depends even more heavily on storytelling and writing than some other parts of our products. Ewa Jozefkowicz shares some valuable best practices in this article.</p><p><a href="https://www.uxbooth.com/articles/ux-writing-is-the-key-to-effective-onboarding/">UX Writing is the Key to Effective Onboarding | UX Booth</a></p><h4>Friday: Wisdom of the Ancients</h4><p>Finally let’s end the week by looking back at some of the basics. Jakob Nielsen first published his “Heuristics for User Interface Design” in 1994 and unlike many other pieces of UX advice, they have aged very, very well. While knowing these rules won’t guarantee that a design is great, it will likely prevent it from being terrible.</p><p><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 Usability Heuristics for User Interface Design</a></p><p>That’s it for this week! I hope you enjoy this collection. If you’re looking for more inspiration and knowledge without having to read any articles, I hope you will <a href="https://push-conference.com/2021?utm_source=medium&amp;utm_medium=inline-link&amp;utm_campaign=weekly-links">join me at PUSH UX this October</a>! The last early bird tickets are on sale now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=638c50f4e7c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/push-ux/design-to-redesign-weekly-links-638c50f4e7c2">Design to Redesign — Weekly Links</a> was originally published in <a href="https://medium.com/push-ux">PUSH UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Red and green problems, information architecture, basic UX principles and how media art can get you…]]></title>
            <link>https://medium.com/push-ux/welcome-to-the-first-edition-of-weekly-links-where-we-from-the-push-team-share-five-of-our-931a333ac029?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/931a333ac029</guid>
            <category><![CDATA[media-art]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Mon, 16 Aug 2021 09:33:14 GMT</pubDate>
            <atom:updated>2021-09-16T15:39:14.722Z</atom:updated>
            <content:encoded><![CDATA[<h3>Red and green problems, information architecture, basic UX principles and how media art can get you a visit from the secret service — Weekly Links</h3><p><em>Every week, we compile a list of 5 great articles — one for every work day of the week. Want to suggest a post for this series? </em><a href="/service/mailto:philipp.sackl@push-conference.com"><em>Let us know!</em></a></p><figure><img alt="Photo of a red notebook on a green surface" src="https://cdn-images-1.medium.com/max/1024/1*BaWr39AH03h-dB65X_PAFA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema">Kelly Sikkema</a> on Unsplash</figcaption></figure><p>Welcome to the first edition of weekly links, where we from the PUSH team share five of our favorite reads — one for every workday of the week. Some of these articles are new, others are already classics. We hope you enjoy the mix! Let’s dive right into it.</p><h4>Monday: From A Colorblind Designer to the World: Stop Using Red and Green Together</h4><p>Red and green is probably the most frequently used color combination when it comes to functional colors in UIs. Unfortunately, they can look almost identical to people with color blindness. Andrew reminds us of this fact and shows some practical ways to make sure your design is more universally accessible.</p><p><a href="https://baselinehq.com/blog/colourblindness-information-ui-design-red-green-problems-tips-tricks.html">From A Colourblind Designer To The World: Please Stop Using Red And Green Together</a></p><h4>Tuesday: Navigating the UK Government</h4><p><a href="https://gov.uk/">Gov.uk</a> has been a darling of the UX community for quite some time. Now they are updating the main navigation for the first time since 2014 and share some insights from their process.</p><p><a href="https://gds.blog.gov.uk/2021/05/17/our-plans-to-improve-navigation-on-gov-uk/">Our plans to improve navigation on GOV.UK</a></p><h4>Wednesday: The Lost Art of the Affordance</h4><p>Let’s get back to basics: UI elements should give users an idea of how they can be interacted with. This is called an affordance and it’s one of the basic principles of UI design. The problem is that good affordances aren’t automatically aesthetically pleasing, tempting us to leave them out in favor of a “cleaner” design. No wonder that <a href="https://twitter.com/edent">Terrance</a> is grumpy about this.</p><p><a href="https://shkspr.mobi/blog/2021/06/whatever-happened-to-ui-affordances/">Whatever Happened to UI Affordances?</a></p><h4>Thursday: Old New Things</h4><p>Since the dawn of the mobile era, UIs have moved from a file-centric to an app-centric mental model. Where before, files containing data have stood on their own and could be manipulated by different apps, the data is now contained within apps themselves. However, there are still many millions of people who’s mental models are centered around the document paradigm (and many of us are switching back and forth contextually). This little piece makes the case for why one of the strongholds of document-centric UI is still useful: the “New” context menu in the Windows file explorer.</p><p><a href="https://devblogs.microsoft.com/oldnewthing/20210720-00/?p=105457">Why does the New menu even exist for creating new empty files?</a></p><h4>Friday: People Staring at Computers</h4><p>Media artist Kyle McDonald was one of our favorite speakers at the very first PUSH conference in 2012 — check out his talk here. Not too long before he gave that talk, he created a project called “People Staring At Computers”, which got him lots of attention, a legal dispute with Apple and a visit from the secret service. Almost 10 years later, Kyle reflects back on his experience in this piece.</p><p><a href="https://kylemcdonald.net/psac/">People Staring At Computers</a></p><p>That’s it for now! Have an enjoyable week and remember to take breaks from staring at your computer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=931a333ac029" width="1" height="1" alt=""><hr><p><a href="https://medium.com/push-ux/welcome-to-the-first-edition-of-weekly-links-where-we-from-the-push-team-share-five-of-our-931a333ac029">Red and green problems, information architecture, basic UX principles and how media art can get you…</a> was originally published in <a href="https://medium.com/push-ux">PUSH UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtual Conferences Are Broken. Let’s Fix Them.]]></title>
            <link>https://medium.com/uxandproduct/virtual-conferences-are-broken-lets-fix-them-eb15898e6203?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb15898e6203</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[event-planning]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Mon, 07 Dec 2020 07:36:06 GMT</pubDate>
            <atom:updated>2020-12-13T16:32:47.490Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Virtual conferences should be awesome — no travel, lower prices and international by default. However, they all too often end up being just another meeting. Why is that? And how might we do better?</blockquote><figure><img alt="Too many virtual conferences feel like just another meeting. Adding puppies isn’t a permanent solution." src="https://cdn-images-1.medium.com/max/1024/0*KJDZ3gqiZGl5X2J-" /><figcaption>Too many virtual conferences feel like just another meeting. Adding puppies isn’t a permanent solution · Photo by <a href="https://unsplash.com/@visuals?utm_source=medium&amp;utm_medium=referral">visuals</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>What makes conferences interesting: the talks and the interactions with other participants.</p><p>In theory, virtual conferences should be great at delivering interesting talks. Speakers don’t have to travel, so it becomes easier to book the best of the best in their field. Unfortunately, that’s part of the problem. Speakers can only come up with new material every so often, so we end up with the same speakers giving the same talks over and over again.</p><p>Besides the talks, the other cool thing about conferences is that you get to meet people and can have interesting conversations with them. But this aspect also gets lost in virtual conferences. You can’t overhear conversations and jump in, you don’t have to sit at a lunch table with strangers that could become friends and you can’t spot interesting people from afar.</p><p>What remains is you sitting in a chair in your office, watching a video by yourself. It’s just another meeting.</p><h3>Screw this. We must do better.</h3><p>When planning the UX &amp; Product Conference, we set ourselves the challenge to come up with a format that is more interesting than the usual sequence of keynotes. We had three requirements:</p><ol><li>It must emphasize generating new insights for everyone involved</li><li>It must involve audience members as active participants (if they so desire)</li><li>It must create the opportunity for serendipitous conversations</li></ol><p>The result: a new talk format that we call <strong>1–2-Everyone</strong>. It’s one topic, two speakers and everyone has a chance to contribute.</p><p>Here’s how it works.</p><ol><li>Each of the two speakers has 7 minutes to pitch their view on a topic.</li><li>Next, the two speakers engage in a moderated debate for 15 minutes.</li><li>Finally, the conversation is opened up to the audience for up to 30 minutes of discussion.</li></ol><p>We think that this strikes a good balance. Speakers still have space to lay out their views and arguments, but the purpose of the talk-part of the format is really to set up the debate-part. Since the two speakers will challenge each other and build on their points in that debate, the topic will unfold in new and interesting ways.</p><p>Involving the audience in the discussion accomplishes multiple things. First, it makes the format more interactive and engaging. Second, it allows for a more diverse set of views to be discussed. And third, it gives visibility to individual members of the audience and to their views. That loads a trigger for conversations in the breaks or after the conference. When members of the audience express their views in this forum, it makes them easier to approach later. It’s a conversation starter.</p><p>Should 1–2-Everyone replace the classic keynotes we see in most conferences entirely? Probably not. Some topics need the space of a 45 minute talk to be laid out entirely. But we think that it will make events more interesting, more colorful and certainly less repetitive.</p><p>At the end of the day, we hope that everyone will come out of events that use 1–2-Everyone a little smarter and a little more inspired than they would otherwise.</p><p>We will debut this format at the <a href="https://conference.uxandproduct.com/">UX &amp; Product Conference</a> on February 4th. We hope that other conferences will join us in adopting 1–2-Everyone, and in thinking critically about how to deliver great guest experiences in the new medium that virtual events are.</p><p>This article also appeared on <a href="https://philippsackl.com/2020/12/13/virtual-conferences-are-broken-lets-fix-them/">philippsackl.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb15898e6203" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxandproduct/virtual-conferences-are-broken-lets-fix-them-eb15898e6203">Virtual Conferences Are Broken. Let’s Fix Them.</a> was originally published in <a href="https://medium.com/uxandproduct">UXandProduct</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Iterations]]></title>
            <link>https://medium.com/project-tofino/iterations-af5ad7d54497?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/af5ad7d54497</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 14:30:32 GMT</pubDate>
            <atom:updated>2016-08-02T15:42:26.635Z</atom:updated>
            <content:encoded><![CDATA[<p>Working in a completely open problem space is, among other things, an exercise in self control. When you’re a designer and you get the chance to invent freely, it is natural to jump onto the most interesting problems first, which are often the ones that can be solved through clever design. Whether or not these solutions would actually benefit users is a different matter altogether. Since the problem space for Project Tofino is as open as can be, we were working very hard on not making that mistake — on not jumping to conclusions too early. Instead, we wanted to start with the problems and desires that actual people had (read: people who don’t work in the technology industry).</p><p>Conveniently, our research team was way ahead of the task and had gathered a wide variety of insights into people’s online behavior over the past years. The most recent of those efforts was also one of the most significant ones: we call it the Workflows Research and we’ll publish more on the results soon. This research provided us with insights about usage patterns, frustrations and problem solving strategies that real people use to solve real issues.</p><p>Among the workflows we picked to investigate first were comparison shopping, saving for later (and contextual recovery), and improving recurring navigational patterns (a.k.a. making it more convenient to visit the sites you go to frequently). We’ll talk more about each of the problems and solutions in another blog post. For now, let’s dive into the methodology we used to work on these problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N_WU2ODcEw6OSpCs7TL0wg.png" /><figcaption>It all starts with good old-fashioned drawing</figcaption></figure><p>After discussing what we learned through research on a topic, we started concepting with pen and paper, going broad and exploring different angles on a given problem. The big question for the design process was how we could get solutions in front of users as quickly as possible while still making sure that we got genuine reactions. I am personally not a fan of paper prototypes for two reasons: first, we can’t test them remotely, and second, they immediately move people from the role of the user into the role of the critiquer. While that would still be valuable, we were sure that we could get more value out of testing by evolving our concepts into low fidelity mockups right away. In addition, the step of turning our paper sketches into something that looks like software forced us to do one more iteration on each design, often sparking new ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rmzmDjdBsPLTzvhu1TRfVA.png" /><figcaption>Our prototypes aren’t pretty, but they are effective tools for learning</figcaption></figure><p>Since we wanted to move quickly, we couldn’t build an entire browser experience for each feature or test. All our prototypes were <em>vertical</em>, meaning that they allowed users to take one very specific navigation path through them. In order to prevent people from anchoring too much on their current opinions on particular browsers, we also made sure that the prototypes didn’t resemble any major browser too closely.</p><p>Each prototype explored a small domain of ideas and over the past weeks we have developed, tested and iterated in a number of areas. Focusing on qualitative testing of rough prototypes allowed us to move faster, broadening our understanding of both the problem and the solution we’re designing.</p><p>The other approach we used was to test other products with users. When we found that some other software already had implemented a concept similar to what we were exploring, we skipped creating prototypes altogether and instead tested that product with users. This allowed us to gather valuable insights from actual users even faster.</p><p>Using this process, we have learned among other things about the kinds of information that people need the most when making a buying decision, what attitudes to expect towards contextually surfaced content and the different mental models that users had towards saving information.</p><p>We are now at the stage of combining those concepts into something that’s more of a coherent product. This is also the point in the process where we can start exploring some of the interesting interaction ideas that we have been holding back on so far, along with the ones that many of you have been proposing through our various channels.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af5ad7d54497" width="1" height="1" alt=""><hr><p><a href="https://medium.com/project-tofino/iterations-af5ad7d54497">Iterations</a> was originally published in <a href="https://medium.com/project-tofino">Project Tofino</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Browser that isn’t a Browser]]></title>
            <link>https://medium.com/project-tofino/designing-a-browser-that-isn-t-a-browser-685b63c4b6f1?source=rss-c533e87035d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/685b63c4b6f1</guid>
            <category><![CDATA[browsers]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Philipp Sackl-O’Neill]]></dc:creator>
            <pubDate>Fri, 08 Apr 2016 15:54:22 GMT</pubDate>
            <atom:updated>2016-04-08T16:15:05.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xAVp6Y6OLxrQVtos." /></figure><p>The web is central to our lives — we probably spend more time in our browsers than in our beds. It has changed the way we do so many things — how we communicate, plan, shop, learn, work, and watch movies. At first, browsing, surfing, or going online was a particular activity; now, the web has melted into everyday life. It has evolved, and the web is now simply part of how we live.</p><p>Our behaviours have changed as well. We have moved significant portions of our lives into the cloud, mobile phones have become our most important touch point with technology, and social media and messaging apps have risen to ubiquity.</p><p>On desktop computers and laptops, browsers have changed their role from being one application among many to acting as a meta operating system (and in some cases, as the actual operating system). For many users, it is the only app they are ever starting on their computers, where it will then keep running for days or even weeks. They are home to everything from quick ephemeral interactions, all the way to long running full-blown applications.</p><p>Meanwhile, the fundamental interaction principles of web browsers haven’t changed in the past 20 years. On the one hand, this is remarkable proof of the quality of those UI concepts and the power of incremental improvement. But there is every reason to believe that a tool originally shaped for reading documents isn’t where you would want to start to support today’s workflows and enable new kinds of interactions with the web.</p><p>When you think of a browser today, you’re probably thinking of tabs, a location bar and perhaps a bookmarking system. But are those still the best tools for the jobs we are aiming to accomplish on the web? Maybe they are. Maybe they are not. We want to find out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evloYqp3MjWO42cHXsxEyw.png" /><figcaption><em>Some of the earliest sketches for Project Tofino</em></figcaption></figure><p>That’s why we are starting Project Tofino. It is our name for a series of experiments and explorations on what a browser could look like when its fundamental paradigms are invented in 2016 instead of 1996. It is about taking a fresh look at where people struggle on the web, but not being bound to 20 years of legacy when we look for solutions.</p><p>What is it going to look like? We don’t know yet! That’s why we see Project Tofino not as a single product, but rather as a series of experiments. We will use it as a platform to explore radical new ideas that go beyond any existing browser.</p><p>You can follow along on <a href="https://medium.com/project-tofino">Medium</a>, <a href="https://project-tofino.slack.com/">Slack </a>(get access <a href="http://tofino-slack-invite.mozilla.io/">here</a>) and <a href="https://twitter.com/projecttofino">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=685b63c4b6f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/project-tofino/designing-a-browser-that-isn-t-a-browser-685b63c4b6f1">Designing a Browser that isn’t a Browser</a> was originally published in <a href="https://medium.com/project-tofino">Project Tofino</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>