<?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 Krzysiek Woliński on Medium]]></title>
        <description><![CDATA[Stories by Krzysiek Woliński on Medium]]></description>
        <link>https://medium.com/@wolinski?source=rss-6ee0ba04aade------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*k4efY_8c4KIOzqWckDJ9Sw.jpeg</url>
            <title>Stories by Krzysiek Woliński on Medium</title>
            <link>https://medium.com/@wolinski?source=rss-6ee0ba04aade------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:47:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wolinski/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[Why I hate to use personas.]]></title>
            <link>https://medium.com/@wolinski/why-i-hate-to-use-personas-99036a131596?source=rss-6ee0ba04aade------2</link>
            <guid isPermaLink="false">https://medium.com/p/99036a131596</guid>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Krzysiek Woliński]]></dc:creator>
            <pubDate>Mon, 09 May 2016 08:40:55 GMT</pubDate>
            <atom:updated>2016-05-09T08:40:55.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*fLNhl7x48ew4xksMzm1oOA.jpeg" /><figcaption>Follow the light.</figcaption></figure><p><em>Summary: the author of the article explain why using persona may not a right decision for your product.</em></p><p><strong>Imagination</strong></p><p>Why companies try to find personas? You have your own product, but don’t have a cool story about it. Your marketing/product/whatever department tries to convince you to focus on some group. The story begins and based on the word <em>imagine</em>. Lets <em>imagine </em>a persona:</p><p>It’s a girl — due to the fact that most of your users are girls<br>She’s 17 years old — data said that’s the average age<br>Her name is Julia — right now she’s a human, trending name will be a benefit<br>Julia has a brilliant new iPhone 6s — why not? we all have such users<br>She return to your application once a week during Tuesday evenings— remember data cannot be wrong — and make some interactions lets say posting a photo from weekend.</p><p>Probably you already have an illustration of red hair girl in cool t-shirt with her smartphone when using your app ans she’s smiling to you. Awesome!</p><p><strong>Fit to your product</strong></p><p>Oops! We forget about the most important part — she loves your product and she fits to your product as nobody else. Your app helps her to develops her hobbies. She’s more than happy, because she never ever complain about your application, never!</p><p>Based on data we have 40% of Julias in our user base.</p><p><strong>Why I hate it?</strong></p><p>The answer is simple — this person doesn’t exists. It’s only what you jus <em>imagine. </em>As humans/designers/marketing people we try to make either the best of the best one or average of the average one — everything based on data. I aware of the fact that the persona I described above is more than exaggerated. Check how you tweak your personas.</p><p>But that’s not the biggest problem — still that persona does not exists. I means that you cannot just ask her what she thinks about your new feature, check her progress by data or just following her actions. Nothing!</p><p><strong>Solution</strong></p><p>You have real user in your user base. <br>Do not create a new one!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99036a131596" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NPS — is it possible to do it wrong?]]></title>
            <link>https://medium.com/@wolinski/nps-is-it-possible-to-do-it-wrong-e8e916884a5?source=rss-6ee0ba04aade------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8e916884a5</guid>
            <category><![CDATA[nps]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Krzysiek Woliński]]></dc:creator>
            <pubDate>Wed, 10 Feb 2016 18:56:39 GMT</pubDate>
            <atom:updated>2016-02-15T06:57:03.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*T0hiRWp4X5CB88B1WgTeUQ.jpeg" /><figcaption>Please do not feed the bear. Thanks!</figcaption></figure><p><em>Summary: an author of this article shares some thoughts what could influence your NPS score and make it less reliable.</em></p><p><strong>Intro</strong></p><p>I’m obligatory to briefly say what NPS is. Net Promoter Score is a tool to help you measure what your customers think about your product. It is based on a simple question:</p><blockquote><em>How likely is it that you would recommend our product to a friend or a colleague?</em></blockquote><p>Respondent has to simple choose from 0 to 10 scale. That’s all! Your role — as analytic — is just collect votes, divide them between three groups: 0–6 votes are dictators, 7–8 are sitters and 9–10 are promoters. Use the magic formula:</p><blockquote>NPS = (no of promoters — no of detractors) / total votes.</blockquote><p>You will get percentage value of how your product is perceive by your customers.</p><p>That’s all! You know everything! Probably you’re thinking to try on your own, right now. I will share my thoughts what might go wrong.</p><p><strong>Questionnaire</strong></p><p>Lets design a simply survey. One question. Simply one. Probably you or someone else may come up with the idea that if you are already doing the survey and taking user’s time it’s good to ask more questions. Are you familiar with such a temptation? Come one — just two more questions?!</p><p>Do not hesitate. Why?</p><p>Each extra question may influence on number of submits. Probably only highly motivated people — both on plus or minus — will do it. You will cheat normal distribution and break the internet.</p><p>Remember that it’s a really good practice to present survey only once, either people with polarized opinion — generally negative — may change the results.</p><p><strong>Target group</strong></p><p>Do we really need define anything here? Just ask x random people. All visitors are equal.</p><p>How about no. Why?</p><p>The answer is simpler than you expect — representative group is the key. Different group of your users use your product in different way — visitors, users, heavy users or moderators. You can define that you measure NPS for particular group or for the whole product. Good practice said that it’s good to start survey when there is particular interaction between a visitor and a product.</p><p>Representative group also means as big as possible. Sometimes it is hard or impossible to reach focus group using wrong mechanism / implementation.</p><p><strong>Value</strong></p><p>We got results! Based on presented formula you can get something between -100% and 100%. You got +5% — is it good? Above the average?</p><p>The answer is — the question is wrong! Why?</p><p>The only way of learning something from NPS is to compare your NPS scores over time. So there is no point to compare your product with the others. It’s good to know how things are going, that’s all.</p><p>Do it regularly!</p><p><strong>Time noise</strong></p><p>Make a year plan with every first Friday of the month survey, schedule it and go!</p><p>Time for bonus — still not?</p><p>It’s hard to image for me a business that is not seasonal. Every holidays, special days or even weekday your visitors may interact differently with your product. Try to avoid doing any research during that time, if it’s possible.</p><p><strong>First rule at the end</strong></p><p>Do it right!<br>Do not fit excuses to the results.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8e916884a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How have websites changed over time?]]></title>
            <link>https://medium.com/@wolinski/how-website-change-over-time-850bd79c0156?source=rss-6ee0ba04aade------2</link>
            <guid isPermaLink="false">https://medium.com/p/850bd79c0156</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[airbnb]]></category>
            <dc:creator><![CDATA[Krzysiek Woliński]]></dc:creator>
            <pubDate>Fri, 05 Feb 2016 16:51:29 GMT</pubDate>
            <atom:updated>2016-02-07T21:15:57.107Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWPAUTFVV44OnammgGHtIA.png" /><figcaption>Next article will be longer, maybe.</figcaption></figure><p>No time to explain!</p><p>Just check what I discovered today: <a href="http://www.uxtimeline.com/airbnb.html">http://www.uxtimeline.com/airbnb.html</a></p><p>Yes, I’m a big fan of Airbnb product :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=850bd79c0156" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A lot of KISSes in your life!]]></title>
            <link>https://medium.com/@wolinski/a-lot-of-kisses-in-your-life-ae458b7eae80?source=rss-6ee0ba04aade------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae458b7eae80</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Krzysiek Woliński]]></dc:creator>
            <pubDate>Thu, 04 Feb 2016 20:50:15 GMT</pubDate>
            <atom:updated>2016-02-04T20:51:55.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*rmaMh4DeB4H4kgt8_oZ6BQ.jpeg" /><figcaption>It’s not me, it’s a lake.</figcaption></figure><p>That’s…</p><p><strong>K</strong>eep<strong> — </strong>the first rule is to remember about the rule</p><p><strong>I</strong>t — team rocks!</p><p><strong>S</strong>imple<strong> —</strong>when you have to describe your solution is too complex</p><p><strong>S</strong>tupid<strong> — </strong>remember that solution is stupid, not your users!</p><p>… it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae458b7eae80" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>