<?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 Dale Owen on Medium]]></title>
        <description><![CDATA[Stories by Dale Owen on Medium]]></description>
        <link>https://medium.com/@daleowendesign?source=rss-1b3084ba849c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*-5TR3u2kfE6WVxF9aXNGFA.jpeg</url>
            <title>Stories by Dale Owen on Medium</title>
            <link>https://medium.com/@daleowendesign?source=rss-1b3084ba849c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:02:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daleowendesign/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is object oriented UX?]]></title>
            <link>https://uxdesign.cc/what-is-object-oriented-ux-19e14c435d18?source=rss-1b3084ba849c------2</link>
            <guid isPermaLink="false">https://medium.com/p/19e14c435d18</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Dale Owen]]></dc:creator>
            <pubDate>Mon, 21 Oct 2019 18:01:01 GMT</pubDate>
            <atom:updated>2019-10-23T23:09:22.219Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Organising Objects Over Actions Can Improve UX Architecture.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TTtI3Wwo_TqwrO-S" /><figcaption>Photo by <a href="https://unsplash.com/@youxventures?utm_source=medium&amp;utm_medium=referral">You X Ventures</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>An object-oriented project approach has been a fairly recent and now staple part of developers’ and programmers’ processes for years. The model is organised around objects rather than actions, or even data rather than logic. Historically, designers have opted a natural tendency to immediately consider how the interactions of a design will function. This action-first philosophy works fine, but there are occasions where a more structured view could improve the process further, which is where an object-oriented approach to UX design in particular comes in. The model does not replace any current process, but can be included where necessary.</p><p>Typically as UX Designers, we adopt a process of defining a problem statement, a user story and later creating a high fidelity prototype. Or at least something similar. However, when dealing with complex amounts of data and complex intentions of data manipulation, sometimes defining a tree of information architecture is not enough as we have not defined meaningful connections between this data. By mapping and analysing this data ‘objectively’, we can discover these connections and potentially result in a simple and efficient user experience.</p><h3>What is Object-Oriented UX?</h3><p>The philosophy of OOUX is to encourage us as UX Designers to think about our core content as objects, and to think about this before considering any procedural actions. So before we dive straight into technical workflows and think about how the interface will function or appear, we can consider how our users will think about data as objects and align the product with a user’s mental model. Typically, users as humans think about their environment as a system of objects, and so the theory here is that if we consider the content/data within our product/project as objects, we can connect with our users better by providing a user experience that aligns with their mental model.</p><h3>What Is The History of OOUX?</h3><p>Although many of us may already be including an object-oriented approach as part of our processes, its use in UX design was not discussed as a truly useful model to apply to UX, until designer Sophia Voychehovski Prater recently proved its value in her work and later coined the term object-oriented UX in 2015. Of course we can attempt to go back further to examine earlier use of an object-oriented approach in both development and design as well, for example Dave Collins discussed its use in interaction design back in 1995. The true origins of an object-oriented philosophy can be traced back to the 70’s and 80’s when object-oriented languages became favoured over procedural ones, however the terminology was first coined in the 50&#39;s.</p><h3>How Can We Utilise OOUX?</h3><p>We can apply an OOUX approach in all of our work by considering data/content as objects before we begin to think of actions. We can achieve this from the beginning of our process, but can also be defined later to enhance your project, and can also live dynamically throughout. The model expects the use of sticky notes, with different colours to represent different components.</p><h3>Step 1</h3><p><strong>Extract Objects </strong>(Sticky note colour: BLUE)</p><p>With a problem statement defined, and perhaps even a user story defined to support it, we can examine this text to simply find the nouns. Recognising the nouns that will become objects is quite tactful, with special care to be taken to avoid using nouns that may be better defined as perhaps an organisation or grouping method. Some objects may also be generated as a result of requirements stated in a problem statement or user story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*chLg1VWfnbK6iRQJquOZtQ.png" /></figure><h3>Step 2</h3><p><strong>Define Core Content of Objects</strong> (Sticky note colour: YELLOW/ORANGE)</p><p>Next, the more detailed content expected to be contained with each recognised object needs to be defined. For example, if one of our objects was called ‘Shoe’, some of the core content could include things like Description or Size. These can sit directly beneath the objects. We can also go a little deeper here and define more metadata-like content that can be filtered or sorted, such as the shoe’s Target Market or Stores That Sell This. We can label these are a little differently but nest them underneath the core content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*MxeG_pWsstHFnDcaBigpLA.png" /></figure><h3>Step 3</h3><p><strong>Nest Cross-Linked Objects</strong> (Sticky note colour: BLUE)</p><p>At this point we can include objects that may have some relationship to the primary object at hand. This could mean displaying an alternate version of an already pre defined object, or be a more detailed type of object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*7otfzKKM7_2X4Ukyxt10BQ.png" /></figure><h3>Step 4</h3><p><strong>Forced Ranking</strong></p><p>Now that everything is in place, we can rearrange the order of all items beneath each primary object by most to least important. This process may take some time and could also be reviewed for frequent iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*hh5_FMmbaIsLUlF3SBOpig.png" /></figure><h3>Step 5 Optional</h3><p><strong>Add CTA’s</strong>(Sticky note colour: GREEN)</p><p>This step was introduced more recently as a way of transitioning from an object-oriented process to an action-oriented process. We can add in specific actions such as those that may be expected in a primary interaction within that object’s experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*5tWGUI__SNqKNeeIBcR59w.png" /></figure><p>The end result is an object based system that can drive and motivate our projects by having data/content defined and understood in regards to their importance, and in line with a user’s mental model. The process above may not be evidently clear without examples, so take a look at some of the learning resources below to see the process in action.</p><h3>What Are The Benefits Of Using OOUX?</h3><p><strong>An object-first approach improves the communication and collaboration between UX and the rest of the engineering team</strong>. Since developers and programmers are familiar and likely already utilise this approach, we can therefore speak the same language and build more efficient relationships with them. This will make it easier to explain our work and our reasonings.</p><p><strong>Defining objects for later use/reuse saves time</strong>. By defining content by objects at the beginning of the project, allows quicker and easier reference and usage at later parts of the project.</p><p><strong>The consideration of user mental models supports a better UX</strong>. Since OOUX is built on representing the mental model of our users, we are ensuring that our work is aligned with how the user is thinking.</p><p><strong>Unexpected complexities are minimised</strong>. When objects are defined at the beginning of the process, there’s a good chance a later addition has already been defined, allowing smoother iterations.</p><p><strong>Adaptable and responsive compatible</strong>. If and when the product needs to be displayed on a device other than desktop, an object-oriented design system can be easily modified to adapt to this, or even used without change as a foundation.</p><p><strong>Relationships can be visualised</strong>. It’s easy to forget to include or reference another part of our product within a designed experience, but OOUX allows us to map out these relationships before hand and visually see how everything could connect.</p><p><strong>The activity can help create organisation amongst chaos within content.</strong> If there’s lots of data/content that is scattered or doesn’t make sense, applying an OOUX approach assists in organising this and encourages understanding of the content itself.</p><h3>What Are Some Good OOUX Learning Resources?</h3><p>Object-oriented UX is often mentioned in more recent courses, books and articles discussing methods of user experience. However here are some stand-out picks:</p><h4>Object Oriented UX</h4><p><a href="https://alistapart.com/article/object-oriented-ux">https://alistapart.com/article/object-oriented-ux</a></p><p>Prater’s article on how she first introduced OOUX (and effectively coined the terminology by adding ‘UX’ at the end!) into her projects is one of the most well known and insightful articles on the process. She goes into detail on how the model helped her and how to apply it yourself in detail too.</p><h4>OOUX: A Foundation for Interaction Design</h4><p><a href="https://alistapart.com/article/ooux-a-foundation-for-interaction-design">https://alistapart.com/article/ooux-a-foundation-for-interaction-design</a></p><p>Following from Prater’s article above, this one discusses how and why she decided to integrate CTA’s into the model afterwards and how you can use them too.</p><h4>A Daring Tool For a Traditionally Analog Audience</h4><p><a href="https://uxdesign.cc/a-daring-digital-tool-for-a-traditionally-analog-audience-ed700875e4c8">https://uxdesign.cc/a-daring-digital-tool-for-a-traditionally-analog-audience-ed700875e4c8</a></p><p>This recent article shows how a software company utilised the model in their work in detail.</p><h4>Crosslinked: A UX Storytelling System Design Game</h4><p><a href="https://www.thegamecrafter.com/games/crosslinked-a-ux-storytelling-system-design-game">https://www.thegamecrafter.com/games/crosslinked-a-ux-storytelling-system-design-game</a></p><p>If you want to have a bit of fun learning and practicing OOUX, this physical card-based game looks worth a try!</p><h3>Final Thoughts</h3><p>Object-oriented UX is not a rule, nor does it contain specific rules to adhere by, in fact it can be manipulated to suit the needs of your project. There may also be reasons not to use it, perhaps a project’s priority is within its actions rather than content, or the content has already been defined previously. The principle of considering actions is still important to align with user needs, however an initial OOUX exercise can also align with closely with user mental models, supporting better decisions when considering actions. Where possible, give it a try to see if it can support your project.</p><h3>References</h3><p>Prater, S. (2019). <em>Object-Oriented UX</em>. [online] <a href="http://alistapart.com/">Alistapart.com</a>. Available at: <a href="https://alistapart.com/article/object-oriented-ux">https://alistapart.com/article/object-oriented-ux</a> [Accessed 13 Feb. 2019].</p><p>Prater, S. (2019). <em>OOUX: A Foundation for Interaction Design</em>. [online] A List Apart. Available at: <a href="https://alistapart.com/article/ooux-a-foundation-for-interaction-design">https://alistapart.com/article/ooux-a-foundation-for-interaction-design</a> [Accessed 13 Feb. 2019].</p><p>zipBoard. (2019). <em>Understanding Object Oriented UX: Interview with Sophia V Prater</em>. [online] Available at: <a href="https://blog.zipboard.co/understanding-object-oriented-ux-interview-with-sophia-v-prater-4df6f422e484">https://blog.zipboard.co/understanding-object-oriented-ux-interview-with-sophia-v-prater-4df6f422e484</a> [Accessed 13 Feb. 2019].</p><p>Collins, D. (1995). <em>Designing object-oriented user interfaces</em>. Redwood City, CA: Benjamin Cummings.</p><p>Medium. (2019). <em>Chapter 3: What is Object-Oriented Programming? — Learn How To Program — Medium</em>. [online] Available at: <a href="https://medium.com/learn-how-to-program/chapter-3-what-is-object-oriented-programming-d0a6ec0a7615">https://medium.com/learn-how-to-program/chapter-3-what-is-object-oriented-programming-d0a6ec0a7615</a> [Accessed 13 Feb. 2019].</p><p><a href="http://web.eecs.utk.edu/">Web.eecs.utk.edu</a>. (2019). [online] Available at: <a href="http://web.eecs.utk.edu/~huangj/CS302S04/notes/oo-intro.html">http://web.eecs.utk.edu/~huangj/CS302S04/notes/oo-intro.html</a> [Accessed 13 Feb. 2019].</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19e14c435d18" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-is-object-oriented-ux-19e14c435d18">What is object oriented UX?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experiential Learning: learning by doing (UX)]]></title>
            <link>https://uxdesign.cc/experiential-learning-learning-by-doing-a374d2a673a4?source=rss-1b3084ba849c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a374d2a673a4</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Dale Owen]]></dc:creator>
            <pubDate>Thu, 17 Oct 2019 18:01:01 GMT</pubDate>
            <atom:updated>2019-10-28T23:39:17.044Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YLrCK0vJDVeRMqvh" /><figcaption>Photo by <a href="https://unsplash.com/@eseamau?utm_source=medium&amp;utm_medium=referral">Amaury Salas</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We are all no strangers to experiential learning; ie <strong>learning by doing</strong>. To put it simply, <strong>we learn from experience</strong>. In fact, Aristotle himself suggested that we learn by doing back in 350 BCE¹. We’re also no strangers to the term ‘practice makes perfect’, suggesting that the more we practise something, the better we get at it. Experiential learning has been used throughout education and business as a core learning methodology, but also arguably naturally in our everyday lives. We should consider experiential learning as a <strong>holistic integrative methodology</strong> that can be considered as a foundation or part of how our users’ minds work when designing a digital product².</p><p>To understand experiential learning at a deep learning, we can look at how the creation of memory works. With this in mind, we can agree that the aim of experiential learning is to eventually create long term memories that can be recalled with ease.</p><p>There are several studied models of the experiential learning process, with particular note from psychologists and philosophers Dewey, Lewin and Piaget. All of which generally conclude that <strong>learning is best conceived as a process</strong>, not in terms of outcomes, <strong>a continued process grounded in experience</strong>, is <strong>dependent on our mental models</strong> and <strong>involves some form of interaction</strong>².</p><blockquote>Learning is the process whereby knowledge is created through the transformation of experience</blockquote><blockquote><em>Kolb</em></blockquote><p>Kolb more recently conceptualised the experiential learning process into a <strong>4-stage cycle</strong> as shown below with concern toward internal cognitive processes³. The cycle describes the process involved from gaining new experience, reflecting on existing experience, creating or iterating a mental model and applying practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*Dzo7lzipDUBCDzALK-PsWg.png" /><figcaption><em>Kolb’s experiential learning cycle³.</em></figcaption></figure><p>Experiential learning can benefit users by facilitating growth of knowledge, assist adaption to change, take account of an individual’s learning ability and responds to their needs⁴. Since it is more of an <strong>active</strong> than passive process, it is a relatively <strong>personal</strong> way of learning. However, this suggests some <strong>motivation or desire to learn</strong>, which is why this learning method should be viewed <strong>holistically</strong> and perhaps alongside a combination of other methods. In our product, we can facilitate with an access to model to help and support.</p><p>However, as designers we can also <strong>guide and encourage</strong> the user towards experiential learning. For example, we can provide a <strong>foundation</strong> or environment of the task ahead. In UI, this could mean presenting the user with an interface, ie layout the core elements that will be utilised in the task ahead. In this case, we are providing some <strong>knowledge of the learning task</strong>. From here, the user can determine the <strong>possibilities</strong> and compare to their <strong>existing mental models</strong> in preparation of updating or creating a <strong>new model</strong>; promoting <strong>order from chaos</strong>. And eventually creating a <strong>long term accessible memory</strong>. This existing mental model could be a <strong>familiar</strong> or <strong>consistently</strong> designed interface when iterations have been made. But this also suggests that straying away from consistency and leaning towards new/intuitive interfaces could put additional strain on one’s experiential learning capacities⁵.</p><p>This method can be proven in a recent study by Professor Viljo Kohonen, who studied experiential learning in foreign language education⁴. He compared learning a language to the metaphor of requiring a topographic map when orienteering in an unfamiliar place; the map equips them some prior knowledge to make sense of the terrain ahead properly. Also, in the case of language learning, one can loosely compare the foundations of the new language to the knowledge they already have from their own native or previously learned languages. Thus facilitating order from chaos.</p><p>To summarise, we can consider experiential learning, ie learning by doing, when users interact with our products. If we understand that users can <strong>learn effectively by actively interacting</strong> with our interfaces, we can produce designs that can be utilised successfully by all via <strong>recall of created long term memories</strong>.</p><h3>References</h3><ol><li>Aristotle. and Rackham, H. (1999). The Nicomachean ethics. Cambridge, Mass.: Harvard Univ. Press [u.a.].</li><li>Kolb, D. A. (1984). Experiential learning: experience as the source of learning and development. Prentice Hall.</li><li>Kolb, D. A., &amp; Fry, R. E. (1974). Toward an applied theory of experiential learning. MIT Alfred P. Sloan School of Management.</li><li>Kohonen, V., Jaatinen, R., Kaikkonen, P. and Lehtovaara, J. (2001). Experiential Learning in Foreign Language Education. Longman.</li><li>Nielsen Norman Group. (2018). The Power Law of Learning: Consistency vs. Innovation in User Interfaces. [online] Available at: <a href="https://www.nngroup.com/articles/power-law-learning/">https://www.nngroup.com/articles/power-law-learning/</a></li></ol><h3>Further Reading</h3><p>Experiential Learning Enhancing User Interface Design Skills through Cognitive Action <a href="https://ieeexplore.ieee.org/document/8049111?denied=">https://ieeexplore.ieee.org/document/8049111?denied=</a></p><p>Best Practices In Experiential Learning <a href="https://www.ryerson.ca/content/dam/lt/resources/handouts/ExperientialLearningReport.pdf">https://www.ryerson.ca/content/dam/lt/resources/handouts/ExperientialLearningReport.pdf</a></p><p>The concept of experiential learning and John Dewey’s theory of reflective thought and action <a href="https://www.tandfonline.com/doi/pdf/10.1080/026013700293458">https://www.tandfonline.com/doi/pdf/10.1080/026013700293458</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a374d2a673a4" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/experiential-learning-learning-by-doing-a374d2a673a4">Experiential Learning: learning by doing (UX)</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Progressive reduction: a brief UX study]]></title>
            <link>https://uxdesign.cc/progressive-reduction-a-brief-ux-study-474a6e0a2c05?source=rss-1b3084ba849c------2</link>
            <guid isPermaLink="false">https://medium.com/p/474a6e0a2c05</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Dale Owen]]></dc:creator>
            <pubDate>Wed, 16 Oct 2019 18:01:01 GMT</pubDate>
            <atom:updated>2019-10-25T00:12:31.530Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1di8vSdcmzw2KPyC" /><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>Introduction</h3><p>A recent exploration on Progressive Disclosure, a means of offering users content/data in increments, provoked its value in the UX of a web application I was recently building with a team of other designers. The subsequently studied Progressive Reduction theory also suggested that it could also potentially offer value to our product as well. This article aims to explore Progressive Reduction in further detail to realise any potential value.</p><p>After the flat design era¹ made its mark on user experience, along with the increasing understanding and concern for usability, the need to minimise as a method to improve usability has become more prevalent. A recent methodology to achieve this is progressive reduction which aims to dynamically adapt a UI to the user’s experience and understanding, ie the UI changes in response to the user’s perceived behaviour. As Alan Grinshtein at Layervault originally described; usability is a moving target². The method is fairly new and is often recognised as being rarely used, however its visibility is not always clear and easily missed on analysis. This article attempts to briefly explore its benefits, what it can teach us, as well as the challenges in its implementation.</p><h3>Background</h3><p>The aim of progressive reduction is not just to minimise for clarity and simplicity, which is more inline with the aims of flat design, but to assist the user in learning to utilise a UI with efficiency, resulting in a personalised experience that not just minimises for the masses, but minimises depending on the user’s individual experience. Since users have individual traits, we could argue that this method can actively adapt to the user, satisfying users more effectively, potentially reducing cognitive effort for at least some users. All of this with the reduced need to hand hold the user.</p><p>The concept of progressive reduction was introduced by Grinshtein². After some analysed mistakes made by over-minimising with consequences, it seems that his studio made an effort to find a solution. They noticed that as designers they tended to produce a bias towards the pro user as they spent more time with a product or feature. As a result of this understanding, they realised that they hadn’t technically been biasing the UI towards one type of user, but actually failing to realise that the user’s bias is changing. In other words, as a user continues to interact with an interface, they actively learn and develop experience. Since each user has different traits, including different usage experience, this suggests that users traits to consider will actively change, possibly invalidating any original user research. We could identify this as a dynamic persona as a result of experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f2aGsswfO3vkVUiU" /><figcaption>Photo by <a href="https://unsplash.com/@easiblu?utm_source=medium&amp;utm_medium=referral">Eftakher Alam</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Progressive reduction actually exists, and has done for some time, in many other mediums. For example, logo designs evolve into simpler forms over time once they become recognisable, even in writing when one tries to convey a message by reducing the amount of text once readers have understood the concepts. Designer Stephanie Oh says progressive reduction is actually everywhere³, and that the need to include it in UX is only human. She describes it as ‘the elegant process of encapsulating the same amount of meaning and function in an ever-simpler vessel.’</p><h3>Why is it useful?</h3><p>The outcome of progressive reduction implemented in an interface is a simpler, cleaner UI. This was proven by the minimalist movement in digital design. It has become known that users prefer a minimal interface for several reasons, mostly now because it has become an expected design standard, but has foundational reasons in being easier to understand and comprehend than more complex interfaces, effectively providing a better UX. For example, progressive reduction can promote a cleaner, simpler UI that has become saturated with action buttons. This saturation may provoke distraction and accommodate a significant amount of design real estate in a layout where content should be the primary focus. The reductive method can promote focus on content by minimising the design of action buttons and also allow more valuable space to be utilised, as the user becomes more proficient and is able to subconsciously recognise actions with minimal or non additional effort.</p><h3>How is it implemented?</h3><p>Grinshtein’s original implemented concept involved dynamically changing the UI that an individual interacts with within features that they have used often. The usage and behaviour is tracked in the back end to achieve this, while the UI adapts accordingly. There are also several stages of dynamism, with the UI gradually becoming more minimal as the back end detects its usage increases. Variations within the design include labels, size, contrast and colour. A proficiency profile is built for every user which gives the product behaviour the opportunity to gradually step away from any hand holding when they believe they become an ‘expert’. However this expertise is likely simply based on usage counts only. This is interesting as it suggests that it also provokes a positive emotional response to the product, therefore further improving the experience for that user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3MwfsyeKZZRkOB7m" /><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>He also believes that users’ experience decays after a period of non-usage, and that a gentle reminder will help. As such, in an almost reverse behaviour, the UI regresses backwards at least one step, ie the UI changes to an earlier state when the user was determined less experienced, to promote their recall of how the feature or product works. Ultimately, this balances the progressive reduction method based on experience by considering both an increase and a decrease in proficiency.</p><p>There has also been discussion in regards to developing its use further by not just simplifying the interface, encouraging certain features that may be suitable or hide those that may not. However, experience determined by usage counts may not be as valid in these situations. In fact this may even cause ‘experience rot’ which describes the frustration manifested by the user when a feature is no longer where it was before.</p><h3>How can we prove that this works?</h3><p>Although Grinshtein²,⁵ made some interesting observations, much of which are likely based on the studio’s own user research, no evidence was actually given, whether this be in-house research or scientific findings. However, we don’t need to delve too deep to provide proof of why this should work effectively by studying how human memory works. This includes how we develop memories as part of our learning abilities, as well as how we can recall them. The evidence also lies in the concept of rote learning, ie memorising based on repetition. It could be argued that progressive reduction on loosely based on this concept, as when we repeat a task multiple times, it has a higher chance of being stored as a long term memory that can be recalled easily. As it becomes easier to recall, there is suggestion that we are able to recognise a task without viewing its complete original context. Since the elements of the task should all still be within the same workflow, the user should be able to recall the task with ease, almost subconsciously, since the associations that make up the neural pattern of the memory are still connected.</p><h3>What are the challenges?</h3><p>As mentioned previously, there is a potential ‘experience rot’ issue that could manifest here⁴. This would be a case where the user responds negatively, consciously or subconsciously, to a dynamically changing interface, since the UX has changed and become unfamiliar to their standardised and expected workflow. It also assumes that all users will respond positively and naturally to a dynamically changing interface based on usage and behaviour. Depending on the detail of the algorithms used to determine this, this could assume homogenous traits between users, when actually users needs may be heterogenous; one user (and their persona) may not have the same traits as another user, and therefore their response may be different. For example, if the button in an interface simplifies via recession, perhaps a text label is removed from a button after significant usage, two users may respond differently. User A may respond well to this as they perceive visuals better than text, while user B responds better to text. User B may react negatively to this as their reliance on textual data as their indicator of UI actions has been removed, and therefore may even be considered broken. This also could present accessibility issues by determining that all users understand colours and shapes in the same way.</p><p>Progressive reduction should be used with caution. If the UI is not dynamically designed with optimal user consideration, it could result in a negative response; the user could become frustrated that the interface has changed, and therefore produce a negative emotional response to it⁶. This falls in line with the peak end rule theory⁷. Designing with attention to detail around the important moments of the customer journey can help prevent this.</p><p>Considering the detail of implementation required, this could become a struggle on the back end to determine appropriate algorithms. This may also be difficult to maintain, as when design changes are made, the algorithms may need to be updated too. Documentation will also need to be updated, but may also become an issue if users are not aware of the dynamic changes, particularly when consuming documentation, since readers will seek to find an interface that is explicitly the same as what is described. If documentation describes an interface with a particular shape or button, but the actual live product displays something different, this may become confusing, disrupting the legitimacy and value of the documentation itself. However again, this can also be managed with effective documentation that aligns with and progressively reduced elements.</p><h3>Can we implement this in our product?</h3><p>Progressive Reduction has been utilised in examples where the user is expected to perform a repeated or monotonous action. Therefore this could work in a product where the same isolated action is performed on a regular basis. This could be as simple as dynamically changing a button’s appearance as the user seems to become more familiar with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*JhXkYih6DaQeG6KhtBDBYw.png" /></figure><p>The example above shows how a Configure button within a dashboard card element could eventually adapt to the user’s usage, and ‘reduce’ to a much smaller button with simply an icon to suggest ‘configure’ instead of a text label. The user is expected to understand that the button’s action is identical to that of its predecessor appearance since it is in the exact same position, utilises the same colours and includes an icon that suggests ‘configure’ rather than explicitly state ‘configure’ in text. On initial presentation, many users may still need to take a brief moment to think about the button, but is expected to understand due to this context, and based on the theories mentioned above. If implemented effectively, many users are expected to even be change blind to these dynamics, relying on muscle memory and automatic reflex to guide their actions. Users are presented with a simpler interface where actions take less screen real estate, create less distraction and allow more focus on content.</p><p>In the long term, the design experience can be progressively reduced as a large user base is built and there are significantly more current users than new users. This would be less of a dynamic reduction that adapts, but one that is purposely overhauled, or at least iterated, to gradually ‘reduce’ the design into a minimal layout that is simpler, easier to use and familiar. Since the primary user base now understand how particular actions work, including their position both physically in design and within their workflow, the visual design can be reduced with minimal or no consequence. This could mean permanently reducing all action buttons, text descriptions, titles, etc by minimising their appearance or removing them, since the user will be expected to understand how the interface works anyway. It could only work over a long period of time and should be based on strong gathered user research.</p><p>However, a more permanent progressive reduction can be seen as less of a dynamic process, and simply that of a long term iterative progression into a minimal interface. But the principles behind it remain the same.</p><h3>Conclusion</h3><p>The method of progressive reduction has created a buzz in the UX industry over the years, however it has not been adopted across many interfaces as yet. It would be useful to see true results from any interface that has already utilised this method to see true proof on how this works. However, the concept remains interesting and a possible consideration for use within a complex product experience; one that could potentially improve the UX.</p><p>But is this just a novel UX methodology? Is it necessary? That depends on whether there is strong enough in-house evidence that it would benefit the UX, suggesting that this is a method that would only suit a small number of use cases. This study has proven that progressive reduction could be implemented in a small number of cases where an action is regularly repeated over a long period of time, and there is a need to provide substantially more focus on content and/or there is a design need to have access to currently accommodated content in favour of content over actions.</p><p>While there is some evidence that this will work, it should be used with caution, and be backed up with internal research and study to prove its use. When utilised effectively, it seems that the overall UX could be positively improved, and possibly even recognised as a marvel UX method in the industry.</p><h3>References</h3><ol><li><a href="https://www.nngroup.com/articles/flat-design/">https://www.nngroup.com/articles/flat-design/</a></li><li><a href="https://layervault.tumblr.com/post/42361566927/progressive-reduction">https://layervault.tumblr.com/post/42361566927/progressive-reduction</a></li><li><a href="https://medium.com/@stephaniehoh/progressive-reduction-is-everywhere-79c736f17cca">https://medium.com/@stephaniehoh/progressive-reduction-is-everywhere-79c736f17cca</a></li><li><a href="https://www.dtelepathy.com/blog/design/progressive-reduction-evolving-the-experience-for-your-most-frequent-users">https://www.dtelepathy.com/blog/design/progressive-reduction-evolving-the-experience-for-your-most-frequent-users</a></li><li><a href="https://layervault.tumblr.com/post/42442865260/implementing-progressive-reduction">https://layervault.tumblr.com/post/42442865260/implementing-progressive-reduction</a></li><li><a href="https://www.invisionapp.com/inside-design/the-challenges-with-progressive-reduction/">https://www.invisionapp.com/inside-design/the-challenges-with-progressive-reduction/</a></li><li><a href="https://www.nngroup.com/articles/peak-end-rule/">https://www.nngroup.com/articles/peak-end-rule/</a></li><li><a href="https://alistapart.com/blog/post/progressive-reductionmodify-your-ui-over-time/">https://alistapart.com/blog/post/progressive-reductionmodify-your-ui-over-time/</a></li><li><a href="https://www.fastcompany.com/3008419/first-time-user-experience-what-developers-need-know">https://www.fastcompany.com/3008419/first-time-user-experience-what-developers-need-know</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=474a6e0a2c05" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/progressive-reduction-a-brief-ux-study-474a6e0a2c05">Progressive reduction: a brief UX study</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing with memory in mind]]></title>
            <link>https://uxdesign.cc/designing-with-memory-in-mind-f109c15f12ff?source=rss-1b3084ba849c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f109c15f12ff</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Dale Owen]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 16:35:32 GMT</pubDate>
            <atom:updated>2019-10-26T12:56:44.781Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Neuron" src="https://cdn-images-1.medium.com/max/1024/0*rZIAxeptGmyROhns" /><figcaption>Photo by <a href="https://unsplash.com/@joshriemer?utm_source=medium&amp;utm_medium=referral">Josh Riemer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>While there are many human mechanisms used to determine our interactions with the outside world, one of the most important is <strong>memory</strong>. Without memory, we could not determine, process or recognise the elements of our surroundings. This information processor is of continuous study, and a vital consideration not just within the tangible world, but within any digital user experience. However, memory isn’t as straightforward as one may perceive, in fact its arguably complex, and impacted by our surroundings. This article will discuss human memory, as well as its <strong>importance and benefits within user experience design</strong>.</p><blockquote><em>Memory is deceptive because it is colored by today’s events</em></blockquote><blockquote>Albert Einstein</blockquote><h4>Human Memory</h4><p>So how does it work? At its most basic level, memory is <strong>the storage of data we collect from our surroundings</strong>. However data is not simply and indefinitely stored, in fact data can be processed in different ways and influenced by many factors. Studies have shown that there are 2 primary types of human memory; <strong>long term memory</strong> and <strong>short term memory</strong>. We can also consider more specific memory types including sensory and working memory, however our utility within UX systems can be simplified by focusing our understanding on LTM and STM¹.</p><p>A recent psychological study which appropriates existing study and evidence on human memory describes short term memory as data stored in our minds temporarily, which may be <strong>accessed consciously or unconsciously</strong>, and stored without repetition². However, there have also been significant studies to suggest that the human mind can only store an <strong>approximate amount of data</strong>, and only hold this data for an <strong>approximate amount of time</strong>. Whereas long term memory can be described as data that is stored for <strong>longer periods of time</strong>, possibly even indefinitely. However the full capacity of our brains has not quite been fully identified. To describe in detail, data is stored as a <strong>pattern of neurons</strong>. The stronger the neuron’s imprint, the stronger its existence in our memory. A key method to increase this strength is repetition. We can reactivate or recall a LTM by stimulating neurons in the same pattern as when the memory was formed. In comparison, most STM’s are forgotten³.</p><p>Despite several studies, there has been <strong>little confirmed deep scientific proof</strong> of the exact mechanisms involved in memory. However, neurobiologist Eric Kandel believes that the existence and methods of storing data in both short term and long term lies at a <strong>chemical level</strong>⁴. In 2012, Kandel conducted a study that revealed the existence of a competition between two agents to throw a ‘switch’ in the brain, a switch that allows a memory to <strong>convert from STM to LTM</strong>. To define, an agent named CREB-1 attempts the conversion, but CREB-2 attempts to prevent it, forming a balance. With enough repetition or definition, CREB-1 is able to bypass CREB-2 to create a LTM. Kandel also found that emotions were involved in the competition and balance between the agents, proving that emotions can affect memory at a neurological level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CUeIAYdabJw4AM-3" /><figcaption>Photo by <a href="https://unsplash.com/@averey?utm_source=medium&amp;utm_medium=referral">Robina Weermeijer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Memory has been considered as a crucial component of the modern computer⁵. We can even loosely compare computer memory to human memory; STM — RAM, LTM — Storage. Our access to this memory was previously restricted to command lines and physical keyboard input, with a gradual progression towards digital GUI systems. These interfaces ease our cognitive load, reduce learning and allow less errors or mistakes to be made. With the development of VR interfaces more recently for example, we are lesser required to think about our steps and decisions. With this comparison, we can further understand the importance of memory consideration in UX design.</p><p>When we consider the flow of data from its initial perception to either a STM or LTM, we can strengthen our own UX workflows, consequently creating a product that promotes <strong>optimum ease of use</strong>. Our priority to design for STM or LTM can depend on the context of the interface. It would be ideal if users could store as a LTM, however, it could be argued that <strong>creating a LTM requires significant cognition</strong>⁶, maybe even resulting errors. Therefore, designing for a STM could promote an <strong>easier and quicker experience</strong>, particularly if data does not need to be effectively remembered. Given our understanding of how memory works, we can anticipate that if a STM is repeated, it will eventually become a LTM. When we create our designs, perhaps we should actively consider whether our aim is for users to store data in their minds as a STM or LTM, and consider the conversion of a STM into a LTM, therefore <strong>minimising cognition</strong> as much as possible.</p><h3>Principles</h3><p>There are several principles within interface design that allows us to <strong>ethically manipulate memory</strong>, and our utility of these principles can determine the possibility of the memory’s term. There are two important and proven principles to consider within the psychology of UX design.</p><h4><strong>Miller’s Law</strong></h4><p>In 1956, cognitive psychologist George Miller released a study that would become of the most cited papers in psychology; <em>The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information</em>³<em>. </em>The study analysed our memory capacities and limits, particular in short-term memory, and created a conclusion that the average human can hold about <strong>seven objects or chunks of data, give or take two (7 ± 2)</strong> during a task that requires cognitive effort, hence the term <strong>‘chunking’</strong>. Miller suggests that we consider data in forms of ‘chunks’, and limit the amount of data displayed to accommodate our STM storage capacity optimally, <strong>without overloading cognition</strong>, which could consequently result in a <strong>failure of data storage</strong>.</p><p>It is important to understand that this guideline amount of data is for memory recognition and processing, and <strong>not for recall</strong>. It has been reported that many designers misinterpreted Miller’s findings by strictly displaying 7 ± 2 chunks of data; for example, seven interactive items in a navigation menu⁷. Miller later responded to this misinterpretation to clarify his theory.</p><p>Miller also made several other discoveries, including the <strong>primacy and recency effect</strong> phenomenon, also named the serial position effect, which describes the importance of the <strong>order of these chunks of data</strong>⁸. He concluded that data chunks at the beginning or end of an experience have a stronger likelihood of being stored effectively, lesser for data presented mid-experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-IgIryhAj1L-Ixj3" /><figcaption>Photo by <a href="https://unsplash.com/@pietrozj?utm_source=medium&amp;utm_medium=referral">Pietro Jeng</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>More recent studies have also concluded that the context or nature of the data can also affect the suggested numerical limit. Richard Shiffrin and Robert Nosofsky discovered that while numerical digits can be held on average in a quantity of seven, the number is reduced to six for letters, and five for words; suggesting that we are able to store more digits as a STM than letters, and even less when we combine letters into words⁹.</p><p>As discussed in Miller’s law theory, we process data in our minds in ‘chunks’. We can reflect this ability in design to promote processing of these chunks, effectively creating a set of data to imprint in the user’s mind. In design we can achieve this by <strong>breaking up content</strong> into digestible chunks to allow more effective processing. In psychology, a chunk is described as an <strong>‘organisational unit in memory’</strong>¹⁰.</p><p>This memorisation technique can be applied in our designs by dividing information into clearly distinct <strong>groups of related content</strong>. For example, chunking text content into digestible paragraphs, shortening lines of text, grouping visually related items together or even simply grouping strings of digits or letters.</p><p>A specific example in online design is separating articles with short paragraphs and separating imagery. Remembering to group content visually, as per <strong>Gestalt Law of Proximity</strong>, to help identify related content¹¹. Another specific and common method is used to display telephone numbers. Since a long number can be difficult to remember, displaying the number in separated chunks allows for more efficient memory storage.</p><p>Miller’s law, and its consequent findings should always be considered within experience design, promoting a product that compliments user memory capacities and capabilities. We can achieve this by paying attention to the <strong>amount of data</strong> we display, the <strong>type of data</strong> and the <strong>positioning or order of that data</strong>.</p><h4><strong>Hick’s Law</strong></h4><p>We have defined that our short-term memory has limitations in processing data, particularly in regards to the amount of data. Psychologists William Edmund Hick and Ray Hyman found in 1952 that the <strong>time taken</strong> to make a decision increases with the number of choices offered, and the complexity of those choices¹². Therefore we must also factor in time taken in addition to the amount of data presented, as well as context.</p><p>It was determined that <strong>the more choices offered, the longer it takes for us to think</strong> and comprehend these choices, therefore making it difficult to make a decision. These decisions become more difficult as more choices are offered, increasing <strong>cognitive pressure</strong>, consequently resulting in <strong>poor decision making</strong> or <strong>failure to make a decision</strong>; a negative experience. As we consider each choice, option or chunk of data, the way we process these can be individual and unpredictable; our minds associate, become distracted and trail off, almost to a fan-effect. This can result in <strong>memory overload</strong> as we process significant information outside the choices offered, and possibly failing to store data for the appropriate amount of time, ie as a STM, or even LTM.</p><p>We can determine from Hick’s law that we should aim as UX designers to present <strong>only the most necessary information</strong> where possible without overwhelming, as this can interfere with efficient memory storage. We should remember that users will struggle or fail to process data and/or convert to an appropriate memory type if we provide too much data at one time. There will be occasions where we must present a high volume of data, and we can prevent cognitive overload by using design methods that still give us access to this data, but via <strong>intuitive design</strong>.</p><h3>Methods</h3><p>With our understanding of the science behind how human memory works, particularly in interface design, as well as some of the foundation theories gathered, we can determine some specific design principles and methods to include in our designs. Of course these are not strict guidelines and must be used with caution, with memory understanding in mind, and with clarified understanding of the purpose, as well as context.</p><p>A key consideration to bear in mind is that we should primarily, but <strong>not strictly aim to design for the short-term memory</strong>. If we want our users to store data long-term, we must remember that this is achieved by converting a STM to a LTM.</p><p>As well as the above considerations and methods, other ways to positively work with human memory in UX include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mEzpTE5_LeZF9K5o" /><figcaption>Photo by <a href="https://unsplash.com/@sabrituzcu?utm_source=medium&amp;utm_medium=referral">Sabri Tuzcu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Optimise Response Times</strong></h4><p>It has been proven that a <strong>slower experience</strong> results in<strong> poor memory performance</strong>. As digital interfaces developed and the performance speed increased, William Doherty noticed an improved experience. He put this theory to the test in 1979 within a study, of which he discovered that the longer it would take for the computer to respond, the longer the user took to think about the next step. Even milliseconds made a significant difference¹³.</p><p>Doherty believed that users were storing the series of steps they wanted to take in working memory, and the<strong> long response times</strong> interrupted their train of thought, <strong>preventing the storage</strong> of that data. This resulted in a decrease in productivity and possibly cause errors.</p><p>Aside from any technical ways to reduce response times, any designed experience should consider potential time taken for a goal to be achieved. This could be simple waiting times or steps between start to finish. Either may <strong>disrupt the user’s goals</strong> by causing a failure to create a clear memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZYiktSQMSAan5FCk" /><figcaption>Photo by <a href="https://unsplash.com/@reskp?utm_source=medium&amp;utm_medium=referral">Jametlene Reskp</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Utilise Help and User Assistance Features</strong></h4><p>As discussed, memorising steps can be disrupted by a poorly designed experience, resulting in a lack of productivity or errors. We can not just prevent this by improving response times, but also by <strong>guiding the user</strong> effectively. For example, if a user gets stuck during their step by step process, a <strong>helping hand</strong> could get them back on track. This can be achieved through various forms of <strong>help or support</strong>¹⁴.</p><p>However, this should always be as <strong>in-line</strong> as possible. Help and user assistance should be offered where needed in context as users will not need to travel away from their current flow, which could potentially disturb their train of thought, disrupting memory storage, and again, poor productivity or errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ep9CdogRlpZXDwVu" /><figcaption>Photo by <a href="https://unsplash.com/@jjying?utm_source=medium&amp;utm_medium=referral">JJ Ying</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Define Patterns</strong></h4><p>Its important to remember that users become <strong>familiar</strong> with <strong>consistent</strong> design patterns, both in-product and in other products (Jacob’s Law). Many of these position things like dialog buttons in predictable places, of which affects our <strong>spatial memory</strong>¹⁵. Our long term spatial memory assists and influences us across many different products given our historical experience and <strong>mental models</strong>, while short term spatial memory assists and influences us within our current session; a single product. So if we create a familiar, and also consistent design pattern within our product, we promote <strong>less strain</strong> on memory. Conversely, by rearranging these patterns, for example changing the position of a CTA from one page to the next, may <strong>disrupt our spatial memory strength</strong> and result in poor data storage. Of course there are cases where this isn’t always possible, plus additional items need to be added on top of existing patterns, which means defining patterns <strong>should not be strict</strong>.</p><p>In addition to design patterns, we can also provide <strong>visual cues</strong> to promote relativity which can then <strong>ease strain</strong> on our memory. This could be icons in addition or in replacement of text or buttons.</p><p>Providing familiarity and recognisable patterns or cues can enable <strong>correct memory processing</strong>, and avoid creating new, and possibly unfamiliar data which could be processed with error or inefficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*no6KJmvlw91CjQLH" /><figcaption>Photo by <a href="https://unsplash.com/@jblesly?utm_source=medium&amp;utm_medium=referral">Lesly Juarez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Considering Emotions</strong></h4><p>Human emotions can also impact our memory data storage, both positively and negatively. A <strong>positive emotional experience</strong> is likely to promote <strong>efficient memory storage</strong> and <strong>good working memory capacity</strong>, whilst a <strong>negative experience</strong> has a <strong>poorer chance of storage</strong>, <strong>strains our working memory</strong>, and of course creates a memory we would <strong>prefer to forget</strong>. So if we create an experience that makes us happy or content, our users are likely to process data in our product effectively, and provoke a comfortable recurrence. Conversely, if our users become unhappy or uncomfortable, their capacity to process data decreases, and are not so likely to return¹⁶.</p><p>As designers there are many ways we can create a positive emotional experience, including more than mentioned here. This could be via aesthetics, appropriate casual language or satisfaction and gratification.</p><h3>Conclusion</h3><p>There are many other concepts of improving the UX of interactive digital products to promote efficient memory processing, much of which can be dependent on <strong>resources and context</strong>. However with our understanding of the importance of memory consideration in design and its effects, we can confidently build experiences that <strong>positively influence one of our users’ core human mechanisms</strong>.</p><p>With this evidence, we can now understand the <strong>importance of memory</strong> in design. Considering the history of interfaces and the introduction and intuitive enhancements of GUI systems, designers have more freedom to produce customised experiences that <strong>align effectively with our users’ memory capacities and abilities</strong>, therefore producing <strong>better product experiences</strong>.</p><h3>References</h3><ol><li>Cowan N. (2008). What are the differences between long-term, short-term, and working memory? <em>Prog. Brain Res.</em> 169 323–338.</li><li>Robertson, L.T. (2002). Memory and the Brain. <em>Journal of Dental Education</em>, 66(1), pp.30–42.</li><li>Miller, G. (1994). The magical number seven, plus or minus two: Some limits on our capacity for processing information. <em>Psychological Review</em>, 101(2), pp.343–352.</li><li>Kandel, E. (2012). The molecular biology of memory: cAMP, PKA, CRE, CREB-1, CREB-2, and CPEB. <em>Molecular Brain</em>, 5(1).</li><li>Johnson, J. (2010). <em>Designing with the mind in mind</em>. Burlington, Mass.: Morgan Kaufmann Publishers.</li><li>Kelley, P. and Whatson, T. (2013). Making long-term memories in minutes: a spaced learning pattern from memory research in education. <em>Frontiers in Human Neuroscience</em>, 7.</li><li>Farrington, J. (2011). Seven plus or minus two. <em>Performance Improvement Quarterly</em>, 23(4), pp.113–116.</li><li>Miller, N. and Campbell, D. (1959). Recency and primacy in persuasion as a function of the timing of speeches and measurements. <em>The Journal of Abnormal and Social Psychology</em>, 59(1), pp.1–9.</li><li>Shiffrin, R. and Nosofsky, R. (1994). Seven plus or minus two: A commentary on capacity limitations. <em>Psychological Review</em>, 101(2), pp.357–361.</li><li>Nielsen Norman Group. (2018). <em>How Chunking Helps Content Processing</em>. [online] Available at: <a href="https://www.nngroup.com/articles/chunking/">https://www.nngroup.com/articles/chunking/</a> [Accessed 6 Nov. 2018].</li><li>Nielsen Norman Group. (2018). <em>Closeness of Actions and Objects in GUI Design</em>. [online] Available at: <a href="https://www.nngroup.com/articles/closeness-of-actions-and-objects-gui/">https://www.nngroup.com/articles/closeness-of-actions-and-objects-gui/</a> [Accessed 6 Nov. 2018].</li><li>Hick, W. (1952). On the Rate of Gain of Information. <em>Quarterly Journal of Experimental Psychology</em>, 4(1), pp.11–26.</li><li>Doherty, W.J., Thadhani, A.J. (1982). The economic value of rapid response time. IBM Report.</li><li>Nielsen Norman Group. (2018). <em>Short-Term Memory and Web Usability</em>. [online] Available at: <a href="https://www.nngroup.com/articles/short-term-memory-and-web-usability/">https://www.nngroup.com/articles/short-term-memory-and-web-usability/</a> [Accessed 6 Nov. 2018].</li><li>Tidwell, J. (2011). <em>Designing interfaces</em>. 2nd ed. Farnham: O’Reilly, p.17.</li><li>UX Planet. (2018). <em>Emotions, Working Memory, &amp; Design — UX Planet</em>. [online] Available at: <a href="https://uxplanet.org/emotions-working-memory-design-ae9ecfa3249b">https://uxplanet.org/emotions-working-memory-design-ae9ecfa3249b</a> [Accessed 6 Nov. 2018].</li></ol><h3>Further Reading</h3><p><a href="https://headrush.typepad.com/creating_passionate_users/2005/12/_but_is_it_memo.html">https://headrush.typepad.com/creating_passionate_users/2005/12/_but_is_it_memo.html</a></p><p><a href="https://www.khanacademy.org/test-prep/mcat/social-sciences-practice/social-science-practice-tut/e/miller-s-law--chunking--and-the-capacity-of-working-memory">https://www.khanacademy.org/test-prep/mcat/social-sciences-practice/social-science-practice-tut/e/miller-s-law--chunking--and-the-capacity-of-working-memory</a></p><p><a href="https://www.nngroup.com/articles/website-response-times/">https://www.nngroup.com/articles/website-response-times/</a></p><p><a href="https://uxknowledgebase.com/ux-human-memory-a306a7dadcb8">https://uxknowledgebase.com/ux-human-memory-a306a7dadcb8</a></p><p><a href="http://uxbert.com/ux-psychology-principles-design-ux/#Memory_Limitations">http://uxbert.com/ux-psychology-principles-design-ux/#Memory_Limitations</a></p><p><a href="https://uxknowledgebase.com/hicks-law-7e9eb8ceaee0">https://uxknowledgebase.com/hicks-law-7e9eb8ceaee0</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f109c15f12ff" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-with-memory-in-mind-f109c15f12ff">Designing with memory in mind</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>