<?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 Alexander Lindqvist on Medium]]></title>
        <description><![CDATA[Stories by Alexander Lindqvist on Medium]]></description>
        <link>https://medium.com/@alexanderlindqvist?source=rss-714d6bf42b0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*itoqmoHW1XQAJ0lAvyijug.jpeg</url>
            <title>Stories by Alexander Lindqvist on Medium</title>
            <link>https://medium.com/@alexanderlindqvist?source=rss-714d6bf42b0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:54:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexanderlindqvist/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[Designers, we need to have a talk about responsibility.]]></title>
            <link>https://medium.com/@alexanderlindqvist/designers-we-need-to-have-a-talk-about-responsibility-ba134dbdc4e5?source=rss-714d6bf42b0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba134dbdc4e5</guid>
            <category><![CDATA[circulareconomy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[climate]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[commerce]]></category>
            <dc:creator><![CDATA[Alexander Lindqvist]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 12:03:55 GMT</pubDate>
            <atom:updated>2019-11-04T12:03:55.109Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8xpTOWl479IOeWne" /><figcaption>Photo by <a href="https://unsplash.com/@timmarshall?utm_source=medium&amp;utm_medium=referral">Tim Marshall</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>With our modern digital tools, the world is getting smaller. It has never been easier to follow events on the other side of the planet and to gain knowledge in any area from your home.</p><p>But with great power, comes great responsibility. We have a climate crisis and governments that persecute their citizens. I know, many of these things are not unique for the modern world but with modern tools, it has become so much easier and cheaper to control, monitor, produce in larger scales.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*2_03ZpJ8uPR6OcLVkkMkfA.jpeg" /><figcaption>Protesters in Hong Kong destroyed a “smart” lamppost on Saturday over fears that the device is equipped with facial recognition software and was being used for surveillance. Source: <a href="https://www.dailydot.com/debug/hong-kong-protesters-facial-recognition-tower/">https://www.dailydot.com/debug/hong-kong-protesters-facial-recognition-tower/</a></figcaption></figure><p>Is there anyone on your team asking the hard questions about how our work will impact people, cultures and our planet? I often lack openness to discuss these topics in projects and with clients.</p><p>We need to talk less about the output and more about the <strong>outcomes </strong>we are looking for and set principles to follow in the development process.</p><h3>Ethics</h3><p>According to <a href="https://www.merriam-webster.com/dictionary/ethic">Merriam Webster</a>, ethics is “the discipline dealing with what is good and bad and with moral duty and obligation.”</p><p>We as designers must consider human rights as a part of our process and not use our knowledge of human psychology for dark experience patterns and shaming people into things they might not want. Show respect to all people no matter what given circumstance they have or what they identify as. We need to understand and include all parts of humanity.</p><p>One thing that is getting bigger and bigger in software development is accessibility. But still, I find it common that we only look for the low hanging fruits like color contrast and big text, but there is so much more we need to understand to build products for everyone. And at the end, when the investment cost of accessibility is brought up or we have to prioritize work, accessibility is often the first to get dropped.</p><blockquote>“There is no beauty in the finest cloth if it makes hunger and unhappiness.”</blockquote><blockquote>— Mahatma Gandhi</blockquote><p>We as designers influence people on how they behave and how they live their lives, that is a great responsibility we need to care for.</p><p>I highly recommend that you have a look at <a href="https://medium.com/u/77d3f63ebe80">Per Axbom</a>s talk about <a href="https://www.youtube.com/watch?v=N41gcRTwwuY">Navigating the ethical minefield of digital design</a>. Per is a huge role model in this topic.</p><p><em>Ethics for designers has a free toolset you can use to gain more knowledge of ethics in design.</em></p><p><a href="https://www.ethicsfordesigners.com/">Ethics for Designers</a></p><h3>Climate</h3><p>Do we know the impact our designs have on our environment through the entire production chain? Children are mining cobalt for our smartphones lithium-ion rechargeable batteries in Congo, risking their lives around toxic dust. Not only bad for the planet but humans are getting exploited for our convenience.</p><p>The role of design needs to include a climate mindset and not only look and feel. It’s a necessity for future business models and we as designers have the influence and power to make a change.</p><p>Circular design and circular economy is something that is growing and is needed now more than ever. The circular economy has three principles. Keep products and materials in use, design out waste and pollution, regenerate natural systems.</p><p><em>You can read more about circular design on the Ellen Macarthur Foundation website:</em></p><p><a href="https://www.ellenmacarthurfoundation.org/explore/circular-design"><em>https://www.ellenmacarthurfoundation.org/explore/circular-design</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BUHT6Ab5xHOlqK4J" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Commerce</h3><p>The way we consume today has an impact on us and the planet in so many different ways. We need to build commerce that has a balance of sustainability, inclusion, and ethics but still generates sales. The reputation of having an unsustainable and inhumane manufacturing process can ruin a brand in modern media that is costly to repair.</p><p>An example of this was when journalists in Denmark revealed that H&amp;M burned 12 tonnes of unsold clothes per year in Denmark alone.</p><blockquote>“ Can we still trust a company that publishes lengthy sustainability reports which fail to mention anything about burning tonnes of clothing? Any brand that spends millions promoting recycling campaigns has to stand up to scrutiny. “ — Kirsten Brodde, Greenpeace</blockquote><p>We need to build commerce that is sustainable and including but still generates business. With modern technology like AI and VR in combination with data, we should be able to design better experiences both digital and physical and look into how Phygital which means digital-physical fusion can change the way we consume for the better. We as designers are part of the problem.</p><p><em>You can read more about Phygital on Forbes:</em></p><p><a href="https://www.forbes.com/sites/sap/2018/08/13/learn-how-a-phygital-strategy-can-help-grow-your-business/#71a6844b770a"><em>https://www.forbes.com/sites/sap/2018/08/13/learn-how-a-phygital-strategy-can-help-grow-your-business/#71a6844b770a</em></a></p><h3>Data</h3><p>According to Domo, in 2017 there was<a href="https://www.domo.com/learn/data-never-sleeps-5?aid=ogsm072517_1&amp;sf100871281=1"> 2.5 quintillion bytes of data</a> created each day! Data is gold we mine in the digital age. We use data to design extraordinary experiences to help people reach their goals and create personalized products and services.</p><p>But there is also another side to the story that can be devastating. Security, ownership, anonymity, and integrity to name a few. We don’t know how collected data about us is used and we can rarely control it. At the end who decides what is ethically okay usage since data is used not only by advertisers but even by organized crime.</p><p>And with the trend of solely data-driven design decisions, we tend to forget that there is a human behind the numbers that have emotions and needs we can’t understand without qualitative research. Just like in The Matrix.</p><blockquote><em>“Neo: Do you always look at it encoded?</em></blockquote><blockquote><em>Cypher: Well you have to. The image translators work for the construct program. But there’s way too much information to decode the Matrix. You get used to it. I…I don’t even see the code. All I see is blonde, brunette, red-head. Hey, you uh… want a drink?”</em></blockquote><p>In 2018 the European Union released the <a href="https://gdpr-info.eu/">General Data Protection Regulation (GDPR)</a> to protect the public from intrusive marketing, invasion of privacy and to ensure data protection. This is a great step in the right direction but it has its flaws.</p><blockquote>“Organised crime, terrorist organisations, investigative journalists and private investigators can all use data sources on the internet and data mining tools to find and target people and groups.”</blockquote><p><em>Source: </em><a href="https://www.bcs.org/content-hub/the-dangers-of-data-collection/"><em>https://www.bcs.org/content-hub/the-dangers-of-data-collection/</em></a></p><p>We need to question how we use data in a proper manner and how we can protect the innocent by preserving anonymity when we design services. Make a risk analysis of the impacts of leaked information getting in the wrong hands.</p><h3>Our role</h3><p>We are designers, a part of the creation of almost every experience in some way. Let’s start asking the hard questions in our companies together and open up communication on how we can improve the problems already in the design phase. We can no longer blame others for what we help to create, let’s take <strong>responsibility</strong>!</p><h3>Before you go</h3><p>Please let me know what you think in the comments below. If you find this post useful, please share and like so it can reach others as well. Thank you!</p><p>I would love to hear more from you so please connect with me on LinkedIn, <a href="https://www.linkedin.com/in/alexander-lindqvist-ba13957a/">here is my profile</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba134dbdc4e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why skipping the retrospective is a big mistake]]></title>
            <link>https://medium.com/@alexanderlindqvist/why-skipping-the-retrospective-is-a-big-mistake-4a78e182e093?source=rss-714d6bf42b0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a78e182e093</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[retrospectives]]></category>
            <dc:creator><![CDATA[Alexander Lindqvist]]></dc:creator>
            <pubDate>Wed, 20 Feb 2019 13:49:38 GMT</pubDate>
            <atom:updated>2019-02-21T01:06:14.217Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rPbWn-hP1ttajRds" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Our beloved Scrum event, from the Latin word <em>retrospectare</em> that means “look back”. This event has a specific meaning in our world of software development, both positive and negative.</p><p>The <a href="https://www.scrumguides.org/scrum-guide.html#events-retro">Scrum Guide</a> states that the retrospective is an event to reflect over what improvements can be made for the upcoming sprint with focus on people, processes, tools, and relationships. Then make a plan how to implement these improvements.</p><p>This appears to be simple and great on paper, but creating a space where all members of a team feel safe enough to speak about difficulties or give possible solutions is not easy at all. It takes time and a lot of work to get a good foundation for the retrospective.</p><h4>Do not create a skipping habit</h4><p>I have been in cross-functional teams that as time passed starts to operate really well because of continuous improvements and reflection over the ways of working and how they behave towards each other.</p><p>But it all came to a point where members of the team said things like:</p><blockquote>“Should we skip the retrospective? We don’t have anything to talk about?”</blockquote><blockquote>“I think that it’s too much to have a retro every second week when we are running two-week sprints”</blockquote><blockquote>“We don’t need the retro anymore, it’s a waste of time we need to deliver instead”</blockquote><p>In my experience, these are warning signs that you need to change the focus of your retrospectives because they are never a waste of time. In moments of deadlines and delivery, the retrospective is more important than ever. You set aside time to reflect and prioritize the forthcoming work. When the going gets tough, the going must retrospect.</p><h3>7 Tips for your upcoming retrospectives</h3><p>I want to share some suggestions and methods for retrospectives that I’ve learned, to improve and create a better outcome when you feel like skipping.</p><h4>1. Futurespective</h4><p>If you have a deadline or a release coming up, use the retrospective as a futurespective to focus on the upcoming challenges. This is a great way to let the team raise anything they are worried about before the release. In a cross-functional team, there might be problems that you in your role haven’t thought about. By doing this, you can discuss and create a plan for a smoother release. <a href="http://www.funretrospectives.com/category/futurespective/">Here you can find examples of Futurespective activities</a>.</p><h4>2. Retro inbox</h4><p>Instead of having the team wait for the retro to suggest topics to talk about, set up a “Retro inbox” on the wall. Members of the team can set up post-its with suggestions for the retrospective at any time during the sprint. You can then simply take the notes with you when the time for the retro has dawned.</p><p><em>Source:“</em><a href="http://visualizationexamples.com/"><em>Toolbox for the Agile Coach — Visualization Examples</em></a><em>” by Jimmy Janlen.</em></p><h4>3. Be creative and uncontroversial</h4><p>If there is some extra time in a retro, be creative and uncontroversial. Once I made a team pick notes from a hat, the notes had numbers on them so they got paired two and two. I then asked them to leave the office for 30 minutes to go do anything they wanted.</p><p>There were only two rules, they were not allowed to return to the office in 30 minutes and they had to spend the time with the person they got partnered with. People came back with more energy and had gotten to know each other better. (No one went to the pub, luckily for me)</p><h4>4. Never leave without actionponts</h4><p>A lot of teams follow the Scrum Guide and have the retrospective every sprint as they should, but they feel like they don’t get any results from it.</p><p>I see teams that don’t create action points during the retro concerning the topics they discussed or found solutions to. Make sure that you never leave the retro without writing down action points that the whole team has approved so you can test and evaluate them. Sometimes it can also be good to have a member volunteer to take responsibility for an action point to make sure that it gets done.</p><p>On the next retro, you use a short amount of time to follow up on the last action points and discuss them.</p><h4>5. Snacks and drinks</h4><p>This might sound silly, but usually, the retro is held in a small conference room where you at other times sit and talk about work and have other meetings. You can change the feeling of the retro and make it more special by providing snacks and drinks, even play some groovy music before starting to set the mood. Make it happy and playful, why so serious?</p><p>I discovered this by accident once when a project manager handed us a bag of candy that we then brought to the retro. The team had huge smiles on their faces and fought over the candy while laughing. It was a great start to the retro. Best of all, it’s a cheap investment to pitch to your manager.</p><h4>6. Don’t forget to be human</h4><p>I have been in retros where topics are all about coding, servers, infrastructure, and other development-related matters. Never forget to be human and talk about feelings and relationships. If the people in the team don’t feel well, they can’t deliver and then the infrastructure or coding does not matter.</p><p>Also, bring up good things, our brains are hardwired to be negative and we often overlook the good and positive stuff. Have a member of the team done something extra good this sprint, let them know because you will improve their day and confidence.</p><h4>7. Make attending optional</h4><p>Nobody likes to be forced to anything, especially not when it might put you in a socially awkward situation.</p><p>Sometimes you might not have the time and by attending the retro you sit there stressed out, maybe you have concerns outside of work that affects you at the moment. Don’t force these people into joining or shaming them for not attending.</p><p>If you have the possibility to leave or not attend, your motivation for staying will be higher since you are there of your own free will.</p><h3>Summary</h3><p>Never skip the retrospective, if you feel like it’s a waste of time right now because of a deadline or a release use the time to improve the outcome for the team and the product. It’s easy to create a habit of skipping the retro that will ruin the foundation you have worked with for a long time to perfect.</p><p>Adjust the retro plan for the current situation, I promise you that it’s never a waste of time to reflect and improve your ways of working or tools.</p><p>I want to share 7 tips for your upcoming retrospective when you feel like skipping:</p><ol><li><strong>Futurespective</strong></li><li><strong>Retro inbox</strong></li><li><strong>Be creative and uncontroversial</strong></li><li><strong>Never leave without actionponts</strong></li><li><strong>Snacks and drinks</strong></li><li><strong>Don’t forget to be human</strong></li><li><strong>Make attending optional</strong></li></ol><p>Thank you for reading this, I hope this gave some inspiration for how you can improve your team’s retros further in the future. To find activities for your retros, I strongly recommend <a href="https://retromat.org/en/?id=43-33-94-49-40"><strong>Retromat</strong></a> that generates random plans for agile retrospectives.</p><h3>Before you go</h3><p>Please let me know what you think in the comments below. If you find this post useful, please share and like so it can reach others as well. Thank you!</p><p>I would love to hear more from you so please <a href="https://www.linkedin.com/in/alexander-lindqvist-ba13957a/">connect with me on LinkedIn.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a78e182e093" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Competence mapping instead of design titles]]></title>
            <link>https://medium.com/@alexanderlindqvist/competence-mapping-instead-of-design-titles-6690ee3a469e?source=rss-714d6bf42b0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6690ee3a469e</guid>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[competence]]></category>
            <dc:creator><![CDATA[Alexander Lindqvist]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 13:22:47 GMT</pubDate>
            <atom:updated>2019-11-01T21:28:45.735Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GZsaJ2BbmThMM55u" /><figcaption>Photo by <a href="https://unsplash.com/@thkelley?utm_source=medium&amp;utm_medium=referral">Thomas Kelley</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We have many names for the things we love. UX-Designer, UI-Designer, Interaction Designer, UX-Researcher, Usability Expert, Web Designer, UX-Engineer, Art Director, Product Designer, Service Designer and so on.</p><p>I work as a UX-Designer and I have heard as many definitions of my role as people I met using it. I often end up in long discussions around responsibility, skills, educations, softwares, processes, methods and more that concern the role as a UX-Designer. And if we, the people that share the same title can’t agree on what it means. Who can?</p><p>The power titles used to come with are slowly fading away in the modern business world. There is also a trend right now where companies and individuals create their own titles to hype their brands in marketing channels. You know what companies I talk about.</p><h3>Supplement the individual with competence</h3><p>To be more clear and transparent amongst titles, you can supplement them with the competence a person holds and not only go on a title used in the company. There are several models around like T-shaped skills and so on but in my experience, we talk more about them than implement them.</p><p>I have seen a common problem within companies, they have not strongly stated what roles they hire and the definition they have of those titles. This creates problems in all parts of a project. It’s hard to sell a role that you as a sales representative don’t fully understand to a client that doesn’t really know themselves what need they really have.</p><p>And if you replace a designer with someone new, it’s not obvious that just because they have the same title they both can deliver the same things.</p><h3>Visualizing the map</h3><p>In this example, I will use a radar diagram with a scale from 0–7 and with eight axles for skills.</p><p>I start off by choosing some core skills that I want to have on the map. In this case, I will use interaction design, prototyping, user research, user testing, accessibility, visual design, workshop facilitation, Lean UX.</p><p>Let’s add them to our competence map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*lZ4H2-5NbyZyrabBKYvvnA.png" /><figcaption>Radar diagram with a scale from 0–7 and with eight axles for skills</figcaption></figure><p>Now I will grade my skills in each axel from 0–7 and visualizing my current level in the map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*U78c_ydMfbRO3kHCbornfA.png" /><figcaption>Current level in a radar diagram</figcaption></figure><p>You can use as many axles as you like and change the scale higher or lower, it’s all about what suits your situation the best.</p><h3>The map to evolve designers</h3><p>If you are a large organization, you want your employees to evolve but it can be hard to keep track of the direction everyone will want to take in the future. The competency map can provide you with clear direction on how someone wants to evolve in their crafts, based on the current skills used in the map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*vO_zwPrPvujw2zAkDsWMkA.png" /><figcaption>Map with current levels and the target designers want to reach</figcaption></figure><p>As you see, its very clear that I want to evolve in visual design, user research, and user testing. Knowing where a employee want to go helps us as a company make better decisions in projects and educational initiatives in the future to meet the target.</p><h3>The map for company competence</h3><p>If all employees with the same title fill out a map with the same core skills that are used in a role you can add all these together to see the level of the current skills inside the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*lk8kvGijWab0ihf3yFerlQ.png" /><figcaption>Map to see the current experience levels as a company</figcaption></figure><p>This also makes it easy to see where you are strong and where improvement is needed inside the company. The management or board can set a target goal, for example, the upcoming next year.</p><h3>The map for sales and project staffing</h3><p>A client called you and said they need one UX-designer for a project, nothing weird here. But as I said before, just because they are looking for a UX-designer does not make it obvious what needs they actually have in that project.</p><p>Ask the client to fill out the same competency map that the UX-designers in your company filled out. Ask them to base it on what they <strong>assume</strong> the needs are in the project because usually, they don’t know themselves.</p><p>This can then be used as a very good basis for the discussion about staffing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*8NNYdsWOaXaYs2VOOBVwNg.png" /><figcaption>The map filled out by a client based on assumptions of needs for a project</figcaption></figure><p>Use this as support both when talking to the client and during the project staffing by comparing it to the considered designer’s maps. This can assist in finding the best potential match.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Ezki3hZMtpthensDLk3EQ.png" /></figure><p>Based on the current levels and targets, I would say that Jane might be the best candidate for this client project. She possesses several skills they are asking for and she also wants to evolve in those fields. Meanwhile, Martin is another type of UX-Designer and he has no motivation going in the direction Jane wants to go in.</p><h3>Summary</h3><p>By using a radar diagram you can map out competences in a role, to create a better understanding of what skills you as a company consider core for that title. It helps you to see what skill levels you currently have in the company and the goals for how the skills should develop in the future, both for individuals but also as a company.</p><p>It can help you with sales by mapping out the needs of a client based on the core skills you offer and make better choices for project staffing.</p><p>I hope I could inspire you to new ideas about how you can improve the understanding of roles and titles in your organization. Transparency and understanding create a better workplace and in the end a better product.</p><p>This is a tool that I used not only when working but also at job interviews to really understand what they are looking for in a UX-Designer. In those situations I let the company decide the skills that go on the map.</p><p><em>Credits go to </em><a href="https://medium.com/@martin.ux.christensen"><em>Martin Christensen</em></a><em> for the inspiration with the charts from his way of </em><a href="http://portfolio.modernux.se/docs/measuringusability/#visualizing-the-baseline"><em>Measuring Usability</em></a><em>.</em></p><h3><strong>Before you go</strong></h3><p>Please let me know what you think in the comments below. If you find this post useful, please share and like so it can reach others as well. Thank you!</p><p>I would love to hear more from you so please connect with me on LinkedIn, <a href="https://www.linkedin.com/in/alexander-lindqvist-ba13957a/">here is my profile</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6690ee3a469e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 principles for good product design]]></title>
            <link>https://medium.com/frank-digital-experiences/7-pricinples-for-good-product-design-8533240ffec?source=rss-714d6bf42b0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8533240ffec</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[principles-of-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alexander Lindqvist]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 15:41:53 GMT</pubDate>
            <atom:updated>2019-10-01T08:55:55.114Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qM7qpruygBWJ8ZE6" /><figcaption>Photo by <a href="https://unsplash.com/@dillon_mangum?utm_source=medium&amp;utm_medium=referral">Dillon Mangum</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I wanted to share some principles I learned while working as a designer in software projects. Of course, there are a lot of other principles and guidelines in the daily work that is important, but these are some I want to write about today.</p><h3>Diversity and Inclusion</h3><p>Have you ever walked into a conference room full of stakeholders only to see middle-aged white men? Yeah me too, and it makes me sad and angry every time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sd00Eo6xXx_9nQI8" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>But when we design and build products for the real world, its a requirement to have a team that is diverse to understand all angles and needs. We need to benefit from peoples different experiences and backgrounds. Don’t exclude anyone over age, religion, origin, gender or looks ever. The person you actively choose to not include because of your own bias might have the solution to your problem.</p><h3>Transparency</h3><p>Internal politics can break a team, product or even a company. It can spawn hidden agendas or even worse, the feeling that there are hidden agendas when in reality there are none.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ul0abnHcbviz_HaL" /><figcaption>Photo by <a href="https://unsplash.com/@alvaroreyes?utm_source=medium&amp;utm_medium=referral">Alvaro Reyes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Fill the walls with designs, wireframes, personas or any other documentation that you have created. Always externalize your work to everyone, it’s not only a great way to get feedback but it can also help spread the “why” among your teams. It’s really important that everyone knows why we make something and what the goal is. If you are expected to drive a car but no one tells you what the destination is, it’s hard to make it. Make transparency part of company policy today!</p><h3>Simplicity</h3><p>Sometimes it feels like I spend hours and hours asking questions like “Do we really need all this text?” or “Is this really a required feature for the user to solve the task?”. If I would be a superhero my name would be Lower The Cognitive Load Man.</p><blockquote>“Genius is the ability to reduce the complicated to the simple.”</blockquote><blockquote>-C.W. Ceram</blockquote><p>I find it rare that time is set aside in a project to reflect if we can solve an interaction in a more simple way by taking features out of an interface. Usually, the users are met with a wall of text that nobody reads and a general cognitive overload.</p><p>The reason why startups like Klarna and Spotify are so successful is not that they have a whole new innovative idea per se, they deliver the same service but it is simpler than the competitor’s products.</p><h3>Empathy</h3><p>I hope we all know by now that we need to test our designs and assumptions with users to make sure we build the right thing to solve the right problems. But most people I come across don’t seem to understand the difference between what some call users and the real end-users.</p><p>I come across a lot of stakeholders that considers themselves users because they used the system and that they can give feedback for the other users. This is called The False-Consensus Effect.</p><blockquote>The false-consensus effect refers to people’s tendency to assume that others share their beliefs and will behave similarly in a given context. Only people who are very different from them would make different choices.</blockquote><blockquote>— Raluca Budiu (NN/g)</blockquote><p>It is so important that you query those stakeholders and spend time learning who the real end-users are and talk to them.</p><h3>Collaboration</h3><p>When I was studying UX-design we talked a lot about the difference between UX and UI and why we should consider them as different things. And they were correct it is not the same, but they also talked down UI design which resulted in a “us and them” situation.</p><blockquote>“UI is the saddle, the stirrups, &amp; the reins. UX is the feeling you get being able to ride the horse.”</blockquote><blockquote>— Dain Miller</blockquote><p>But to create a great product both are equally valuable and the most important is that a UX-designer and a UI-designer work together from the start until the end. The worst thing that can happen is when there are deliverables between the designers in a team.</p><p>When you go to a restaurant you expect the food to taste good, but also look good right?</p><h3>Fidelity</h3><p>I have learned the power and importance of animations in software design, not only to create a smoother design but also how it can be used to strengthen interactions and give visual feedback to the user.</p><blockquote>“In a world where your finger often covers the button you’re pressing, animation plays a huge roll in providing the user the reassurance they need.” -José Torre</blockquote><p>Years ago I used to think this area belonged on a UI-designers table. But after designing more applications for mobiles and complex systems it dawned on me how it can improve my work as a UX-designer if I think about this in my wireframes early. Also, this can help the developer understand how a feature is designed to work so they can implement it in the smartest way possible.</p><h3>Validation</h3><p>In the beginning, you set a target goal for the product but meanwhile, you work on the design the world changes. Not only the world but also the users of your product and the reason why they use it. To hit a moving target you can’t shoot an old-school cannonball, the chances of hitting the target is slim to none. What you need is a targeting missile, that will do the job!</p><blockquote>“Good designers want to be proved wrong, bad designers hope to be proved right.”</blockquote><blockquote>— Andy Budd</blockquote><p>The only way to make sure that you are doing the right thing is to measure and keep iterating over and over. Not only with users but you need to align with the business and technology. All of these areas are important for the success of the product. It’s cheaper to redesign the wireframe then rebuilding the finished product. Do your research and measure your success and iterate until you hit your goals!</p><h3><strong>These are the principles I live by as a designer</strong></h3><p>And if you work with me, this is what you get. I would love to hear more from you so I would love to connect with you on LinkedIn, <a href="https://www.linkedin.com/in/alexander-lindqvist-ba13957a/">here is my profile</a>.</p><p><strong>Before you go</strong>, please let me know what you think in the comments below. If you find this post useful, please share and like so it can reach others as well. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8533240ffec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/frank-digital-experiences/7-pricinples-for-good-product-design-8533240ffec">7 principles for good product design</a> was originally published in <a href="https://medium.com/frank-digital-experiences">Frank Digital Experiences</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>