<?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 Nora Pekker on Medium]]></title>
        <description><![CDATA[Stories by Nora Pekker on Medium]]></description>
        <link>https://medium.com/@norapekker?source=rss-9cd7953d9457------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*D63BBVG-v00yXFC7zyWBxQ.jpeg</url>
            <title>Stories by Nora Pekker on Medium</title>
            <link>https://medium.com/@norapekker?source=rss-9cd7953d9457------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:31:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@norapekker/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[Best Practices for Navigating the UI Paradigm Shift]]></title>
            <link>https://medium.com/design-bootcamp/best-practices-for-navigating-the-ui-paradigm-shift-9c7ff81f4aa3?source=rss-9cd7953d9457------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c7ff81f4aa3</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[prompt]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Nora Pekker]]></dc:creator>
            <pubDate>Tue, 20 May 2025 15:20:30 GMT</pubDate>
            <atom:updated>2025-05-21T16:21:27.953Z</atom:updated>
            <content:encoded><![CDATA[<p><em>We’re in the middle of a major paradigm shift in how we interact with computers. For decades, our interfaces were based on commands — whether it was typing lines into DOS or clicking around a GUI. But now, thanks to AI and especially large language models (LLMs), things are changing fast.</em></p><p><strong>Instead of telling a computer how to do something, users are increasingly just telling it what they want done. It’s a move from command-based interaction to intent-based outcome specification.</strong> As Jakob Nielsen puts it in his excellent article on the subject: <a href="https://www.nngroup.com/articles/ai-paradigm/">The AI Paradigm Shift</a>, we’re shifting towards simply stating a goal — and getting a result, often in seconds.</p><p>Some tasks are easy to prompt. Need a 500-word essay on the Industrial Revolution? Type it in, and ChatGPT will spit it out almost instantly. <br>It works because the desired output is clearly defined and easily expressed in words.</p><figure><img alt="Illustration: Ai and prompts" src="https://cdn-images-1.medium.com/max/1024/1*p1pU6lpWCFauVOS5lp0M3g.jpeg" /><figcaption>Credit: <a href="https://icons8.com/illustrations/illustration/665d61047b83db0bb4a1ffd4">Sky, Icon8</a></figcaption></figure><h3>1. Defining What Users Want</h3><p><em>But what happens when users can’t clearly define what they want — especially with visual tasks?</em></p><p>You’ve probably seen those viral “Ghibli-style” images or “Wes Anderson-style” videos floating around the internet. They’re popular because they’re based on recognizable artistic styles. And more importantly, they’re easy to prompt.</p><p>When someone says, “make a video in Wes Anderson style,” what they’re <em>really</em> asking for is a specific visual language — carefully composed symmetry, pastel color palettes, quirky characters, tight framing, bird’s-eye shots, etc. These are things that even professional designers might find hard to articulate.</p><p>The issue here (beyond the obvious copyright concerns) is that in real-world products, users often struggle to describe visual intent in a prompt. Unless you’re literally building a “Wes Anderson video Generator,” you can’t assume your users will know how to specify their vision with just words.</p><p>At Colossyan, we developed a prompt-to-video feature and quickly encountered a common challenge: while most users could easily define the video’s content — its message, tone, and audience — they struggled with the visuals. The time they spent editing the look and feel of the output was too high, clearly revealing a pain point in the process.</p><p><strong>Our solution? Split the process.</strong><br>We divided video creation into two distinct steps and matched each with the most suitable UI element:</p><ul><li><strong>Content Creation</strong> — where users define the script and the general message of the video (via a prompt).</li><li><strong>Visual Styling</strong> — where users select the look and feel using predefined templates and visual references.</li></ul><p>We also introduced helpful <strong>guidance </strong>to support users in writing prompts that lead to better results — for example, by encouraging them to identify their target audience or define the desired video length.</p><p>Additionally, we encourage users to <strong>add context </strong>to their prompts using other formats. In our case, many video creators already had a rough script in mind, so allowing them to attach documents often resulted in more relevant and accurate output.</p><figure><img alt="Illustration person sitting at computer, plus user interface elements are shown" src="https://cdn-images-1.medium.com/max/1024/1*pxHDesIMkWyDOrPXc16uvw.jpeg" /><figcaption>Credit: <a href="https://icons8.com/illustrations/illustration/665d61047b83db0bb4a1ffd4">Sky, Icon8</a></figcaption></figure><h3>Key Takeaways:</h3><ul><li><strong>Think about the best way users can define the desired output in your product. </strong>Sometimes, drawing something (like a flowchart) is easier than describing it in text.</li><li><strong>If needed, split the process.<br></strong>Different aspects of intent — such as content vs. visuals — may require different UI elements.</li><li><strong>Use prompts only where they add value.<br></strong>They’re best suited for capturing general intent or defining content.</li><li><strong>Make it easy to provide relevant context.<br></strong>Let users attach supporting material (e.g., documents, links) to improve output quality.</li><li><strong>Offer helpful prompt guidance.<br></strong>In our case, we encouraged users to define things like length, tone, and audience to ensure more relevant output.</li><li><strong>For visuals, offer reference options.<br></strong>Style presets or templates can help users achieve the look they want .</li></ul><p>By supporting users with the right structure and tools, we help them get better results — without requiring them to become prompt engineers.</p><h3>2. Modifying the Output</h3><p>Another area where it’s worth thinking twice about using prompts is editing. In our case, after generating a video draft, many users just wanted to change minor details — like text alignment or background color. <strong>Letting them do that through familiar interfaces </strong>— click, drag, dropdown — was far <strong>more effective</strong> than making them describe those changes in a new prompt.</p><p><strong>Micro-generations</strong> can also help minimise user effort during editing, allowing users to make small tweaks without restarting the entire prompt flow.</p><p>We’re also experimenting with <strong>predictive AI suggestions</strong> — trying to give users advice on how to improve their videos without needing them to write a prompt at all. But that’s a tough one to get right.</p><h3>Main Takeaways:</h3><ul><li>Classic, <strong>command-based GUI elements can work better for quick edits.</strong></li><li><strong>Let users choose:</strong> adjust output via standard UI tools or refine with follow-up prompts.</li><li>Offer <strong>micro-generations</strong> instead of forcing full re-generations.</li><li>Experiment with <strong>predictive AI suggestions </strong>— where it makes sense.</li></ul><figure><img alt="Illustration: User interface, editing, design tool interface" src="https://cdn-images-1.medium.com/max/1024/1*7iSb-UbK1Lk4JsyeNqHjVg.jpeg" /><figcaption>Credit: <a href="https://icons8.com/illustrations/illustration/665d61047b83db0bb4a1ffd4">Sky, Icon8</a></figcaption></figure><h3>Conclusion</h3><p>We’re moving toward a world where users care less about <em>how</em> something gets done, and more about just getting the outcome they want. That’s the essence of outcome-focused design. But as designers and builders, we shouldn’t feel pressured to go “prompt-only” just because it’s trendy. The real question to ask is:</p><p><strong>What’s the easiest way for our users to express their intent and get what they want?</strong></p><p>Sometimes, that’s a prompt.<br>Sometimes, it’s drawing a chart.<br>Sometimes, it’s a template.</p><p>Design accordingly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c7ff81f4aa3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/best-practices-for-navigating-the-ui-paradigm-shift-9c7ff81f4aa3">Best Practices for Navigating the UI Paradigm Shift</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[How to build a professional UX Research portfolio]]></title>
            <link>https://medium.com/design-ibm/how-to-build-a-professional-ux-research-portfolio-fc925750bdc0?source=rss-9cd7953d9457------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc925750bdc0</guid>
            <dc:creator><![CDATA[Nora Pekker]]></dc:creator>
            <pubDate>Wed, 09 Feb 2022 18:06:34 GMT</pubDate>
            <atom:updated>2022-02-10T06:22:45.662Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyFnFfxtfmlS6N_mUSyRpg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p><strong>A hands-on guide for how to create a UX research portfolio that will stand out</strong></p><p>When it comes to displaying our work, UX researchers are in a difficult position. Most of the studies we conduct, the artifacts we create, and the insights we deliver are confidential. On top of that, it looks nothing like a visual designer’s portfolio. Unlike designers, UX researchers do not have well-polished design artifacts to display.</p><p>I collected some <strong>practical tips</strong> for you about how to overcome these challenges and <strong>create an outstanding UX Research Portfolio.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lOoD9mBmLUO0FhJ5RVGNIw.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>Tell a story</h3><p>The most important advice I can give is to <strong>tell a story</strong>. The best way to display what you’ve done is to <strong>write case studies for your work. </strong>A good case study allows you to focus on what really matters from your research without going into unnecessary details. It can help you highlight the impact of your work.</p><p>Telling a story instead of focusing on research artifacts<strong> can also help solve confidentiality problems. </strong>You can choose the appropriate amount of details to include on that particular study and you can build an engaging story without showing a single artifact that might contain sensitive information about the project.</p><p>When you are writing your case study, the <strong>narrative arc</strong> is essential. These are five basic steps to make your story more engaging and easy to follow.</p><ol><li><strong>The intro:</strong> Let’s start by providing some context for your study. Start with a short introduction to your employer/client then think about the basic information they might need for context. What kind of industry are they in? What is their core offering? What product you were working on?</li><li><strong>The challenge: </strong>Every project starts with a challenge. Use this section to explain <strong>the problem</strong> you were trying to solve to your audience. <strong>What questions</strong> were you trying to answer with your study? <strong>What frameworks</strong> were you trying to improve?</li><li><strong>The solution</strong>: It’s time to get into some details of your study by describing your experience setting up and conducting your research plan. Which methodologies did you chose? Why? Who were your participants? How many were there? How did the study go? Did you face any difficulties? Did you have to adjust your plan?</li><li><strong>The findings: </strong>This is the most tricky part of your story. You should find the balance between sharing detailed, sensitive information and not sharing anything at all. A good approach is to<strong> focus on the high-level findings.</strong> Highlight the most impactful insights.</li><li><strong>The impact: </strong>Your story doesn’t stop with your findings. <strong>The key is to highlight the business impact of your work.</strong> How did your insights impact the product strategy? How did they affect the roadmap or the design decisions? Have they sparked new conversations? These will be the questions everyone will want to know. In the end, stakeholders are most interested in how your work can drive changes to the product.</li></ol><p>Of course, these five steps are very generic. It is possible that your case study doesn’t map closely to this model. That’s perfectly fine! For example, if you are working on research operations projects you might not have an extensive ‘findings’ sections, but may be able to put more focus on the frameworks you improved. As long as you highlight <strong>the</strong> <strong>challenges</strong>,<strong> the solution</strong>, and<strong> the impact of your work</strong>, you can be flexible with the sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyG2Ek769zuMwfGquYcFJg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p><strong><em>How to choose stories to share?</em></strong></p><p>You don’t have to include every project you’ve worked on throughout your career. Quality is more important than quantity. <strong>Choose 3–6 studies that you are proud of </strong>and select projects which display a wide range of skills.</p><p><strong>Don’t wait for the perfect study!</strong> Do you feel that none of the studies you have conducted are perfect? That’s OK. We all have to deal with changes in priorities, limited resources, or other constraining factors. <strong>Good case studies don’t come from ideal research projects. They display your ability to overcome those obstacles and deliver the best possible result given the circumstances.</strong></p><h3>The tools</h3><p>The easiest way to showcase your studies is to create an <strong>online portfolio.</strong> Nowadays there are many tools available for researchers (Behance, Wix, etc). <br>You don’t have any design background? No problem! There are many tools that offer <strong>templates </strong>you can leverage. You don’t have to be a designer to create a beautiful portfolio site. Online portfolios are <strong>easier to share</strong> than large PDFs and take less effort to keep up to date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bMio5ANoKoBn6gs0BjeoQ.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>The format</h3><p>The<strong> format of your study is just as important as the content </strong>when you’re writing your story.<strong> </strong>There are some basic visual tricks that can make your case studies easier to read.</p><ul><li><strong>Keep it compact: </strong>Keep your study as short as possible without compromising the story arc. Shorter paragraphs work better- no one likes reading a long chunk of text online. Respect your audience’s time. You can always go into more detail while you are presenting your studies later on.</li><li><strong>Highlight keywords:</strong> By highlighting keywords you make it easier for your audience to scan your story and remember the most important takeaways.</li><li><strong>Highlight numbers:</strong> Numbers are great way to communicate the impact of your work. It’s important to highlight key figures to display the scale and impact of your work. For example the number of study participants etc.</li><li><strong>Use illustrations</strong>: If you can share your research artifacts, such as personas, journeys, etc, do so. However, most of the time those artifacts are confidential. If that’s the case, you can still use illustrations in your portfolio. It will break the monotony of having just text, increase your study’s readability, and make your work look visually appealing.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7kxBKv6Ttua4hs1k8Ikuw.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>It will take time and it’s OK</h3><p>Building a portfolio is a lot of work. You are summarizing the highlights of your career. Make sure you <strong>take your time</strong>. Don’t try to make it in one go. Choose the stories you want to share. Write the case studies. Make it look nice. Review it. Review it again. Ask your friends and colleagues to review it. Check it on different devices. Check it again.</p><p>With multiple rounds of iteration, your portfolio may take a few weeks to complete, and that’s fine. If you <strong>build up a good base it will be easy to maintain your portfolio in the future.</strong></p><h3>Keep it up to date</h3><p>As you progress in your career, you might want to <strong>update your portfolio from time to time.</strong> The good news is that you don’t have to start from scratch every time. Adding a new case study or refreshing your visuals will be less time-consuming than the initial work.</p><p>Building a great UX Research Portfolio is a lot of work but you will benefit from it greatly. I hope this short article will get you started — so go ahead and write your first case study today!</p><p><em>Nora Pekker is a Design Researcher at IBM based in Budapest. The above article is personal and does not necessarily represent IBM’s positions, strategies or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc925750bdc0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/how-to-build-a-professional-ux-research-portfolio-fc925750bdc0">How to build a professional UX Research portfolio</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a compelling UX Research Roadmap]]></title>
            <link>https://medium.com/design-ibm/how-to-build-a-compelling-ux-research-roadmap-227448005c82?source=rss-9cd7953d9457------2</link>
            <guid isPermaLink="false">https://medium.com/p/227448005c82</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-researcher]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Nora Pekker]]></dc:creator>
            <pubDate>Wed, 29 Sep 2021 15:27:05 GMT</pubDate>
            <atom:updated>2022-02-13T06:52:57.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZffPnFgGGNEBHF_em01oFg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p>A step by step guide on how to build a UX Research roadmap.</p><p>Research roadmaps can be one of the most valuable assets for a UX researcher. They help you gain alignment and communicate your priorities, plan your studies with ease, and maintain sight of the big picture.</p><h3><strong>What is a UX research roadmap?</strong></h3><p>A UX research roadmap is a plan that <strong>defines</strong> your team’s key <strong>research goals</strong> and the strategy to reach them.</p><p>It shows a <strong>timeline for the studies</strong> that will be conducted during the year to achieve those research goals.</p><h3><strong>Why do a UX research roadmap?</strong></h3><ul><li><strong>Maintaining focus:</strong> It helps you and your team maintain focus on the research goals. It is easy to get lost among all those tactical studies and the ever-changing priorities during the year. A research roadmap will help you keep the focus on the main research goals and priorities.</li><li><strong>Creating transparency: </strong>Research roadmaps help you to communicate with other stakeholders. You can share a detailed timeline of what studies the research team will be working on.</li><li><strong>Prioritize studies</strong>. One of the biggest challenges for a lot of researchers is knowing which studies to prioritize. Everything is important, right? By having the research goals clearly defined, and a timeline laid out, it will be easier to prioritize what to work on and when.</li><li><strong>Support continuous data-driven product design:</strong> By having a timeline planned, you can ensure that you will deliver insights to your design team just in time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NO0BAihF_v_edvpHoBmNvg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3><strong>When and how to build a UX research roadmap?</strong></h3><p>Whenever you join a new project or team, it’s a good idea to start by putting together a research roadmap. If you are lucky enough to work with the same product team for years, I recommend making a new research roadmap every year.</p><p>Putting together a research roadmap is a straightforward process. Just follow the steps below.</p><h4><strong>1) Understand stakeholders’ needs</strong></h4><p>Understanding stakeholders’ needs is the most valuable thing you can do to create an actionable and impactful research roadmap. The focus of any research roadmap should be to support your product team. The best way to understand needs of your team is to conduct <strong>stakeholder interviews. </strong>I recommend that you not only talk with the designers working on the product, but that you also set up one-on-ones with members of the broader product team (e.g., developers, product managers, copywriters, etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsVUj7e0odGiAX1pYb5Png.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p>Understand the<strong> product roadmap.</strong> Every researcher’s main task is to support the product team with relevant insights. You might conduct generative studies to help the team kick off new projects and explore new opportunities, or you might do more evaluative studies to assess the usability and effectiveness of new designs. The best way to identify these studies is by understanding the product roadmap. With the help of the product manager and the design manager, you can set clear timelines and milestones. This way you can ensure that your research studies are conducted in time to be the most valuable to your team.</p><h4><strong>2) Assess the current state of research</strong></h4><p>Except for some greenfield projects, chances are high that <strong>related research materials </strong>exist. Find out what has been done. There’s no reason to reinvent the wheel. Contact any previous researchers who have done work with the team as well as any other researchers doing work on the same or related topics. This will help you understand what has already been done. It’s good to reach out not only to researchers but also to designers and product managers, they often have useful information about the product.</p><p>Be sure to dedicate enough time to understand what you and your team already know about the product, users, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5DiZ5Q9Nmyq9XQnU4SWF4g.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p>Collect all existing <strong>artifacts</strong> ( e.g., personas, user journeys, need statements, etc.) and identify what’s known and unknown. Where are there gaps in the research or team’s understanding? What’s changed or is out-of-date?</p><p>These steps will help you to evaluate the current level of understanding the team has about the users. Clarifying what the team already knows will also help you to avoid doing redundant studies.</p><h4><strong>3) Identify the key research goals</strong></h4><p>Based on stakeholders’ needs and the existing research materials,<strong> identify the key research goals and the main directions. </strong>For example: Our goal is to learn more about usage and validate our personas.<br>Try to <strong>list out the most important questions</strong> your team has about the users, use cases, etc. Think about the <strong>artifacts </strong>you need to provide them to be successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PRgASe8Vf_AfEqVc7rbBg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p>And don’t forget research or design operations. Think about how you might improve existing frameworks and best practices, or how you might provide guidance to others based on your knowledge. For example, enabling more data-driven design or helping product managers to create more research-based roadmaps.</p><p>Feel free to set high-level goals. Remember you are not listing studies here but rather the desired outcomes.</p><h4><strong>4) Plan the research studies</strong></h4><p>After you have identified the key research goals, try to <strong>think about </strong>which<strong> studies</strong> will help you to achieve them.</p><p>It usually makes sense to differentiate between tactical and strategic studies.</p><p><strong>Tactical studies </strong>are closely tied to the product roadmap. For example, usability tests following the implementation of a new design or concept. These studies are usually simple and completed in a short period of time.</p><p><strong>Strategic studies</strong> are not as closely related to the existing roadmap, but rather focus on achieving more long-term goals, such as understanding the whole user journey or creating personas. These studies often combine several methodologies and are run by multiple researchers.</p><p>Almost all <strong>studies will support more than one research goal.</strong> And it’s perfectly okay to have multiple researchers working on different studies that in the end support this goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N_8J48dsuEJt1YNo9cgRRg.jpeg" /></figure><p><strong>Organizational tip</strong>: One easy way of <strong>visualizing the connection between studies and research goals</strong> is to create a table. In the header part or for the columns, list all of the key research goals you have set. On the left side or for the rows, list all the research studies you are planning for the year. Then, for each and every study you have planned, mark which research goals they support. Doing so will give both you and your stakeholders confidence that you have designed a plan to meet the team’s goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oTK-sRCX1lNIiDaCB72DRg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h4><strong>5) Create a timeline</strong></h4><p>As a next step: <strong>create a timeline</strong>. When you have identified and listed all the studies valuable to the team, you need to think about timing and prioritisation.</p><p>It’s usually a good approach to start with <strong>tactical studies</strong>. Those are easy to plan as they mirror the product roadmap. Make sure you give yourself enough time to be able to provide meaningful insights. Design managers can usually help you estimate the time the design team needs to create the first prototypes so you can plan your evaluative studies accordingly.</p><p><strong>Strategic studies </strong>don’t always have an exact start and end date. As they are not closely tied to the product roadmap, you can plan them more flexibly.</p><p>Preferably you should be working no more than one or two strategic studies plus one tactical study at a time. <strong>Try not to overwhelm yourself. </strong>More is not always better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*CpFuHlfBH_C7KszeF6w-mA.jpeg" /></figure><p><strong>Create a timeline: </strong>A good timeline will help you to communicate your plan to your stakeholders.I approach creating a timeline by first distributing the studies across the quarters. Then I lay them out in a <strong>Gantt chart</strong> in a monthly breakdown. In this way I am able to give a clear overview of the timing of all the studies.</p><h4><strong>6) Share your plan</strong></h4><p>After creating the roadmap, it is best practice to meet with your stakeholders and share your plan. It is important to highlight the primary gaps and the plan to address them. It is time to present your research roadmap.<br>Sharing your plans with your stakeholders will assure them that you have listened, and will keep them invested in the outcomes. It will also allow you to get their feedback and establish continued engagement as you embark on the research roadmap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WEnkvtIziyfOvFJzDe3mhQ.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p>Some last words of advice</p><h4><strong>Remember, it’s a team effort</strong></h4><p>A research roadmap is not your personal calendar or to-do list. A research roadmap should communicate what the entire research team is working on. So always <strong>align with your fellow researchers </strong>and include their studies in the roadmap as well.</p><h4><strong>Be flexible</strong></h4><p>How should you deal with the constantly changing priorities during the year? My advice: don’t try to stick with the original plan at all costs. As product roadmaps change, tactical items will shift and that’s perfectly OK. So<strong> be flexible with your tactical studies.</strong> Just make sure you keep your roadmap up to date and communicate the changes. If tactical studies change a lot, it’s also worth revisiting your roadmap halfway through the year.</p><p>Try to <strong>stick to the original planning with the strategic studies</strong> as much as possible, however. Those studies aren’t strictly driven by the product roadmap. Therefore you can do those studies at your own pace, so try to stick with your plan.</p><p>The most important thing is: <strong>your research goals should not change. </strong>Don’t let last-minute requests or the growing number of tactical studies steer you away from achieving the research goals you have set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yySWDduM12a-LSmzT_V-WQ.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h4><strong>Reflect on the roadmap</strong></h4><p>I like to reflect on the roadmap at the end of the year. It helps me understand the progress we have made and identify the questions and goals we need to continue focusing on the following year.</p><p>This activity also provides you with a <strong>good opportunity to share your achievements with your stakeholders. </strong>Provide a condensed summary of the year.</p><p>Research roadmaps will help you to be organized, transparent, and work towards your research goal through the year.</p><p><em>Nora Pekker is a Design Researcher at IBM based in Budapest. The above article is personal and does not necessarily represent IBM’s positions, strategies or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=227448005c82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/how-to-build-a-compelling-ux-research-roadmap-227448005c82">How to Build a compelling UX Research Roadmap</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for kids]]></title>
            <link>https://medium.com/@norapekker/designing-for-kids-75539789d3e6?source=rss-9cd7953d9457------2</link>
            <guid isPermaLink="false">https://medium.com/p/75539789d3e6</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[children]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nora Pekker]]></dc:creator>
            <pubDate>Sun, 13 Jan 2019 18:00:23 GMT</pubDate>
            <atom:updated>2022-02-13T09:03:18.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ey-z5-fOuvA7ki8U_EXS-g.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>UX Research with children</h3><h4>What to keep in mind when running research studies with kids</h4><p>Running research studies with kids can be one of the biggest challenges for UX Researchers. In this article, I collected some useful tips on how to work with children during research studies.</p><h3><strong>Development stages</strong></h3><p>The first thing to remember is that children are not one user group. <strong>The mental and physical abilities of kids vary a lot among the different age groups. </strong>There are significant differences in how a three years old uses an interface compared to nine years old. In the next section, I collected some basic facts about the development stages.</p><p>If you would like to learn more, I recommend you to read the following book<em>: The development of Children — Michael Cole, Sheila R. Cole, Cynthia Lightfoot -Worth Publishers, 2005</em></p><p><strong>Age 3–4</strong></p><ul><li>They can’t think abstract</li><li>They can’t see in 3D on screens perfectly</li><li>They are just learning to interact with digital devices</li><li>Children at this age can’t read</li></ul><p><strong>Age 4–6</strong></p><ul><li>They can’t think abstract</li><li>Children at this age can’t read</li><li>They like to create and explore on their own</li><li>Sharing their achievements is important</li></ul><p><strong>Age 6–8</strong></p><ul><li>Children at this age learned how to read, but not all of them has mastered it yet</li><li>Their attention span is much longer than kids in previous age groups</li><li>They learned to follow rules</li><li>They are more focused</li><li>They are keen to get it right</li></ul><p><strong>Age 8–10</strong></p><ul><li>They are more independent</li><li>They start to question adults</li><li>They like to behave like experts</li><li>They can evaluate and solve complex problems</li><li>They are not afraid to bend the rules</li></ul><p><strong>Age 10&lt;</strong></p><ul><li>This is the pre-teenager and teenager age</li><li>They start to think about themselves strongly as individuals</li><li>It becomes important what peers think about them</li><li>They mastered abstract thinking</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-XTfTKC5DQzDO4EqaCV1MA.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3><strong>Research techniques</strong></h3><p>When you’re planning your research study, you have to approach it in a slightly different way than if you would do it with adults. <strong>Not every technique you use will work with children, and most importantly, not the same methods will work for kids of different age groups. </strong>To be able to gather sufficient information, apply research techniques that work for your particular age group.</p><p>If you are designing for <strong>children between 3 and 6 years old</strong>, the best you can<strong> </strong>do is <strong>contextual inquiries</strong>. Observe the children in their comfortable environment <strong>with a trusted adult present</strong> in the session. Ask them to show their favorite toys, apps, or give them your product to see how they interact with it. Avoid asking them hypothetical questions. <strong>Children at this age are not able to think abstractly. Use questions to lead the observation like</strong>: What is your favorite part of this game, can you please show it to us.</p><p>Children <strong>aged 6–8</strong> are more articulate and capable of expressing their thoughts. However, I still do not recommend solely relying on interviews. You can ask them questions, but you should combine it with<strong> co-creation</strong> or <strong>observations</strong>. You can also do <strong>group sessions</strong> with this age group. In my experience, kids at this age are very eager to follow the rules, not to make any mistakes.</p><p>Children at this age <strong>will be less likely to make any critical comments</strong> on your product. Once I conducted a usability test where none of the 12 children had any negative feedback on our app.Therefore I recommend you <strong>not to ask for direct feedback. Focus only on the behavior </strong>when evaluating the flaws of the products.</p><p>At the same usability test, children asked for help when they were not 100% about how to proceed with a task. Even if you emphasize at the beginning of the sessions that you are not testing them but the product, at this age, <strong>they will still be eager to do everything correctly and to please you</strong>. While adults are more likely to try and only ask for help when they fail, children at this age act differently. <strong>They stop and ask for help immediately if they are not sure how to go on</strong>. A gentle reassurance that they are doing fine usually helps to move on.</p><p>If you are designing for kids <strong>older than 8,</strong> it becomes more similar to how you approach adults. At this age, you can conduct interviews and will be able to gather sufficient data from them. At this pre-teenager, teenage age cool factor comes in. If you are opting for a group session, they will try to impress their peers. I found <strong>1on1 sessions (with a teacher present)more suitable</strong>. They tend to be very reasonable and helpful. The easiest to <strong>conduct the interviews/ usability test at schools. </strong>When you’re interviewing, make sure you are not looking down on them and don’t make them feel like children.</p><p>You also have to keep in mind that children get bored faster and get distracted easier. They are usually way more enthusiastic than adults, but it wears out faster. Therefore <strong>plan your session short</strong>er than you would with adults.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GO7nSekOMb-6G4vbi4NKYw.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>How to find research participants?</h3><p><strong>I recommend you contact schools directly </strong>(or kinder-gardens if you are designing for the little ones)when starting to recruit to your study. Try to build up a long-term agreement with some schools. I would suggest you <strong>contact the principals of the schools or teachers directly</strong>. Ask for a meeting in person where you can explain the details. I usually created a short document that explains the purpose of the sessions and some practical information. In the case of a usability test, I also included information and images about the product we will test with the children.<strong> The teacher/director can distribute these documents and get the consent of parents</strong>. This way, you can access a large number of children relatively easily.</p><h3>Legal forms</h3><p>Another aspect of researching/testing with children is <strong>legal consent</strong>. <strong>You have to have permission from the parents.</strong> Teachers can help you to distribute these forms to parents.</p><h3>Incentives</h3><p>While vouchers work well for adults as incentives, I don’t recommend them for children. Older children can end up buying things their parents/teachers would not allow. I advise you to prepare <strong>an appropriate gift package</strong> relevant to their age/gender. <strong>Parents/teachers can help </strong>you with that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-tK6kG9TrJJpHQVQcCSEJQ.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>Take away</h3><ul><li>There are huge differences among the different age groups</li><li>Apply research techniques that work for your particular age group</li><li>Plan your sessions shorter</li><li>Collaboration with schools, teachers can help with recruiting</li><li>Always get consent from parents</li><li>Be smart with the incentives</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75539789d3e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inclusive Web Design]]></title>
            <link>https://medium.com/@norapekker/inclusive-web-design-7c99690bc0cf?source=rss-9cd7953d9457------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c99690bc0cf</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nora Pekker]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 17:56:58 GMT</pubDate>
            <atom:updated>2022-02-13T09:12:34.880Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to design accessible user experiences</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cx3MuNwYOjrLObfXjsWigg.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><p>An <strong>estimated 15% of the entire population lives with some form of disability.</strong> It is our duty as designers to make sure that our products are accessible to everyone.</p><p>In this article, I would like to give some tips on <strong>how to make your product accessible to a wider audience </strong>by considering the requirements of people with diverse needs.</p><h3>Types of disabilities</h3><p>First do not treat people with disabilities as one group.<strong>There is a wide range of disabilities which include varying degrees of capabilities and needs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wJX70UbQjdls-Da2J6jlw.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3><strong>Visual impairment</strong></h3><p>An estimated 253 million people live with vision impairment.<strong>Visual impairment has a broad scale</strong>, starting from moderate vision impairment to blindness. According to WHO it’s classified into four different groups:</p><ul><li>normal vision</li><li>moderate vision impairment</li><li>severe vision impairment</li><li>blindness</li></ul><p><strong>Moderate vision impairment: </strong>Most commonly related to macular degeneration<strong> amongst people over the age of 65</strong>. <strong>Reading small</strong> or even average size <strong>texts can cause problems.</strong></p><p><strong>Severe vision impairment: </strong>One of the most common reasons behind it is glaucoma. People with severe vision impairment have to enlarge the screen to see and process all the information. Most of them use<strong> screen magnifying software and high-resolution settings</strong> for daily operations.</p><p><strong>Colour blindness: </strong>The percentage of people with color blindness can reach up to 8% among men. Color-blind people <strong>experience colors differently</strong> than people with normal eyesight. If the design communicates certain information only with colors, those will be lost. <strong>Reading text with a low contrast value can also cause problems.</strong></p><p><strong>Blindness:</strong>Blind people use <strong>screen readers and braille displays</strong> to understand the information on the screen. These devices can only interpret text format.</p><h3>Hearing impairment</h3><p>Around<strong> 466 million people worldwide</strong> have disabling hearing loss. In the world of the web, the primary source of information is images and text. We could rightfully conclude that people with hearing impairment are not facing any particular difficulty while browsing the net. However, this is not entirely true. Most people with severe hearing impairment usually use ASL (American Sign Language) as their primary language. Although they can read and understand written language, <strong>complex grammar, and lengthy text can scare them away</strong>. As videos are becoming a popular source of information online, more and more<strong> people get excluded from the information because no caption is provided</strong>.</p><h3>Autism</h3><p>According to WHO: <strong>1 in 160 children has an autism spectrum disorder</strong> (ASD). ASD refers to a range of conditions characterized by some degree of impaired social behavior, communication, and language, and a narrow range of interests and activities that are both unique to the individual and carried out repetitively.</p><p>For users with ASD, it is <strong>more challenging to keep focused and achieve certain goals on a website</strong>. It is more difficult for them to understand visual information or <strong>complex language expressions such as metaphors</strong>. Too many choices can overwhelm them. Too many visual elements, especially moving and flashing images, videos can distract them and prevent them from succeeding with their original goal.</p><h3>Dyslexia</h3><p><strong>Dyslexia is a common learning disability,</strong> especially amongst children and teenagers. Children with dyslexia have problems reading fluently. It might also cause difficulties in writing and spelling.</p><h3>Physically challenged users</h3><p>For people with disabilities in movement such as cerebral palsy, the biggest challenge is navigation in general. In most cases, they <strong>can not operate a mouse, keyboard at all or not precisely.</strong> They often use special keyboards or joysticks to navigate on the web.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMD7dDIb_-991a0f3zj_CA.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3><strong>Special user groups</strong></h3><p><strong>Non-native speakers:</strong> It is possible that people who visit your website speak a different language than the language of your product. For non-native speakers, it is especially important to use <strong>simple language.</strong></p><p><strong>People with limited access to technology:</strong> Some people face difficulties when browsing the net because of t<strong>echnological limitations.</strong> Many use <strong>outdated browsers</strong> usually because they do not know how to update them as well as that the hardware used is not powerful enough to run a newer version of the browser. <strong>Old hardware or a weak internet connection</strong> can also result in long load times during browsing.<strong> Outdated monitors</strong> may not be able to display the designs accurately. For example, text with low contrast might be unreadable on old devices.</p><p><strong>Children: </strong>Another special group to design for is children. They have <strong>different needs than adults. </strong>Their needs and capabilities can vary significantly between different ages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Az-uAY7KINBZd1QjQPOELA.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>Integrating the process</h3><p><strong>Not a version: </strong>One of the <strong>most common misconceptions </strong>with accessibility is that it has to be <strong>a version of the website </strong>made for people with disabilities. There are several problems with this approach. First of all, these versions are only meant for people with visual impairment and do not consider any other user groups with special needs.</p><p>Often these versions only contain a <strong>limited amount of information or limited functionalities</strong>. It is also costly to maintain several versions. Therefore they lack regular updates and contain outdated information.</p><p>Another common problem is that <strong>access to these versions is not easily recognizable by the target audience</strong>. In many cases, the users do not manage to reach or access those versions of the website.</p><p><strong>Early integration: </strong>In recent years companies have realized the need for UX professionals to be involved from early on in the product development flow. Research and user needs became the main focus of the design processes.</p><p>The same is true for accessibility. I<strong>t should be integrated into your entire design flow.</strong> You should include people with a wider range of abilities in your research and keep their needs in mind during the design process, as you would do with any other users.</p><p><strong>Team effort: </strong>It is not only a design effort that makes a website more accessible. <strong>Most of the work is done on the code level or in the content.</strong> It is important to raise awareness about accessibility amongst the entire team.</p><h3>Practical tips</h3><p>Accessibility doesn’t mean compromising your visuals but instead implies a neat and inclusive design for everyone. Most of the work is done at the code or content level. You do not have to make sacrifices in your aesthetics to make your product accessible.</p><p>Most of the steps you have to take to improve accessibility will remain invisible to your able users. You will not harm their experience at all. On the contrary. Every visual improvement that will help your disabled users, will in general benefit all the users.</p><p>Now let’s see how you can improve accessibility in your designs.</p><h3><strong>Accessibility 1.0</strong></h3><ul><li><strong>Clarity:</strong> Keep designs as clear and concise as possible</li><li><strong>Avoid overloading</strong> the user with too much content.</li><li><strong>Consistency:</strong> Your designs should be consistent across several aspects including style, navigation, typography, use of language, etc.</li><li>Create <strong>responsive designs</strong> which can be accessed from all types of devices</li><li><strong>Optimize</strong> your designs <strong>for all the major web browsers</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEejWsTdVL50xdX1kIQGRQ.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3><strong>Navigation</strong></h3><p>One of the most important elements of a website is navigation. <strong>Clear navigation helps everyone, but for some, it is indispensable.</strong></p><ul><li>Guide your users<strong> step by step</strong></li><li>Show titles, <strong>breadcrumbs</strong> to show where they are at</li><li>Show <strong>alternative ways for navigation</strong> like: menus, sitemaps, search bars</li><li>Try to<strong> minimise steps</strong></li><li>Use logical sections on your site and <strong>mark the different sections in code </strong>. This enables users with screen readers to be able to navigate between the sections.</li></ul><h3><strong>Interaction</strong></h3><p>When we are talking about the accessibility of interactions, one of the most important thing is <strong>affordance</strong>. Make sure it is clear for your audience what they can interact with. <strong>Use buttons instead of text links whenever it is possible</strong>. Make sure your buttons are designed based on web standards and they clearly show their different states.</p><p>Once they have found what they can interact with it is equally important that those interactions can be executed easily. <strong>Try to minimise the need to use fine motor skills</strong> when using interactive elements.Some users will prefer a keyboard over a mouse, do not forget about them.</p><p><strong>What do you have to pay attention to?</strong></p><ul><li>Make sure the<strong> clickable areas are large enough</strong>, especially on touch devices.</li><li>Make sure you leave <strong>enough white space between interactive elements</strong>.</li><li><strong>Minimise complexity </strong>in interactions like multilevel menus where precise mouse movements are required.</li><li>Make sure your users <strong>can use a keyboard to navigat</strong>e and execute functions with tabs, enter, etc.</li></ul><p><strong>Try to prevent errors.</strong> No one likes to fill in a form again because of a missing field. Make sure you do all you can to prevent mistakes. For example, if there is a missing/incorrectly filled text field warn the user before submitting the entire form.</p><p><strong>Pay attention to forms:</strong></p><ul><li>Provide a <strong>logical tab order</strong></li><li><strong>Name your input fields</strong> properly</li><li><strong>Name</strong> your input fields <strong>in code as well</strong></li></ul><p><strong>Do not rush your users.</strong> People with autism or dyslexia, for example, might need more time to read the texts carefully or to navigate on your site. Setting a time limit might prevent them from succeeding with their goals.Do not use time limits on your website unless it is necessary. (For example, banking application or other security reasons might justify the time limit.) If you have to use a time limit make sure it can be expanded at the request of the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZ2pcvlwMkwPUig6W3fj0w.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3>Content</h3><p>When you are thinking about accessibility the content of the website is just as important as the interface.</p><h3><strong>Text:</strong></h3><p>All texts must be easily readable for everyone. People with moderate visual impairment have difficulty reading small text. Make sure you are using <strong>large enough font sizes</strong>. Low contrast between text and the background can also be challenging because the texts can easily ‘disappear’. This can be problematic for people with limited eyesight or to anyone who is viewing your website on old monitors or their phone in unfavourable light conditions. Always <strong>keep enough contrast between your background and your text.</strong> You can easily check that with online contrast checkers. Some people have so severe visual impairment that they will enlarge the text of your website from the browsers. Make sure you are using relative text size, not fixed, so it is easily scalable.</p><p>Around 8% among men is colour-blind. Therefore, it is very important to<strong> not use colours as the only way to show information</strong>. Put labels, use shapes or textures to make sure that no information is lost for them.</p><p>The layout and format of the text can also help readability.</p><ul><li>Use Sans Serif fonts online</li><li>Keep enough line height between the rows.</li><li>Short chunks of texts are easier to read.</li><li>Make sure you are optimising your text for scanning by highlighting keywords.</li><li>Use bullets and lists to structure your text.</li></ul><p>Another important aspect of textual content is the language it is written in. You should use <strong>Plain language</strong> on your website. The goal of plain language is to make your text easily understandable for a wide audience.To learn more visit: <a href="https://www.plainlanguage.gov/about/definitions/">https://www.plainlanguage.gov/about/definitions/.</a></p><p>Although it might be trivial, we tend to forget that people with different degrees of literacy might be reading our content. Some of your visitors that might use your website, may <strong>not be native-speakers</strong> of your choice of language. Make sure your text is written in a simple format. <strong>Do not use jargon</strong> unless you have a special target audience (for example a medical journal).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNGTZtR4Du_nd_FB0jPHgQ.jpeg" /><figcaption>Image credit: Adobe Stock</figcaption></figure><h3><strong>Media:</strong></h3><p>The most important thing to remember is: <strong>never rely on one sense</strong>.<br>Make sure you provide alternatives. Screen readers can’t understand images so <strong>make sure you are writing a description of the image in the code</strong>.</p><p><strong>Show captions on videos</strong> so those with hearing impairments, limited language skills or simply those in a noisy environment can understand what they are seeing.</p><p>Let the user be in charge. <strong>Do not play elements automatically</strong>, like videos or starting carousels. This can be extremely disturbing to visitors with ASD for example.</p><p>For the same reason, <strong>do not use flashing</strong> or rapidly moving <strong>content</strong> on your site, this can be annoying to everyone and potentially dangerous for users with epilepsy.</p><p>Size is critical for both images and videos. We tend to believe that fast internet access is obvious these days, but it isn’t for everyone. <strong>Too large images and videos load very slowly</strong> or not at all on small bandwidth.</p><h3>Take away</h3><ul><li>Include people with a wide range of abilities in your research</li><li>Keep their needs in mind during the entire design flow, from research to testing</li><li>Accessibility is never a version of the original website</li><li>Making your product accessible will not ruin the aesthetics</li><li>Making a product accessible is a team effort</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c99690bc0cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>