<?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 Justin Seto on Medium]]></title>
        <description><![CDATA[Stories by Justin Seto on Medium]]></description>
        <link>https://medium.com/@jsetomsc?source=rss-29473f7d4887------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hfkRceXS_kLRZThBzYoF-w.jpeg</url>
            <title>Stories by Justin Seto on Medium</title>
            <link>https://medium.com/@jsetomsc?source=rss-29473f7d4887------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:32:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jsetomsc/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[LCBO|next Product Management 101]]></title>
            <link>https://medium.com/@jsetomsc/lcbo-next-product-management-101-9cbf209c04e6?source=rss-29473f7d4887------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cbf209c04e6</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Justin Seto]]></dc:creator>
            <pubDate>Tue, 03 Dec 2019 18:08:50 GMT</pubDate>
            <atom:updated>2020-07-25T20:44:46.431Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Product management</strong> is an organisational life-cycle function within a company dealing with the planning, forecasting, and production, or marketing of a <strong>product</strong> or <strong>products</strong> at all stages of the <strong>product</strong> life-cycle….</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZbwMIIrykGRAevUq.jpeg" /><figcaption>10/10 internship with a 10/10 work space</figcaption></figure><p>Those three lines would be the opener to the most impactful summer of my professional career as a PM for the Liquor Control Board of Ontario. Over 4 months in 2019, I was given the opportunity to work at LCBO|next, taking on the challenge of working as a product manager for the first time in my career. Under my manager and mentor Danny Ho, I experienced a 4 month long crash course into the world of product management, learning step by step how to build, release and scale sustainable and innovative products.</p><p>Although I had a term of digital strategy at <a href="http://jseto.me/TD.html">TD</a> under my belt, as a rookie product manager and co-op student leading a team (for the first time!!) in the creation of a product was something far out of my realm of expertise. I recall my first few days on the job as one filled with doubt and impostor syndrome, with a background in UX and front-end development my scope of problem solving had always lay on user facing issues, now as a PM I would need to transition my mindset to understand business facing problems as well. A strong mentor and supporter, Danny provided me a framework for product management by teaching me the foundations of pragmatic marketing, encouraging me to take confidence in my decisions and empowering me to set my own goals working towards product strategy. Following a 2 week sprint where I focused on learning and equipping myself with the tools needed to succeed such as Product board, Azure Devops and Roadmunk, I was ready to lead a team of 3 other coop students to deliver on our first product, <em>LCBO QuickRate</em>.</p><h3>QuickRate</h3><p>At LCBO|next our ability to be nimble and agile meant that we would look for opportunities to develop and build over buying. With our lab building from our own ecosystem and untethered by any restraints politically or technically from the LCBO head office, as the Product Manager it was my responsibility to look for potential innovations to meet the LCBO’s goal of sustainability, responsibility and serving Ontarians the best we could. Drawing from this directive came the idea for a recommendations engine. Based off of collaborative filtering, a recommendations engine would cut down on search time for customers browsing the eCommerce site, in addition to intelligently suggesting products in a none invasive manner. From a business perspective this would reduce cart abandonment in cases where a user could not find a product, and also serve to market new additional products that a user might enjoy. With the business value validated the solutions design for the recommendations engine then came into play. In order for a recommendations engine to suggest products the machine learning model would first need to understand what types of products users would enjoy together; essentially we would need to feed parings and ratings data to train the model. This would prove to be the first roadblock in development, as ratings were not currently a feature supported by LCBO’s eCommerce site. A Friday afternoon brainstorming session would result in our answer to the problem, the application QuickRate.</p><p>Built as an internal application to quickly gather user rating data, QuickRate would serve as my team’s first challenge. With barely over two weeks to complete as the product manager I knew that we had to work fast. With experience working with Agile development in the past I sought to implement a bare-bones framework, Agile stripped to its core for the QuickRate project. Stripping down the fundamentals, we broke the Quickrate application into design, back-end and front-end utilizing azure dev-ops’ built in ticketing system to ensure we could keep on track for our tight release. Thankfully the team was more than capable to stand up to the challenge. Utilizing gamification theory learned in my undergrad, I worked with the designer <a href="https://www.sharonchan.me/">Sharon</a> to create an experience that would encourage users to “play” by rating drinks in an attempt to maintain points on a leader-board. With the support of Jay &amp; Max, two fantastic developers the team was able to create a fully functional progressive web application in time for our release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/0*G8mrYjfHD0LCCdhG" /><figcaption>QuickRate’s main page, utilizing a “tinderized” &amp; gamified experience to drive ratings</figcaption></figure><p>My experience managing QuickRate came down to understanding the dynamic between development and design in creating a product. As the product manager I had to ensure at the highest scope, that the project would be feasible; finding the balance between perpetuating the best user experience while building with zero technical debt; all while meeting a challenging time constraint. Although concessions had to be made in order for our product to meet its deadline, finding those concessions, those small functionalities that didn’t “matter” in the final picture was a lesson as a product manager I won’t soon forget, and I look forward to applying the same strategic decision making to many future projects to come.</p><h3>Challenge and Refusal</h3><p>Challenge and Refusal, was a project undertaken by the LCBO|next team as a directive from LCBO head office. It was a project that was conducted jointly by both the head office and the Lab’s development, security and product teams to digitize the LCBO agency store Challenge &amp; Refusal process.</p><p>In compliance with the Integrity Shop Program and in tandem with Check 25, the Challenge Refusal process was a required process of LCBO’s social responsibility standards to restrict the access of alcohol to minors and maintain the integrity of the alcohol retail process. Agency stores were authorized retailers serving remote and rural communities across Ontario, meaning they were not LCBO stores but rather separate retailers. However these stores were still held to the same high standard to ensure that alcohol access would be restricted to minors. This meant recording instances of a challenge (asking for id) and refusal to serve alcohol. Due to the large variety of retailers authorized as agency stores, these stores did not have access to the same point of sale system offered in traditional LCBO stores. As such agency stores across Ontario would rely on a paper and pencil method to record cases of Challenge and Refusal. The proposed project was thus to develop a stand-alone Progressive Web Application to digitize the process of Challenge and Refusal in agency stores, providing them with an efficient way to track, store and submit cases of refusal in the purchase process. This project would prove to be a challenging one, requiring me to exercise organization and communication skills to a degree higher than of the past. As the Challenge and Refusal project was a join initiative, my role as product manager would entail speaking with stakeholders, organizing meetings with project managers from the head office and ensuring that design and development would meet the strategic outline set out by our product road map. Challenges I faced during this project involved receiving sign-off from stakeholders, finding feature concessions that everyone could agree on and building component diagrams for the very first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*_loNhMl1WZiTnIZbCcdkgQ.png" /><figcaption>sample component diagram from the early days of C&amp;R development</figcaption></figure><p>Furthermore although development would be handled by the LCBO|next team, integration with the main LCBO environment and rolling out an external application meant that vigorous security checks needed to be conducted before a release could be made. This added pressure meant that any last minute changes, be it bug fixes or features would be virtually impossible as new tests would be necessary every time code was pushed. With this hard deadline in mind managing the building process for C&amp;R would prove to be one of the toughest challenges on my journey to product management. However I would not be deterred. Over the course of 3 sprints C&amp;R would take shape as the zenith of my summer PM experience. Through the challenge and refusal initiative, I learned how invaluable communication and cohesion was for a team building a project, recalling having to work around multiple schedules to set up meetings and ensure goals were being met on time. I also learned how to push back, to work with a stakeholders rough vision and requirements and reign in when necessary if requirements morphed into out of scope features. Finally, and perhaps most importantly, I learned that I as a PM had to <strong>always </strong>be learning; it wasn’t important that I didn’t know how to draw a component perfect technical diagram, or answer every question related to system security, what did matter was my ability to adapt and willingness to learn new things — a skill I will make sure to utilize as I continue to grow as a product manager.</p><h3>TL;DR</h3><p>All in all my experience at LCBO|next was truly career defining. In my exit interview with Danny I remember him mentioning that I wasn’t the strongest candidate. My grades were average and to say I had a wealth of experience wasn’t factual either. However the reason he took a chance on me was my hunger to learn and drive to grow. If I wasn’t 100% sure I wanted to be a product manager prior to my internship I am a 110% now. It took me 22 years 5 different jobs and 5 years of school to do it but I’ve realized my passion for product, working to build fantastic digital experiences and turning scribbles on a white board into projects that make an impact and I look forward to a future doing just that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cbf209c04e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Perpetuating the Best UX]]></title>
            <link>https://medium.com/@jsetomsc/perpetuating-the-best-ux-ae858b60a8dd?source=rss-29473f7d4887------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae858b60a8dd</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Justin Seto]]></dc:creator>
            <pubDate>Fri, 06 Oct 2017 23:55:22 GMT</pubDate>
            <atom:updated>2019-01-22T06:37:25.309Z</atom:updated>
            <content:encoded><![CDATA[<p>Sears Canada: a Case Study</p><p>In our world today companies are attracted to the concept of UX and user centered design like flies are to honey. As explained in my previous <a href="https://medium.com/@jsetomsc/ux-for-the-creatively-impaired-f7e3bacfe1bb">article</a> user experience in the present is a giant in the technical and corporate world. Not a trend nor a fad the once fringe idea of creating not just for aesthetic but with a focus on usability for <em>every </em>user has permeated directly into the mainstream.</p><p>Over the summer I had the opportunity and the privilege to intern as a front-end developer at Initium Commerce lab in Toronto. A subsidiary of Sears Canada the majority of my time spent there was on the development and design of E-commerce solutions and what I experienced was eye-opening.</p><p>Sears Canada had a host of extremely talented designers. Hours a week would be poured into making sure each button, each colour, and shade would mesh perfectly to form the most pleasing aesthetic design. However the intrinsic difference between aesthetic design and <em>good </em>design was often lost.</p><p>Although design in essence is subjective, user-centered design is not. Properly executed, UX design will be backed up by data and research on every aspect of a users’ interaction with the subject. Thought is given on not just how something looks, but on how a person will interact with it. Empathy is required to understand the journey the user takes from the first step to the last, a road map of their experiences noted, desire lines analyzed and a prototype created. In contrast these needs for good design were often not met due to pressure from leadership and priority on the wrong things. Which brings me to my first point, in order for a firm to create an excellent user experience, a culture that fosters this mindset must first be established.</p><h4>Stairway to UX Heaven</h4><ol><li>Foster the right mindset</li><li>Understand your audience</li><li>Communication between ALL parties involved</li><li>Design for them, not for yourself</li></ol><p>Fundamentally abstracting the techniques that go into UX design leaves us with research, planning, design and development. Having worked as both a freelance designer in my own capacity as well as a professional front-end developer I’ve come to understand that the most important aspect and very first step to creating a good user experience is to have the right mindset. Working in an industry that has been laden with years of politics and structured answers to every problem, the radical and frequently out-side-the-box solutions that UX needs is often a point of friction for senior leadership and designers to wrap their heads around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N07UApidXCt0RQczDPY0Fg.png" /><figcaption>Colour swatches for “decoration only”</figcaption></figure><p>During my time at Sears one of the strongest examples of this clash in perspective were the existence of colour swatches on one of the landing pages. These swatches were a direct order from upper management and for the design team enormous pressure was put on implementing them. They had to have the designs finished by <em>yesterday</em> which meant there was little to no time to do things the right way, no time for guerrilla tests, no time to look at analytics and no time to even consider the idea “hey maybe this might be confusing to our user”. We live in an age dominated by eCommerce and anyone who’s ever shopped online would be familiar with the idea of swatches, they help a user navigate the page easier and allows a preview in the colour of a product by hovering over them. Effective implementation of this feature is a standard in almost all eCommerce businesses, conversely due to the intense time constraint brought upon by upper management the correct implementation was never given the time to develop. Instead the team at Sears simply created a static image in Photoshop and slapped it on the front page. Not only was this confusing to any user who expected a dynamic and interactive experience, the styles weren’t even consistent with the rest of the Sears site. A quick foray one level deeper displayed square instead of circular swatches, breaking the design principle of cohesion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZgiExQWN5aobyBT7UDe3Aw.png" /><figcaption>Don’t worry we only design inconsistently on days that end with the word “day”</figcaption></figure><p>Through no fault of their own the design team was hindered at an institutional level. Due a lack of understanding of what UX was and how to implement it from the upper management, the result of their pressuring request was a poorly designed feature and a kink in the user journey.</p><h4>Who’s this for Anyways?</h4><p>Know your audience, know yourself.</p><p>Picture yourself walking into a restaurant in Amsterdam. Maybe you’re craving some Dutch Cuisine, perhaps some Pofferjes or a nice meal of Bitterballen. You walk down a narrow dutch street and cross a scenic bridge spanning a nearby canal. The ambient sounds of water gently lapping at boats in the background is music to your ears. The world is good. As you approach the restaurant you can smell the delicious scent of freshly made Kroket waft through the air. With apprehension you waltz right through the front door, until BAM! it hits you. Instead of being greeted by a friendly waitress in what you can only assume would have been clogs, you’re instead met with a bruise on the head, the front door stands only 5 ft tall! As extreme an example as this sounds, its safe to say building a restaurant with a door barely fitting Bilbo Baggins in a city with the statistically tallest people in the <a href="https://www.liveandinvestoverseas.com/news/top-10-countries-with-the-tallest-people/">world</a> would be a very bad idea. Why then would designing and developing a product or service be any different?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*952-LDtQucnYyNh9qO9kUQ.png" /><figcaption>Legible text! … if your screen brightness is set to to 1000%</figcaption></figure><p>Another trap that many corporations often fall into is the lack of understanding of whom they are developing for, at least not in their audience’s entirety. A total and holistic understanding of any and all users is the foundation for UX design and often times the best solution for user issues <em>isn’t </em>the most aesthetic one, or the one with most features. Like the beaten path analogy, many times the desire line created through grass is unsightly and detracts from the over all scenery, however in hindsight the path itself should have been created where the beaten path stands and it’s only through understanding all the nuances of a companies’ users can great UX be developed. For Sears Canada the opposite approach to problems was taken more often than not. Rather than focusing on maximizing the ease of use for their audience, focus was put on other aspects of development. Fonts lacking contrast were sporadically set through the site, alienating users who had vision problems or users who didn’t understand how to manipulate their computer’s brightness. Instead of implementing fixes such as bolder colour contrasts and tones, effort was pushed towards creating the nicest effect or the trendiest look.</p><h4>Teamwork Makes the Dream work</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7Fgvzk1V42c%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7Fgvzk1V42c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7Fgvzk1V42c%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f02b126f7fa64a9dd4247a1075113f3/href">https://medium.com/media/5f02b126f7fa64a9dd4247a1075113f3/href</a></iframe><p>If you’ve ever played a team sport or worked in a group then you’re probably familiar with the age old idiom of team work. There simply isn’t an “I” in team and just like high octane sports, or for people like me e-sports (League of Legends pictured above), If you don’t work united you’ll fail divided. Parallel to this concept in product development are the different teams operating in their realms. Data, Dev-ops and Design, all work together towards building the perfect outcome.</p><p>During my tenure at Sears one of the largest blockages to a cohesive team environment was communication. Although a team slack existed the idea that it would serve as an omni-channel tool to foster team contact was far from the truth. Instead of building avenues of conversation it evolved into a shelter for separate teams and group cliques. This culture of teams working and communicating only domestically and not together meant that there were constant gaps in the transmissions process. Deliverables took longer to complete and deadlines weren’t met because a proper network of correspondence simply didn&#39;t exist.</p><blockquote>the most successful designers will be those who can work with intangible materials — code, words, and voice.</blockquote><blockquote>John Maeda</blockquote><p>As I will mention in a future article another common hindrance to the success of teams looking to develop UX lies in the inability for separate teams to efficiently communicate <strong>even if</strong> a reliable communications infrastructure is laid. This is due to the fact that developers and designers today still speak different languages. The jargon behind both worlds at current creates a chasm that is often difficult for either parties to cross. Nonetheless according to an <a href="https://www.wired.com/2017/03/john-maeda-want-survive-design-better-learn-code/">article</a> written following John Maeda, a Giant in the design world, the fine line dividing development and design is quickly blurring and in 50 years might not even exist. The onus is thus on designers and developers to start learning to speak the lingo of the other.</p><p>The age of single channel segregation of teams are no longer enough to sustain a user centered design ecosystem. Like the railroad boom of the 1800’s that connected Canada from sea to shining sea, Inter team communication has to be created out so that a network of cohesion and unity with a singular goal in mind is developed. Will this take more time? Yes, however Rome wasn’t built in a day and a lasting brand won’t be either.</p><h3>Selflessness is a Virtue</h3><p>ARIA — more than just a nice sounding name</p><p>If today you were to tell someone that they couldn’t access a certain business or restrict their ability to do things like enter a park or use a water fountain you’d face massive backlash — and rightly so. Equality is a global concept that I’d like think we can all agree on. Why then would it be fair to design applications on the internet don’t follow the same rules of common sense equality? Besides as a business, estranging potential customers, designing and developing unaccesible applications is simply ethically wrong.</p><p>Released more than a decade ago ARIA stands for <em>Accessible Rich Internet Applications </em>and it’s exactly what the acronym implies. It’s a set of standards supported by the World Wide Web Consortium that explains how to create internet applications that work, for everybody. And it’s not just for developers. <a href="http://universaldesign.ie/What-is-Universal-Design/">Universal design</a>, design meant to include the needs of everyone goes well and far beyond just web applications. Engineering, urban planning, materials science, all these things take into account the idea of universal design. With over a decade of precedence and a diverse amount of resources dedicated to teaching and even <a href="https://www.w3.org/WAI/ER/tools/">checking</a> ARIA compliance, it’s simply unacceptable to be unaware or ignorant about its implementation. Features such as screen reader functionality, tabbing through various content, readable font and kearning design and hover descriptions over buttons are foundational examples of what every site should have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtovnGWVONknBjloXZfhiA.png" /><figcaption>Wow an E-Score of 46! Wait what do you mean the scoring is like golf…</figcaption></figure><p>Lastly to add to the focus on the user, load time optimization also needs to be taken into account. Although not necessarily a design issue the golden second, or the amount of time it takes for a user to get bored has implications in UX as well. Simplicity and minimalist design is all the rage in current times; trendy and light these designs display only the core features that are necessary for a user to optimize their experience. And the reason behind their success is a very simple concept. Designers need to learn to design not for themselves but for the user. The age old saying of “more features, more problems” holds ever true. Bloated effects, navbars, animations and buttons all may look cool, however designers have to remember that at the core their designs have to be scale-able and practical. Painting the most beautiful painting in the world means nothing if no one ever waits long enough to see it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hAtjjQnX--JJsvSOXXG1MA.png" /><figcaption>Loading times longer than it takes for my grandmother run a mile. She’s 98.</figcaption></figure><h3>Too Long; Didn’t Read</h3><blockquote>“There is nothing more dangerous than standing still in a world that is changing.” — French President, Jacques Chirac</blockquote><p>At it’s fundamentals I didn’t write this article to bash on Sears. They offered me a golden ticket to understand the process behind a multi billion dollar corporation and the people behind them and for that I’m grateful. Rather in the spirit of heurism I took my experience as a outlet to learn and to develop.</p><p>The story of Sears Canada is age old, a King in the North, Sears had a virtual monopoly over the retail market in the late 90’s and early 2000’s. However In a rapid industry that is always changing its adapt or die, and at a quintessential focal point in the history of commerce, the introduction of the big “e”, Sears failed to change. Although they didn’t adapt in the past they still have a chance to fix the present. UX design will dictate the way people create for the foreseeable future and modifying old trends to acclimate for the new is only the first step in the bearing of a new entity. However with dedication, understanding and a nudge in the right direction a brand that champions the user experience and paves way for a legacy immortalized is sure to be born.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae858b60a8dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX for the Creatively Impaired]]></title>
            <link>https://medium.com/@jsetomsc/ux-for-the-creatively-impaired-f7e3bacfe1bb?source=rss-29473f7d4887------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7e3bacfe1bb</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Justin Seto]]></dc:creator>
            <pubDate>Thu, 05 Oct 2017 07:35:35 GMT</pubDate>
            <atom:updated>2018-01-29T19:45:04.871Z</atom:updated>
            <content:encoded><![CDATA[<p>A guide to what your designers are actually saying.</p><p>Disruption. Innovation. Change. These words today invoke feelings everywhere from inspiration to perspiration, they are the buzzwords of the present and the building blocks of the future. Yet at the core of these concepts lies a movement that’s been gaining traction in recent times, a movement that highlights a shift in the centenarian views of old development, that challenges the corporate walls of old and in place bring a new perspective to the technical industry; and that movement is a single two letter word. UX.</p><h3>&lt;Us·er Ex·pe·ri·ence&gt;</h3><blockquote><em>noun</em></blockquote><blockquote><em>Digital Technology. </em>the perception and response of a person toward design elements of software or digital media while interacting with it. (Dictionary.com)</blockquote><p>So what is UX? Well, A dissection of its basic English components gives us the words “user” and “experience”, user being the customer, consumer or foundation for any business and experience being the perception, feeling and encounter of the said user. Although a simple concept in theory to understand, UX at its core is more than that. To perpetuate the best user experience requires an amalgamation of research, design and development, along with the correct mindset and leadership. UX or rather the pursuit of its optimization isn’t per-say a new concept and on paper it really shouldn’t be. Basic business models have always lauded the customer as the number one foundation for any success, conversely in the last decade it is the paradigm shift of user centered design that has led the charge in renovating the technological space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/0*86rHdajk45FotJE7." /><figcaption><a href="https://sugoru.com/2012/09/16/desire-lines-of-design/">https://sugoru.com/2012/09/16/desire-lines-of-design/</a></figcaption></figure><h4>Desire Lines</h4><p>Now that we’ve defined UX we’re left to ask ourselves, what’s so important about it? Why does a buzz exist around something that sounds so fundamentally simple? To elaborate on this, is an analogy often used to understand the comprehensive impact UX has, the idea of a desire line. Even if you don’t know what a desire line is you’ve most probably seen them or interacted with them in the past. The best example of of a desire line would be a path adjacent to a sidewalk that shortens a corner at your local park. Instead of using the sidewalk that was designed for them, pedestrians stray to the left or right and create their own trails. Desire lines are products of users utilizing something in a way the designers had not foreseen or intended. In turn UX is about intercepting and planning for these lines, even before they exist. Moreover the point still stands, the need for UX permeates far beyond just the digital world. Every facet of design, industrial, urban, media related and everything else in between thrives when efficiency and ease of use are put forward as question, and met with an answer in UX.</p><blockquote>“Design is not just what it looks like and feels like. Design is how it works.” — Steve Jobs</blockquote><h4>The RoadMap</h4><p>So we’ve boiled down UX to what it is and why its important but if you’re like anybody else getting started with a new concept involves learning the language, and UX is no different. Much like in software development, experience design is packed with its own nuances, syntax and jargon. Every design task is created to meet the needs of a unique audience and the building blocks of the experience must be tailored as such. Despite this however, each UX project follows a project road map that features 6 steps unique steps.</p><figure><img alt="Image result" src="https://cdn-images-1.medium.com/proxy/1*g6DrAXyHxpO5I3B1oTMFRw.jpeg" /><figcaption><a href="https://blog.prototypr.io/7-steps-to-become-a-ui-ux-designer-8beed7639a95">https://blog.prototypr.io/7-steps-to-become-a-ui-ux-designer-8beed7639a95</a></figcaption></figure><p><strong>1. Recognizing the problem</strong></p><p>If we lived in a world where design was mastered and every interaction streamlined, one of two things would happen. Firstly UX wouldn’t be needed and secondly I’d be jobless. However and luckily for me the world we live in is imperfect and problems are always bound to exist. Thus the first step to UX design is to understand the issues that users face. Empathizing with the user journey is fundamental here and data is usually collected through focus groups and analytics.</p><p><strong>2. Researching the User</strong></p><p>Often tied in with the first step, user research encompasses a broad field that contains everything from who the user is to how they interact with the app. Designing an app that automatically locates the fanciest restaurants is cool, Designing an app that automatically locates the fanciest restaurants when your audience consists of broke college students…. not so much.</p><p><strong>3. Ideation, how do we solve it?</strong></p><p>Now comes the important part, we’ve researched our users and we’ve empathized with them on a holistic level, their problems have now become our problems and its time to bring a solution. When dealing in this phase its always important to loop back to the user at the end of the day, you don’t want to work on a project for two weeks only to realize that your solution to a problem has created another thousand issues.</p><blockquote>“If a picture is worth 1000 words, a prototype is worth 1000 meetings. “ — <a href="https://twitter.com/kelleybros">Tom &amp; David Kelley</a>, Creative Brothers at IDEO</blockquote><p><strong>4. Designing and Prototyping</strong></p><p>The prototype phase is arguably the most volatile and dangerous, akin to a 20 hour hackathon binge, prototyping involves the careful application of the ideation phase as a Proof-of-Concept. Be it on paper, a model or a digital mock-up, prototyping will almost always involve critiques, bitterness, denial, crying and an empty drawing board.</p><figure><img alt="Image result for guerilla testing meme" src="https://cdn-images-1.medium.com/proxy/1*XojpBkcV3_wllUgv_yE0xw.jpeg" /><figcaption><a href="https://engineering.zalora.com/guerilla-testing-in-singapore-fc724aea22f9">https://engineering.zalora.com/guerilla-testing-in-singapore-fc724aea22f9</a></figcaption></figure><p><strong>5. Guerrilla Testing</strong></p><p>Unlike what the name implies guerrilla testing has neither anything to do with monkeys or radical socialists movements, instead it is the systematic approach to collecting test data on prototypes and in-development applications. Like a beta test in game development or alpha development cycles in new applications, guerrilla testing is a key part in weeding out any bugs or kinks in the user experience — before anything is made live.</p><p><strong>6. Release and Continued feedback (feedback loop)</strong></p><p>Last but certainly not least is the release and continued feedback of a project. Often one of the most overlooked aspects of UX design is what comes after a project is complete and released. Analogous to the care of a vehicle preventative maintenance is important in keeping the car in good shape and the user experience isn’t any different. Checking back every so often on user data and analytics is a measure that ensures that the User Experience is maintained in perpetuity.</p><h3><strong>The Bottom Line</strong></h3><p>At the end of the day UX is a melting pot of many various concepts, ideals and techniques; however more than that, UX is a mindset, it’s a mentality on approaching problems and guide on creating solutions, when designers design with empathy, and take a look at the bigger picture, good design follows. UX is isn’t simply a trend, its a revolution and it’s here to stay. So the next time you open up an IDE, text editor or Adobe product always remember, <strong>good </strong>design may attract attention, but <strong>great</strong> design creates devotion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7e3bacfe1bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>