<?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 Tyler La on Medium]]></title>
        <description><![CDATA[Stories by Tyler La on Medium]]></description>
        <link>https://medium.com/@tylerla?source=rss-257b8d26f432------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bj4uMyR2N0u5CLkT.</url>
            <title>Stories by Tyler La on Medium</title>
            <link>https://medium.com/@tylerla?source=rss-257b8d26f432------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:53:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tylerla/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[On walking and solitude]]></title>
            <link>https://tylerla.medium.com/on-walking-and-solitude-58b869e495c8?source=rss-257b8d26f432------2</link>
            <guid isPermaLink="false">https://medium.com/p/58b869e495c8</guid>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[solitude]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[digital-minimalism]]></category>
            <dc:creator><![CDATA[Tyler La]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 09:05:42 GMT</pubDate>
            <atom:updated>2020-12-22T21:22:31.081Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQGvd5VMrKzH4qyIRHF4PQ.jpeg" /></figure><p>I moved to the States by myself at 17, whenever I felt homesick or had a hard time adjusting, I skipped the train to take a walk home. On days when I felt burned out and couldn’t pick myself up, I turned my phone off and walked around Castle Island. When I graduated college and wasn’t satisfied with my career prospect, I spent hours walking along the Charles River. When I lost a loved one and couldn’t fly back to Saigon, I took the day off and drove to Walden Pond, walking and contemplating in silence.</p><p>Walking started out as a way for me to escape from the moment and create a space to unbottle my feelings. The silence of the walk took me away from the busy world and allowed my senses to emerge. I started to notice the sound, feel the air, and become more aware of my surroundings. Walking brought me back to the present and put things in perspective. In that moment of difficulty, I knew that I still have the air to breathe and the ground to stand on; they will always be there no matter how big or small my problems were.</p><p>Cal Newport defines solitude in his new book ‘<a href="https://www.calnewport.com/books/digital-minimalism/">Digital Minimalism</a>’ as a subjective state in which you’re isolated from input from other minds. Solitude and spending time alone is one of the ways our brains could process and regular complex emotions. Reflecting on my experience, walking has been how I practice solitude and push through challenging times.</p><p>During the pandemic when walking has become one of the few activities one could partake, I find myself taking a walk every morning. Instead of seeking solitude only as a refuge, I’ve learned to incorporate it as a part of the morning ritual.</p><p>A dose of solitude has provided me with clarity and a much better headspace to power through each day. I find walking provides me the same benefits as meditation does. I am able to observe my thoughts come and go. Once I give myself the time and space to notice what is bothering me, it starts to behave. I’ve learned to treat distraction and anxiety as if they were human beings wanting to be recognized and heard. The more I try to avoid or suppress, the angrier they become; my best bet is to take the time to listen. I walk first thing in the morning so I could put the racing thoughts to bed. Walking gives me a chance to look inward and ground my intention. It sharpens my focus and allows me to filter through the things that actually matter.</p><p>Practicing solitude is even more crucial when putting it into a larger context. It’s getting harder and harder to make sense of the modern world. While technology has improved many aspects of our lives, it also brings about new challenges. The year 2020 also adds to that complexity by exposing many societal issues and decay in our governing structure. We are no longer solving linear problems but are forced to navigate through layers and systems of complexities. Perhaps practicing solitude could nudge us in a better direction. We can’t solve these problems simply just by diving in, we need to take a step back and we need to do it more often.</p><p>The planets rely on the sun’s gravity to maintain their orbit. A spacecraft borrows a planet’s gravity to accelerate and redirect its path. I think of walking and practicing solitude the same way I think of gravity. I walk to organize my thoughts, to be present with myself, to make sense of my feelings, to grieve, and to heal. Taking a walk has been the gravity that most times, helps me stay in my orbit and oftentimes, gives me the extra energy to perform a slingshot maneuver and travel with a new trajectory.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58b869e495c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why designers should find the balance between systems thinking and design thinking?]]></title>
            <link>https://uxdesign.cc/why-designers-should-find-the-balance-between-systems-thinking-and-design-thinking-efdb57b9949f?source=rss-257b8d26f432------2</link>
            <guid isPermaLink="false">https://medium.com/p/efdb57b9949f</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Tyler La]]></dc:creator>
            <pubDate>Sat, 06 Jul 2019 05:57:05 GMT</pubDate>
            <atom:updated>2019-07-14T21:17:33.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AuJHd1Lwf7bVxKjTJDWxKA.png" /></figure><h3>Foreword</h3><p>It’s been a little over 2 years since I started transitioning into the design field. I received a dual degree in Marketing and Big Data Analytics. This background has equipped me with the technical capabilities for quantitative research. Whether it’s performing market research or conducting statistical analysis, I was fluent in the language of data. And systems thinking has been a big part of my work process.</p><p>During my transition to design, I’ve found myself in a position where I needed to make sense of how my background could benefit me as a designer. I started to compare between quantitative research and qualitative research, systems thinking vs. design thinking. And yes, it wasn’t an easy process.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FtzNyMk9OxjDVu%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FtzNyMk9OxjDVu%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FtzNyMk9OxjDVu%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/de2019644228eb5ede00e5fb78d23652/href">https://medium.com/media/de2019644228eb5ede00e5fb78d23652/href</a></iframe><p>Design is a discipline that thrives on constant synthesis and reflection. It’s the art of finding ways to make implicit knowledge becomes explicit. One of the things that I appreciate about design is the process of learning by doing, the art of creating artifacts to make sense of complex problems. The ultimate goal of design for me is to be able to make sense of my own thinking. The more problems that I can solve for others, the closer I am to being able to untangle information in my head.</p><p>As I write this article and reflect on my transition, I am giving myself the opportunity to go through the sense-making process. I hope to better organize my thoughts and make sense of my journey to design through writing.</p><h3>Before we start</h3><p>I will be mentioning systems thinking and design thinking a lot in this article so I will refer to them as <strong>ST (systems thinking) </strong>and<strong> DT (design thinking)</strong>.</p><h3>What is Systems Thinking?</h3><p>ST is often misunderstood due to its vast collection of tools and methods. However, just like DT, it is a philosophy. The philosophy of ST can be traced back to the work of Ludwig Von Bertalanffy in 1968 and other contributors. ST is an approach that considers how elements within a system interact and influence one another.</p><p>A system could be an ecosystem, an organization, or a specific problem domain. It recognizes that there’s a role of structure and order in the conditions that we face. It observes closely the relationships of events and data in a system, trying to identify common patterns, and anticipating the potential impact of each trade-off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iy_3bjeyfT-zJnGGul80sA.png" /></figure><p>With ST, there’s always a need to assess the overall picture and find a cause or a reason. Because of this characteristic, ST is often recognized by the Iceberg model. The model typically has 4 levels: events, patterns/behaviors, structures, and mental models. It indicates that the piece of information above the surface is only a single “event”, in other words, a mask for the real issue. To gain increased leverage for solving the problem, there’s a need to understand the system as a whole, and all levels submerged below the tip of the iceberg. It’s also useful to move up and down the underlying levels and improve the model throughout the process.</p><p>ST became widely accepted and other industries such as economics, marketing, management, etc. began to adopt its practice. Using ST as a foundation, each industry created its own systems methods and frameworks. Many thinkers associated with cybernetics, operation research, chaos theory, complexity theory, etc. also developed their own interpretation of the same concepts and applications. As technology and business problems became more complex over time, the original philosophy of ST and its tool kits became fragmented.</p><p>Even though DT considers itself to be a new discipline, the philosophy behind it was an iteration of ST. The design industry also borrowed and tweaked many terms and methods to accommodate its design process. Terms like ‘mental model’ or framework like ‘competitive analysis’ were carried over from ST.</p><p><strong>Pros</strong></p><p>✅ Problem framing</p><p>ST is sensitive to the circular nature of the world we live in. It has a tendency to explore as much as possible to find structures that hurt the system. As a result, it’s a good diagnostic tool to put the problem in its appropriate context. ST helps examine the problem more holistically and accurately before acting and jumping into conclusion.</p><p>✅ Themes and patterns recognition</p><p>ST seeks to uncover relationships among elements within a system; the process of analysis helps in understanding the interconnectedness and how each element relates to one another.</p><p><strong>Cons</strong></p><p>❌ Analysis paralysis</p><p>Because ST requires an extensive assessment of the system as an input, it creates an environment where all decisions require thorough theoretical analysis. The analysis is time-consuming, risk-taking is less prevalent, and the process could produce so much data it is impossible to act.</p><p>❌ Self-detachment</p><p>In ST, there’s a split between theory and practice. The philosophy gives the impression that an individual can step out of an organization and sees it as a system, thinking in abstract terms and changing it from the point of view of an outsider. The act of self-detachment eliminates nuances that are critical to the system. The actual experience of being in the organization is hardly considered.</p><h3><strong>What is Design Thinking?</strong></h3><p>Rapid technological development throughout the twentieth century brought about a need for a formal academic study of the science of design. The 1960s in America was the ‘design science decade’. It started with the first attempt to distant industrial and product design from engineering and science; the goal was to ‘scientise’ design processes and bring the field within the objective of rational sciences. Horst Rittel and the term ‘<a href="http://web.mit.edu/jrankin/www/engin_as_lib_art/Design_thinking.pdf">Wicked Problems</a>’, Herbert Simon and the book ‘<a href="https://www.goodreads.com/book/show/676046.The_Sciences_of_the_Artificial">The Sciences of the Artificial</a>’, Nigel Cross and the paper “<a href="http://larossa.co/cross_1982_designerlywaysofknowing.pdf">Designerly Ways of Knowing</a>” etc. are all pioneers in bringing design to the forefront.</p><p>The term DT was coined by David Kelly and IDEO was one of the companies that helped bring DT to the mainstream. Stemming classical product philosophy, DT has a systematic approach to problem solving. While the starting point is unknown, it is structured based on the desired outcome. The process is developed on the notion that you do not know what the real problem is, which requires problem solvers to focus on the needs and desires of the end-users.</p><p>DT was initially applied to business, especially product design to craft product requirements that meet people’s needs. Because of its human-centric mindset and versatility, DT is able to solve a wide range of complex problems. The philosophy is now being employed in various domains ranging from product development to organizational and societal problems.</p><p>Once DT entered the management domain, it was confronted by “wicked problems”. The cause of wicked problems cannot be traced back easily until after the formulation of a solution; it requires a more structured and systematic approach than the original DT ideology. To accommodate this, the discipline started to create its own set of methods and tool-kits. As a result, DT has adopted a systemic stance even though design thinkers do not necessarily use ST language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q9OsdjH7xwNHiYTUHiHTTA.png" /></figure><p>A well-recognized framework of the DT process is the Double-Diamond model developed by the British Design Council in 2005. It breaks down the design process into 4 phases: Discover, Define, Develop, and Deliver. The model places an emphasis on 2 modes of thinking: ‘diverge’ and ‘converge’ from which many ideas are generated, before narrowing down and selecting the best one. This happens at least twice in the design process where designers need to switch between divergent and convergent modes to confirm the problem definition and craft a solution.</p><p><strong>Pros</strong></p><p>✅ Need finding</p><p>Because of its human-centric nature, DT places a heavy emphasis on identifying human’s needs and desires. Applying DT early on in the process can help designers build rapport and develop empathy for the people they’re designing for.</p><p>✅ Iterability</p><p>With divergent and convergent thinking, DT has an iterative approach to problem-solving. Initially, the design process values the number of ideas over the individual’s quality. This opens the door for designers to come up with out-of-the-box solutions to problems.</p><p><strong>Cons</strong></p><p>❌ Lack of business integration &amp; constraints</p><p>Unlike ST, designers with a DT mindset do not perform a comprehensive analysis of the system and the relationships among its components. The solution produced by DT reflects the needs of the end-users yet it might not be feasible or central to the organization as a whole.</p><p>❌ The term DT still signifies a heavy emphasis on “thinking” and not “making”</p><p>At the end of the day, DT is a mindset. It’s impossible to extract thinking from doing; thinking alone doesn’t solve problems. Many short-term programs and school seminars aim at teaching DT within a few weeks or days; they neglect the fact that DT requires years of practice. Good designers are good thinkers, makers, and craftsmen.</p><h3>So why finding the balance between ST and DT?</h3><p>The mistake that I made early on when transitioning into design from the business field was forcing myself to give up ST to pick up DT.</p><p>The design industry as a whole has its bias. And designers and design schools, while advocating for DT, they neglect that DT and ST can complement one another. DT and ST are not mutually exclusive. The role of a designer isn’t to pick and choose which philosophical model to follow, but to recognize the limitations and develop the ability to shift between ST and DT dynamically throughout the design process.</p><p>The movement to make design a scientific discipline started back in the 1960s. It’s been almost 50 years since we started. Though we have achieved many successes, we have not yet reached the intended goal. Design as a field began to gain traction yet the benefits of DT aren’t well comprehended by top management in organizations.</p><p>I’d argue that as designers, we need to stop boasting DT but start the conversations on integrating the two. Designers need to find the balance between ST and DT in order to solve problems effectively and make impacts at a larger scale.</p><h3>How to make the transition easier</h3><p>If you find yourself in the same position as I am, a systems thinker transitioning into the design field, I hope my mistakes and reflections could save you a few dilemmas. A few things to keep in mind:</p><p><strong>Avoid analysis paralysis</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o7btPCcdNniyf0ArS%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o7btPCcdNniyf0ArS%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExMjA2M3h2a3V0cmRiZjV3bW10a3E0eWwzYTBiaTh2YmY1MnBtYTUyNCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F3o7btPCcdNniyf0ArS%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/c024468167360d75ef959adcfaed632b/href">https://medium.com/media/c024468167360d75ef959adcfaed632b/href</a></iframe><p>The starting point of ST and DT contradicts with one another. As a systems thinker, the first step in the transition is to avoid analysis paralysis.</p><p>ST starts out by formulating the problem by developing a holistic understanding of the whole situation before moving forward. This process involves many stakeholders, as a result, it is time-consuming and may lead to analysis paralysis.</p><p>Designers with ST backgrounds need to develop a good level of self-awareness, being able to recognize when they’re falling into the trap of overanalyzing the problem or collecting too much unnecessary data. A good strategy to approach this is to become comfortable with uncertainty; systems thinkers need to define the appropriate level of confidence in order to move forward.</p><p><strong>Don’t abandon ST, leverage it</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F13sbWMa0NGNq2A%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F13sbWMa0NGNq2A%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F13sbWMa0NGNq2A%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/788b6289e0d23cde5185014f6ee992f4/href">https://medium.com/media/788b6289e0d23cde5185014f6ee992f4/href</a></iframe><p>Because DT is on a rise, it doesn’t mean it ST is going away. ST is particularly good at breaking things down into components for better understanding. Applying this to the design process, designers can evaluate design feasibility efficiently. ST will provide designers the ability to balance multiple stakeholders’ needs, align design solutions with business goals, and keep engineering constraints in check.</p><p>Another potential benefit of ST is defining the interactions of the interface. ST can help designers identify the order of the interactions, how each component interact with one another, and assess how much value it could add to the whole system.</p><p><strong>Don’t just be a thinker, be a maker</strong></p><p>The transition is hard, especially for those who did not have a formal background in design. But as systems thinkers, we are good at diagnosing problems. Use this skill to assess your strengths, shortcomings, and draft a plan to bridge those gaps. Good craftsmen aren’t created overnight. Stay humble, have curiosity, get a mentor, follow other designers, and give yourself all the opportunities to learn and practice design skills.</p><p>If you want to look for an inspiration, my favorite is t<a href="https://medium.com/@tiantianxu">he 100-day project</a> by Tiantian Xu.</p><h3>Closing</h3><p>I don’t think my transition to design will ever be complete (and it’s a good thing). There will be many things that I need to learn and many skills that I want to practice. And every day, I am reminding myself that design is not black and white. It’s not systems thinking vs. design thinking, or quantitative vs. qualitative. Coming from a different discipline and having a variety of skill sets can only benefit you as a designer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efdb57b9949f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-designers-should-find-the-balance-between-systems-thinking-and-design-thinking-efdb57b9949f">Why designers should find the balance between systems thinking and design thinking?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The experience of attending a 3-hour prototyping hackathon and things I learned]]></title>
            <link>https://uxdesign.cc/the-experience-of-attending-a-3-hour-prototyping-hackathon-and-things-i-learned-d6532ec42ba1?source=rss-257b8d26f432------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6532ec42ba1</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-challenge]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Tyler La]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 19:04:38 GMT</pubDate>
            <atom:updated>2019-07-22T04:48:44.306Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>What I learned attending a 3-hour design protothon</strong></h3><p>Last month, my friends and I from the <a href="https://mhcid.washington.edu/">Masters of Human-Computer Interaction + Design</a> program attended a 3-hour prototyping hackathon (aka protothon) to put our design skills to practice. The event was sponsored by Google Cloud Platform and was hosted by <a href="https://www.facebook.com/Dubstech/">Dubstech</a> at the University of Washington.</p><p>The design prompt:</p><blockquote>“A 2015 Google study found about 60% of millennials cook with their smartphone in hand. Design a solution that simplifies the cooking process. Users should be able to navigate through the platform to find helpful information that would adapt to their needs for planning, prepping, and cooking a meal.”</blockquote><p>The cooking experience can vary significantly depending on the context that millennials are in. There could be multiple challenges at each phase of the process from planning and prepping to cooking. The experience is also different for those that do big-batch meal prep vs. those that cook with a small portion on a daily basis. Leveraging <a href="https://www.thinkwithgoogle.com/consumer-insights/cooking-trends-among-millennials/">existing research</a> and our personal experiences, we speculated that millennials struggle most in the prepping and cooking phase. There are 2 main challenges that millennials are facing:</p><ol><li>There’s a lot of task-switching between reading cooking instructions and prepping ingredients.</li><li>Cooking apps and their instructions currently don’t personalize or accommodate people’s cooking styles and preferences.</li></ol><p>In 3 hours, our team went through the design process from discussing the user journey, brainstorming, and prototyping high fidelity screens. After the discussion, while Yomna and I defined in-app structure and interactions, Oliver turned paper sketches into high fidelity mockup screens. We then pitched Google Chef to the judges and the protothon attendees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZRCinujCWLO4fKXUufTYpw.jpeg" /><figcaption>Google Chef won the competition and each of us received a Google Home Mini (thanks Google!).</figcaption></figure><h3>About Google Chef</h3><p>Google Chef is a conversational partner that guides users through the cooking process. Making cooking handsfree, personal, and easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-NvSVNnHut16qn94CNQ-A.png" /></figure><h3>What I’ve learned</h3><p><strong>Embrace uncertainty</strong></p><p>Time was the biggest constraint for the whole experience. While I would have loved to have a thoughtful design process that required more user research than just some quick searches, I had to be realistic with our time. We definitely didn’t explore the full spectrum of challenges that millennials face during the cooking process, yet the experience allowed me to feel more comfortable moving forward with uncertainty. This 3-hour experience articulates a crucial perception that also applies to any full-scale project. There are always more things to learn and a desire to conduct more research, identifying what the right level of confidence is and when to move forward is a critical skill that helps designers carry out an efficient design process.</p><p><strong>Teamwork and time management</strong></p><p>One of the factors that helped our team win the competition was trust and time management. We communicated and leveraged each other’s strengths and skill sets as soon as we received the brief. Once trust and expectations were well established, the entire collaboration effort fell into place when it came to brainstorming, generating ideas, wireframing, and producing high-fidelity mockups. To make sure we wouldn’t fall into any rabbit hole or overspend our time in a particular area, our team rigidly kept track of time for each step while providing good amount flexibility for the overall process.</p><p><strong>Have fun!</strong></p><p>Above all, hackathons serve as a platform to help designers practice their skills and bring people with similar interests together. Competition is only an entertaining component that helps make the experience fun and incentivizes teams to perform better. When attending a hackathon, walk in with a beginner mindset, get ready for the challenge, and have fun!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6532ec42ba1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-experience-of-attending-a-3-hour-prototyping-hackathon-and-things-i-learned-d6532ec42ba1">The experience of attending a 3-hour prototyping hackathon and things I learned</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>