<?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 Ikenna Agu on Medium]]></title>
        <description><![CDATA[Stories by Ikenna Agu on Medium]]></description>
        <link>https://medium.com/@kenelight?source=rss-4ead279da0b3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wpNlDKWTKeLbayt3dOZxUQ.jpeg</url>
            <title>Stories by Ikenna Agu on Medium</title>
            <link>https://medium.com/@kenelight?source=rss-4ead279da0b3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:24:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kenelight/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[When is the design done?]]></title>
            <link>https://kenelight.medium.com/when-is-the-design-done-4260f8314068?source=rss-4ead279da0b3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4260f8314068</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Ikenna Agu]]></dc:creator>
            <pubDate>Wed, 07 Feb 2024 09:01:11 GMT</pubDate>
            <atom:updated>2024-02-07T09:01:11.796Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Overview image of the topic displaying on the right, the topic heading and sub-headings which are when is the design done? Definition of the word done, methodologies, varying meanings of done for design and summary. While on the left is a vector illustration of a lady looking at a taskboard." src="https://cdn-images-1.medium.com/max/1024/1*S16MlIXh4ZB5UoS8D2yRLA.png" /><figcaption>Abstract vector illustration by vectorjuice on <a href="https://www.freepik.com/free-vector/woman-reading-business-agreement-special-offer-contract-clipboard-deal-arrangement-terms-use-document-studying-paper-form-vector-isolated-concept-metaphor-illustration_12470267.htm#query=task%20complete&amp;position=16&amp;from_view=search&amp;track=ais&amp;uuid=3e0b302d-7158-473c-bbfe-3fd2dcb4a8df">Freepik</a></figcaption></figure><h3><strong>Definition of the word done:</strong></h3><p>To do is to perform an action and done is the past participle of do. That simply means that you have performed the action.</p><p>But, is that what we mean here? Probably, but let us also look at a simple definition of design. In very simple terms, a design is a plan produced to show the look and function or experience of a product or service before it is made.</p><p>As a designer or even as someone working on a project that involves design, development and product management, you may have come across this question a few times, “So, when is the design done?”. Or as a designer, you keep asking yourself, “when will I be done with design?” Sounds familiar? So, let us find out when a design is actually “<strong>done</strong>”.</p><h3>A bit about project management<strong>:</strong></h3><p>Firstly, let us start with the quick knowledge about different product development methodologies such as the <strong>traditional waterfall</strong> where each stage had to be fully completed before going to the next stage. In this method, teams agree to what I call, “a development contract” for each stage that must be completed before the big launch “<strong><em>Go-Live</em></strong>”. There is also the Agile methodology which takes a more flexible approach with short timelines called <strong><em>Sprints. </em></strong>In this method, teams collaborate at different stages such that multiple stages of the product development lifecycle can run simultaneously. Here we are not diving too deep about project management methodologies but if you are curious about them, find out more by checking this article by <a href="https://medium.com/u/a25927236a14">Leeron Hoory</a> on <a href="https://www.forbes.com/advisor/business/agile-vs-waterfall-methodology/"><strong>Agile Vs. Waterfall: Which Project Management Methodology Is Best For You?</strong></a><strong> </strong>and this by <a href="https://medium.com/u/5aa6b9976187">Atlassian</a> about <a href="https://www.atlassian.com/agile/project-management/project-management-intro"><strong>Agile vs. waterfall project management</strong></a><strong>.</strong></p><h3><strong>Varying meanings of done for design:</strong></h3><p>So, why did I mention the methodologies, because for each of the above-mentioned methodologies, the definition of done varies, or so we may think. If an organisation or team is using the waterfall methodology, they can argue that design is done when the design stage has achieved its objectives and handed over the design to development. For those applying the agile methodology, their argument would be that the design is done when a sprint has ended or they could also say the design is never done since it is an iterative approach and there will always be another version.</p><p>Products and services are never fully done as there is continuous work to improve and optimise their experiences (I mean that is why some of us have a job) however, here, I am addressing the design of a feature or product for a particular version of that product or service.</p><blockquote>I would say, the <strong>design</strong> is not considered“<strong>done</strong>” until you can <strong>measure</strong> its <strong>impact</strong> to see if it has <strong>achieved</strong> the <strong>goal</strong> <strong>or</strong> <strong>objective</strong> that it was intended to solve for that particular version of a product, process or service.</blockquote><p>The design of a feature can be validated and ready for development but because the design is basically like the plan on how to solve a user need or achieve a business goal, it cannot be considered done until that objective is met. This is why after handing over a “ready for development” design to the software engineering team, there should be a follow-up process or design quality assurance testing process to ensure that there has been a good implementation of the proposed design.</p><p>This is also why <strong>usability testing</strong> is important. One of the key goals of any design is ensure that the experience on a product is smooth and usable for the intended users. Someone might ask what if it is not a user interface design (because somehow, people attribute usability to only interface testing) or what if it the design has to do with process optimisation? What if it is more of an experience change that has no visual change?</p><p>Do you want to know the <strong>good news</strong>? Yes, you can still test those. You can still measure the impact of whatever design decisions you make there. It all comes down to the goals and objectives for the design as well as what metrics your team has defined for that feature. This is why it is important that key results of teams are broken down to be as simple as possible and that designers are able to contribute as to what they think the metrics for the intended design should be. Remember we talked about ROI of design? (Check out <a href="https://medium.com/design-bootcamp/roi-return-on-investment-of-ux-user-experience-3dac6333c851"><strong>ROI (Return On Investment) of UX (User Experience)</strong></a><strong> </strong>if you have not seen it). This is how you show the value of design to an organisation.</p><p>What <strong>metrics</strong> you and your team choose to use to measure the impact or results of the proposed is entirely up to all of you. However, bear in mind that those metrics should be <strong>relevant</strong> to ensure a smooth user experience based on meeting user needs as well as achieving business goals.</p><h3><strong>In summary:</strong></h3><p>The design of a version of a feature, product or service, can be considered done when there is relevant feedback on the impact of that proposed design.</p><p>If you got to this part, <strong>thank you!</strong> 🎉</p><p>And to <strong>everyone</strong> reading this, when is the design done or rather maybe the question should be when is the design <strong><em>‘good enough’</em></strong> for now? What do you think?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4260f8314068" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk feature creep]]></title>
            <link>https://medium.com/design-bootcamp/lets-talk-feature-creep-449839313825?source=rss-4ead279da0b3------2</link>
            <guid isPermaLink="false">https://medium.com/p/449839313825</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Ikenna Agu]]></dc:creator>
            <pubDate>Wed, 25 Oct 2023 00:23:24 GMT</pubDate>
            <atom:updated>2023-10-25T00:23:24.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="overview image of the topic" src="https://cdn-images-1.medium.com/max/1024/1*_igMj8GxT_WZObAu48TEVg.png" /></figure><p>Hi there, it has been a while since the last topic. Today, let us have a quick chat about features, feature creep and product thinking.</p><h4><strong>What is a feature?</strong></h4><blockquote>A feature in product development, I would say, refers to a characteristics, traits, elements or attributes of a product that deliver value to the users.</blockquote><p>If we look at streaming products like Netflix, Primevideo or DisneyPlus for example, the “Skip intro” button that usually appears at the beginning of a video is a feature of those products.</p><p>Features are relevant in product development as they help to enhance the user experience of products however, product teams should not focus entirely on features rather the focus should be on the product.</p><h4>Feature creep or featuritis</h4><p>When the main focus of development shifts from the core experience to the features of the product, there is a tendency for <strong>feature creep or featuritis</strong> which refers to an excessive addition, increase or expansion of new features in a product.</p><p>Some product teams usually do this and end up adding unnecessary features to their products that users do not need and may never use. These end up spending resources such as time, effort and brainpower in the team that could have been used to further optimise the product, its existing processes and features.</p><h4>Causes of feature creep</h4><p>Several factors can lead to the process of having an ongoing excessive amount of features. Some of these are:</p><ul><li>Users who are super enthusiastic and keep sending feature requests for elements they probably do not need.</li><li>The Business part of an organisation that feels certain features will enhance the user experience of a product without carrying proper research or spending time ideating.</li><li>Power or “key” users who have very “loud” voices (their opinions matter a lot to the organisation as they contribute significantly to the revenue generated by the organisation when compared with other users).</li><li>Designers or developers trying to “flex their technical muscles”.</li></ul><p>When the product team just accepts all requests coming from the users and the business part of the organisation, there are high chances for feature creep.</p><h4>Dealing with featuritis or feature creep</h4><p>One of the ways to effectively deal with feature creep is through <strong>product thinking and strategy. </strong>When you focus more on the <strong>core experience</strong> of a product then you can <strong>shed off unnecessary features</strong> that add no value to the users. Going back to the streaming example, the main objective of that product is for users to watch videos whenever they like. Features such as skipping the intro are used to enhance the experience however, if you take that away, as long as users are able to watch their videos without buffering, the users will still use the product.</p><p>In product thinking, you define the vision of the product, the value to users and what needs it is meeting for the users that are also positively impacting the business goals.</p><p><strong>Understanding and interpreting the right data in the right way</strong>, is also important in avoiding feature creep. This can be achieved by carrying out relevant research and analytics (qualitative such as talking to users or potential users of the product as well as quantitative through surveys and questionnaires). For digital products, there are many tools out there to assist such as powerBI, hotjar, Fullstory, Google analytics, Dovetail and so much more.</p><blockquote><strong>Always seek to understand the why and how of a product, request, feature, experience or opportunity.</strong></blockquote><figure><img alt="writing a checklist" src="https://cdn-images-1.medium.com/max/1024/0*mjtXsddbQBRctNAX" /><figcaption>Photo by <a href="https://unsplash.com/@glenncarstenspeters?utm_source=medium&amp;utm_medium=referral">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A small checklist to help resolve feature creep issues when there is a new opportunity would be:</p><ul><li>Document the product vision, goals and user needs it is solving.</li><li>Identify the core experience of the product.</li><li>List the core features needed for the product to solve the user needs while meeting the business goals</li><li>Identify the existing features and processes to see if these would work for the new opportunities rather than introducing new features.</li><li>Check what features are irrelevant to the core experience and put them away.</li></ul><h4>Why avoid feature creep?</h4><p>Minimising or avoiding feature creep will make the product feel <strong>less bloated</strong> and <strong>reduce cognitive overload</strong> (<em>this means when there is too much information to process</em>).</p><ul><li>When a product is overloaded with a lot of features, chances are that users will become confused or overwhelmed while using such products.</li><li>Also, the core features might get buried and users might forget the actual goal of that product and eventually stop using it as they are unable to solve the problem that the product was initially meant for.</li></ul><p>Another advantage to minimising or avoiding feature creep is that resources will also be directed towards more productive and impactful activities in the development and management of the product.</p><h4>Summary</h4><blockquote><em>In summary, </em><strong><em>focus more on the product strategy and thinking</em></strong><em> rather than feature thinking. As said in “corporate” terms, look at the bigger picture by thinking about the product more holistically.</em></blockquote><p><strong>These articles below also offer more insights on Feature creep:</strong></p><ul><li>Interaction Design Foundation — IxDF. (2015, July 5). Featuritis (or creeping featurism). <a href="https://www.interaction-design.org/literature/book/the-glossary-of-human-computer-interaction/featuritis-or-creeping-featurism">https://www.interaction-design.org/literature/book/the-glossary-of-human-computer-interaction/featuritis-or-creeping-featurism</a></li><li><a href="https://medium.com/u/bab76dfc19b0">Shopify</a> blog — Feature Creep: What Causes It and How to Avoid It. <a href="https://www.shopify.com/partners/blog/feature-creep">https://www.shopify.com/partners/blog/feature-creep</a></li><li>Check out this article by <a href="https://medium.com/u/af434fd67626">Ian Batterbee</a> on the <a href="https://medium.com/u/8863cbbfbca7">UX Collective Editors</a> about Feature Creep: what is it, and how does it affect the user experience. <a href="https://medium.com/user-experience-design-1/features-creepers-the-customer-experience-horror-story-124c8fa73edf">https://medium.com/user-experience-design-1/features-creepers-the-customer-experience-horror-story-124c8fa73edf</a></li><li><a href="https://medium.com/u/b90ef6212176">Jared M. Spool</a> also talks about <strong>using scenarios to fight off feature creep</strong> in this article as well. <a href="https://medium.com/@jmspool/a-fantastic-way-to-fight-feature-creep-1c3a3bad662">https://medium.com/@jmspool/a-fantastic-way-to-fight-feature-creep-1c3a3bad662</a></li></ul><p>Any thoughts on features, feature creep and how to deal with it? It would be insightful to hear about them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=449839313825" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/lets-talk-feature-creep-449839313825">Let’s talk feature creep</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[ROI (Return On Investment) of UX (User Experience)]]></title>
            <link>https://medium.com/design-bootcamp/roi-return-on-investment-of-ux-user-experience-3dac6333c851?source=rss-4ead279da0b3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dac6333c851</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-roi]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Ikenna Agu]]></dc:creator>
            <pubDate>Thu, 11 Feb 2021 09:33:40 GMT</pubDate>
            <atom:updated>2021-02-13T03:15:24.710Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPP2brW9N8taZXCPtWMk4w.png" /><figcaption>Abstract vector illustration created by vectorjuice — <a href="http://www.freepik.com/">www.freepik.com</a></figcaption></figure><p>Hi there, it has been a while. Today, let us look at the <strong>ROI of UX.</strong></p><p>First, we shall start with, what is ROI?</p><blockquote>ROI is an acronym for <strong>Return On Investment</strong>. It is a financial metric that shows the effectiveness and efficiency of an investment. It shows that investment is profitable, has value, and is a worthy one.</blockquote><p>Now we know what ROI is. Also, from previous conversations, we understand what UX (User Experience) is. But what we want to know here today is, are there case studies that show that UX design has value? How can that be calculated and translated to something that all stakeholders can understand?</p><p>So, without further ado, let us begin.</p><h3><strong>1. Does UX design have any ROI?</strong></h3><p>Yes, it does. In a world where digital transformation seems to be taking over, you will be surprised at what user experience design can do for a product.</p><p>When looking at the ROI of UX, there are some metrics we can use. Before that, let me say that sometimes the ROI of UX is not a direct financial one but could be one that deals with retention, impact, or perception. What this means is that <strong>the ROI of UX design should reflect what is valuable to the audience</strong>. It should show <strong>what positive impact it is bringing to the business.</strong> Remember from previous discussions, UX design also entails connecting business goals with user needs.</p><h3><strong>2. What UX metrics can we use for ROI conversion?</strong></h3><p>A UX metric is numerical data that gives information about the user experience of a product or service.</p><p>Some of these <strong>UX</strong> <strong>metrics</strong> are:</p><ul><li>Conversion rate</li><li>Success rate</li><li>Completion rate</li><li>Ease-of-use rating</li><li>Satisfaction rating</li><li>Error rate</li><li>Time on Task</li><li>Customer Support Tickets</li><li>Number of customer complaints</li></ul><p>There are many other metrics. We can obtain these through several methods. Some of these are Surveys, Quantitative Usability Testing, Analytics, and Customer Support.</p><p>We can convert the data from the metrics to a <strong>KPI (Key Performance Indicators)</strong> that reflects the business goals (what the organization cares about). Examples of KPIs include profit, customer retention, customer loyalty, employee productivity, and many more.</p><p>Converting those UX metrics into KPIs will give stakeholders a better understanding of the importance and value of UX because it breaks down UX to their language.</p><h3><strong>3. Are there any examples that show how we can convert UX metrics to KPIs?</strong></h3><p>Yes, there are. At the end of this writeup, I will drop links to case studies put together by <a href="https://medium.com/u/8863cbbfbca7">UX Collective Editors</a> and some by <strong>Nielsen Norman Group (NNgroup)</strong> that show clear real-life examples of UX and its ROI.</p><p>Before dropping those, let me try and show a simple example of how UX can yield good ROI using some metrics.</p><p>For example, there is a loan product that takes over two weeks to process for an individual. Now, if there are twenty customers, chances are they will not have the patience to wait two weeks for that processing resulting in the organization having ten customers booking for loans at the end of the two weeks.</p><p>After deciding to add UX design for digital transformation, the UX team designs a loan platform that reduces the turnaround time for loan booking from two weeks to two days. What happens here is, the twenty customers that apply do not have to wait a long time before getting the loan and so they won’t get impatient and leave.</p><p>The addition of UX design results in customer retention and as a loan product yields profit through increased interest as a result of increased customers.</p><p>So with a physical process without any UX design thinking, let’s say ten customers were generating a profit of 100 USD each, totaling 1000 USD. With the addition of UX design, we have twenty customers producing a gain of 100 USD each, amassing to 2000 USD, twice what the loan product was initially earning. Here was a simple example of a real-life product that a UX team that I happened to be a member, designed.</p><p>Another simple example is a decline in customer support tickets or customer complaints because of UX design. We can use this to project a reduction in the cost of customer support and bug fixes that has an indirect increase in profit through cost savings, customer satisfaction, and growth.</p><h3><strong>4. Examples of UX bringing in good ROI</strong></h3><ul><li><a href="https://www.nngroup.com/articles/testing-decreased-support/"><strong>Iterative Testing Decreased Mozilla Support Calls By 70% (nngroup.com)</strong></a><strong>: </strong>Read how User Experience design decreased support calls for Mozilla’s Support website by 70%. Quite an interesting read. You can read it on the nngroup’s webpage.</li><li>Read the article by <a href="https://medium.com/u/aeaa8759b380">Miklos Philips</a> on<strong><em> </em></strong><a href="https://medium.com/u/aa065423705f"><strong>Toptal</strong></a><strong><em> </em></strong>about<strong><em> </em></strong><a href="https://www.toptal.com/designers/ux/roi-of-ux-redesign-case-studies"><strong><em>The True ROI of UX: B2B Redesign Case Studies</em></strong></a><strong><em>. </em></strong>There are various examples of case studies involving the ROI of UX including, how yield metric nearly doubled and exceeded the desired ROI benchmark due to Prototyping and iterative testing at Bank of America. Very informative article.</li><li>This article about <a href="https://uxdesign.cc/ux-roi-i-can-prove-it-44ded1b0e25b"><strong><em>UX+ROI = I can prove it</em></strong></a> on <a href="https://medium.com/u/8863cbbfbca7">UX Collective Editors</a> shows a list of UX ROI cases that will get you convincing stakeholders. Another very informative one.</li></ul><p>Some other vital additions that can help you in calculating the ROI of UX are:</p><ul><li><a href="https://www.nngroup.com/articles/calculating-roi-design-projects/"><strong><em>Calculating ROI for Design Projects in 4 Steps by NNgroup</em></strong></a></li><li><a href="https://www.nngroup.com/articles/three-myths-roi-ux/"><strong><em>Three Myths About Calculating the ROI of UX by NNgroup</em></strong></a></li><li><a href="https://uxdesign.cc/the-true-roi-of-ux-convincing-the-executive-suite-6eed40cba79b"><strong><em>The True ROI of UX: Convincing the Executive Suite</em></strong></a> by <a href="https://medium.com/u/8863cbbfbca7">UX Collective Editors</a></li></ul><h3><strong>5. Is ROI important to UX?</strong></h3><p>In my opinion, yes, they are. ROI shows the value that UX design brings to an organization, notably those with low UX maturity. It will help to increase the UX maturity of such organizations.</p><blockquote>Also, because ROI deals with quantitative data, it is easier for stakeholders to understand and flow with it. ROI helps in building the buy-in for UX.</blockquote><p><strong>In conclusion</strong>, I hope we have seen the importance of UX, how it yields good ROI, and how ROI can be measured and presented as an estimated case for UX design in an organization.</p><p><em>What are your thoughts on this? I’d like to know in the comments.</em></p><h3>Thank you!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dac6333c851" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/roi-return-on-investment-of-ux-user-experience-3dac6333c851">ROI (Return On Investment) of UX (User Experience)</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[User Experience Design]]></title>
            <link>https://kenelight.medium.com/user-experience-design-b1ea3f1e518?source=rss-4ead279da0b3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1ea3f1e518</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ikenna Agu]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 09:33:19 GMT</pubDate>
            <atom:updated>2020-07-09T09:33:19.093Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGhLnxD2VykAsSjOaAs57A.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@picjumbo-com-55570?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">picjumbo.com</a> from <a href="https://www.pexels.com/photo/blur-cellphone-close-up-device-196646/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>Hello people, it has been a while since my first post “<a href="https://medium.com/@kenelight/design-to-me-1c40db4fba5f?source=friends_link&amp;sk=8f0bcc943d321e5f92d87dde836bd6d8"><strong>Design to me</strong></a>”. However, today, I will be talking about User Experience Design.</p><p>Hopefully, this will be a series touching several topics in UX design so I suggest you hit the follow button to get notified when new write-ups are out.</p><p>So today, I will be starting with, <strong>What is User Experience Design. (UX Design)</strong></p><p>One of the reasons for doing this is to first clarify what UX design is about because, over time, I have heard software developers and stakeholders refer to UX design as visuals, graphics and colourful. Please, that is not what UX is about.</p><p>UI which stands for User Interface is a subset of UX. (<em>With time, I will explain more</em>). So UX design is not interface design but interface design is a component of it.</p><p>So before talking about what user experience design is, let’s talk about what it is not.</p><ol><li>It is not just about pixel pushing, graphics, visuals or button placements or input field placements / effects.</li><li>It is not just a step. This means that it is a process not something you do and just conclude. Part of this reason is due to the ever changing needs of users and you keep iterating for better experience.</li><li>User Experience Design is not just about technology. It is about everything we do and the context of use hence the name user experience, that is, the experience of the user.</li><li>It is not solely about functionality, the visuals also add to the psychological and emotional side of it.</li><li>It is not just about the users or customers but also about the business and the creators of that product. It entails considering both user needs and business goals.</li></ol><p>So what exactly is User Experience Design?</p><p>Let’s start by breaking it down to the three words. User, Experience and Design.</p><ol><li><strong>User</strong> — in simple terms refers to a person who makes use of a product, process or service.</li><li><strong>Experience</strong> — refers to the observing, encountering, or undergoing of things generally as they occur in the course of time. Hence it also entails what you do and don’t do in the course of time.</li><li><strong>Design</strong> — Based on my first topic, you have a fair idea of what design is. So I see design as planning, structuring and creating innovative solutions.</li></ol><p>So, to me, <strong>user experience design</strong> has to do with <strong>creating innovative solutions</strong> that give a <strong>seamless experience</strong> to the <strong>users</strong> while meeting <strong>user needs</strong> and <strong>business goals.</strong></p><p>In a simple equation format,</p><p><strong>User experience design</strong> = user needs + business goals + frontend process / user interface + backend process and in some cases + third party support/services.</p><p>User Experience Design entails some processes or activities like</p><ul><li><strong>User research</strong> — finding out about the user needs, who the users are, how they act and react.</li><li><strong>Problem identification</strong> — identifying the problem that the product, service or process is trying to solve.</li><li><strong>Ideation</strong> — brainstorming on different ways to solve the problem already identified.</li><li><strong>Prototyping</strong> — coming up with a prototype of the solution which could be an interface, an optimised process or service.</li><li><strong>Testing</strong> — testing the usability of the prototypes to get feedback from the users for improvements.</li></ul><p>This above process is usually referred to as <strong>Design thinking</strong>. Each of these processes also have other activities under them to allow for effective user experience. (<em>This will further discussed in subsequent write-ups</em>)</p><p>Now it is good to note that the above processes are in no way linear. So a design could start with prototyping and from there, testing and then research could be carried out and so on.</p><p>To also add, a <strong>good design</strong> is usually one that is <strong>simple, seamless and satisfactory</strong>. This can also mean effective, efficient and satisfactory. It is one that minimizes the cognitive load of the user. (<em>Feel free to correct me if I am wrong</em>).</p><p>A practical example is the emergency hospital door. You hardly have to think to use that door. Why? It has no complex handles or opening system. All you have to do is just push and it gives way. It is so simple that we mostly don’t even know when we are doing it and it meets the need of an emergency hospital door since patients will be rushed in.</p><p>Another example is the toothbrush. A simple yet seamless design. You wake up in the morning, take out your toothbrush, put paste on the brush side and brush your teeth. There is hardly much brain activity while doing this. Simple, seamless and satisfactory.</p><p>So applying this to digital products also, you see that a good design with good user experience should not ideally give room for a maximised sense of effort and cognitive load.</p><p>Also, I will like to say that a good user experience design consists of three layers.</p><ul><li><strong>Visceral</strong> — the aesthetics and visuals. How the product interface appears. How appealing it is .</li><li><strong>Behavioural</strong> — the way users interact with the product which has to do with the functional part of the design also.</li><li><strong>Reflective</strong> — the conscious layer where users put thought to the product and weigh the pros and cons.</li></ul><p>Lastly for now, a good user experience design will seek to balance desirability, feasibility and viability to bring about an innovative product.</p><p>In <strong>summary</strong>, user experience design is not user interface design and it is much more than graphics, visuals, aesthetics and prototypes.</p><p>It is a continuous process that entails research, problem identification, business goals, user goals, brainstorming, user stories, personae, service design blueprint, journey maps, information architecture, ux writing, interface design, wireframes, prototyping, usability testing, frontend scripting, backend scripting/services and feedback.</p><p>More of these will be discussed in subsequent write-ups. Hope you enjoyed it. Please feel free to leave a comment on what you think about user experience design. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1ea3f1e518" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design to me]]></title>
            <link>https://kenelight.medium.com/design-to-me-1c40db4fba5f?source=rss-4ead279da0b3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c40db4fba5f</guid>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[engineering-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ikenna Agu]]></dc:creator>
            <pubDate>Sat, 16 Nov 2019 23:47:50 GMT</pubDate>
            <atom:updated>2019-11-16T23:47:50.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*swwliBypcumr_hpm" /><figcaption>Photo by <a href="https://unsplash.com/@edhoradic?utm_source=medium&amp;utm_medium=referral">Edho Pratama</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Design</strong> to me, means to create but it does not stop there. For me, I think it means to <strong>create solutions to a problem</strong>.</p><p>Now, problems are ever growing and so is design. So that is why I consider design as a <strong>continuous process of bringing out innovative solutions</strong>. It involves iterating solutions upon solutions. Looking at all forms of design, you see there is a problem being solved; whether it is architectural design, engineering design, digital product design, industrial design, graphic design, fashion design, game design, web design, user experience design and so on, there is always a solution being provided by such design.</p><p>This brings me to say that design therefore is not all about the aesthetic (visuals) but also the relevance. Now, maybe I have not built up so much experience but I have a degree in <strong>Electrical and Electronics Engineering</strong>, worked as a <strong>graphic designer</strong> and currently I am a <strong>UX designer (User Experience Designer).</strong></p><p>What I have come to realize is that, each field has a goal for solutions proffered. For example, graphic design has the goal of delivering a message to the viewer in an aesthetically pleasing way. Hence, it looks at the problem of making sure information is delivered in an engagingand exciting way to the audience type.</p><p>For Electrical and Electronics Engineering design, the little I could gather from it, is that the goal is to optimally utilize resources for the development of efficient and effective systems. It could be electrical systems or could be electronic circuits.</p><p>For User Experience design, the goal is to develop seamless solutions that are <strong>effective, efficient</strong> and provide <strong>satisfaction </strong>to the user. This can only be done after carrying out research to identify the <strong>user needs</strong>.</p><p>One thing is common in all three mentioned so far, a problem is being solved whether it is optimization, communication, information, satisfaction, efficiency, effectiveness, simplicity, clarity or whatever the problem is.</p><p>Solutions are meant to make things easier because a difficulty is most likely a problem, so <strong>design should make things easier</strong> and not cause more headache for the user.</p><h3><strong>Importance of design</strong></h3><p>Design is one of the most important factor when building a brand. If time, effort and even money is not put into it, it can, in the long run affect one’s business or product.</p><p>Your product or service design is what sets you apart. Be it the way you design an experience, optimize a system or pass information. Some other importance of design are:</p><ul><li>Brings customer and the business together</li><li>Helps to structure a solution.</li><li>Minimizes trial and error and guesses.</li><li>Improves already existing solutions.</li><li>Optimization</li><li>Satisfaction</li><li>Ease of use</li><li>Clarity</li></ul><p>Later, I will talk to a large degree on the importance and ROI of design especially in my current field, User Experience design.</p><p>This so far, is what I had in my thoughts as to what design is to me. Of course we learn everyday and the more we learn, the more we grow.</p><p>I will like to know <strong><em>what design is to you</em></strong>. Feel free to comment.</p><p>Thank you for reading, hope you enjoyed it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c40db4fba5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>