<?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 Ahsan Jalil on Medium]]></title>
        <description><![CDATA[Stories by Ahsan Jalil on Medium]]></description>
        <link>https://medium.com/@vertage?source=rss-177fe98f9209------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WrtOXBNrTN52blP9hOW1aw.jpeg</url>
            <title>Stories by Ahsan Jalil on Medium</title>
            <link>https://medium.com/@vertage?source=rss-177fe98f9209------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:58:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vertage/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[UX design challenges for SaaS Products and how to mitigate them!]]></title>
            <link>https://vertage.medium.com/ux-design-challenges-for-saas-products-and-how-to-mitigate-them-a204795aef47?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/a204795aef47</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 15:39:12 GMT</pubDate>
            <atom:updated>2023-03-20T15:39:12.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="SaaS Application UX design challenges… and how to mitigate them!" src="https://cdn-images-1.medium.com/max/1024/1*OXkDSrnsvQbkMWIgNwwyzA.jpeg" /></figure><p>Product and UX design vary from industry to industry. You might be perfect in one industry but may find it difficult to be impactful in another. It’s not your skills or experience, it’s how that industry works.</p><p>Product designers for SaaS (Software as a Service) applications face many unique challenges compared to designing for other types of products. Some of these challenges include:</p><ol><li><strong>Complexity</strong>: SaaS products often have a wide range of features and functionality, which can make the design process more complex. Product designers need to find ways to present this information in a clear and user-friendly manner.</li><li><strong>Consistency</strong>: SaaS products are typically accessed by users through a web browser, which can make it difficult to ensure consistency across different devices and platforms. Product designers need to consider the different screen sizes, resolutions, and interactions that users may have with the product.</li><li><strong>Scalability</strong>: SaaS products are often used by a large number of users, and the design needs to be able to accommodate this scale. Product designers need to consider how the product will perform and look across different usage patterns and traffic levels.</li><li><strong>Security</strong>: SaaS products often handle sensitive user data, and designers need to ensure that the product is secure and compliant with regulations such as GDPR and HIPAA.</li><li><strong>User feedback</strong>: SaaS products are often updated regularly, and designers need to be able to respond quickly to user feedback and incorporate it into the design. This can be a challenge, as it requires designers to be agile and able to pivot quickly.</li><li><strong>Usability over Aesthetics:</strong> Usability is a critical aspect of designing any application, however for SaaS products the focus should be on how the application functions and meets the needs of users, rather than on aesthetics. It is important for designers to prioritize usability and functionality over the visual design until the usability of the application has been fully established.</li><li><strong>Lack of product knowledge:</strong> The lack of product knowledge can be a significant challenge, especially for a growing company, particularly for a new product designer who may not have been involved in the product’s development from the beginning. This can make it difficult for them to fully understand the product’s core functionality and how it meets customers’ needs.</li></ol><p>Overall, designing for SaaS applications requires designers to have a deep understanding of user needs and behaviours, as well as the technical constraints of the platform. Additionally, designers need to be able to work collaboratively with other teams such as engineers and data scientists to create a cohesive, user-friendly and efficient product.</p><h3><strong>How to overcome these challenges</strong></h3><p>Many companies focus on the solution they are offering, rather than considering the needs and wants of the end-users. This can lead to products that are not intuitive or easy to use, resulting in poor user adoption and satisfaction.</p><p><strong>Designing with the end-user in mind</strong> is crucial for creating a successful SaaS product. This means understanding the user’s goals, pain points, and behaviour, and designing the product accordingly. It also means conducting user research and testing throughout the design process to ensure that the product is meeting the needs of the users.</p><p>Sometimes it’s difficult to get hold of end users when working in SaaS, however, it’s very important to work closely with end-users whenever you can. The more you collaborate with the users, the more you can create a product that is tailored to their needs, making it more likely that they will adopt and continue to use it. This can lead to increased customer satisfaction, retention, and ultimately revenue.</p><p>It is vital to keep all users in mind when designing a SaaS application, as each user group may have different needs and requirements. For example, in the case of Netflix, there are three main user groups: <strong>end users</strong> who watch videos, <strong>employees</strong> who manage the content, and <strong>business partners</strong> who have different needs and requirements. Focusing on more than one user group, such as end users, can lead to a lack of functionality or usability for other user groups. Keeping all users in mind during the validation process helps ensure that the application meets the needs of all users and is more likely to be successful.</p><p><strong>Understand The Tech Stack Constraints:</strong> As a product designer in a SaaS environment, one of the challenges you may face is dealing with the tech stack. Since these applications often rely heavily on engineers, the technical aspects of the product can take precedence over the user experience. As a result, the user may be exposed to unnecessary complexity or technical jargon that they do not understand or care about. The product designer must ensure that this does not happen and that the user is presented with a simple and intuitive interface that meets their needs. This can involve working closely with engineers and product managers to balance the technical requirements with the user experience.</p><p><strong>Know the Financial Impacts:</strong> One significant challenge for product designers working for start-ups or SMEs is that many companies rely on large clients for their revenue. When dealing with large clients, there is often pressure to customize the product to meet the specific needs of those clients. This can include adding new features, modifying existing functionality, or changing the overall design of the product.</p><p>However, customizing the product for one client can have a ripple effect on other clients, as well as on the overall product strategy and vision. For example, customizing the product for one client may make it less user-friendly for other clients, or it may make it more difficult to add new features in the future.</p><p>Additionally, when customising the product for one client, it can be difficult to manage the balance between meeting the needs of that client and maintaining the integrity and usability of the product for all other clients.</p><p>To address these challenges, product designers must work closely with the client to understand their needs and determine how best to meet them without compromising the overall user experience and product vision. This may involve finding ways to add new features without disrupting the existing product, or creating separate custom versions of the product for different clients.</p><p>Product designers should work closely with their team to ensure that any customizations made for one client do not negatively impact the other clients and that they are aligned with the overall product strategy and vision. Use <strong>effort vs impact matrix</strong> wherever possible.</p><p><strong>Start Questioning:</strong> It is the responsibility of the product designer to ensure that the application does not become a “feature factory” and instead focuses on delivering value to the end-users. One way to do this is by questioning the product team and validating the requirements with end-users to ensure that the features being added are solving real problems and meeting the needs of the users.</p><p>It’s important for the product designer to critically evaluate the requirements and avoid adding features for the sake of adding them, or because they are “cool” or trendy. Instead, the designer should focus on creating a product that is user-centred and addresses the needs of the target users.</p><p>User research and testing can also play an important role in avoiding the feature factory trap. By conducting user research and testing, product designers can gain a deeper understanding of the users and their needs, which can help them to identify the features that will add the most value to the product.</p><p>Designers should be open to feedback and willing to iterate on the design based on user feedback. This can help to ensure that the product is always evolving and improving to meet the needs of the users.</p><p><strong>Don’t assume:</strong> If you are working for an organization where the knowledge of the core product is limited to a small group of people, it can be challenging to align the needs of the business with the needs of the users. In such situations, it is important to be proactive in seeking out information and knowledge about the product. This can include being vocal about the need for more information, actively participating in leadership meetings and decision-making processes, and asking questions to gain a deeper understanding of the product and its functionality. It is important to remember that the goal is to improve the product and user experience, not just make superficial changes. Being assertive and persistent in seeking out information will help ensure that the product aligns with the needs of both the business and the users.</p><p><strong>Don’t create a Solution to a problem that doesn’t exist:</strong> It’s also important to note that sometimes, it may be the case that we are solving a problem that does not exist, or that the problem can be solved differently. In those situations, the designer must be able to make that call and redirect the team to focus on something more relevant. Your user’s problem needs a solution so even though you think you’ve identified a problem it’s worth checking with your users. They might have a different opinion.</p><p><strong>Enterprise or Start-up, challenges are similar: </strong>Large enterprises can also face similar challenges to start-ups and SMEs when it comes to SaaS applications. As a Lead UX designer, working for a large organization I had to navigate the complexity of designing an enterprise application that offered various service offerings for internal users, such as virtual servers, PaaS offerings, hosting applications on the cloud, deploying AKS clusters and requesting CaaS.</p><p>One major challenge in this scenario I had was that end-users often have to navigate different platforms for different services, which can lead to a fragmented and inconsistent user experience. That made it difficult for users to find the information and services they need, and also lead to confusion and frustration.</p><p>To address this, I worked closely with the different teams responsible for each service offering to ensure that the user experience was consistent across all platforms and that the information and services were easy to find and use. This required close collaboration and coordination between different teams and stakeholders, which was challenging in a large enterprise due to each team’s different roadmaps and goals. I did a lot more research with users, learn their pain points and shared with stakeholders and then offered a single pane of glass solution. Persistency and consistency were my best friends took a long but I was able to achieve my goals.</p><p>When working for large enterprises, especially on internal SaaS applications, it is important to understand the internal needs and processes of the company, and how the organization can support and optimize these processes. This can be challenging, as different departments and teams may have different needs and priorities.</p><p>Another challenge can be the scalability and security of the applications. You have to ensure that the application can handle what you are proposing as a solution while also maintaining security and compliance with regulations and industry standards.</p><p>If you have finished reading, you might be thinking SaaS application design is very complex and rather boring, but trust me if you understand how the industry works, and love challenges, you will never be bored and tired of solving design challenges. The SaaS industry is constantly evolving, which means there will always be new challenges to tackle and opportunities to improve your skills. If you enjoy problem-solving, design, and technology, designing SaaS applications can be a very rewarding and fulfilling career.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a204795aef47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX and UI Design Career Advice for the youngsters…]]></title>
            <link>https://vertage.medium.com/ux-and-ui-design-career-advice-for-the-youngsters-a9d60dd18c63?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9d60dd18c63</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[new-to-ux]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Thu, 15 Jul 2021 09:58:45 GMT</pubDate>
            <atom:updated>2022-01-25T16:41:44.035Z</atom:updated>
            <content:encoded><![CDATA[<p>So I was asked some really interesting questions by my niece, who is getting into university with an interest in UX, UI and games development. I thought I should publish the questions and answers so other youngsters can benefit if they have similar interests and questions.</p><h4><strong>Q. What do I have to study or take in university to go into UX designing?</strong></h4><p>There are various courses and degree programmes related to UX design you can go into. However, few are purely UX degree programmes. You would need to study programmes like below to go into the UX design profession. Although relevant education is not prerequisite to getting into UX design.<br>Master of Interaction Design<br>Bachelor of Information Technology (User Experience Design)<br>Bachelor of Computing Human Interface Technology (HIT)<br>Bachelor of Science Interactive Systems Design<br>Masters of Interaction Design<br>Masters of Information Architecture<br>Bachelor of Arts Product Design</p><p>Look for the keywords in the programme name, interaction design, Human Interface, User Experience, Design System, Information Architecture, Human-Computer Interaction etc.</p><p>There is another route you can take, which will take you to the UX profession mainly towards the research side and that is behavioural sciences or physiology degree, both play a big role in UX design.</p><h4><strong>Q. What do I have to study or take in university to go into UI designing?</strong></h4><p>For UI design there are more options as it’s been around for a very long. Again, the degree is not a prerequisite to go into a UI design career but is good to have. One major thing that separates UX from UI is that you can learn UX with passion, you can’t learn to be creative when it comes to UI. So you should have a creative mind that you’ll be able to polish via education or experience.</p><p>Interestingly, when you look for a UI degree, it will most likely be accompanied by UX. As knitting both together is the new norm now, although it shouldn’t.</p><p>For UI design education, simply look for the keywords:<br>Visual Design<br>Interface Design<br>Digital Design<br>Graphic Design (it’s more towards non-digital mediums)<br>User Interface</p><h4><strong>Q. Can I become a software engineer and still be a UX designer?</strong></h4><p>Absolutely, besides software engineer turned UX designer is much better than UI designer turned UX designer. Mainly due to knowledge of the complexity and understanding the technological constraints UX will have.</p><p>The only word of caution is that it will be fairly difficult to juggle both at the same time. That’s why I always stress to master 1 skill and learn a few more. So you can master software engineering and learn UX or vice versa.</p><h4><strong>Q. What is an example of a problem that UX designing strategies can solve?</strong></h4><p>UX design has multiple-use, UX and UX design are completely different things. Please read my article to understand the difference.</p><p><a href="https://medium.com/ux-masters/ux-and-ux-design-arent-the-same-things-abbd95b241f">https://medium.com/ux-masters/ux-and-ux-design-arent-the-same-things-abbd95b241f</a></p><p>However, both solve users problems, one with design and mostly with digital touchpoints, the other complete experience encompassing the customer experience and offline interactions.</p><p><em>A good example of how UX design can solve the user’s problem is that a business has launched a website selling shoes without UX design input. 1000s of people visit the site every day but only a few sales. The Business has no idea why. Then the business asks the UX expert to have a look. After data analytics and some digging, the UX expert finds out that selecting a shoe size is very difficult, feature looks really cool but it’s not usable. The business has spent millions already on the development and launch and now they will have to spend more to fix the problem. Had there been UX input from the start, this would have been pinned down and fixed during usability testing and business could have saved millions in lost expenditure and many more millions in lost revenue.</em></p><h4><strong>Q. Can I be both a UX designer and a UI designer?</strong></h4><p>Absolutely, this is a very common combination nowadays. The majority of UX experts in the industry have a UI background at some point, or their journey begins from UI. But as said earlier, don’t be both, be one and be a master. Knowledge of UI will extremely helpful if you are a UX designer or vice versa but trying to be perfect at both does not work out well.</p><h4><strong>Q. How can I start my own business in UX designing? What are the first steps to the basics and business plan developments?</strong></h4><p>Ok, to start your own UX business, I would highly recommend a few years of experience in the industry so you know inside out. Unless you have a lot of money and you hire designers who work for you and you to look after the operational side of the business.</p><p>The best approach would be to start working as a freelance/contractor. This gives you the flavour of being an independent business. You work with the client, not the employer, you work with SOWs (statement of work), that are working as B2B. <br>You would need a really good portfolio to win the UX business; hence, working a few years as a freelance UXer is very important. Even if you have to volunteer to build your portfolio, do it.<br>UX is not just knowing the tools and delivering the artefacts/metrics. 50% of UX is communication and presentation. So polish them, try public speaking, join events, take part in bigger groups where you can present your ideas.<br>A business plan is always good to have, but first, you’ll need to ensure that you understand the UX clearly. Then prepare a business plan, set goals, give yourself a timeline and achieve them.</p><h4><strong>Q. How can I start my own business in UI designing? What are the first steps to the basics and business plan developments?</strong></h4><p>Most are the same steps as UX design, but I think you can get away with not having very solid communication skills in UI. As there is less rationale explanation behind UI than UX.</p><h4><strong>Q. Can I do UX or UI designing for game developing companies?</strong></h4><p>In game development, UX and UI become gamification. Basic principles are the same but technology changes. Have a read at: <a href="https://en.wikipedia.org/wiki/Gamification">https://en.wikipedia.org/wiki/Gamification</a> to understand how UX/UI works in the gaming industry. With digital UX or UI design expertise, you would not be able to enter the game designing industry. You will have to take a different route for that.</p><h4><strong>Q. Can I do UX or UI designing while being a graphic designer or a video game developer?</strong></h4><p>You can do anything and still be UX or UI designer, but everything boils down to your ability and capacity to juggle different expertise at the same time. UX, UI, game development is verticle towers and then there are many horizontal paths under them, it’s nearly impossible to learn all and then use them at the same time. Better to stick with one and learn another for a hobby if you want.</p><h4><strong>Q. If I start my career as a UX designer, can I grow into starting a video game publishing company?</strong></h4><p>I would recommend if game publishing is your passion, follow that. UX will not help much in game development. Better to start from the game development and take that as your career path and business opportunity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9d60dd18c63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design without (or little) testing can cost lives!]]></title>
            <link>https://medium.com/ux-masters/design-without-or-little-testing-can-cost-lives-917e64a68eda?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/917e64a68eda</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[faulty-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[design-flaw]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Sun, 14 Jun 2020 12:05:54 GMT</pubDate>
            <atom:updated>2022-01-25T14:16:50.017Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*stNmTD37zKCYIes8zZolEw.jpeg" /></figure><p><em>There is a design without testing.. and then there is a design without the </em><strong><em>right</em></strong><em> testing. Both are equally dangerous whether it’s your digital application or a machine.</em></p><p>Alongside UX, I am an aviation enthusiast as well. And there is no better example to explain design without testing than the Comet disaster.</p><h3>The Comet (de Havilland DH 106 Comet)</h3><h4>Design with not enough testing!</h4><p>In 1952 the first aerodynamically clean design passenger jet with four engines buried in the wing roots, a pressurised cabin, and large square windows took the skies for the first time.</p><p>The de Havilland DH 106 Comet was the world’s first commercial jet airliner. Developed and manufactured by de Havilland at its Hatfield Aerodrome in Hertfordshire, United Kingdom. First prototype Comet 1 was built in 1949, just over 2 years before its debut.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2QDo7ytwAsaIjk9O5YPwwQ.jpeg" /><figcaption><a href="https://www.baesystems.com/en/download-en/heritageimage/webImage/20160812113642/1434577833224.jpg">BAE System</a></figcaption></figure><p>Design and features were praised globally within the airline industry and the passengers alike. However, within the first year of service, 3 Comet aircraft were lost after suffering catastrophic in-flight break-ups resulting death of everyone on board.</p><h4>What went wrong?</h4><p>Despite being the state of the art aircraft of the era, Comet suffered a catastrophic failure. And when you hear the reason for the crash, it gets even more puzzling. Investigators found the main cause of these deadly crashes were the design of the window and escape hatch! That’s right… windows design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*cp2lfNg81WRt201pGwSa3w.jpeg" /><figcaption><a href="https://aerospaceengineeringblog.com/dehavilland-comet-crash/">Aerospace Engineering Blog</a></figcaption></figure><p>The design of window did not cater for extreme compression and decompression, fuselage go through during each flight. The engineers did test the prototype, but not rigorously enough to identify the extreme forces involved. Only after the disasters, they grounded the fleet and started testing the aircraft and discovered the design flaws.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*POC7j1gGyy_7m2MCYesmbA.jpeg" /><figcaption><a href="https://aerospaceengineeringblog.com/dehavilland-comet-crash/">Aerospace Engineering Blog</a></figcaption></figure><p>It was a brand new design, therefore testing should have been even more in-depth and rigorous. I will leave the link here if you want to read about the disaster further. <a href="https://aerospaceengineeringblog.com/dehavilland-comet-crash/">Aerospace Engineering Blog</a>.</p><blockquote>Comet disaster is a reason we see oval shape windows in today’s aircraft. Design was eventally fixed but at the cost of many lives…</blockquote><h3>Smart Motorways</h3><h4>Testing without the right users!</h4><p>For the last decade or so, England is converting its motorway network to smart using technology to monitor and manage the flow of traffic. The technology is controlled by regional control centres which can activate and change signs and variable speed limits.</p><p>Part of that was to convert the hard shoulder into an active lane whenever there is a traffic load. And in an event of a breakdown, shut the lane with the broken-down vehicle using motorway communication signs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ohXz5-XnMs6IQPKHxUWVg.jpeg" /><figcaption>Photograph: Dawson Images/Alamy</figcaption></figure><p>The first smart motor was M42, a road outside Birmingham (if you live in the UK, you will know). The government used this as a testing ground to validate the idea of the smart motorway. If you have driven on the M42, you’ll see the motorway is most of the time chocked with the traffic and you hardly get a chance to drive past 40 or even 30mph.</p><h4>So what went wrong here?</h4><p>After removing hard shoulders, the government introduced emergency refuge areas on M42 around 600 meters apart. In case of breakdown, the driver can pull over in a safe place and wait for the rescue (what hard shoulder does really). The plan and testing proved to be a success and the government started to roll it out nationally.</p><p>That’s where the problem started to emerge. M42, drivers were different from M1, M6 or even M25. Using data from the M42 pilot, the government started converting other motorways to smart ones. So much so, the government increased the distance between each emergency refuge area to 2.5miles, thinking if 600 meters was fine on M42, it should be fine to increase it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*c7jWPFm5u2AOvmOV2lblxA.jpeg" /></figure><p>This change has resulted so far in 38 deaths in the last 5 years. When people break down in the active lane, they had no choice but to stay in the active lane and hope that someone in the control room will see them and shut the lane. Unfortunately, in some cases, it didn’t happen and they lost their lives.</p><p>What government failed to understand that driver on M42 is different than M6 or M1. Their driving habits and requirements are different. I use M4 regularly, but when I was using M25 for a few years, the way I drove on M25 was different from the way I drive on M4. Had the government piloted each motorway and changed the plan accordingly, it would not have resulted in causalities.</p><h3>What to learn from this?</h3><p>In the <strong>Comet</strong> case, I learnt that when designing something new, you have to test the prototype as rigorously as possible. Since it’s a new design, you will have to make sure the design does not have major flaws. Minor can be corrected later, but major flaw can cost you product as well as the user their lives!</p><p>In the case of <strong>Smart Motorways</strong>, all government has to do is test each motorway separately. Yes, difficult but at least should have got more qualitative and quantitative data instead of relying on a single pilot.</p><p>The reason for this article is that, whether you are an engineer/scientist or a UX designer, if you don’t test your finding and design or don’t use the right user for the testing, you are not only risking the failure of your product but risking people lives as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=917e64a68eda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-masters/design-without-or-little-testing-can-cost-lives-917e64a68eda">Design without (or little) testing can cost lives!</a> was originally published in <a href="https://medium.com/ux-masters">UX Masters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to align  Product & UX Design with Agile Development…]]></title>
            <link>https://medium.com/ux-masters/how-to-align-product-ux-design-with-agile-development-915bc7e7acaf?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/915bc7e7acaf</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[agile-ux]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Sat, 29 Feb 2020 11:47:57 GMT</pubDate>
            <atom:updated>2020-03-02T20:32:37.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to align Product &amp; UX Design with Agile Development…" src="https://cdn-images-1.medium.com/max/1024/1*y9QWMdQTWYHxR1TaqGODNQ.jpeg" /></figure><h3>How to align Product &amp; UX Design with Agile Development…</h3><p>Every day 100s of online job adverts appear for UX experts. Alongside the usual job description, there is a new trend starting to creep in recently, that “demands” UX to work within an Agile development environment.</p><p>I am in the UX field for almost 15 years working with enough organizations to prove this ‘demand’ unthoughtful. I am not sure who is actually responsible for this requirement, Product Owner, HR, Project Manager, or perhaps Development team. But one thing is confirmed that whoever wants a UX expert to follow the Agile sprints and deliver according to the agile framework from day one, haven&#39;t got a clue what is UX and how it works.</p><p>I am not implying that UX experts should stop working with Agile development completely, but knowing where UX connects with Agile development will make UX, Devs and stakeholders life a lot easier and lead to a great product.</p><h3>Scenario</h3><p>This is the most common scenario I have come across.</p><p><em>The business hired a UX expert to improve their current product UX. The existing development team is already working agile. The project plan has factored all the deliverables within 2 weeks sprints.</em></p><h3>Problems</h3><p>There are 4 fundamental issues with this scenario:</p><h4>1- Business does not know the difference between UX and UI.</h4><p>The business actually wanted a UI designer, but since they (like many others) did not know the difference, they hired a wrong expert for the job.</p><h4>2- Business is too late to hire a UX expert.</h4><p>Let’s assume business understand the difference between UX and UI. But they were too late to hire one. You cannot hire UX expert and push them into deliverables.</p><h4>3- UX isn’t about deliverables.</h4><p>This is totally wrong assumption that UX is all about deliverables. You cannot ask UX expert “We need wireframe for ABC, or information architecture for XYZ within a current sprint or next sprint. <strong>UX is about understanding the problem, finding the solution, validating it with the users and only then converting into deliverables.</strong></p><h4>4- User Stories have been written already.</h4><p>The business has got the user stories written already, without UX experts involvement. The biggest mistake businesses do is to write user stories from a business perspective and not from the users perspective.</p><blockquote>By doing this, you are asking a UX experts to work with one hand tied behind their back!</blockquote><h3>Solution</h3><blockquote>The solution is very simple, don’t force UX experts into following the existing project plan for deliverables. Create your plan only when UX have reached a valid outcome. Based on that outcome prepare your agile development plan.</blockquote><h4><strong>Here is my easy and proven solution if you really want to produce great products.</strong></h4><figure><img alt="UX and Product Design with Agile Development" src="https://cdn-images-1.medium.com/max/1024/1*lniv9CIcNzFUEOaHxxHMdA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915bc7e7acaf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-masters/how-to-align-product-ux-design-with-agile-development-915bc7e7acaf">How to align  Product &amp; UX Design with Agile Development…</a> was originally published in <a href="https://medium.com/ux-masters">UX Masters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New to UX Design? Things you should avoid!]]></title>
            <link>https://vertage.medium.com/new-to-ux-design-things-you-should-avoid-7f5eb516b31f?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f5eb516b31f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Fri, 08 Nov 2019 13:36:33 GMT</pubDate>
            <atom:updated>2019-11-08T14:00:59.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7rdxsQQAa4zj9dpo-f2fA.jpeg" /></figure><p>As the UX industry grows at an exceptional rate and businesses globally realizing it’s potential, more and more people are switching their profession to become UX experts.</p><p>Like any industry with an influx of newbies, it creates some issues. I’ll point out some here, which should be avoided by the newbies, that will definitely help the UX experts to identify the bad practices knowingly or unknowingly used by them, which are affecting the good UX and help the new UX breed to adapt to what is right instead of what is quick!</p><h3>If it’s not prototyped… It’s not UX’d</h3><p>The trend of not prototyping the design is on the rise like I have never seen before and once in a blue moon when I hear word prototype, it’s something that only allows users to navigate left, right top and bottom.</p><p>I am all up for low fidelity prototyping like above, but this is just to quickly validate your idea, similar to a low fidelity wireframe. Once you’ve validated your idea, prototype it properly to validate your design.</p><blockquote>“Prototype as if you know you’re right, but test as if you know you’re wrong.” Stanford’s d.school</blockquote><p>Without an interactive prototype, you cannot test your design and without testing, it’s not UX, simple as that.</p><h3>Don’t fool yourself with disruptor tools!</h3><p>Back in the days, there were design tools like, Photoshop, Illustrator, Fireworks, Axure that required proper hardcore training and learning to call yourself even average users. Most of these tools are still around and the only limit is your imagination. You can achieve literally anything with these tools if you know what do you want.</p><p>But now tools like Figma, Innvision, Sketch, Framer, Adobe XD, Balsamiq and list goes on are disrupting (or destroying) the proper UX. I am seeing big complex systems are fully designed in Framer or Figma.</p><p>These tools are destroying the good UX and churning wannabe UX experts like never before. With few youtube videos and online tutorials, people are turning into Sketch expert user or master of Figma.</p><p>I am not against these tools as long as they are only used for quick validation although paper and whiteboard is still a better medium for this. But relying your design solely on these disruptors is a bad idea and should be discouraged by industry experts.</p><blockquote>“Learn the tools where the only limit is your imagination… Not the ones that limit your imagination!”</blockquote><h3>Designing without Interaction? You sure you are a UX Designer?</h3><p>I cannot stress enough: <strong>DON’T</strong> ignore the interaction design when working on a UX project. Time and time again I have seen design projects are being produced without any consideration to interaction design. Yes, there are some situations where you probably don’t need to define interactions, but for most projects interaction design is as important as the design of the project.</p><p>It gives you the ability to test your prototype with the users and the more interaction you add to your prototype more realistic feedback you’ll get from the users. If you have ever observed the users during usability testing, you will notice that they tend to explore the site or app rather sticking to your test script, that’s human nature. Therefore your prototype depiction should be as real as possible wherever your user’s touchpoints are on the prototype.</p><p>If your prototype has no or very little interaction, your users will know it’s a fake and their behaviour will change towards your prototype and you’ll miss out on very real and useful insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZtqEz59Fq5io04VG1glKg.jpeg" /></figure><blockquote>How users will feel if you are testing a car <strong>auto park feature</strong> and give them a car without side and back mirrors? Although both aren’t relevant to test case but you have to add realism!</blockquote><h3>Don’t mess with the process… It will mess you up!</h3><p>In a nutshell, UX is a combination of various exercises done in certain steps. Don’t change it. It’s like nature, as soon as you start messing with it, it hit back with brutal force. Same goes with UX, if you start changing the process, you will disturb the whole UX ecosystem.</p><p>If you start with the UI, then go on testing the UI with the users, then prototype it, or wireframes then UI and then prototype… There is something seriously wrong with this process. I am not making it up, I have seen it happen. This kind of approach can significantly increase the project cost, slow down the process.</p><blockquote>In general UX process is: Research &gt; Wireframes &gt; Prototype &gt; Test &gt; UI &gt; Launch &gt; Measure. You should never swap these. Maybe you don’t have time to follow the whole journey, then drop something but never swap!</blockquote><h3>The client is innocent until proven guilty!</h3><p>There are some clients who want to drive your UX approach as per their own wishes, and you’ll struggle to get your thoughts across. But even then, always treat your client innocent, until they come across difficult during the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jfa03MDPBz988ZSPvE-rPQ.jpeg" /></figure><p>In most cases, they will take your lead and trust in your abilities and approach. They are like a child, they will believe whatever you say wrong with their system and what you think is the best way forward.</p><p>Don’t betray their trust. Don’t present them something purely based on your recommendation. You may be wrong, you may be biased. Always validate your design with the real users if users are backing your design only then stand firm on your grounds!</p><blockquote>Design like you are 100% right but validate it with the users as they might prove you wrong and there is no shame about it, that’s what UX is at the end!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f5eb516b31f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX and UX Design aren’t the same things!]]></title>
            <link>https://medium.com/ux-masters/ux-and-ux-design-arent-the-same-things-abbd95b241f?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/abbd95b241f</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 15:39:40 GMT</pubDate>
            <atom:updated>2019-08-01T15:58:40.939Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oyd5SmwZU84d_lVB82vpA.jpeg" /></figure><h4>Let me tell you what UX Design is…</h4><h4>Let’s look at the popular UX definitions first</h4><h3><strong>Wikipedia UX Definition</strong></h3><blockquote>In commerce<strong> User Experience</strong> (UX) refers to a person’s emotions and attitudes about using a particular product, system or service.</blockquote><h3>Don Norman &amp; Jakob Nielsen UX Definition</h3><blockquote>User experience” encompasses all aspects of the end-user’s interaction with the company, its services, and its products.</blockquote><p>If you haven’t noticed already, both definitions are referring to User Experience (UX) without word Design. These are User Experience definitions, not UX Design. It shows that user experience goes beyond design, for example, I buy something from Amazon, the buying experience is mainly driven by the UX Design, however my experience as a user does not end here, if something goes wrong with the item I have purchased and I need to return it; how they accept my return, how they deal with my complaint, how they rectify the problem etc is all part of my experience. Although their digital experience might be great, overall experience what matters most.</p><p>In this article, I’ll be mainly explaining the UX Design, not the UX. We must differentiate between UX Design and UX as a whole.</p><blockquote>User Experience is born as a result of a successful marriage between Design and Customer Experience.</blockquote><blockquote>A great UX is a seamless handover of users to relevant teams like sales, support etc that convert a design into the great Customer Experience. This completes the User Experience.</blockquote><h3>Let’s focus on UX Design</h3><p>UX design involves understanding the user and implementing the UX Design best practices using various exercises. It is a big part of user experience as a whole. UX Design mainly based on 6 key phases.</p><h4>1 — Define</h4><p>This is the first phase of any project or product. In this phase, we define the directions. This involves exercises such as:</p><ul><li><strong>Project kick-off meeting<br></strong>This exercise is to know everyone involved, stakeholders and other people directly or indirectly linked to the project. This is normally done by the UX Designer and PM by inviting relevant people into the meeting.</li><li><strong>Information Gathering<br></strong>As it’s clear by the name, once kick-off meetings are over, you should collect all the information related to the project. In some cases, it’s already available in a written format, but mostly you’ll have to go around and gather everything on your own or with PM.</li><li><strong>Stakeholder Interview<br></strong>Interviewing stakeholders is very important. Sooner you do it better for the end-results. You would have identified the stakeholders by now after project kick-off meetings, now you would need to book meeting with all stakeholders whose decisions can impact the project and understand what their objectives and targets are and how it will align with the user needs.</li><li><strong>Understanding Business Objectives<br></strong>You would need to understand the business objective behind the project. For example, if a business is launching a website selling ebooks. You would need to understand what business is trying to achieve with that. It’s just might not be the same reason as you might think. They might be building a database so they might not be interested in money at all. So it’s extremely important to understand the business objectives.</li><li><strong>Project Strategy<br></strong>The most important exercise in the Define phase is the project strategy. This is a document where you write down your strategy from start till the end of a project. This will include key information you’ve learnt from the Define phase and show your project plan from UX Design perspective. Don’t make it a long document, few pages are more than enough and always circulate it with the main stakeholders so they know what your plan is and what has been agreed.</li></ul><h4>2 — Analyse</h4><p>This is the second phase where we analyse the project in details. This phase consists of various segments explained below.</p><ul><li><strong>Product/Project Analysis<br></strong>It’s very important to understand the product or project you going to work on, you can do that by working with product owners, UX researchers and project managers. Without understanding the product, you cannot design experience, it’s as simple as that.</li><li><strong>Competitor Analysis<br></strong>In most cases, you will be working on a project whether it’s new or improvement, that has been built before either like for like or similar concept. While staying well clear from copying the idea, it’s important to analyse those products, learn how they have built it, what you can learn from their mistakes, where their UX could have been better etc. For example, if you are designing a new financial application, and majority competitor have a similar sign-up process, you will get an idea that what kind of constraints you could face from compliance.</li><li><strong>Existing Flow Mapping<br></strong>It only implements to existing products. You don’t have to do it, but I always prefer doing it if time permits. This let me see the full product right before my eyes. Just map every user engagement touchpoint with the product and soon picture starting to appear where the main pain points are.</li><li><strong>Users Interviews<br></strong>Well, it’s very obvious to know your users before you try to offer them something. I cannot stress enough to involve users in a very early stage of the project to test your idea with them. Presuming you already have user data from UX researchers beforehand, if NOT this is the best time to talk to them. Ask them about their habits, run your raw idea to them, ask them questions, NOT a lot, but the right ones.</li><li><strong>Information Architecture<br></strong>It works for both new or existing products. IA help you place the information and content that flows with the user needs. It’s very important to work with users to build the right IA. Card sorting is a good exercise to conduct with users for this.</li><li><strong>Journey Mapping<br></strong>It’s similar to the flow mapping, but this can be applied on new and existing projects. It is focused on to journey rather the whole product. There will be one main journey and then multiple journeys with different scenarios within that, so you have to be careful to map the ones you are working on. For example, if your project has a feature to send money abroad, this is your user’s main journey, and scenario can be existing users only, or new users only etc.</li></ul><blockquote><strong>Content is the KING</strong></blockquote><blockquote>This is not part of the formal UX process, but you should make it. A wrong message can ruin the best user experience!</blockquote><blockquote>Before going into the design phase, try to get the original content if you can, if it’s too early, which it might be, but at least get the essence of content from PMs or POs. You can use placeholder content in wireframes, but try to use original or close to original content on your prototypes.</blockquote><blockquote>Also, insist the content creators, PMs, POs to tell a story when writing a content.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UN8xr9OElx65Mjbc4BqYTg.png" /></figure><h4>3 — Design</h4><p>I hope you are starting to see the big picture by now as to where Design falls in the UX design process. If you do not follow the above processes, and jumping straight to design, it’s not UX Design, but UI design.</p><ul><li><strong>Wireframes<br></strong>Now that&#39;s the time to put everything you’ve learnt so far on a paper. You can use paper to quickly validate your idea or use tools like Axure, Sketch to draw detailed wireframes. But don’t spend too much time on wireframes. Wireframes are for idea validations not to drive the design.</li><li><strong>Prototype<br></strong>The prototype is probably one of the most important elements of your whole UX Design process and when I say don’t spend too much time on a wireframe, I want to say to use that time on the prototype instead. The prototype is your product, so it has to look and work like a product. It is debatable whether to go for a fully interactive prototype or just basic interactions. My vote is with fully interactive one, or at least make your core features fully interactive as it would be in the live product. Imagine if Elon Musk had created the first Tesla car with full metal body with batteries inside but left the steering out, or digital display out.</li></ul><blockquote>Give your users a feel as they are using the real product to get <strong>real</strong> feedback.</blockquote><ul><li><strong>Interactions<br></strong>This should be part of the prototype but due to its importance, I am keeping it separate. I have seen many times that great user experience is ruined by bad interactions. Error handling, haptic feedbacks, transitions etc are as important as any other design elements. These small bits play a major role in overall UX success. AND this should be done by you, not developers or designers. You as UX Designer, it’s your job to define interactions in a prototype. For example, if you think you lightbox should be used instead of a popup, or error should be displayed over the button instead underneath, it is your call, you have to design that interaction in the prototype and then test it with your users.</li></ul><blockquote><strong>Test it NOW!</strong></blockquote><blockquote>This is the time to test your prototype. I won’t go into details explaining how or where to recruit your users but you have to test your prototype now. If you don’t test it now, I can guarantee, it will be a very costly lesson for you and your organization not very far in future. No matter how great or experienced designer you are, the user will prove you wrong sooner or later, therefore I cannot stress enough to test your prototypes with real users.</blockquote><blockquote>Identify the flaws, go back to prototype and fix them, and retest. This is your best bet to fix the product without spending a fortune.</blockquote><blockquote>There are multiple tools to test your prototypes, e.g <a href="https://www.userzoom.com/">Userzoom</a>, <a href="https://www.trymyui.com/">TryMyUI</a> and <a href="https://www.usertesting.com/">UserTesting</a> etc.</blockquote><h4>4 — Launch</h4><p>This is the phase where UX Designers handover their deliverables/findings to other teams, like UI designers, developers etc.</p><ul><li><strong>User Interface<br></strong>Again, it’s debatable but I believe that UX Designers should not design the UI even if you can, presuming you have dedicated UI team. If you’ve done the UX design properly, you deserve a break now. You can surely observe the UI, but don’t influence it. Let the experts do their job now.</li><li><strong>Development<br></strong>You as a UX Designer keep a very close connection with the development team. These are the people who will have to translate your prototypes in to live product. Development should be involved from the beginning of the project, so you know the limitation system might have before you suggest something.</li><li><strong>Go Live<br></strong>That’s it, project/product goes live.</li></ul><blockquote><strong>It’s not over YET!</strong></blockquote><blockquote>Most UX designers will think that their job is done once the product is launched. It’s NOT. You can safely work on other projects now but YOU have to measure the success of the live project. Now the feedback you get will be in it’s purest form and that data is no less than gold for you.</blockquote><blockquote>Collect the data from the live project, identify any flaws, see if something can be improved, go back to Analyse phase and start again.</blockquote><blockquote>If you don’t measure, you will never know that months of hard work you put in this project was successful or not. Measure it, even for your own peace of mind!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abbd95b241f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ux-masters/ux-and-ux-design-arent-the-same-things-abbd95b241f">UX and UX Design aren’t the same things!</a> was originally published in <a href="https://medium.com/ux-masters">UX Masters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How stakeholders destroy Products UX!]]></title>
            <link>https://vertage.medium.com/how-stakeholders-destroy-products-ux-5e9c7389a247?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e9c7389a247</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 10:28:35 GMT</pubDate>
            <atom:updated>2022-01-25T16:52:00.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFCgolCElsUASWBhT--aLw.jpeg" /></figure><h3>How stakeholders negatively impact Product’s UX!</h3><p>I have been to quite a few job interviews throughout my career from small to big and all sorts of organizations. I will share my experience and what I have learned about how some stakeholders knowingly or unknowingly destroy the product UX.</p><h3><strong>The Situation</strong></h3><p>Once I went for an interview for one of the biggest British household names from the courier sector for a UX designer contract position. Sat in a room with 3 stakeholders, after introductory discussion, one of the interviewers who happened to be the product owner, presented me a PDF containing a nicely designed user interface of the project they were looking to hire a UX designer for. I did know beforehand about the project, I was also told that it’s an ongoing project, which I have to take over from an agency. I was expecting that the agency would have done the user research, information gathering and other analysis. However, all I was being shown was a PDF slide after slides of pure UI design.</p><p>I asked, What is this? if you don’t mind me asking, their response; it’s a UX deliverable we’ve commissioned a few months ago to a “very well known” agency as mentioned in the role description.</p><p>I politely told them that what they are showing me is a UI design, which is kind of the last step of a fairly complex UX design process. And it is usually based on identifying your users, analysing your competitors, idea generation, testing the ideas, designing wireframes, testing the prototype with users etc. There must have been something your agency has based this UI design on. To my surprise, that was all they’d been given.</p><p>This was the point where I realized that they have no idea what UX is. What exactly happened was that agency, sold them cool looking user interfaces claiming to be the UX design and obviously billed them for the UX. (Agency side story after this section)</p><p>Another interviewer who was quiet until this point said that she agrees with everything I have said but unfortunately a significant amount of money has been spent in this UI in the last few months therefore even UX best practices haven’t been implemented, we aren’t able to go back to the drawing board and start from scratch. And this has been seen and approved by the top management. I asked what exactly they need me for? The answer was to convert this UI into an interactive prototype for the developers!</p><h3>The Lesson</h3><p>Obviously, that’s where I decided not to go ahead with this role. We carried on talking for a full hour though.</p><p>Now you can see, how stakeholders went on spending loads of money without actually understanding the UX, or perhaps misguided by the agency. In either case, there was no way back without having some serious accountability. Senior management had approved their UI and a lot of money was spent already, at this point saying oops, we’ve messed it up would have definitely had some heads rolling.</p><blockquote>No one wants to bell the cat now. And that’s my friends how BAD product is borns!</blockquote><h3><strong>Now the Agency side</strong></h3><p>This time I was working on a project for another big UK household name from the financial sector. I was part of an agency that was working for this organization. During this short contract, I was able to witness in great detail, how the agency delivers the UX project.</p><p>Here goes: I was given one chunk of a fairly large ongoing project, but I saw that agency was delivering just UI to their client for other parts of the project I wasn’t involved with. I cannot name the client but I can guarantee that if I name it, at least UK residents will not comprehend that this company would actually accept UI inside the UX envelope. Anyhow, I did my part of the project using UX best practices as much as I could. From time to time I warned the agency project owners, account managers and PMs of what we are doing is not really a UX, it’s just a UI. And how it could actually harm their relationship with the client if someone like me ends up working for them and starts asking the question as I did during my interview.</p><p>But that probably fell on the deaf ears and things remain the same, unfortunately. I moved on after completing my bit. I don’t think there was a deliberate attempt to misguide the client, but just a lack of basic UX understanding, since there are so many UX designers whose main focus is still UI design could be another reason.</p><p>Now picture the first part of this story, where I have been shown exactly the same thing as the agency I was working doing for their client. You can see exactly where is the problem, both sides stakeholders do not have a clue what UX really is.</p><blockquote>These are just 2 experiences out of many more with very similar situations. UX is still relatively new to many businesses and without proper training to their non-UX staff, this issue will not be resolved. I am sharing some tips for the people who deal with the client from either side, without UX background.</blockquote><h3>Tips for Stakeholders</h3><ul><li>Whether agency or internal stakeholder, please learn the basics of UX if aren’t familiar with it.</li><li>UX field is very vast and with a lot of misinformation floating around, if you do not have a UX designer, get one, or at least take advice from one if you cannot have one onboard.</li><li>Understand the difference between UI and UX design.</li><li>Colourful UI printed on paper or converted into PDF does not become UX design. Don’t be fooled by that.</li><li>Always ask the agency to provide the details and results from different UX exercises they’ve conducted before reaching the UI design.</li><li>Always ask about your user’s research.</li><li>If you’re agency side stakeholder, always ask for the user analytics from the client and use that data to build your concepts.</li><li>Demand proofs of the user testing, remember if it hasn’t been tested by the users, you may as well just go straight into UI.</li></ul><p>Last but most important, if you realize that you missed the UX process, there is always a time to do it correctly. You may don’t realize but the best time to fix the product is before it goes live, yes you might lose some initial investment and miss some deadlines, but it’s still worth comparing to what you might end up launching without fixing it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e9c7389a247" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Tips from Google HR, when applying for UX Designer job!]]></title>
            <link>https://vertage.medium.com/8-tips-from-google-hr-when-applying-for-ux-designer-job-3dda97780ed8?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dda97780ed8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[ux-design-job]]></category>
            <category><![CDATA[working-at-google]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Fri, 22 Feb 2019 08:35:52 GMT</pubDate>
            <atom:updated>2019-02-22T08:35:52.271Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*scjc9d-1o_MQCiYEdXDKpQ.png" /></figure><p>There is no second opinion when it comes to working for a Google, especially in the UX team. Google is one of the very few organizations where UX possibilities are endless, with 100s of products and services portfolio and billions of users worldwide, what else you need to stretch your UX limits.</p><p>A recruiter from Google once approached me for a UX Designer position they were recruiting at Google London. I wasn’t able to proceed due to other commitments but the recruiter kindly provided me with some tips when applying at Google for UX designer position. Tips are mainly focused on the portfolio as what they want to see and what you need to present to make your chances significantly higher.</p><p>So if you applying for UX designer position at Google, following these tips might increase your chances to get a UX designer job at Google.</p><ol><li><strong><em>We’d love to see how you think and what your design process is.</em></strong></li><li><strong><em>We appreciate samples of lo-fi work, such as conceptual models, sketches, storyboards, scenarios etc.</em></strong></li><li><strong><em>Avoid only showing single screenshots of products or websites when possible.</em></strong></li><li><strong><em>Do show us navigation flows, explaining how features are connected.</em></strong></li><li><strong><em>Annotate each project and tell us what you have contributed. What were your role and responsibilities? What did you design? What was the motivation for the design?</em></strong></li><li><strong><em>Please make sure your images are resized to keep the file size reasonable.</em></strong></li><li><strong><em>Add links to live websites wherever possible.</em></strong></li><li><strong><em>Please do not include any confidential material.</em></strong></li></ol><p>These tips are provided directly by Google HR, you can obviously add your personal touch.</p><p>Hope this helps</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dda97780ed8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Designers — Contracting or Permanent?]]></title>
            <link>https://vertage.medium.com/ux-designers-contracting-or-permanent-bab45b4ea4d?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/bab45b4ea4d</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[contracting-or-permanent]]></category>
            <category><![CDATA[ux-jobs]]></category>
            <category><![CDATA[ux-designer]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Sat, 26 Jan 2019 13:30:02 GMT</pubDate>
            <atom:updated>2019-01-29T09:28:55.625Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hTcJA6rI3x6GNxliQXigkw.jpeg" /></figure><h3>Pros &amp; Cons of Permanent UX Designer Job!</h3><p>Whether you are experienced or a newbie, unless you run a business your employment is either permanent or contractor/freelancer. These are the choices we make regardless of the profession.</p><p>In the first article, I will be pointing out the pros and cons of permanent employment. In the following article, I will do the same for contracting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R34iTrf2J266DADszvvO1g.jpeg" /></figure><h3>Permanent UX Designer</h3><p>I won’t explain what actually permanent employment is because it’s a very common type of job across the globe, so let’s just jump straight into pros and cons.</p><h4>Pros:</h4><p><strong>Financial stability &amp; security:</strong> The main advantage of working as permanent UX designer is obviously financial stability, this is rather applicable to everyone in the permanent job regardless of UX or otherwise. You know exactly what and when you going to get which gives you more stability and security.</p><p><strong>Perks and privileges:</strong> You get the benefits of permanent employment, such as medical, pension, life cover, paid holidays, sick leave etc. With these many perks, you can focus more on producing great UX rather worrying about your retirement or getting ill.</p><p><strong>Less pressure in the beginning:</strong> Being permanent UX designer, you aren’t expected to start producing as soon as you land in the job, you can take your time, settle down, know the people and processes around you and pick up the steady pace. It can be between few weeks to few months.</p><p><strong>Progression and growth:</strong> When you work in an organization as a permanent employee, you have the chance to grow. You can climb the ladder and can reach senior and management levels.</p><p><strong>Your name on the leaderboard:</strong> If you are confident enough and producing great UX, your name goes on the leaderboard and have a face in the company. Your words will be taken more seriously with an authority.</p><p><strong>Powers to implement processes:</strong> The best advantage being permanent UX designer I have seen is that you have the powers and authority to implement the processes, educate the colleagues and set the UX culture in the organization. You can aim for short and longterm goals and then achieve them.</p><p><strong>Lead the direction:</strong> Since you have joined the company for longterm, you can set the UX directions and lead the rest. You can plan well ahead for the future.</p><p><strong>More money to spend:</strong> You can push for new ideas, new tools and if that requires financial backing, the organization is very likely to allow that.</p><p><strong>Friends rather colleagues:</strong> Well, it can fit on both, but being contractor it’s unlikely you going to stay at one place for long. At permanent your stay is longer, your colleagues become your friends, there are stronger connections between people you’ve been working with for years rather 2 months.</p><p><strong>Appreciation:</strong> If you are producing great UX, you will be appreciated by everyone, you will be commended by the top management, unlike contractors who mostly are unsung heroes regardless of their achievements.</p><h4>Cons:</h4><p><strong>Your skills can become rusty:</strong> Unless you’re working in an organization where you have a chance to work on various projects and they are evolving with UX trends, it’s very likely that in few years time, your skills will become rusty and you will end up doing the same thing again and again.</p><p><strong>Internal politics:</strong> Well, we all know it exists, some places have little some have a lot, but there isn’t a single place without politics.</p><blockquote>“As a UX designer, internal politics is cancer for your profession. Unfortunately, how to avoid and manage this will be up to you but if untreated, it can destroy your career”</blockquote><p><strong>Slow pace:</strong> There will be many occasions, you will end up moving at snail pace. The most common reason is that there is no push and if the stakeholder isn’t available you are less likely to find the alternative way to move forward.</p><p><strong>Appeasement over delivery:</strong> You are more likely to appease colleagues and management because your financial and progressional benefits are directly linked with performance report in the hand of management.</p><blockquote><strong>Non-UX related manager:</strong> Not always the case but if you end up reporting into a manager whose background is not UX, it can be very disastrous for your career. Unfortunately, this is something you will not be able to change and very likely outcome is you quitting if you are true user advocate. Unless your manager gives you open playing field and moves out of your way when it comes to UX related decisions, which is very unlikely.</blockquote><p><strong>Stolen credit:</strong> It happens all the time in every industry if you are unlucky to fall in the category where your hard work credit has been stolen by someone else, there is nothing much you can do about it. Unlikely contracting where you are not bothered about internal credits but rather building up your portfolio.</p><p><strong>Wife, not a girlfriend:</strong> Permanent UX designer is like being in the marriage, ups or downs, good or bad, like or hate it, you have to deal with it. There is no easy way out, as your employment goes longer, harder it becomes to quit no matter how unhappy you are. Obviously, there’s always the option to quit, but looking in contracting context, it’s fairly difficult.</p><p><strong>Less time for yourself:</strong> In permanent employment, you will have less personal/family time to enjoy compared to contracting. When your contract finishes, you can easily take month or 2 breaks obviously if you’ve got the finances to do so. In UX job market, if you are good, I can almost 100% guarantee you that you aren’t going to sit on the bench for very long so you can take long breaks between contracts, unlikely in permanent jobs where you have 25ish holidays to take and you can’t take more than 3 weeks consecutively.</p><p><strong>Feeling Stagnant:</strong> It does not apply if your company has multiple products/services and you are involved with some or all of them. But if you end up working for just single project/product/service, at some point you will be starting to feel stagnant. If you are after challenges and experimenting ideas, rather happy to receive a pay cheque and other benefits at the end of a month, then you could become depressed with this situation pretty quick.</p><p><em>These are some the advantages and disadvantages of being a permanent UX designer from my 12+ years career. Obviously, everyone has a different experience and may not agree with some points. As a UX designer, it’s your decision at the end based on your circumstance to decide whether you want a permanent or contracting, I have pointed out some points to make your decision little easier.</em></p><h4>In the next article, I will be reviewing contracting. Stay tuned :)</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bab45b4ea4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get a UX Designer job!]]></title>
            <link>https://vertage.medium.com/how-to-get-a-ux-designer-job-ada697fd5b45?source=rss-177fe98f9209------2</link>
            <guid isPermaLink="false">https://medium.com/p/ada697fd5b45</guid>
            <category><![CDATA[ux-careers]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-portfolio]]></category>
            <dc:creator><![CDATA[Ahsan Jalil]]></dc:creator>
            <pubDate>Tue, 01 Jan 2019 18:27:35 GMT</pubDate>
            <atom:updated>2019-01-02T15:50:46.978Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81375dWhIaBaRlL7xCt9OQ.jpeg" /></figure><p>If you haven’t read my previous article about <a href="https://medium.com/@vertage/how-to-become-a-successful-ux-designer-929502473356">how to become a successful UX designer</a>, please read it <a href="https://medium.com/@vertage/how-to-become-a-successful-ux-designer-929502473356">here</a>. How to land in a UX job is a continuation of my previous article.</p><p>In this article, I’ll give you insight from both sides of a table, as a candidate and as a hiring manager.</p><h3><strong>Preparation</strong></h3><p>Let’s start with the preparation. Like any job, whether experienced or beginner, you have to prepare yourself. The first thing you need to ensure that you are mentally ready for your next or the first job if you have any doubts or plans, which clashes with your search, it’s best to solve them first. For example, you think you aren’t ready yet, or you have long holidays booked etc. Don’t go to the market if you are unsure about anything, this can harm your reputation amongst organizations and recruiters in the long run.</p><h3>Your CV — Do’s and Don’ts</h3><p>A CV is a key part for any job, I am not going into details explaining how important CV is when it comes to searching for a job. So let’s go straight into what you need in your CV as a UX Designer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Y7EgPa2q7Q6KpI-kaVXLw.jpeg" /></figure><h4><strong>Don’t</strong></h4><ul><li>I have seen countless times that UX designers CVs are excessively filled with graphical elements, although I am not against such style, but <strong>don’t overdo it</strong>. Consider your CV solving a problem of a hiring manager, if they have to think or struggle to understand it, you aren’t good UX designer.</li><li><strong>Don&#39;t write a long summary</strong> of your interests, extracurricular activities and your charity work. Keep it short and a very brief overview of yourself explaining, who you are and what are your strengths.</li><li><strong>Don’t try to cramp your CV into 2 pages.</strong> Yes, it’s better to keep it short, but don’t compromise the content just because someone told you to stick to 2 pages.</li><li><strong>Don’t use CV templates.</strong> It’s a lot easier to pick the template and change the details, but not a good idea. Take the inspirations from the template and others CVs, but create your own. For UX jobs, you have to be creative with your CV and can’t just use a text-based word document</li><li><strong>Don’t list every skill/software you’ve used once. </strong>Only the ones you are experienced and the ones you have a working knowledge.</li><li>Don’t write long paragraphs in your job summaries. Paragraphs are good, but they don’t give the answers quickly enough, so <strong>avoid long paragraph</strong>.</li><li><strong>I don’t want to know your “A day in your life”</strong> avoid using self-centred content which isn’t relevant to the job or the profession.</li><li>Finally, whatever format you design your CV in, <strong>make sure you have Word format readily available</strong>. Most recruiters ask for this format for mainly 2 reasons, one; their CV filtering system cannot read pdf or other image formats, secondly; when they forward your CV, they remove your personal details, which is not easy to do in other formats.</li></ul><h4><strong>Do’s</strong></h4><ul><li>It’s very important to <strong>list your key skills right at the top</strong> of the page, ideally right next to your summary. When I am hiring, the first thing I’ll be looking for your skills, the tools you use and other non-software related skills, like UX exercises you can perform.</li><li>If you are experienced (even in a different industry) <strong>list previous experience</strong>. This will show your professional acumen.</li><li><strong>Include the logos </strong>of the organizations you’ve worked for. This will colour up your CV stand up more than text and a lot easier to get noticed even without reading your CV.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TollAJrRI4T0gnq2g0O3AQ.png" /></figure><ul><li><strong>Use bullet points</strong> when writing your past experiences. Make it clear what you did and how you did it. Remember, it’s UX designer CV, you solve problems, so tell what was the problem and how did you solve it.</li><li><strong>Include infographic showing your UX process.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MK9B_5qLdz8LaDYxgRmWyA.png" /></figure><ul><li><strong>Your CV should reflect your professionalism</strong>. If you aren’t a good writer, it’s worth getting it checked by a professional writer, it will cost a little bit but it’s worth it.</li><li><strong>Create your LinkedIn profile</strong>, and keep it up to date along with your CV, there shouldn&#39;t be any discrepancies between your CV and LinkedIn.</li><li>If you have worked in many companies, <strong>I highly recommend drawing your timeline</strong> with very little information alongside detailed CV, use your employer, date worked, your position and employer URL.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3PwSzcGtKz2DpGhfWc3Mw.png" /></figure><ul><li><strong>Always keep your CV up to date</strong> even if you aren&#39;t looking. It’s not a great analogy, but it fits perfectly here. <em>Countries who aren’t even in the war still keep spending billions on their defence budget, because you never know when you need to defend yourself.</em> The same logic applies here, you never when you are out of job or when the great opportunity knocks.</li></ul><h3>Your Portfolio</h3><p>Being a UX designer, the one most important thing for you to land a job is your portfolio. Over 15+ years of my UX experience, I have seen very few portfolios that are actually well crafted. Below are few helpful tips.</p><ul><li>If you don’t have past experience, <strong>do experimental work</strong> and create a portfolio so the hiring manager can understand your UX approach and process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okkxeAPLed3r5eaEq3PaMg.jpeg" /></figure><ul><li><strong>List every project as a case study.</strong> As I said, you are a UX designer and your job is to provide solutions. Your portfolio should highlight the problem then how did you solve it and what was the outcome.</li><li><strong>Don’t write too much text</strong> with each exercise you have conducted. For example, if you did a card sorting exercise to create navigation, just write what you were trying to achieve and show the visual results.</li><li>If you’ve worked on many projects, <strong>don’t create a portfolio for every project</strong>, just 3 or 4 case studies are more than enough. All I need to see is your UX processes and the solution you offered.</li><li>You can create your portfolio either PDF or online, but make sure it’s not huge file if PDF, as most of the time you will be emailing it to the people and most organization’s email server does not accept large files.</li><li><strong>Include your CV into the portfolio</strong> so it starts with your CV list your portfolio in the same file. It’s easy to keep track of it and you will not have to send multiple files.</li></ul><h3>Applying for jobs</h3><p>I would strongly recommend going for contracting initially. Contracting is a great way to gain a wealth of experience in a short span of time. You will get loads of opportunities to work on multiple projects and to polish up your UX skills. Apart from that, some useful tips:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*ewg--qnNdLpvqZ_8.png" /></figure><ul><li><strong>Don’t post your CV on every single job site</strong> on the internet. Instead pick the most reliable and authentic websites like:<br>- <a href="http://www.monster.co.uk/">www.monster.co.uk</a><br>- <a href="http://www.linkedin.com/">www.linkedin.com</a><br>- <a href="http://www.cwjobs.co.uk/">www.cwjobs.co.uk</a><br>- <a href="http://www.jobserve.co.uk/">www.jobserve.co.uk</a><br>- <a href="http://www.jobsite.co.uk/">www.jobsite.co.uk</a></li><li><strong>Tweak your CV slightly if you have to</strong> for the job you are applying.</li><li>It’s old school and not asked very often but if asked, <strong>write a cover letter</strong>, and highlight your good points and how you are a good candidate for the specific job.</li><li>When applying for a job, <strong>keep the emotions away and stay dignified</strong>. If you are searching for a while without luck, don’t let those negative emotions reflect in your application.</li><li><strong>Stay positive and persistent.</strong> Keep applying even if you aren’t getting any response. You’ll eventually reach your goal, trust me.</li><li>If you’ve applied for a job, which you were very positive about hearing back and did not get any response, <strong>don’t lose your sleep over it</strong>. Remember, there is always someone better than us out there who might have got that job.</li><li>This is slightly controversial and some may not agree, but I <strong>never chase up after applying for a role</strong>. I have done my part, if they like me, it’s their part to reach out to me for the next step. I will never recommend chasing companies after you’ve applied for a job. If they need you, they’ll come to you.</li></ul><h3>An Interview</h3><p>Well done for coming this far. If you’ve been invited for an interview, it means you’ve beaten a big pile of CVs. The interview is the last stage to impress the hiring manager so you have to put all your energy and passion at this stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0fCtjHhw_rodUx63aGm2BQ.jpeg" /></figure><ul><li>This stage can be a bit stressing on the nerves. I have seen many experienced candidates getting nervous, and that is absolutely fine. Just be normal and <strong>don’t over think or pretend to be someone else</strong>.</li><li>I won’t go into details how to dress up or don&#39;t’ turn up as you’ve just woke up, but one very important bit, which I haven’t seen mentioned anywhere, that if you can, <strong>wear a nice perfume</strong>. You’ll be spending an hour at least with the group of people, if you smell good, this will make the overall room atmosphere fresh and fragrance has the tendency to change the mood to positive.</li><li>Before the interview, <strong>do your research on the company</strong>, more you know about your potential employer is better. What they do, what are their products and services, what is their culture and what is their mission.</li><li>If you have time and opportunity, I highly recommend <strong>picking some existing UX issues</strong> from their products or service or even a website and provide some solution to those issues. Don’t spend too much time doing it. This will show the hiring team that you are proactive and keen to take initiative on your own. But remember, don’t come across arrogant, present the issues in a friendly way and end with telling them the solution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0M85BJAs2ddWXvr9IXhZTA.jpeg" /></figure><ul><li>If the interview room has the whiteboard or flipchart try to <strong>draw your process</strong>. Ask for permission first and then draw your UX process. This will show the team that you 1- you can draw 2- you are confident 3- you can present. It’s very important to step and highly recommended if given a chance. <em>I assign a 10 minutes challenge to the candidates during an interview to draw quick end-to-end journey on a whiteboard e.g sell the drone to the first-time website visitor, what they do on the whiteboard is the 80% of the decision making</em>.</li><li><strong>Don’t come across desperate</strong> during the interview but passionate. You have to show that you need UX challenges not “just a job”.</li><li>Some interviewers will be loaded with questions taken from google, like where you see yourself in 5 years, what you will bring to the organizations etc. These are standard questions, so while preparing for UX interview, don’t overlook these as they can be thrown at you anytime.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VlAr9-PTyfsIMGdpOgePxw.jpeg" /></figure><ul><li>It’s extremely likely that you will be working in a small or large team of similar people. The last thing you have to show is that you like flying solo. If you are experienced, <strong>learn where to use “I” and where to use “WE”</strong>. For example, you did the prototype on a project where 20 other UX designers were working, the prototype is <strong>I</strong> and the project is <strong>WE</strong>.</li><li><strong>Ask questions</strong>, every interviewer will ask you at the end do you have any questions for us. Ask them about the company’s UX culture, their UX processes, how they recruit users for testing, how much access you will have to raw or filtered data, who you will be reporting to etc. You need to determine that the job you’ve applied for is UX designer job and not UI designer. The last thing you want to do is a job titled as UX and responsibility of UI. Don’t do it!!</li><li>One question, you should never leave the interview without asking</li></ul><blockquote><strong>“Where do you think I could have performed better?”</strong></blockquote><p>This is million dollar question, trust me I cannot stress enough to ask this question. You may not always get an answer but most of the time you will get an honest answer. I always respond to this question if someone asks. I always ask this question myself, you will be surprised how many time answer of this question will help you improve further and prepare for your next job.</p><p>Goodluck!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ada697fd5b45" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>