<?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 Aleksandra Novakovic on Medium]]></title>
        <description><![CDATA[Stories by Aleksandra Novakovic on Medium]]></description>
        <link>https://medium.com/@acaciawoods?source=rss-855eac8a2616------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*n_13UejAR2JQKv_FSLe2sg.png</url>
            <title>Stories by Aleksandra Novakovic on Medium</title>
            <link>https://medium.com/@acaciawoods?source=rss-855eac8a2616------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:56:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@acaciawoods/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[The grass is greener on the other side.]]></title>
            <link>https://medium.com/@acaciawoods/the-grass-is-greener-on-the-other-side-5ae327a1260?source=rss-855eac8a2616------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ae327a1260</guid>
            <dc:creator><![CDATA[Aleksandra Novakovic]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 14:33:40 GMT</pubDate>
            <atom:updated>2022-01-31T14:33:40.156Z</atom:updated>
            <content:encoded><![CDATA[<h3>The grass is greener on the other side</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4TcCyxdzA9LU2Kc3Dz92w.jpeg" /></figure><blockquote>As a product designer, this is how I see companies behaving nowadays.</blockquote><p>Too many companies are trying to add features on top of features on top of other features just to beat the market. They are afraid of the competition, of Company X, Y or Z stealing their market share.</p><p>And there the infinite match begins, a competition no one can really win because: <em>the more the better </em>is not always true.</p><h3>The more the better</h3><p>It is not always easy to comprehend that adding a feature to the product portfolio doesn’t really guarantee a return of investment. Experience il left behind while the <em>rush for new features</em> is saturating the market with the same boring ideas that have already been seen somewhere else.</p><p>I like to compare products to human bodies. I can add “features” to the body to improve my look, the health, the performance… but at the end there comes a point where one should simply accept what their body is: perhaps imperfect, but at least authentic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WPbUJohc3RiFuAZPIJk8Hg.jpeg" /></figure><h3><strong>Acceptance</strong></h3><p>Understanding what can or cannot be done, doesn’t necessarily make your product less attractive. Investing in these features that make you shine and that make you unique is one way to fight the feature overload.</p><p>Choose to invest on Experience. Rather than being a basic average in all fields, choose be the star in one. Make your brand a great brand by talking about people, not about features. As Steve Jobs said</p><blockquote><strong>“No products”</strong></blockquote><p>talking about Nike never talking about the “<em>what the shoe is”, </em>but the <em>“how the shoe makes you feel”.</em></p><p>It’s not easy for a marketing team to sell a product without really talking about the product, but there are brands out there doing it well. Define who you want to be, not what you want to have. Being over having.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ae327a1260" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yoga for design: Finding presence in UX]]></title>
            <link>https://medium.com/design-bootcamp/yoga-for-design-finding-presence-in-ux-fbfb1c63bc9c?source=rss-855eac8a2616------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbfb1c63bc9c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[yoga]]></category>
            <category><![CDATA[dont-make-me-think]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Aleksandra Novakovic]]></dc:creator>
            <pubDate>Thu, 14 Oct 2021 14:58:08 GMT</pubDate>
            <atom:updated>2021-10-15T00:45:00.547Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, during my yoga lesson the teacher asked us to place one hand on the chest and feel how our heart is beating 100,000 times per day, effortlessly and without thinking that it has to beat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1q5oJ-r5e5DvYT4GDzsEcw.jpeg" /></figure><p>My meditation session didn’t go as well as expected. I couldn’t find the “presence” because I kept on thinking: isn’t that how design should be?</p><p>I spent the 15 min meditation session thinking how experiences should be as simple as a beating heart. And how users should feel lighthearted while doing their everyday tasks.</p><p>How would it feel to go through your everyday tasks effortlessly, lighthearted, without overloading the mind with useless tasks? There are something like 30,000 instruction sets we would need to remember on regular basis. If we had to memorise each of those by heart, it would take us months to execute a single task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*rSZxDY0dBNtzivR6VkoCmg.jpeg" /></figure><p>I’ve never liked the title of Steve Krug’s book “Don’t Make Me Think”. I always thought it was misleading. I don’t recognise myself as a designer in that title. Instead I like my users to think about what matters the most to them. My role as a designer is to find a way to nurture users’ lightheartedness so that they can find presence on things that are really important for them.</p><p>If you could rename Steve Krug’s book, how would you call it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VZAzc1jLBjUSQIztL3TIzw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbfb1c63bc9c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/yoga-for-design-finding-presence-in-ux-fbfb1c63bc9c">Yoga for design: Finding presence in UX</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When users come first, they come back]]></title>
            <link>https://medium.com/design-bootcamp/when-users-come-first-they-come-back-5acbd1d5d0da?source=rss-855eac8a2616------2</link>
            <guid isPermaLink="false">https://medium.com/p/5acbd1d5d0da</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Aleksandra Novakovic]]></dc:creator>
            <pubDate>Thu, 14 Oct 2021 09:33:21 GMT</pubDate>
            <atom:updated>2021-10-15T00:46:07.471Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever sat in a chair that was beautiful to look at, but really uncomfortable to sit in?</p><p>Imagine your task is to design a new chair. You collect all the requirements, analyse the market, all you need is the material to build it. So you put together 3 legs, a seat.</p><p>Now, let’s imagine to do user testing on it.</p><p>You call a bunch of potential users, you create a survey hoping that your product is ready for the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BLYQgpVwuwKnJBXOK_i0g.jpeg" /></figure><ul><li>Do you think you would like to use this product frequently?</li><li>Do you think the product was unnecessarily complex?</li><li>Do you think it was easy to use?</li><li>Do you think the various functions were well integrated into the product?</li><li>Would you recommend this chair to a friend?</li><li>etc?</li></ul><p>What will you get at the end will be most likely a score that will certainly help you understand the satisfaction of your users. But it will be very hard to use this score to actually improve your product.</p><p>Unless your questions were very detailed.</p><p>Or unless you received answers from thousands of participants (yes! that would take months to organize!)</p><h3>I don’t care about the score</h3><p>Did you ever watch a football game and thought that the score really didn’t matter, the team that had lost played a better game anyhow…</p><p>It’s the same with design.</p><p>We don’t really care about scores. Scores give us an approximate idea on our customers’ satisfaction.</p><h3>Delightful experiences</h3><p>We all want to experience intuitive, delightful experiences. To help explain what I mean by <em>“intuitive, delightful experiences”</em> I like to use Aaron Walter’s <strong>hierarchy of user needs</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*_mQFLKZ1kwqx38ONg6GldA.jpeg" /></figure><ol><li>A digital product needs to be <strong>functional. </strong>It means it works as programmed.</li><li>Only then can it start to be <strong>reliable</strong>, when we acknowledge the availability of this product.</li><li>Once it is complete tasks without error becomes <strong>usable, </strong>but individual tasks being usable doesn’t make the product intuitive or delightful.</li><li>Only when a product is<strong> functional, reliable, and usable</strong> it could become <strong>intuitive.</strong> But WAIT — it doesn’t mean that it works as<strong> you think, </strong>but as<strong> your users think </strong>it should<strong>. </strong>When a product is easy to understand and to use, only then start to talk about it being <strong>delightful, pleasurable </strong>or beyond.</li></ol><p>Superficial delight could be visually pleasing, animated, with sound effects or containing stereotyped UI elements. <strong>Deep delight</strong> means the product works <strong>exactly</strong> how the users think, and it gets you <strong>exactly</strong> where you want to be, with very little thinking. It takes UX research to create deep delight because only by understanding how people think you may get a perfect score.</p><p>Going back to the chair…</p><h4>TL;DR</h4><blockquote>Making a user testing without proper UX research just because you need a score to prove success/failure is pointless. <strong>If you want to make your product better make better research upfront.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwcWAcqTBnDh4fC_40p2qA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5acbd1d5d0da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/when-users-come-first-they-come-back-5acbd1d5d0da">When users come first, they come back</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Big ideas often fail]]></title>
            <link>https://medium.com/design-bootcamp/big-ideas-often-fail-ux-strategy-78d1941d4207?source=rss-855eac8a2616------2</link>
            <guid isPermaLink="false">https://medium.com/p/78d1941d4207</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Aleksandra Novakovic]]></dc:creator>
            <pubDate>Wed, 13 Oct 2021 14:23:24 GMT</pubDate>
            <atom:updated>2021-10-15T00:37:46.169Z</atom:updated>
            <content:encoded><![CDATA[<h4>UX Strategy: staying away from solutioning</h4><p>Many product teams work in a very specific way:</p><ol><li>They acknowledge there’s a problem that needs a solution.</li><li>Requirements are written down.</li><li>Requirements are passed to the design team.</li><li>The design team provides a solution.</li></ol><p>However, in this scenario, the original requirements that are given to the team play a tremendously and dangerously big role! This is because requirements are often dictating a solution, rather than defining the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QzSwCt9iwjiwJgSGnExa3Q.jpeg" /></figure><p>Before starting to sketch a solutions, <strong>the focus should be on the requirements. </strong>It is crucial that designers understand the problem very well and that the designer is involved in the first stage. To understand why this step is so fundamental, we should have a look on the reasons why often big ideas fail.</p><h3>The greatest idea (often fails)</h3><p>You just had the greatest idea, you present it to the stakeholders and everyone seems excited about it. Once a new design is on the table and it has been discussed with the stakeholders, it is inevitable that 2 questions will determine the future of your idea:</p><ul><li>How much will it cost?</li><li>When will it be ready?</li></ul><blockquote>“In the vast majority of companies that I first meet, large and small, this is essentially how they work and have worked for many years. Yet these same companies constantly complain about the lack of innovation and the very long time it takes to make it from an idea to customer’s hands.”</blockquote><p>Marty Cagan</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IebHLRor1e_DPIk3B2M0bw.jpeg" /></figure><p>Instead, the organisation should acknowledge the reasons<strong> why the new ideas tend to fail,</strong> even when the greatest idea is presented to them:</p><ol><li><strong>The source of the idea: </strong>Although organizations have access to more data than ever before, they don’t have an effective way to evaluate their ideas for new products; therefore, they rely on their own understanding of the world or, even worst, on the idea they have of their customers.</li><li><strong>Pre-determined solutions and profit margins assumptions</strong> set the wrong expectation. If a business case is committing to a profit margin and go-to-market date, the cold truth is that at this stage we have no clue on either of these. We can’t know how much money we’ll make: if the team does an excellent job, this could be widely successful and literally change the company. On the other hand, the truth is that many product ideas end up making absolutely nothing. Without knowing the actual solution, we cannot know exactly how much it will cost implementing this solution. And the engineering team estimation would be noting more than a bet.</li><li><strong>Half of our ideas are just not going to work. </strong>There are many reasons for an idea not to work out. The most common one is that the customers just aren’t as excited about this idea as we were, so they choose not to use it. Also, it typically takes several iterations to get the implementation of this idea to the point where it actually delivers the necessary business value.</li></ol><p>Tony Ulwick, the founder of Strategyn, leading innovation consulting firm, states that failure rates are constantly over 80%. Capgemini suggests that is extremely challenging to make innovation lab works and reports that up to 90% of the innovation labs are failing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xs4AdXrjCKpRWfC-GNq9Ww.jpeg" /></figure><p>Other reasons why big ideas fail is that UX design functions is reduced to mere “beautification” and seen as a marketing tool to make your product appealing. Often, engineering gets brought in way too late, agile enters the picture far too late or the customer validation happens way too late.</p><h3>Why some big ideas succeed?</h3><p>To give an answer it is crucial understanding the basics of human psychology and the foundations of the UX strategy.</p><p><em>Users are not “addicted” to the product, they are addicted to the “value” this product brings.</em></p><p>Never heard of Theodore Levitt’s quote? <em>“People don’t want to buy a quarter-inch drill. They want a quarter-inch hole.”?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*guyJ7rEV88MTPDxcdStEYw.jpeg" /></figure><p>Think about the music you’re currently listening in your car: isn’t it awesome that you can listen to an infinite playlist anywhere and at any time? Why did you buy your Spotify subscription? Because of the product or because of the value it brings you? Qualitative research methods revealed customer needs that weren’t met yet with LPs, CDs or walkmen... They didn’t allow an endless selection of music at hand at any time and in any place!</p><blockquote>You must acknowledge is that you don’t need <strong>a big idea</strong> to innovate.</blockquote><p>We first define the customer, then defined the value and we progress by uncovering customer needs, discovering unmet needs, which allow us to find <strong>segments of opportunity.</strong> Then we are able to start conducting competitive analysis to later formulate<strong> the innovation strategy</strong>. Pricing strategy comes next and the product is then positioned on the market.</p><blockquote><em>Innovation is a product agnostic process.</em></blockquote><p>This is absolutely key to success. And what a surprise: <strong>it’s not about the product, it’s about the service that you are offering to your users.</strong> It’s about the job that we as humans want to get done. <em>The technology comes and goes.</em> If you focus on the human aspect, your chances of getting it right are way higher than if you focus on the specific technology or device.</p><p>When clients come to me for UX consultation, their goal sheets are full of words such as “Smart”, “AI”, “cloud”... They are already proposing a solution to a problem that hasn’t been identified nor studied adequately. This is an indication that the product team will become another casualty of the product failure statistics. UX strategy helps organizations take a step back and think about the human aspect before the product or the technology.</p><p><em>You must not start with the idea to innovate, you must start with an unmet user need, a real human problem that has not been solved yet or it has been solved poorly.</em></p><h3>The design process</h3><p>We are usually ready to start once specific pillars are defined.</p><p>A great starting point is having a look at the <strong>context, </strong>focusing on how many designers will you have available to work on a UX strategy and goals? Where are the requirements coming from? What is the actual problem we are trying to solve?</p><p>The mindset of the organization you’re working for should also be taken into consideration when deciding what will be the UX Strategy: is it very hierarchical or does it tend to be flat? Are the decisions being taken top-down or bottom-up?</p><p>Once you have some answers, you could start by organizing design sprints to co-design to generate as many ideas as possible. This process is also known in design as <strong>divergence.</strong> The idea is to produce as many ideas as possible, with no judgement. Then the team selects the best ideas for design implementation and evaluation. This other process is known in design as <strong>convergence</strong>.</p><p>The rest is known:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uc7GDPGE053NaxqoInPLTA.jpeg" /></figure><h4>Prototype.</h4><p>Build your design in a way that is meaningful to the user so you can collect feedback. This could be a paper prototype, as well as a fully-interactive high-fidelity prototype.</p><h4>Test.</h4><p>When the prototype is built, put it in front of customers so you can learn from observing how they go about completing the task the prototype allows them to accomplish.</p><h4>Iterate.</h4><p>As you collect learnings from the testing session, you can then take those learnings back to the team and iterate on your idea.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78d1941d4207" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/big-ideas-often-fail-ux-strategy-78d1941d4207">Big ideas often fail</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>