<?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 Renee C. on Medium]]></title>
        <description><![CDATA[Stories by Renee C. on Medium]]></description>
        <link>https://medium.com/@wired_crow?source=rss-383f7f7038ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*leuVR7g6FqXn4usPVS9cMg.jpeg</url>
            <title>Stories by Renee C. on Medium</title>
            <link>https://medium.com/@wired_crow?source=rss-383f7f7038ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 08:51:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wired_crow/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[A Lesson in Scaffolding]]></title>
            <link>https://blog.prototypr.io/a-lesson-in-scaffolding-dc1eb2e52cc1?source=rss-383f7f7038ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc1eb2e52cc1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Renee C.]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 19:01:59 GMT</pubDate>
            <atom:updated>2018-04-19T10:02:03.035Z</atom:updated>
            <content:encoded><![CDATA[<h4>Usability through the eyes of a toddler</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8sucjYWgB4L6eJTgVx-ZfA.jpeg" /><figcaption>Source: <a href="https://pixabay.com/en/baby-hand-small-child-child-access-3308893/">Pixabay</a></figcaption></figure><p>As a mother, I love watching my toddler learning to interact with the world around him. As a designer however, I am also fascinated by the how different interfaces, from physical objects like a book, to digital like the screen on my phone, teach him how to interact, how he internalizes those interactions and build a mental model of expectations.</p><p>For instance, although we tried to limit screen time earlier on, he did grow up watching everyone around him swipe across our phone screens. I have lost count the number of times he has clambered up the entertainment unit to try to swipe the TV. (Parenting aside: we are so glad we wall-mounted the TV early on.)</p><p>Another neat example: my son is fascinated with buttons. Whenever he sees a button, whether it is the elevator, the big steel push plate for door activation, or the on/off on my laptop, he has to push it. I suppose he must have learned early on from his toys. And now that he has acquired language, he will happily point and say push.</p><p>So the other day, I noticed that he was toying with a button on my sweater and I casually named it for him as I usually do when he points at things. Immediately, he became fascinated, trying to push it. At first, I thought he was being half-playful/half-rude, poking me until suddenly it clicked in my head that he had come to associate buttons as things to push so that something would happen. For him, buttons are for pushing. Their form factor wasn’t just a signifier for him, the action was a learned behaviour stemming from a pattern of interaction that he had come to associate with the word.</p><p>So all in all, watching a toddler interact with interfaces proves some interesting insights. In no way are the things I discuss here new and there are already countless articles about similar topics but I thought it was really neat watching how these design considerations come to life through a toddler learning about the world around him.</p><h3>A Tale of Two Toys</h3><p>My son, like most toddlers, has an obsession with phones (as you may have guessed by now). So for Christmas, he got two toy phones from two separate gift-givers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDxPPmOaY99VRj38xKLQhA.jpeg" /><figcaption>Original image captured of the two toys at home</figcaption></figure><p>Curious to see which one he would take to, I offered both to him side-by-side like you see in the photo.</p><p>Some behaviours observed:</p><ul><li>There was a much more instantaneous attraction to the Leapfrog phone</li><li>Over time, however as he grew both in cognitive ability and familiarity with the phone, the VTech one would hold his attention slightly longer</li><li>When he starts interacting with the phones for the first time in the day, he often starts with the Leapfrog phone but will transition eventually to the VTech one</li></ul><p>Now there are some factors that may also contribute to some of the behaviour:</p><ul><li>The Leapfrog phone’s primary character is a dog, my son’s current favourite, while the VTech one is a parrot, an animal he is less familiar with</li><li>The Leapfrog phone is louder</li><li>The Leapfrog phone uses a younger voice as the voice of the narrator</li></ul><p>However, one other important factor became an AH-HA moment for me. As you can tell, the one on the left from LeapFrog is much simpler in design and features compared to the one from VTech.</p><h4>The Features Difference</h4><p>In more details, the LeapFrog phone has buttons 0–9 with a ring and a music button. the 0–9 buttons generate the exact same interaction every time. The two other buttons generate a series of different interactions on rotation. But each button does precisely one thing and different combinations of buttons do not generate different interactions.</p><p>The VTech one has a lot more options including games that require various amount of inputs such as asking the user to choose which number is the right one. It also relies on a combination of buttons, such as pressing the image gallery then asking the user to use the arrows to scroll through the photos.</p><h4><strong>Consistency of Interactions and Focused Features</strong></h4><p>To be frank, I think my toddler probably learned how to count numbers on the LeapFrog phone. He also learned that flowers are for sniffing (with the number 3, the puppy sniffs the 3 flowers on the screen.) Because the buttons are always consistently generating the same interaction, my toddler learned quickly on how to generate the reaction he wanted from the toy.</p><p>The number of different interactions from different buttons on the VTech toy confused not only my son but myself as well. He still likes to press them but there’s a lot more random button pushing rather than with purpose.</p><p><strong>Design take away: </strong>A simplistic feature sets lets your UI be a lot more focused. Single interactions associated with single UI elements will help users learn a lot faster. Complexity comes when you are trying to do too much with each element or worse, with combination of UI elements.</p><h4>Progression to Expertise</h4><p>As I mentioned previously, my son would eventually move to playing with the more complex phone (even if he’s not sure how it works). I believe eventually he just gets bored of the more simplistic phone which is totally fair. In that sense, I think there is a place for more complex interactions and features depending on the situation. For instance, once a user has mastered the simple functionality, more complex combinations and interactions are entirely appropriate, especially if it meets the design goals (keep users interested or help speed up their task).</p><p><strong>Design take away: </strong>Best to save complex interactions for those that have acclimatize to the simpler features. And depending on the type of user and the interface’s raison d’êre you’re trying to design, it may even be a way to meet design goals to provide more complex interactions, especially for the expert user.</p><p>For instance, in one of the Neilsen Norman training classes I took, the instructor spoke of a model discussed by <a href="https://docs.lib.purdue.edu/cgi/viewcontent.cgi?referer=https://www.google.ca/&amp;httpsredir=1&amp;article=1024&amp;context=jhpee">Peter A. Hancock and Joel S. Warm in <em>A dynamic model of stress and sustained interaction</em></a>, that details a psychological zone of max adaptivity, where too much stress (in this case, produced by cognitive load) can lead to the commonly known problems but also if there was too little stress, users can become inattentive, make mistakes or simply not even care. In my toddler’s case, I believe the Leapfrog phone eventually becomes that as time progresses.</p><p>However, I do want to emphasize that I believe this is specific to very unique circumstances and is highly dependent on the goals of the application, service or product you are trying to build. For instances, games, where the goal is to keep the user engaged with the product, is a great place to leverage this idea.</p><h3>Thoughts on Scaffolding</h3><p>This of course, brings us to the idea of scaffolding. Simply put, it is the progressive disclosure of more features or functionality as users become more familiar with the product or service. The most prevalent example is in games, often in the guise of tutorials or levels (and sometimes a combination of the two.) For example, in games such as <em>Mirror’s Edge</em> or <em>Assassin’s Creed, </em>the game gradually introduces you to more key combinations that produces more complex moves.</p><p>I have yet to see scaffolding used commonly however in a single product. However, I believe it is a great technique that can be used in broader just games. For instance, imagine helping the elderly learn how to use the smart phone by progressively disclosing features over time to make the devices less intimidating. Imagine design tools that natively have scaffolding built in so that first-time users are not so overwhelmed.</p><p>If you know of some examples of this, please leave a comment! I’d love to study them more.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc1eb2e52cc1" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/a-lesson-in-scaffolding-dc1eb2e52cc1">A Lesson in Scaffolding</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In Defense of Personas]]></title>
            <link>https://blog.prototypr.io/in-defense-of-personas-e12199c06a6d?source=rss-383f7f7038ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/e12199c06a6d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Renee C.]]></dc:creator>
            <pubDate>Sat, 07 Apr 2018 21:47:49 GMT</pubDate>
            <atom:updated>2018-05-01T16:07:23.035Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l103qHf1eLn_wO0E_RfupQ.jpeg" /><figcaption>Source: <a href="https://pixabay.com/en/social-media-digitization-faces-3271590/">Pixabay</a></figcaption></figure><p><em>Personas are profiles of targeted users that sums up who they are, their backgrounds, behaviours and attitudes in a way that helps inform design decisions for a product, site or service.</em></p><p>A while back, a friend asked for my opinion on personas and whether they were genuinely useful. I had always been a big proponent for personas but his question gave me pause. He was definitely not the first person to tell me that he wasn’t a fan of them, just the latest in line, and that made me wonder why there was such a dislike for personas.</p><h3>Mistaken and Abused</h3><p>On the surface, the definition of a persona is easy to understand. It’s a profile of your typical user, given a name and an identity to help guide design decisions, whether you are designing a service or a product, whether you are doing it for profit or not. However, I knew that coming up with personas was not an easy task so I dug deeper with my friend and asked him what he meant by his question.</p><p>He went on to elaborate, stating that he felt that personas too easily become broad stroke generalization of the target audience and you would lose all nuances of designing for the right audience. Specifically, he gave an example of an average software product sales site other a common design pattern like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VtyUI0cYgt3Vug8WNv4sbg.png" /><figcaption>Screen capture <a href="https://www.adobe.com/ca/creativecloud.html">Adobe Creative Cloud</a> site</figcaption></figure><p>Now in his defense, my friend was a developer and not in the field of UX himself. His description, however, was an AH-HA moment for me. To me, what he pointed out was more of a segmentation, necessary in a software sales site to funnel users to the right area once they are ready to purchase. However, I do not believe, for one moment, that this is reflective of the many personas Adobe used in the creation of their site.</p><p>It’s easy to mistaken the end-result designs as direct translations of the personas themselves when you are trying to backwards-engineer a design without being in the process. However, I think if a persona did translate directly into a design, then something has gone wrong.</p><p>This happened on a project I worked on once. Rather than using personas to help figure out what tasks users coming to our site were trying to accomplish, then directing them accordingly, we asked users to identify themselves as one of our personas before they could find the relevant links (much like how segmentation in the screenshot above worked.) But while the screenshot above was deeper into the site, we actually used that interaction as the main homepage element. This confused users and forced additional cognitive load on them rather than take them directly to the information they needed. The design worked (our segments were pretty exclusive luckily) but it didn’t work as well as it could have been. We have redesigned since.</p><p>There are, of course, a myriad of other ways personas can get abused. Part of a set of personas’ purpose is to drive and ground design decisions but if they are not used at all, not updated regularly with new research (more on that later), then there isn’t much of a point to them, is there?</p><p>Given the number of poorly designed experiences out here, including misused personas like in my case, no wonder personas get a bad rep.</p><h3>Ungrounded and Unfound</h3><p>In my early days of learning UX on my own, before UX got all popular enough with lots of online articles, web courses and accessible online courses, I had visions of personas as ideal audiences my designs would target. This would be no further from the truth. (Hey, we were all naive once…right?)</p><p>A good, useful set of personas can take months of hard work. They may stem from a business and/or product vision, strategy and goal, but then it’s the job of the UX practitioner to go out and do research to flesh out who in reality are these people you are designing for. And research is such a short word for the breadth of work that needed to be done, from interviews and diary studies to analytics and market and competitive analysis, just to name a few.</p><p>The research can lead to groundbreaking insights, from whether it IS the right audience for the product to discovering previously unknown needs. Coupled with the right set of other artifacts (remember the part about using the personas?) such as user journeys and empathy maps at the right moments of the journey, they can tell powerful stories about how users use a product or service. These stories help bring stakeholder buy-in, align decisions and ground conversations in user-centric thinking, especially if they are grounded in reality.</p><p>I found the <a href="http://www.designkit.org/methods">Design Kit</a> site to be particularly helpful in articulating some of the activities that can be done to help form personas.</p><h3>Too Specific and Too General</h3><p>Part of my friend’s concern about the use of personas was that they seemed to be too general and too specific at the same time, in that they speak to a particular user but is used to generalize all users. I think, however, that the flaw in viewing a persona in silo. There is never one persona for a product but rather, a set of personas that represent a diversity of users. Still, each persona should also represent general trends found in research, whether it’s in attitudes, background, believes, behaviours and other contexts. People are messy and so I would expect personas are too, such that one persona may contradict another. But together, they should paint a general idea of who the audience is.</p><p>Yes, personas can be abused to make generalizations but I believe all designs have to start somewhere. This is why designs need to be tested and iterated on. One of my managers I’ve had in my career always liked to remind me that no designer ever got their design right 100% the first time. Every time I missed something in my design, I try to remind myself of that.</p><h3>Purpose Built</h3><p>Personas can be used in a variety of ways. One of my favourite is to use them to ground subsequent design exercises and narrows the focus for individual artifacts. For instance, mapping a user journey would be nearly impossible without a persona in mind for the journey would try to cover too many scenarios and too many types of users. I’ve also heard of instances where UX teams created large cardboard stands of their personas and brought them into design workshops. I have yet to try it but it sounds like a great idea to visually and physically remind others that you are designing for real people, even if your personas are fictional in the first place.</p><p>I remember an anecdotal story my instructor at the Centre of Digital Media told me once. At Dreamworks, he was working on a big Hollywood animated film and they would use personas to ground their storytelling. It got to a point that whenever decision makers for the film would argue about a particular direction, someone just had to mention the persona’s name and it would make everyone sit back and rethink their arguments.</p><p>I’d like to get to that point someday with personas in my UX practice.</p><p>For more information on what personas are and other pro-personas arguments, here’re some articles I found helpful:</p><ul><li><a href="http://UX is Process: Actionable User Insight">UX is Process: Actionable User Insight</a></li><li><a href="https://www.nngroup.com/articles/why-personas-fail/">Neilsen Norman: Why Personas Fail</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e12199c06a6d" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/in-defense-of-personas-e12199c06a6d">In Defense of Personas</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>