<?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 Isuru Ranaweera on Medium]]></title>
        <description><![CDATA[Stories by Isuru Ranaweera on Medium]]></description>
        <link>https://medium.com/@isuruasiri?source=rss-17220954e05e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QLa-NKQ__uIhrv3ZDh6yfQ.jpeg</url>
            <title>Stories by Isuru Ranaweera on Medium</title>
            <link>https://medium.com/@isuruasiri?source=rss-17220954e05e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:43:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isuruasiri/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[How to start a UX Research Repository?]]></title>
            <link>https://medium.com/@isuruasiri/how-to-start-a-ux-research-repository-e031713bc5ca?source=rss-17220954e05e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e031713bc5ca</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[research-repositories]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Isuru Ranaweera]]></dc:creator>
            <pubDate>Mon, 06 Feb 2023 16:56:33 GMT</pubDate>
            <atom:updated>2023-02-06T16:56:33.288Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a User Research Repository?</h3><p>User research repositories, commonly referred to as UX repositories, give product teams a central location to collect, organize, and collaborate on user research for the purpose of enhancing products. These technologies are used by product teams and developers to categorize customer input data and come up with potential solutions or new product features to handle it appropriately. Team members utilizing UX repositories can categorize comments using custom tags rather than sifting through paragraphs of data to identify interesting trends. Additionally, certain archives for user research automate processes including labeling, user sentiment analysis, and trend discovery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i9dgmQpBWKwCOLVF" /></figure><p>Source: <a href="https://www.nngroup.com/articles/research-repositories/">Research Repositories for Tracking UX Research and Growing Your ResearchOps (nngroup.com)</a></p><h3>What is included in a Research Repository? A research repository’s content can be divided into two categories:</h3><ul><li>The input for UX research is data used for planning and conducting research.</li><li>Study results and reports are the end result of conducting UX research.</li></ul><p>There are certain things to keep in mind before creating a repository. It is important to analyze the procedures related to UX and technologies currently being used (or anticipated to be utilized) in your current company and create a plan of the research process, or service design, to show how research is begun and how development teams use the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AECDy8KqowQRtTTx" /></figure><p>Source: <a href="https://www.nngroup.com/articles/research-repositories/">Research Repositories for Tracking UX Research and Growing Your ResearchOps (nngroup.com)</a></p><p>A research repository can include the following information:</p><p><strong>Infrastructure</strong></p><ul><li>The<strong> goal and vision statements </strong>of the infrastructure research team explain who the team might be, how it operates, and the way it plans to operate in the future. Others may use this information to better understand the team’s capabilities as well as what they might anticipate and ask for. User research team’s objective might be something like this: To maximize the utility, usability, efficiency, enjoyment, and support for the organization’s vision. For all services and systems provided by the company, the user research team can begin research on users and customers, whilst providing advice.</li><li>The team might learn about or be prompted by a procedure and the justifications for various study types thanks to <strong>descriptions of research methodologies</strong>. Best practices and method descriptions can help to encourage persistent, superior work and even impart knowledge to less experienced researchers.</li></ul><p><strong>Research planning</strong></p><ul><li>The team comprising of the researchers and others can look into the most crucial areas to investigate rather than on each and every product feature with the help of <strong>strategic research plans</strong> for the organization and for specific projects, such as those found within a research roadmap. These are simple to locate and retrieve when kept in a research repository.</li><li>By revealing the method of research, its location, time and date, and the subject being examined, <strong>schedules </strong>make research accessible to everyone. With this knowledge, anyone can request to participate in learning or look for results at the end.</li><li><strong>Research plans </strong>that are in-depth explain the what and how of the study. They act as a vision document to unite stakeholders and the rest of the organization when kept in a repository.</li></ul><h3>The need for a Research Repository</h3><p>In most organizations, the user research conducted by product designers often stayed at the bottom level and was rarely used again for future projects. Unless the team knows who had worked on a project, it is incredibly difficult to consult previous research work. In most cases, several departments in an organization could be conducting their own research and it is a hassle to find out who worked on what research and how to retrieve the findings.</p><p>What transpired after these observations to UX researchers is that previous user research was under-expolited. If there was a centralized location where everyones’ research results and findings could be stored, it would only enrich the knowledge of the team and allow them to better answer the questions of users.</p><p>This is the main motive behind building a User Research repository.</p><h3>Steps for creating a Research Repository</h3><ol><li><strong>Defining the vision</strong></li></ol><p>It is important that organizations clearly articulate their vision for a research repository right from the beginning. Creating a new UX research position requires structuring the practice and outlining the goals for user research practice. User research should, however, also be “generative,” or assist the business in “building the appropriate thing”:</p><p>The goal of user research should be to ensure that the users’ voices are acknowledged and heard by team members as they make decisions for products. The vision could be to “empower a strategic, user-centric vision” and “assist collaborators in making data-driven decisions” through user research.</p><p><strong>2. Grasp of Atomic Research</strong></p><p>A good understanding of this model would give a solid start and is a great help for restructuring the repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/0*GbaYhM5Dpx46gMXo" /></figure><p>Source: <a href="https://consider.ly/blog/atomic-ux-research/">Atomic UX Research as a Research Framework — The User Research Platform (consider.ly)</a></p><p><strong>3. Define the users</strong></p><ul><li><strong>Owners</strong> are the repository’s initial contributors. They organize the repository, laying out the rules and procedures. Maintenance and assisting in determining which sources of user feedback ought to be utilized are some of their tasks.</li><li><strong>Regular contributors</strong> continuously update the repository with all the data they’ve gathered while conducting their research, and they also share insights when they come across something noteworthy.</li></ul><p><strong>4. The correct tools</strong></p><p>The Atomic Research principles can be followed using free tools such as Notion or AirTable. Even a Google Sheet can be used to store links to research elements and will help in testing the methods and refining the needs.</p><p><strong>5. Taxonomy</strong></p><p>This is especially important for the research repository as it is where people come to find the information and insights that they are after. Collaboration with other teams such as the data team could help in defining the taxonomy as they may already have one in place.</p><p>The following main types of properties could be used:</p><ul><li>Type of user</li><li>Country and language</li><li>User journey moment</li><li>Domain</li><li>Feedback type</li><li>Research methodology</li></ul><h3>Maintaining the repository</h3><h4>Collaborative in nature</h4><p>As the repository only becomes valuable with the amount of data in it, the user research teams need to train other people to use it as much as possible. Documentations can be created on Notion on how to upload data, use the tool and generate insights.</p><h4>Sharing other projects</h4><p>Designers in teams should be encouraged to share their research projects so that everyone gets a good understanding and scope of the projects, and they can improve others’ work as well.</p><h3>Conclusion</h3><p>It can be a lot of work to create a UX research repository, but it can be very rewarding. It is important to keep training the teams on creating insights and have a continuous research process in place. The teams can continue to map the user feedback resources and collaborate better with other teams. A common vision and knowledge bank of main user pain points can then be established.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e031713bc5ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I switched from Software Engineering to UX]]></title>
            <link>https://medium.com/design-bootcamp/how-i-switched-from-software-engineering-to-ux-7debbeffd08?source=rss-17220954e05e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7debbeffd08</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[virtusa]]></category>
            <dc:creator><![CDATA[Isuru Ranaweera]]></dc:creator>
            <pubDate>Mon, 24 Oct 2022 17:40:27 GMT</pubDate>
            <atom:updated>2023-04-08T03:47:44.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6Psha6mOj5v6LKUu" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Where I come from</h3><p>Hi everyone! My name is Isuru and I hail from the little island of Sri Lanka in the Indian Ocean. I am 27 and I am currently working as a UX Designer for Virtusa, a global IT services company. I recently finished my Bachelor of Software Engineering from the Kingston University in UK with a first class.</p><p>I developed an interest towards computer science a couple of years ago and thanks to the internet, I was able to learn almost everything all by myself. YouTube and Udemy helped me a lot and I still to this day use these platforms to improve my knowledge!</p><h3>My first internship</h3><p>Little more than a year ago in April 2021, I found my first internship in software engineering at a small startup in Colombo. This is where I was able to put my skills in coding and technology to the test. I was able to learn various technologies such as NextJS, ReactJS, Express, and React Native. The exposure to mobile development that this internship gave me really opened my eyes to the world of mobile technologies and development. I learnt to build skills for the Amazon Alexa platform and was able to enjoy this more than I expected.</p><p>However, I knew in my heart that this was not what I wanted to do long-term. I was drawn towards the artistic side of things and intrigued by the beautiful interfaces that people have built and shared on platforms such as Dribble and Behance. At the time I did not have much idea about UI and UX and therefore I turned to google and started researching more on this topic. I was able to find some really good YouTube channels on UX such as UX Mastery, The Futur and Flux. The content on these channels really inspired me to follow a career in UX.</p><h3>Building my portfolio 🎨</h3><p>The more I researched about UI and UX, the more it became apparent that I need to build a portfolio in this area. However, I was still confused about the difference between UI and UX. It turns out that these two are very different things and employ different people with specialized skills. However, in Sri Lanka, most of the job openings still goes as UI/UX and there are only few jobs for only UX specific roles.</p><p>I was also working part-time for my brothers online clothing business, and I knew that this would be a good place to start for my portfolio. The business is called ‘Prime Culture’ and you can view its website here — <a href="https://primeculture.co/">Prime Culture — Comfort, Style &amp; Quality</a>. The business sells athleisure and gym wear for the local and international market through a WordPress website. I thought of creating a mobile app design for this business and therefore dabbled around with Abode XD for the first time. Little by little, I was able to build the mobile app screens using images from the website to make it more visually pleasing. Thereafter, I watched a couple of videos on YouTube to learn how to make a portfolio. I landed on one video which taught me how to create a beautiful portfolio and I followed it to make my portfolio. After a few weeks, I was ready with my portfolio, and I was bit proud of my achievement.</p><h3>Switching to UX</h3><p>After my first internship ended after 6 months, I focused on building my UX portfolio. At the time, I did not have much understanding of this field and I was just focusing on designing interfaces. Around January 2022, I got an opportunity to attend a career fair organized by my college. This event was attended by Virtusa, one of the top employers in Sri Lanka in the IT industry. I decided to attend this and made sure to take my portfolio designs on my iPad. At the event, a person first asked me in which area I was interested to apply jobs for. I immediately said I wanted to go into UI/UX side and then he directed me to a row of desks on the left side of the room. I was greeted by a panel of three people from Virtusa. I was further asked whether I wanted to go into UI or UX. I was bit confused at first because I still believed that these two fields were the same! How wrong was I as I soon found out!</p><p>I mentioned that I was interested in UX and then a couple of people started interviewing me. They asked me about my background and why I thought of coming into UX side. I told them that I completed an internship in software engineering and that I really did not enjoy coding as much as I expected and therefore wanted to try something in the designing side. Then they were interested to see my portfolio and I showed them all the designs that I was able to create. I was asked questions from my designs, specifically the reasons I used certain design elements, colors and my choice of typography and so on. I was also questioned on the design thinking process, which I had no clue about at that time!</p><p>Here’s a few links to learn about design thinking process!</p><p><a href="https://www.interaction-design.org/literature/article/what-is-design-thinking-and-why-is-it-so-popular">What is Design Thinking and Why Is It So Popular? | IxDF (interaction-design.org)</a></p><p><a href="https://www.nngroup.com/articles/design-thinking/">Design Thinking 101 (nngroup.com)</a></p><p><a href="https://careerfoundry.com/en/blog/ux-design/design-thinking-process/">A Complete Guide to the Design Thinking Process in 5 Steps (careerfoundry.com)</a></p><p>After a few more questions on a case study related to an app for farmers and their activities, I was given the chance to ask them questions. I used this opportunity to learn more about the UX field and what the day to day is like being a UX designer at Virtusa. After like 30 minutes, I was able to conclude my interview and leave the premises.</p><h3>First UX job! 💻</h3><p>The very day I received an email and I got to know I was accepted into an Associate Engineer Technology UX! I was ecstatic and really happy I made it! After a few grueling and tiresome weeks of preparing documents and verification process, I was able to formally become part of the company. My team includes several other UX engineers and a UX architect who handles all UX related matters within the company.</p><p>The first few months, we were not allocated to any projects, but we had plenty of exams and internal certifications to complete as part of the hiring process. After this was done, our UX seniors introduced us to the UX field and gave us a lot of resources including books and YouTube channels to improve our knowledge. Then came the time for them to see us in action as we got a case study to complete within a month! All the new UX people got together for this, and we went through the whole UX process, all the way from research to wireframing and prototyping. The seniors were happy with our presentation and encouraged us to continue improve our UX skills and design skills.</p><p>This was a highly enjoyable process and I got to know my teammates on a deeper level. I am currently working in my ninth month with the company and I am allocated to a project with a British Telecommunications company.</p><h3>Career goals🔥</h3><p>My long-term career goal is to improve my UX skills, build a better portfolio and land a more senior role in UX after I gain some experience. I also began the ‘Google UX Design Certificate’ which is a 7-part intensive course for beginners to UX. This course has taught me so much new information about this field, and I would highly recommend it to anyone thinking of starting a career in UX. I will leave the link to this course below! Thank you!</p><p><a href="https://www.coursera.org/professional-certificates/google-ux-design?utm_source=google&amp;utm_medium=institutions&amp;utm_campaign=gwgsite&amp;_ga=2.264888587.502921991.1666633010-108955762.1666633010">Google UX Design Professional Certificate | Coursera</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7debbeffd08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-switched-from-software-engineering-to-ux-7debbeffd08">How I switched from Software Engineering to UX</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 I created an Amazon Alexa Skill: From Ideating to Publishing]]></title>
            <link>https://medium.com/@isuruasiri/how-i-created-an-amazon-alexa-skill-from-ideating-to-publishing-c3c8bd3417f1?source=rss-17220954e05e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3c8bd3417f1</guid>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[alexa-skills]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Isuru Ranaweera]]></dc:creator>
            <pubDate>Thu, 14 Oct 2021 09:56:07 GMT</pubDate>
            <atom:updated>2021-10-14T09:56:07.532Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>My approach as a Software Engineer</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zZTs7joR96D5NRkj.png" /></figure><p>Amazon Alexa is a cloud-based voice service that powers all Amazon Echo devices. There are many things that you can perform using just your voice with these Alexa-powered devices such as creating to-do lists and creating alarms. Alexa skills are tasks that users can request through this voice service. An Alexa Skill can be considered a voice-driven Alexa app.</p><h3>Ideating</h3><p>I am currently a software engineering working in Sri Lanka and I was able to come across this niche market in technology known as Alexa skills through my first tech internship. After several weeks of learning React, React-Native and Next.js were introduced to <strong>Amazon Alexa Skills</strong>. This project involved creating a skill that could be deployed on the Amazon Alexa marketplace, which was the ultimate goal.</p><p>To generate ideas for the project, a brainstorming session was carried out that enabled me to come up with several different ideas. Some of the initial ideas included a skill to:</p><ul><li>Track train schedules in Sri Lanka, find out the departure and arrival time of the next train, find out a train schedule for a specific day or date, find out if there are any delays, find out which train arrives at a destination</li><li>Check bank balances, expenses, and pending transfers</li><li>Check Formula 1 schedules and points.</li></ul><p>However, the idea that stood out for me personally and for my manager was the idea for a <strong>skill-based on the ‘Friends’ TV show</strong>. This skill would enable users to hear the funniest dialogues between the cast in this show. Having won 6 Emmy awards, this was one of the most popular TV shows ever created and it has a huge fan base. This was one of the most compelling reasons to go ahead with this idea since there is a large user base from throughout the world. It was decided to call this new skill ‘Central Perk’ based on the iconic café used throughout the TV show.</p><h3>Challenges and how I overcame them</h3><p>Having studied technologies such as HTML, CSS, JavaScript, C#, Java, Python, and React in college, transitioning towards Node.js chosen for creating the Alexa skill was not that difficult for me. Amazon has a set of tools that help fresh developers get accustomed to the developer environment fairly quickly including the <strong>Alexa Skills Kit (<em>ASK</em>) </strong>which is a framework that allows the creation of <em>skills.</em></p><ul><li><em>Getting accustomed</em>: It took a bit of time to get used to the development environment and I was finding it difficult to grasp the different terminology such as intents and voice interaction models. Nevertheless, navigating around the development environment for a while enabled me to get comfortable with the interfaces.</li><li><em>Custom slots:</em> The initial struggle was to design the skill in such a way that allows users to access funny dialogues from different characters in the show. This required me to create slots and assign the character names: Ross, Phoebe, Rachel, and so on to these. This proved to be a challenge initially as I was confused about where the slots have to be placed in the development environment and how to access these slot information. Upon further investigation and help from my manager, I was able to correctly configure these custom slots so that the dialogues align with the correct character.</li><li><em>The flow of the skill: </em>In addition, configuring the flow of the skill from the initial initiation and subsequent steps required a bit of planning. Since this is a voice app, it was especially critical that I focused on making sure that the user is not left in the dark at any point in the skill and directing them towards the intended destination. This task was further complicated with the addition of a new requirement to enable in-skill purchasing within the skill. Therefore, the flow of the skill had to be freshly generated to support this.</li><li><em>In-skill purchasing: </em>This was a whole new challenge in itself as it required the addition of new intents to purchase the skill, refund, process subscriptions, and cancel subscriptions. To help me with this process, I was given a template skill to follow by my manager which I found to be helpful. In addition, there was a couple of online video tutorials and articles to help me further. After a few days of tinkering, I was able to come up with the proper intents and the general flow of the skill was complete.</li><li><em>Content: </em>At this point, I was still a complete newbie to the ‘Friends’ TV show. I know! I know what you are thinking but that was the truth. How could I possibly come up with funny dialogues if I have not watched the show right? Therefore without further ado, I started binge-watching from Season 1 and quickly fell in love with the show. I also remembered to note down the noteworthy and hilarious dialogues between the cast members. These dialogues are then required to be ordered according to the character names and stored in a JSON file to be accessed from the skill. As the skill had in-skill purchasing, I had to create two JSON files, one for the free tier with limited content and one for the premium tier with additional content.</li><li><em>Testing</em>: The development of the skill was not at all complete without testing it. Oh boy! Testing was initially the toughest job as constant errors were appearing and required many hours of debugging. Debugging is not particularly my strong suit and therefore I was spending a considerable amount of time absorbed in this process. A feature known as ‘CloudWatch’ built into the Alexa development console is intended to help developers easily debug and test the skill. This enabled me to pinpoint where the errors were occurring but it did not explain why it was occurring. After several days of debugging and testing the skill, it was finally ready to be sent to certification and published. The skill was flowing nicely, the in-skill purchasing was working and the correct dialogues were uttered according to the character names.</li></ul><h3>Publication</h3><p>The process of certification and publishing is very much straightforward in the Alexa Development Console. It requires you to enter all the details of the skills, intended audience, your subscription fee, the invocation name, and any logos that you may want to use. After this process is complete, it was ready to be sent to Amazon for final verification. This was the moment that was the most difficult, the waiting. We received a response from Amazon after a couple of days and it turned out we had a few errors in our code.</p><p>Upon fixing these errors, we sent it back for final verification. and this time around, we received the good news that the skill had been verified and it will be published on the Amazon Alexa Skills marketplace. Finally getting your product to market was a huge step and I felt incredibly happy along with my manager at having accomplished this goal.</p><h3>Final thoughts</h3><p>If you are also wondering or are curious to create an Amazon Alexa Skill, I think I have done justice with this article. Amazon Alexa Skills are an exciting field in this vast technology space and you will surely have fun along the way by creating a skill that you are passionate about and will hopefully bring value and entertainment to the world.</p><p>So, therefore, please do not hesitate to start! There are a bunch of tutorials that can help you get started and there are also a lot of template skills on games, food ordering, music and audio, smart home, flash briefing, and news and knowledge skills. Have fun and hopefully my experience will enable you to envision your own Amazon Alexa Skill soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3c8bd3417f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>