<?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 Björn Seibert on Medium]]></title>
        <description><![CDATA[Stories by Björn Seibert on Medium]]></description>
        <link>https://medium.com/@webzeugkoffer?source=rss-e647f3119fe4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yc1CoE6kYF0oomVSR_RGkw.jpeg</url>
            <title>Stories by Björn Seibert on Medium</title>
            <link>https://medium.com/@webzeugkoffer?source=rss-e647f3119fe4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:46:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@webzeugkoffer/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[What drives users’ actions?]]></title>
            <link>https://medium.com/@webzeugkoffer/what-drives-users-actions-244fc35ce63c?source=rss-e647f3119fe4------2</link>
            <guid isPermaLink="false">https://medium.com/p/244fc35ce63c</guid>
            <category><![CDATA[users]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Björn Seibert]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 14:52:53 GMT</pubDate>
            <atom:updated>2018-11-16T14:52:53.936Z</atom:updated>
            <content:encoded><![CDATA[<h3>“The user” is not a thing</h3><p>Don’t forget that users are also human beings. E.g. people who shop online, have motivations and emotions — <strong>MotiMotions</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Ule4sYlnFhnSrtC5_GPgMA.png" /></figure><p>Users not only have needs and requirements regarding the products they want to purchase, or regarding the platform which they are using. Also personas are often only referring to the users’ attributes, most of all sociodemographic characteristics and their key tasks they have to/want to perform, when interacting with our platform, in (a) specific scenario(s).</p><p>A thing/system may be usable and enjoyable or not. Keeping the users’ motivations and emotions in mind, makes things sometimes appear in a different light.</p><h3><strong>Users’ basic MotiMotions</strong></h3><p>Let’s compare some basic motivations and emotions exemplarily before we make a cut set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VIiQ6tuwCh8A43SrmJdlmQ.png" /></figure><p>If you’ve taken a closer look at the motivations you may have noticed, that “Purchase a product” was mentioned twice. This is an example for how motivations may differ. On the one hand they may be originated more intrinsic. E.g. purchase a certain product to fulfill a long-cherished wish. On the other hand the motivation to purchase a product may have a more extrinsic origin. E.g. purchasing a product to fulfill a job’s requirement.</p><p>Same but more complex for “Fill out forms”. It’s motivated (extrinsic) and it triggers emotions (hate). They hate it but they have to. Motivation and emotion are reciprocal. But now let’s see how users’ motivations and emotions merge.</p><h3>The cut set</h3><p>Users will always hate to fill out forms (negative emotion), but they have to (extrinsic motivation) in order to purchase a product online. Badly usable forms forms exponentiate the effect of the negative emotion about filling out forms online.</p><p>Mostly it’s when negative emotions and extrinsic motivations merge, where we can help users. UXers may positively influence the users’ MotiMotions:</p><ul><li>Design highly usable forms -&gt; allow users to complete their tasks quickly and without friction and frustration</li><li>Users hate to wait -&gt; shorten perceived loading time -&gt; keep them in an active mode</li><li>Users hate ads -&gt; only offer well-dosed and relevant things, by knowing your target users and their needs</li><li>Users have to give consent to the usage of cookies -&gt; privacy by design</li></ul><p>This was a short introduction to the interplay of motivations and emotions. Sometimes, for example, it’s not about shortening form fields at any cost. It often maybe <em>only</em> a matter of context, relevance, and usability.</p><p><em>First published under </em><a href="http://uxygenic.com/motimotions-drive-users-actions"><em>MotiMotions drive users’ actions</em></a></p><p><em>Credits: Thanks Colorlib for sharing the </em><a href="https://colorlib.com/wp/free-icons-adobe-illustrator/"><em>Top 32 Adobe Illustrator Icon Sets in 2018</em></a><em> from which this article’s visual was composed.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=244fc35ce63c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get Appreciation for UX and become a Key Player]]></title>
            <link>https://medium.com/@webzeugkoffer/how-to-get-appreciation-for-ux-and-become-a-key-player-687e41031a52?source=rss-e647f3119fe4------2</link>
            <guid isPermaLink="false">https://medium.com/p/687e41031a52</guid>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Björn Seibert]]></dc:creator>
            <pubDate>Tue, 06 Feb 2018 19:06:56 GMT</pubDate>
            <atom:updated>2018-02-06T19:06:56.944Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/212/1*FKTHZ_vES-qUHPGDNM5_Fw@2x.jpeg" /></figure><p>Until today UX often remains nothing more than buzz, a noble goal. And still UX Designers are complaining about not being understood by others or over customers who are not getting their point. Even in agile organizations and those that generally recognize the value of UX, UXers fail, e.g. when being part of a SCRUM team.</p><p>The fields to be tackled can be summarized under two main areas, focussing on process and acceptance.</p><h4>Lack of holistic Planning and Prioritisation of User Experience</h4><p>For SCRUM teams, often running sprints of two weeks, it’s nearly not possible to define UX user stories/tasks that fit into their backlogs. In particular defining/seeing a MVP (minimum viable product) delivered by an UXer. That’s not always because they don’t understand User Experience, but UX often needs time for research, analysis etc. (discovery) before being able to start ideating and creating solutions. Nothing built, nothing delivered? Sure we know better, but we’re having trouble showing it.</p><h4>Perception of UX as less valuable than Development and Acceptance Criteria are neglected</h4><p>The second and most challenging aspect that we’re facing as UX Designers has to do with a lack of appreciation. UX work often is considered as the finishing decoration. For me, this is the key point. UX Designers often don’t succeed in explaining the valuable contribution UX makes to products. Although companies have now understood that (UX) design is an important success factor and are currently hiring hordes of UX Designers, we the UX Designers are failing to make our crucial contribution visible and to leverage it. BTW For some organizations, the need to have a ux designer is as similar as it was in 2009 when everyone had to have a blog. But this is another story to discuss 😉</p><h4>Crack the Nuts</h4><p>So how to crack these two nuts from a UX Designer’s perspective. No big nutcracker is needed. It’s more a question of the right technique. You just have to change your perspective and at some small extend change the way you collaborate with your teammates.</p><h4>Process: Planning and Prioritization of UX</h4><ul><li>(To some extend) be one Step ahead of the Sprint; e.g. collect data, conduct (rapid) user tests, build hypotheses, sketch, … -&gt; Discover &amp; Ideate</li><li>(To some extend) be one Step behind of the Sprint 😉 e.g. collect data, conduct (rapid) user tests, define optimization tasks, sketch, … -&gt; Validate &amp; Adapt</li><li>Build a strong, evidenced-based platform from which to advocate your users needs and design approaches -&gt; Document &amp; Record and later reach back to your treasure of experience</li></ul><h4>Acceptance through Collaboration: uncover the Value of UX</h4><ul><li>Invite every team member to give feedback on your ideas and design and listen to ideas from everyone</li><li>Share user feedback with the whole team. E.g. show video sequences from Usability Tests</li><li>Share summarized key findings from user tests or data analysis</li><li>Post persona posters in the Scrum room as reminders to remind everybody who you’re doing this for</li><li>Make all team members to users -&gt; that’s gonna happen more or less automatically 😉 through sharing (videos, data etc.) and caring (listen to ideas)</li></ul><h4>Conclusion</h4><p>Our claim must be:</p><blockquote>UX shouldn’t be a bolt-on or just a box that needs to be ticked! – <a href="https://manifesto.co.uk/agile-ux/">Agile and UX</a></blockquote><p>Sure that wont be easy to make the change. But it’s worth trying and sooner or later, you will reap the fruits. You’ll help your organization to really focus on the users, customers and their needs. As UX Designers you’re a key player helping to really make UX a cornerstone of the entire organization. Otherwise UX remains buzz, maybe people already started talking about AI and other fancy stuff 😉</p><p>Recommended reading: <a href="http://www.uxforthemasses.com/ux-and-agile/">Tips for bringing UX to the Agile party</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=687e41031a52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You really need to moderate your Deliverables]]></title>
            <link>https://medium.com/@webzeugkoffer/you-really-need-to-moderate-your-deliverables-8bd76456d1fa?source=rss-e647f3119fe4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bd76456d1fa</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Björn Seibert]]></dc:creator>
            <pubDate>Thu, 21 Dec 2017 08:23:46 GMT</pubDate>
            <atom:updated>2017-12-22T12:35:21.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/473/1*fbVfhpge5YlZvaJyBokH-g.jpeg" /></figure><p>All too often you can observe the following: It’s review time and the first public deliverables are to be shown and discussed. The beamer launches and the UX Designer starts describing the <em>pictures </em>(e.g. wireframes). But obviously nobody seems to get what he’s talking about. The following discussion gets out of hand and carried away — if there’s any discussion at all.</p><p>The above scenario lacked context. This is where communication and moderation skills come into place. Don’t worry you don’t have to be an entertainer to succeed. But we need to moderate our deliverables. Especially for scribbles and wireframes, which mostly describe a solution in little detail — which is ok and in early stages even suitable — it is necessary to moderate. We need to start with creating the context.</p><h3>Giving Context</h3><p>Before diving into the details, we have to:</p><ul><li>Describe what was observed or general needs that were addressed</li><li>Tell the audience more about the problem or specific requirements and restrictions</li><li>Give them an overview of the possible approaches</li><li>Use the deliverables (here wireframes) to describe the rough concept/solution</li><li>Get feedback which will fuel the following steps</li></ul><p>Did you notice anything? Here also you can approach to a better result by Design Thinking. It’s the red thread spinning for you. Keeping the Design Thinking Process in mind, can help you build your argumentation chain.</p><ul><li><strong>Empathize</strong>: develop knowledge about what your users or business need</li><li><strong>Define</strong>: in depth description of the problems and/or requirements</li><li><strong>Ideate</strong>: talk about a range of ideas that crossed your mind</li><li><strong>Prototype</strong>: create the deliverables and present them to the audience</li><li><strong>Test/Validate</strong>: finally get feedback for your solution approach, e.g. in a sprint review</li></ul><h3>Conclusion</h3><p>Structured moderation of your deliverables really helps you to move on. If you can get them all on the boat, everyone has the chance to really understand the core of your solution, presented e.g. with lo-fi wireframes. Then your chances are really good to get valuable feedback and you will well equipped step into the next iterations.</p><p>This post was first published on <a href="http://uxygenic.com/blog/">UXygenic</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bd76456d1fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile First!? Think First!]]></title>
            <link>https://medium.com/@webzeugkoffer/mobile-first-think-first-2c0e99e6880?source=rss-e647f3119fe4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c0e99e6880</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[mobile-first]]></category>
            <dc:creator><![CDATA[Björn Seibert]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 13:29:05 GMT</pubDate>
            <atom:updated>2017-12-22T12:40:02.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*Q04tTP8x0WEBagEpP4ly6w.png" /><figcaption><a href="https://decaf.de/en">DECAF</a>: “Mobile First? Yes, and no. It’s not that simple”</figcaption></figure><p>Now! And that’s actually too late! The Mobile First Index will eat us up and users won’t be able to use our website! Yeah, that can happen, but it’s no reason to panic.</p><p>The term Mobile First and the associated strategies have existed for <a href="https://www.lukew.com/ff/entry.asp?933">more than 8 years</a>. Well advised where those who were not immediately caught up in the hysteria and didn’t headlessly rush away. Even though Luke Wroblewski was right in his article from the year 2009 and thus laid the foundation for many meaningful developments and strategies.</p><p>Today Mobile First is also being questioned, at least in its radical and often short-sighted form. Radical, because always and without exception Mobile First is considered as the only way to go — often too easy and patchy. Short-sighted, because seemingly needless ballast is thrown away in a rush and what remains is made responsible. In disadvantage of — surprise! the users.</p><p>A brief retrospect to other approaches in web design that were adopted far too shortsighted. Fluid Web Design. It was considered to be barrier-free per se and in general it was en vogue somehow, many will remember. Thousands of websites were quickly liquefied. Literally. The result was often ugly and from certain monitor sizes badly readable. 1,000+x pixel wide text lines. Barrier-free? The solution to this was very easy: max-width.</p><h4>Mobile First as a Conceptual Guideline</h4><p>Mobile First is not a (technical) solution. Rather, it is a way of thinking, a method, perhaps even a philosophy, with which one approaches the development of websites, shops, apps, etc. — to start as simple as possible and enhanced by the mobile context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*AQo4wEMdUIQ2O8o9HG_vBA.png" /><figcaption>Tweet by <a href="https://twitter.com/_lizzelo_/status/930029242817138688">@_lizzelo_</a></figcaption></figure><p><strong>The simplest possible solution. </strong>Sounds good and has always been valid, even before there were smartphones. Mobile first is always a good starting point — at least mentally. <strong>Mobile First forces us to focus</strong>. But not only technically, as Luke Wroblewski noted in 2009.</p><blockquote>So when a team designs mobile first, the end result is an experience focused on the key tasks users want to accomplish without the extraneous detours and general interface debris that litter today’s desktop-accessed web sites.</blockquote><p>I think that many of us already get stuck in the purifying and responsive approach of their concepts and designs — Desktop Diet Delusion. But we shouldn’t forget to look at users needs, content, technology and strategy in its sometimes very complex interplay — the context. Please don’t think Mobile First too narrowly and don’t just look at your (responsive) frontends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Di_FnB4MOV4nrdSnXyyNLQ.jpeg" /><figcaption>Dieter Rams, <a href="https://medium.com/@ashergodfrey/meaningfulmemes-design-mantras-611124e126a6">Image Credit</a></figcaption></figure><p>No matter how, the focus is on User Experience and must be the best possible, in every context. <strong>User first!</strong></p><p>Recommended Reading:</p><ul><li><a href="https://www.lukew.com/ff/entry.asp?933">Mobile First</a></li><li><a href="http://www.uxbooth.com/articles/where-do-we-go-from-mobile-first/">Where Do We Go from Mobile First?</a></li><li><a href="https://www.smashingmagazine.com/2017/02/mobile-first-is-just-not-good-enough-meet-journey-driven-design/">Mobile First Is Just Not Good Enough: Meet Journey-Driven Design</a></li><li><a href="https://blog.prototypr.io/mobile-first-desktop-worst-f900909ae9e2">Mobile First, Desktop Worst</a></li><li>[German] <a href="https://www.konversionskraft.de/trends/mobile-first-erfolgreicher-ansatz-oder-hype.html">Hört bitte auf von Mobile First zu sprechen</a></li><li>[German] <a href="https://userlutions.com/blog/konzeption-prototypen/mobile-first-digitale-strategie/">Mobile First oder Context First? Wann Mobile First die falsche Strategie ist</a></li></ul><p>Originally written, “Mobile First!? Aber Uffbasse!” in German, for <a href="https://webzeugkoffer.de/mobile-first-aber-uffbasse">webzeugkoffer.de</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c0e99e6880" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>