Usability: the ability of a user to accomplish a task successfullyUX: entire interaction of a user using a product, including thoughts, feelings, perceptionsMetric - way of evaluating a particular phenomenonMyths:<ol><li>Too much time to collect data -> Data can be collected in a few extra mins during an interview or testing session</li><li>Too much money -> Even free tools offer reliable insights</li><li>Not useful when focusing on new improvements -> Improvements need to have a baseline when measured throughout the change</li><li>Data doesn't help understand causes -> It can if done properly with qualitative data</li></ol>

Introduction to main definitions and myths

5.Too noisy -> You don't need to measure everything, only what is important6.You can trust your gut -> No, you cannot, we are biased7.They don't apply to new products -> They do because they set baselines for future improvements8.No metrics for our specific issues -> There is a metric for everything9.Not appreciated by management -> If presented properly it should be10.Small sample size -> You don't need a big sample size to use UX metrics, even <20 users is enough

More myths about collecting UX data

Independent variables - you can control in your studies (e.g. age of participants)Dependent variables: you cannot control, you get as a result of the experiment (e.g. success rate)Data types:<ul><li>nominal/categorical: unordered groups (e.g. gender). Cannot be compared against each other</li><li>ordinal: it can be compared against each other but the distance between the values is not meaningful (e.g. excellent, good, fair, poor)</li><li>interval: differences between values are meaningful but there is no 0 point (e.g. freezing point of water is not the absence of heat)</li><li>ratio: they have an absolute 0 (e.g height)</li></ul>

Types of data in UX metrics

You cannot improve what you cannot measure.

Measuring the User Experience was the first book that focused on how to quantify the user experience. Now in the second edition, the authors include new material on how recent technologies have made it easier and more effective to collect a broader range of data about the user experience. As more UX and web professionals need to justify their design decisions with solid, reliable data, Measuring the User Experience provides the quantitative analysis training that these professionals need. The second edition presents new metrics such as emotional engagement, personas, keystroke analysis, and net promoter score. It also examines how new technologies coming from neuro-marketing and online market research can refine user experience measurement, helping usability and user experience practitioners make business cases to stakeholders. The book also contains new research and updated examples, including tips on writing online survey questions, six new case studies, and examples using the most recent version of Excel. Learn which metrics to select for every case, including behavioral, physiological, emotional, aesthetic, gestural, verbal, and physical, as well as more specialized metrics such as eye-tracking and clickstream data Find a vendor-neutral examination of how to measure the user experience with web sites, digital products, and virtually any other type of product or system Discover in-depth global case studies showing how organizations have successfully used metrics and the information they revealed Companion site, www.measuringux.com, includes articles, tools, spreadsheets, presentations, and other resources to help you effectively measure the user experience

business

Business

product

Product & Design

Measuring the User Experience was the first book that focused on how to quantify the user experience. Now in the second edition, the authors include new material on how recent technologies have made it easier and more effective to collect a broader range of data about the user experience. As more UX and web professionals need to justify their design decisions with solid, reliable data, Measuring the User Experience provides the quantitative analysis training that these professionals need. The second edition presents new metrics such as emotional engagement, personas, keystroke analysis, and net promoter score. It also examines how new technologies coming from neuro-marketing and online market research can refine user experience measurement, helping usability and user experience practitioners make business cases to stakeholders. The book also contains new research and updated examples, including tips on writing online survey questions, six new case studies, and examples using the most recent version of Excel.<ul> <li>Learn which metrics to select for every case, including behavioral, physiological, emotional, aesthetic, gestural, verbal, and physical, as well as more specialized metrics such as eye-tracking and clickstream data</li> <li>Find a vendor-neutral examination of how to measure the user experience with web sites, digital products, and virtually any other type of product or system</li> <li>Discover in-depth global case studies showing how organizations have successfully used metrics and the information they revealed</li> <li>Companion site, www.measuringux.com, includes articles, tools, spreadsheets, presentations, and other resources to help you effectively measure the user experience</li></ul>

Bill Albert

Tom Tullis

Measuring the User Experience

A UX audit is a relatively cheap way to inspect the experience of your website. It is conducted by professional reviewers that are aware of common design patterns and UX best practices and can therefore empathise with the users of a website while running the UX analysis.

What is a UX audit?

1. Know your personas well A UX auditor needs to familiarize themself with at least 2 core personas who will be using the website. Write their main characteristics and navigate the website with their traits in mind.2. Know the company's business goalsIt is ideal if the UX auditor is aware of the main business and financial goals of the company, particular milestones or KPIs.3. Competitor AnalysisIt is useful to look at a few competitors to see how they compare with you. 4. UX best practicesThe auditor should consider looking at industry UX best practices to establish a baseline for great UX.

What to do before conducting a UX audit

Conducting a UX audit for a product is a cost-effective way of noticing important issues 

💬 Title UX Audit & Analysis | Heuristic Evaluation ===== 📒 Description In this video, we're going to look at one of my favourite companies websites @Gymshark @Ben Francis and run a UX Evaluation on their Homepage and Navigation to learn how to conduct and report an analysis like this with a realistic project. Like & Subscribe Episode 15 ===== 🔗 Links mentioned in this video • NNG Heuristic Evaluation - https://www.nngroup.com/articles/ten-usability-heuristics/ ===== 🎥 Watch next 👉 Learn Figma for Beginners - https://youtu.be/ZYHIhcAWudg 👉 UX Sitemap Tutorial - https://youtu.be/dyU2gRqXuEM 👉 UX Card Sorting Tutorial - https://youtu.be/9ux5OMaO7Bk 👉 UX Tree Testing Tutorial - https://youtu.be/IVlzrE30K5E 👉 Intro to UX Research - https://youtu.be/dFlACTzeq0w 👉 UX Tutorial Playlist - https://www.youtube.com/watch?v=9ux5OMaO7Bk&list=PLeE9jCDOL6iypebNVjwCsT_V8oTjdjp-f ===== 🕰 Timestamps 0:00​ - Introduction 00:14 - Project Overview (What you'll learn) 00:32 - What is UX Audit & Analysis 01:33 - Why do we do it? 02:20 - When to do the Audit & Analysis 02:54 - How to do it 03:32 - What you need to get started 06:14 - The Project & Self-assessment to understand your experience and shortcomings 07:07 - Initial Research to fill your knowledge gap 07:39 - Why GYMSHARK as our project? 08:16 - Competitors and Design Patterns I looked at 08:56 - Our Customer Personas & Journeys 10:37 - Audit & Analysis Template Walkthrough 12:33 - Conducting the Audit & Analysis 12:47 - E-Commerce Navigation Evaluation 13:40 - Navigation Problem #1 15:22 - Navigation Problem #2 16:55 - Navigation Problem #3 18:18 - Navigation Problem #4 19:47 - Navigation Problem #5.0 #5.1 #5.2 #5.3 23:29 - Navigation Problem #6 24:35 - Navigation Problem #7 25:30 - Navigation Comments / Questions 26:00 - E-Commerce Homepage Evaluation 26:10 - Homepage Problem #1 26:50 - Homepage Problem #2 27:48 - Homepage Problem #3 28:30 - Homepage Problem #4 28:47 - Homepage Problem #5 29:03 - Homepage Problem #6 29:13 - Homepage Problem #7 29:30 - Homepage Problem #8 29:50 - Recommendations Report 32:10 - Post Audit & Analysis 32:22 - Outro ===== 🔗 Connect • https://linktr.ee/arysh ===== 👍 Like & Subscribe If you appreciate the hard work that went into this video, please show me some love by dropping a Like 👍 and sharing it with other people that you think can also benefit from this. If you have any questions, post a comment down below, and I’ll get back to you when I can. If you haven’t subscribed already, what are you waiting for? Subscribe and turn on the notification 🔔 so that you know when I upload new videos. ===== 🙃 About me My name is Ari. I’m a digital product designer and developer with over 12 years of experience based in Sydney, Australia. I currently work for a startup, freelance on the side and make these videos to give back to our tech community. If you have any suggestions on how to improve these videos, then let me know! ===== 📧 Contact me If you have any questions, comment on one of the videos or follow me and ask me on Instagram via DM. If you have a business-related question, email me at - ary@arysh.com ===== 🔢 Subscriber Count 714 ===== 📑 Hashtags #UIUXDesign #UXResearch #HeuristicEvaluation

💬 Title

UX Audit & Analysis | Heuristic Evaluation

=====

📒 Description 

In this video, we're going to look at one of my favourite companies' websites @gymshark @BenFrancis and run a UX Evaluation on their Homepage and Navigation to learn how to conduct and report an analysis like this with a realistic project.

Like & Subscribe

Episode 15

=====

🔗 Links mentioned in this video

• NNG Heuristic Evaluation - https://www.nngroup.com/articles/ten-usability-heuristics/
• Figma Template - https://aripxl.com/content/ux-audit-&-analysis-heuristic-evaluation-2022

🔗 Referral Links
You can support this channel by using my referral links

♥️ Download Figma - https://psxid.figma.com/it2ka6qdk5dl
🦆 Sign up for Spaceduck - https://spaceduck.com

=====

🎥 Watch next

👉 Learn Figma for Beginners - https://youtu.be/ZYHIhcAWudg
👉 UX Sitemap Tutorial - https://youtu.be/dyU2gRqXuEM
👉 UX Card Sorting Tutorial - https://youtu.be/9ux5OMaO7Bk
👉 UX Tree Testing Tutorial - https://youtu.be/IVlzrE30K5E
👉 Intro to UX Research - https://youtu.be/dFlACTzeq0w
👉 UX Tutorial Playlist - https://www.youtube.com/watch?v=9ux5OMaO7Bk&list=PLeE9jCDOL6iypebNVjwCsT_V8oTjdjp-f

=====

🕰 Timestamps

0:00​ - Introduction
00:14 - Project Overview (What you'll learn)
00:32 - What is UX Audit & Analysis
01:33 - Why do we do it?
02:20 - When to do the Audit & Analysis
02:54 - How to do it
03:32 - What you need to get started
06:14 - The Project &  Self-assessment to understand your experience and shortcomings
07:07 - Initial Research to fill your knowledge gap
07:39 - Why GYMSHARK as our project?
08:16 - Competitors and Design Patterns I looked at
08:56 - Our Customer Personas & Journeys
10:37 - Audit & Analysis Template Walkthrough
12:33 - Conducting the Audit & Analysis
12:47 - E-Commerce Navigation Evaluation
13:40 - Navigation Problem #1
15:22 - Navigation Problem #2
16:55 - Navigation Problem #3
18:18 - Navigation Problem #4
19:47 - Navigation Problem #5.0 #5.1 #5.2 #5.3
23:29 - Navigation Problem #6
24:35 - Navigation Problem #7
25:30 - Navigation Comments / Questions
26:00 - E-Commerce Homepage Evaluation
26:10 - Homepage Problem #1
26:50 - Homepage Problem #2
27:48 - Homepage Problem #3
28:30 - Homepage Problem #4
28:47 - Homepage Problem #5
29:03 - Homepage Problem #6
29:13 - Homepage Problem #7
29:30 - Homepage Problem #8
29:50 - Recommendations Report
32:10 - Post Audit & Analysis
32:22 - Outro

=====

🔗 Connect

• https://ariurl.com
• https://aripxl.com

=====

👍 Like & Subscribe 

If you appreciate the hard work that went into this video, please show me some love by dropping a Like 👍 and sharing it with other people that you think can also benefit from this. If you have any questions, post a comment down below, and I’ll get back to you when I can. If you haven’t subscribed already, what are you waiting for? Subscribe and turn on the notification 🔔 so that you know when I upload new videos.

=====

🙃 About me

My name is Ari. I’m a digital product designer and developer with over 12 years of experience based in Sydney, Australia. I currently work for a startup, freelance on the side and make these videos to give back to our tech community. If you have any suggestions on how to improve these videos, then let me know!

=====

📧 Contact me

If you have any questions, comment on one of the videos or follow me and ask me on Instagram via DM. If you have a business-related question, email me at - ari@aripxl.com 

=====

🔢 Subscriber Count

714

=====

📑 Hashtags

#UIUXDesign #UXResearch #HeuristicEvaluation

Mission & Purpose:
My mission is to help and enable Designers around the world to do what they love and get paid for it. 

Channel:
This channel is dedicated to all things design and development. I talk about and teach UI Design, UX Design, Product Design and Development. 

Please consider subscribing in order to support the channel :)

About Me:
Hi, my name is Ari, I'm a Product Designer and Developer with over 12 years of experience. I live in the beautiful city of Sydney in Australia.
 
Throughout my career, I have been lucky to have worked with some amazing companies (from Startups to Corporates) with multiple positions from Junior to Head/Director to VP in order to build teams, and improve brands and product experiences. I've also owned a design and dev studio for a small period where I've worked with incredible brands. 

I have a passion to teach, learn and sharing knowledge and that is the sole purpose of this channel.

Ari Pxl

UI UX Audit & Analysis Tutorial | GYMSHARK Case Study Included | 2022

Games have existed probably for more than 3000 years, the first we can recollect being the invention of rolling the dice in Persia. However, gamification is a different term, which is defined by including the game experience in elements that are naturally not necessarily all fun and games.

What is gamification? 

In order for a game to be fun, it has to respect four principles:<ul><li>it is tied to a goal: every goal has an outcome in mind, a definition of win or lose or of finding something</li><li>it has rules: every game has constraints that its players has to know and respect in order for the game to exist</li><li>feedback: there is constant feedback on how you are progressing in the game</li><li>voluntary participation: what makes it fun is that it is not mandatory to play it, and people can choose not to enter it or start it whenever they want</li></ul>

Basic principles of game fun

The easiest way to boost endorphin release with gamification is create situations where your users will feel they have achieved something. Rather than giving rewards for clicking buttons, you need to create challenges that actually require skill and effort to complete. If they feel they have worked hard, they will get that feeling of fiero and with luck a hit of endorphins.

<ol><li>Manage the mission: whenever using gamification, it is crucial to have a mission tied to it (e.g. we want our gamification to result in 80% of people coming to our platform 1 week after onboarding) </li><li>Monitor motivation: at each step, understand what motivates the user and if your game mechanics are applied correctly</li><li>Measure the metric: at each step, measure where you are compared to the original mission</li></ol>

The 3Ms of Gamification

There are different types of players in a game with different motivation: <ul><li>The Achiever - the objective is to collect accomplishments among the way and showcase status (10% of people)</li><li>The Explorer - he/she wants to discover and learn new things (10% of people). Likes to gradually discover new areas and skills</li><li>The Socializer - wants to collaborate with others, the objective is to achieve things but not on their own, rather in teams (70-80% of people)</li><li>The Killer - want to see other people lose and he/she winning compared to them (1% of people)</li></ul>

Player-Centered Design

Gamification can boost engagement in a product if tied to the right motivation

What You’ll Learn: The power of gamification and how it can increase user engagement and fulfilment . Why and how gamification is not the same as game design. H...

problemsolving

Problem Solving

creativity

Creativity

Gamification - How to Create Engaging User Experiences

Useful = allows a user to accomplish an objective in a certain contextUsable = useful + enablement of the user to perform an actionUsed = useful + enablement + adoption. The ultimate goal of a product.

Useful,  Usable and Used have different meanings

Some questions to guide<ul><li>Life goals – what does the user aspire to in their life? How might your product get them to that goal? What would motivate a user to choose your product over a competing product that achieves this objective?</li><li>Completion goals – what do users expect to happen at the end of using your product? What can you measure when this takes place?</li><li>Behavioral goals – when users undertake achieving the goal without using your product, how do they do it? How can your product mimic that process so that the product is familiar to them? </li></ul>

Ease of Use

Oftentimes, usability is mistaken with user experience, but in reality, it is just a part of it. Usability, on its own, is also not only ease of use, but rather a sum of multiple aspects: <ul><li>effectiveness - the ability to complete a task</li><li>efficiency - effectiveness + speed</li><li>engagement - looking right (typography, navigation)</li><li>error tolerance - preventing users to do errors</li><li>ease of learning - appropriate onboarding on a product or learning about new releases</li></ul>

Usability

Imagine a product has 7 different buttons, that whenever pressed with low or high intensity, they produce different results for users: <ul><li>Useful - has a purpose in the user's life</li><li>Usable - enables the purpose of a product to be brought to reality</li><li>Findable - the product and its content are easy to find</li><li>Credible - has built trust that it can accomplish the promised purpose</li><li>Desirable - good brand, image, identity, aesthetics and emotional design</li><li>Accessible -  a product's ability to be used by as many people as possible (e.g. impaired people)</li><li>Valuable (its production costs don't outweigh its usefulness)</li></ul>

The 7 Factors of User Experience

<ul><li>Top Management Support: Getting resources from top management to test innovative ideas</li><li>Market Orientation: Ability to conduct user and market research to bring them closer to the need of users</li><li>Technology: Suitable for the market selected</li><li>Knowledge management: Information sharing between teams helps bring down the knowledge silos</li><li> Development Strategies: Teams can negotiate and bring input to the roadmap</li><li> Development Speed: Being fast enough to provide value ahead of competitors</li><li> Development Process: Clear processes for design and development</li><li>Product Teams: Bringing different input for the product </li></ul>

Factors of success for new product development

Adoption is the ultimate goal of a product. For it to happen, the Product works with the marketing teams:<ul><li>Pre-Design Phase: Market research determines if the user base is large enough to make a product profitable; user research looks into its value & usability. </li><li>Design Phase: Designers ensure the product is desirable & usable, and marketers work to release news and build anticipation for the release.</li><li>Launch Phase & Beyond: Involve channel partners, distributors, influencers to spread the word; press releases, social media, free trials where possible. Get meaningful metrics to measure adoption.</li></ul>

Turning prospects into users

Appropriation can have two meanings: <ul><li>the usage of existing objects to create different contexts than originally thought (e.g. dressing in clothes from another culture)</li><li>the usage of a product in an unintended way  (e.g. using a block of cement instead of a hammer with a nail). </li></ul>It is desired that companies look to integrate their products in other contexts to attract more users, but should pay attention to copyrights issues.

Appropriation

There are different stages of a product and different strategies apply to each of them: <ol><li>Market Introduction: High costs, low sales, little competition, customer education, marketing investment, low profitability</li><li>Growth: Declining costs, higher sales volumes, profitability appears, brand awareness, competitors appear</li><li>Maturity: Declining costs, sales at peak, more competitors, brand differentiation needed, profitability declines</li><li>Decline: costs not optimal, sales decline, prices fall, profitability depends on efficiency of production and distribution</li></ol>

Using the Product Lifecycle

There are different types of adopters at each product stage:<ol><li>innovators: like taking high risks and have a good discretionary income. Naturally knowledgeable in the product space. Marketing and UX teams should identify them before launch to design for mass scale</li><li>early adopters: influential, thought leaders in the product space, educated in social media, with high level of education and reasonable income</li><li>early majority: risk averse, like to compare products before buying, lower income than the first 2 </li><li>late majority: skeptical, like to use trial and tested products</li><li>laggards: don't like change</li></ol>

Types of product adopters

Having a used product is more important than product market fit and usability

What You’ll Learn: Why adoption and appropriation matter to a product’s success. How to place adoption and appropriation in context with UX and usability work.....

personaldevelopment

Personal Development

marketingandsales

Marketing & Sales

entrepreneurship

Entrepreneurship

Get Your Product Used: Adoption and Appropriation

What is Continuous Discovery? It is a product management framework for embedding customer input on every product decision.  You know when a company does Continuous Discovery when members building the product have weekly discovery calls with customers to reach a desired outcome.

The definition of Continuous Discovery

To make this a reality, a team needs to live by: a) Being outcome-oriented: to think about the value they provide rather than the outputb) Being visual: expressing  ideas not only through written/spoken words, but also by drawing c) Thinking in continuous terms: to regard research not as a project, but as a continuous action done at any step they needd) Being experimental: to be bold to consider experiments and not fully-built features to validate assumptionse) Being collaborative: anyone can bring any input when brainstormingf) Being customer-centric: to think from the customer perspective

The mindset of Continuous Discovery

The most important thing to clarify is the outcome, which should be narrow enough to be managed by the team realistically, but large enough open new opportunities.When exploring a new discovery space, the Product Trio (Developer, Designer, PO, but not limited to these roles) should start individually drawing out what they think the current experience of the customer is. It is important that everyone does it individually, at first, as to not bias each other when presenting. After exposing their opinions and discussing, it's time to merge all the experiences into one.

How to start

When interviewing users, do not ask them direct questions, but try to elicit stories and past experiences. Once they start remembering events, dig deeper and excavate these stories in more detail to capture the full experience. Set this expectation from the beginning with the user.During an interview, imagine each user event is a story, so set the scene right (location, event that triggered it, other people involved in the scene, steps taken, failures, end state). After you collect your insights quickly in an interview snapshot, go back and update your experience map based on what you learned.

Continuous Interviewing

Metrics that can be used in product management:<ul><li>Business Outcomes (measures business value): e.g. number of customers, retention, number of users</li><li>Product Outcomes (measures how the business value is created through product): e.g. time saved performing an action, satisfaction during onboarding</li><li>Traction Metrics (measures usage of specific features): number of clicks on a feature</li></ul>Other important definitions: <ul><li>Lagging Indicators: usually business outcomes, measuring something after it has happened</li><li>Leading indicators: usually product outcomes, they can predict the direction of the lagging indicator</li></ul>

Outcomes

Ideas to recruit for continuing interviewing<ul><li>ask support from customer success teams: If a customer calls to cancel their subscription, schedule an interview; If a customer has a question about feature x, schedule an interview; If a customer requests a customization, schedule an interview</li><li>recruit in-app in specific user journeys</li><li>form a customer advisory board (recruit few loyal customers that you get to interview every month)</li></ul>

Recruiting for interviews

Imagine the problems users have as trees. The root of a tree is a big problem, that causes multiple other problems/branches to arise. Every branch needs to be different from the others, otherwise, it needs to be rethought. To decide whether an opportunity belongs to a tree, we need to ask:<ul><li>Is this opportunity framed as a customer need, pain point, or desire and not a solution? </li><li>Is this opportunity unique to this customer, or have we seen it in more than one interview? </li><li>If we address this opportunity, will it drive our desired outcome? </li></ul>

Opportunity-Solution Tree (OST)

<ul><li>Vertical Opportunities - not recommended, either add multiple branches into one root or do more research on sibling opportunities</li><li>Multiple parents -no opportunity should have two parents</li><li>Opportunities not specific - wishes and feelings do not constitute opportunities (eg I wish this had a good user experience)</li><li>Solutions in disguise - opportunities should not mean or use features, but needs</li><li>Capturing feelings as opportunities - Capture the cause of the feeling and not the feeling itself (e.g.  I feel frustrated when using the product)</li></ul>

Anti-Patterns of OST 

<ol><li>Assess your first level opportunities by contrasting them against each other. </li><li>Do the same for the children of the opportunities until you reach one you'd like to test</li></ol>Criteria:<ul><li>Number of users and customers affected</li><li>Frequency of the problem</li><li>Market factors</li><li>Company factors</li><li>Customer factors</li></ul>

Prioritizing Opportunities

Different types of assumptions can exist for an idea: <ul><li>Desirability: Is the product wanted by users or has it been only mentioned once in a discussion? </li><li>Viability: Is the idea realistic for the business? Even the most desirable idea is not worth investing in if it is not profitable.</li><li>Feasibility: Do the law and regulations or technology allow it? </li><li>Usability: Is it usable enough for the user? Can customer actually do their tasks in good time? </li><li>Ethical: Should it be built, or is it against moral principles? Does it collect potentially dangerous data, that can be used for unintended purposes? </li></ul>

Identifying Hidden Assumptions

First, we imagine an existing solution for the opportunity. We map users and write the steps they need to do in the solution sequentially over time (e.g. User comes to create content -> Users opens the editing mode -> User edits content -> User publishes content)For each step we start writing its assumptions. E.g.User comes to create content:<ul><li>Desirability: Our user wants to create content.  Our user wants this on our platform.</li><li>Usability: Our user knows to create content on our platform.</li><li>Feasibility: Our platform is available for the user to create content.</li></ul>This continues for all steps.

Story-map solutions to find assumptions

Not all assumptions need to be tested. To identify what is more critical at this moment, we can prioritise them on a quadrant, in which horizontally we have scale of evidence (how much evidence we have for it to be true) and vertically importance of the assumption (how critical it is to happen so that the idea is possible). We then place each assumptions on the quadrant relative to each other. This is not a precise exercise, but rather one that helps us select what we know now. We then start with few of them from top-right corner (most important with the weakest evidence).

Prioritising Assumptions

A team can run around 15-20 discovery iterations a week. The tools that should be in a team's toolbox are:<ul><li>unmoderated user testing: allows you to test a prototype with participants at their own time, for which you get a video of their work</li><li>one-question surveys</li><li>database data. E.g. what people are searching in the search bar</li></ul>What not do to:<ul><li>avoid overly complex simulations</li><li>not defining evaluation criteria</li><li>testing with the wrong audience</li><li>designing for less than the best case scenario</li></ul>

Running Assumption Tests

Having the right framework and process in place makes 80% of the work in product management.

"If you haven't had the good fortune to be coached by a strong leader or product coach, this book can help fill that gap and set you on the path to success." - Marty Cagan How do you know that you are making a product or service that your customers want? How do you ensure that you are improving it over time? How do you guarantee that your team is creating value for your customers in a way that creates value for your business? In this book, you'll learn a structured and sustainable approach to continuous discovery that will help you answer each of these questions, giving you the confidence to act while also preparing you to be wrong. You'll learn to balance action with doubt so that you can get started without being blindsided by what you don't get right. If you want to discover products that customers love-that also deliver business results-this book is for you.

books

Books

"If you haven't had the good fortune to be coached by a strong leader or product coach, this book can help fill that gap and set you on the path to success." - Marty Cagan How do you know that you are making a product or service that your customers want? How do you ensure that you are improving it over time? How do you guarantee that your team is creating value for your customers in a way that creates value for your business? In this book, you'll learn a structured and sustainable approach to continuous discovery that will help you answer each of these questions, giving you the confidence to act while also preparing you to be wrong. You'll learn to balance action with doubt so that you can get started without being blindsided by what you don't get right. If you want to discover products that customers love-that also deliver business results-this book is for you.

Teresa Torres is an accomplished writer whose work has resonated with readers around the world. Teresa Torres has published several books that explore a range of topics, from fiction to nonfiction, and has received critical acclaim for the ability to weave compelling narratives. Teresa Torres's writing style is known for its depth and authenticity, and has earned quite a loyal following of readers.

Teresa Torres

Continuous Discovery Habits

The fundamentals of any UI Designer to know are:<ul><li>color & contrast</li><li>white space (the space between design elements)</li><li>visual hierarchy (fonts, bold, italic, etc)</li><li>complexity vs simplicity</li><li>consistency</li><li>scale (size of the text and design) </li></ul>

UI Fundamentals

https://skl.sh/designcourse19 - First 500 people to sign up will get their first 2 months free! -- The Frontend Dev Course using this mockup is here: https://www.youtube.com/watch?v=8gNrZ4lAnAw -- Are you frustrated that you simply can't produce a good UI design? Sure, you clearly know and SEE what a great design looks like from the top designers on sites like Dribbble and Behance, but why can't you produce them? In this course, I'm going to help answer that question and provide you with a blueprint that's going to speed up your transition from producing ugly UI's as a beginner, to producing fantastic UI's. First, we're going to spend some time discussing the very important design fundamentals that you need to understand before you can start designing UI's. Then, we'll step into a design and prototyping app (Adobe XD, it's free! https://www.adobe.com/products/xd.html) and design a beautiful UI from scratch. While doing this, I'm going to describe exactly what's going through my mind as I piece together a UI. Let's get started! - - - - - - - - - - - - - - - - - - - - - - Subscribe for NEW VIDEOS! My site: https://designcourse.com My personal FB account: http://fb.com/logodesigner Coursetro FB: http://fb.com/coursetro Coursetro's Twitter: http://twitter.com/designcoursecom Join my Discord! https://discord.gg/a27CKAF ^-Chat with me and others - - - - - - - - - - - - - - - - - - - - - - Who is Gary Simon? Well, I'm a full stack developer with 2+ decades experience and I teach people how to design and code. I've created around 100+ courses for big brands like LinkedIn, Lynda.com, Pluralsight and Envato Network. Now, I focus all of my time and energy on this channel and my website Coursetro.com. Come to my discord server or add me on social media and say Hi!

https://skl.sh/designcourse19 - First 500 people to sign up will get their first 2 months free!
-- The Frontend Dev Course using this mockup is here: https://www.youtube.com/watch?v=8gNrZ4lAnAw
-- Are you frustrated that you simply can't produce a good UI design? Sure, you clearly know and SEE what a great design looks like from the top designers on sites like Dribbble and Behance, but why can't you produce them?

In this course, I'm going to help answer that question and provide you with a blueprint that's going to speed up your transition from producing ugly UI's as a beginner, to producing fantastic UI's. 

First, we're going to spend some time discussing the very important design fundamentals that you need to understand before you can start designing UI's. Then, we'll step into a design and prototyping app (Adobe XD, it's free! https://www.adobe.com/products/xd.html) and design a beautiful UI from scratch. While doing this, I'm going to describe exactly what's going through my mind as I piece together a UI. 

Let's get started!

- - - - - - - - - - - - - - - - - - - - - -

Subscribe for NEW VIDEOS!

My site:                                 https://designcourse.com
My personal FB account:   http://fb.com/logodesigner
Coursetro FB:                       http://fb.com/coursetro
Coursetro's Twitter:             http://twitter.com/designcoursecom

Join my Discord!                https://discord.gg/a27CKAF
^-Chat with me and others

- - - - - - - - - - - - - - - - - - - - - -

Who is Gary Simon?  Well, I'm a full stack developer with 2+ decades experience and I teach people how to design and code. I've created around 100+ courses for big brands like LinkedIn, Lynda.com, Pluralsight and Envato Network. 

Now, I focus all of my time and energy on this channel and my website Coursetro.com.

Come to my discord server or add me on social media and say Hi!

https://designcourse.com 👈 Learn UI/UX and CSS with my custom interactive courses.

New videos weekly on UI/UX

Hi, I'm Gary. I've created close to 100 courses from graphic design to advanced frontend development. I've worked with Envato Network's TutsPlus.com, DigitalTutors.com, Pluralsight.com, LinkedIn Learning & Lynda.com.

I teach full stack development! Which means you will see tutorials regarding UI/UX, Frontend Dev, Backend Dev, Graphic Design and more!

Interested in a sponsorship opportunity or review?  Contact me: contact@designcourse.com

DesignCourse

The 2019 UI Design Crash Course for Beginners

Ideally, the entire team should be onboarded before making a website accessible (product owner, developers, designers). It doesn't really work if there is only one person solely responsible for accessibility in an organization since that person will push against the goal of others to deliver fast. Make sure that it is a priority to train others during the work day to avoid people not prioritizing learning due to time.

1. Make sure everybody is onboard

A critical or primary user journey is a basic flow everybody has to perform in order to use the app.(E.g. Add an item to the card)A secondary user journey is a flow only power users can perform.(E.g. Change your profile avatar)Identify the user journeys (primary and secondary) of your product to identify the future work to be done on the most important product areas.Then, apply an accessibility checklist to each step of each user journey. Run through the checklist with every team member.

2. Identify critical and secondary user journeys

Steps each design has to confirm:<ul><li>Content has good color contrast (4.5:1 for smaller text, 3.5 for larger text, 14pt bold, 18pt regular)</li><li>Tab order is identified</li><li>Controls have accessible labels</li><li>There are multiple ways to interact with the UI</li></ul>

3. For the UX Designer

What the developer should pay attention to:<ul><li>Tab order is logical</li><li>Focus is properly managed and visible</li><li>Interactive elements have keyboard support</li><li>ARIA roles & attributes applied as needed</li><li>Elements are properly labeled</li><li>Testing is automated</li></ul>

4. For the Developer

Making your site more accessible can be a daunting task. If you are approaching accessibility for the first time, the sheer breadth of the topic can leave you wondering where to start - after all, working to accommodate a diverse range of abilities means there are a correspondingly diverse range of issues to consider. This talk will explain how to effectively review a site for accessibility and how to build accessibility considerations into your team process so each team member knows their role, and has the appropriate training material. The goal is for attendees to walk away with an actionable process which they can immediately use to assess and improve their products' accessibility and overall user experience. See all the talks from Google I/O '17 here: https://goo.gl/D0D4VE Watch more Android talks at I/O '17 here: https://goo.gl/c0LWYl Watch more Chrome talks at I/O '17 here: https://goo.gl/Q1bFGY Watch more Firebase talks at I/O '17 here: https://goo.gl/pmO4Dr Subscribe to the Google Developers channel: http://goo.gl/mQyv5L #io17 #GoogleIO #GoogleIO2017 event: Google I/O 2017; release: Publish;

career

Career

teamwork

Teamwork

Making your site more accessible can be a daunting task. If you are approaching accessibility for the first time, the sheer breadth of the topic can leave you wondering where to start - after all, working to accommodate a diverse range of abilities means there are a correspondingly diverse range of issues to consider.

This talk will explain how to effectively review a site for accessibility and how to build accessibility considerations into your team process so each team member knows their role, and has the appropriate training material. The goal is for attendees to walk away with an actionable process which they can immediately use to assess and improve their products' accessibility and overall user experience.

See all the talks from Google I/O '17 here: https://goo.gl/D0D4VE
Watch more Android talks at I/O '17 here: https://goo.gl/c0LWYl
Watch more Chrome talks at I/O '17 here: https://goo.gl/Q1bFGY
Watch more Firebase talks at I/O '17 here: https://goo.gl/pmO4Dr

Subscribe to the Google Developers channel: http://goo.gl/mQyv5L

#io17 #GoogleIO #GoogleIO2017 event: Google I/O 2017; re_ty: Publish;

Subscribe to join a community of creative developers and learn the latest in Google technology — from AI and cloud, to mobile and web.

Explore more at developers.google.com



Google for Developers

Pragmatic Accessibility: A How-To Guide for Teams (Google I/O '17)

<ul><li>/word/ - matches any string containing the substring "word". Note: it's case sensitive.</li><li>/[ab]/ - disjunction of characters: "a" or" b"</li><li>/cat|dog/ - disjunction of string cat and dog. To be read as: String containing "cat" or "dog"</li><li>/pupp(y|ies)/ - To be read as: string containing "puppy" or "puppies"</li><li>/[a-z]/ - shows an interval: any letter between "a" and "z"</li><li>/[^a] / - "^" shows negation when it's the first character inside brackets. To be read as: not containing "a"</li><li>/^The/ - Here "^" matches only the string which starts with the expression that follows it. E.g. The dog barks.</li><li>/s.$/ - "$" matches the end of the line. E.g. expression that matches any string ending with .s</li><li>/words?/ - "?" implies zero or one instances of the previous character. E.g. word or words</li><li>/b.y/ - "." shows any character between b and y. E.g. for the expression "busy life", the answer would be "us"</li><li>/a*/ - "*" shows any string of 0 or more "a"'s. To be read as: "String containing no a's or 1 ore more a's</li><li>/[ab+] / - "+" shows 1 ore more occurences of the previous character. To be read as:Any character containing 1 ore more ab's.</li><li>/\bthe \b/ / "\b" matches a word boundary. To be read as "matches a string which contains "the" isolated by other words. E.g. "in the club" but not "the other", </li><li> \d - contains any digit</li><li>\D - contains any non-digit</li><li>{n} - n occurences of the previous char or expression</li><li>{,n} - up to n occurences of the previous char or expresssion</li><li>{n, m) - from n to m occurences of the previous char or expression</li></ul>

 Natural Language Processing: Regular Expressions

Morphology is the study of word structure.
Words consist of one or more morphemes (cats= cat+ s). A morpheme is the smallest unit of language.
Morphemes can be of several types:
<ul>
<li>stem (can stand on its own)</li>
<li>affix (can't stand on its own)</li>
</ul>
Word formation can develop through:
<ul>
<li>inflection: forms of the same word. E.g. word, words; work, worked</li>
<li>derivation: not applicable to all words in a class; the meaning changes: e.g. act -> actor</li>
<li>compunds: stardust = star + dust</li>
<li>clitisication: word + clitic. E.g.: we're, you're</li>
</ul>
For counting words:
<ul>
<li>tokens: distinct occurences of word strings</li>
<li>types: distinct words</li>
</ul>
Lemmatization is a vocabulary reduction process of mapping words to their stem. E.g. sang, sung, sings to sing  
Stemming is the process of reducing words to stems. E.g. information to inform, retrieval to retriev
Types of errors:
<ul>
<li>ommision: related words are not reduced to the same stem. E.g. European and Europe</li>
<li>commision: unrelated words reduced to the same stems. E.g. policy and police are reduced to polic </li>
</ul>
Note: look at Minimum Distance Algorithm to determine the distance between words

Natural Language Processing: Word Formation

This book takes an empirical approach to language processing, based on applying statistical and other machine-learning algorithms to large corpora.Methodology boxes are included in each chapter. Each chapter is built around one or more worked examples to demonstrate the main idea of the chapter. Covers the fundamental algorithms of various fields, whether originally proposed for spoken or written language to demonstrate how the same algorithm can be used for speech recognition and word-sense disambiguation. Emphasis on web and other practical applications. Emphasis on scientific evaluation. Useful as a reference for professionals in any of the areas of speech and language processing.

writing

Reading & Writing

artsandculture

Society, Arts & Culture

scienceandnature

Science & Nature

Dan Jurafsky

James H. Martin

Speech and Language Processing

<code>There are 2 types of errors:</code><ul><li><code>slips </code><code>(a person intends to do an action and ends up doing something else). Can be: </code><code>action-based</code><code>(correct action applied to the wrong object), </code><code>memory-lapse</code><code> (forgetting)</code></li><li><code>mistakes </code><code>(wrong goal or wrong plan formed). Can be: </code><code>rule-based</code><code>(correct diagnose, wrong action), </code><code>knowledge-based</code><code>(incorrect diagnose), </code><code>memory-lapse</code><code> (failing due to distraction)</code></li></ul>

Types of Errors in Design

There are 3 levels of processing that inform the action a user does:<ul><li>visceral (lowest level, correlated with calm and anxiety). Actions: perform and perceive.</li><li>behavioural (middle level, correlated with expectations and emotions). Actions: specify and interpret.</li><li>reflective (highest level, correlated with satisfaction). Actions: plan and compare.</li></ul>

The 3 Levels of Processing that inform the 3 Stages of Action

<code>Affordances </code><code>- the relationship between the properties of an object and the capabilities of an agent</code><code>Signifiers </code><code>- an indicator that communicates appropriate behaviour to a person</code><code>Constraints </code><code>- impediments of using a system</code><code>Mappings </code><code>- the relationship between the elements of two sets of things</code><code>Feedback </code><code>- communication of the results of an action</code><code>Conceptual model </code><code>- explanation of how something works</code>

The fundamental concepts of Interaction

<ul><li>Incremental - Continuous Testing and Refinement. Starts from an existing product. Called also Hill Climbing (move your foot in one direction - if it is uphill, take one step. If not, change direction. Do that until the top of the peak). Con: cannot find a higher hill. </li><li>Radical - Starts fresh, many times from scratch. Offers potential very high opportunities. Con: the hill might be even lower than the one previously tried.</li></ul>

2 Innovation Forms

The more things change, the more they are the same.

Design doesn't have to complicated, which is why this guide to human-centered design shows that usability is just as important as aesthetics. Even the smartest among us can feel inept as we fail to figure out which light switch or oven burner to turn on, or whether to push, pull, or slide a door. The fault, argues this ingenious -- even liberating -- book, lies not in ourselves, but in product design that ignores the needs of users and the principles of cognitive psychology. The problems range from ambiguous and hidden controls to arbitrary relationships between controls and functions, coupled with a lack of feedback or other assistance and unreasonable demands on memorization. The Design of Everyday Things shows that good, usable design is possible. The rules are simple: make things visible, exploit natural relationships that couple function and control, and make intelligent use of constraints. The goal: guide the user effortlessly to the right action on the right control at the right time. The Design of Everyday Things is a powerful primer on how -- and why -- some products satisfy customers while others only frustrate them.

Design doesn't have to complicated, which is why this guide to human-centered design shows that usability is just as important as aesthetics.   Even the smartest among us can feel inept as we fail to figure out which light switch or oven burner to turn on, or whether to push, pull, or slide a door.   The fault, argues this ingenious -- even liberating -- book, lies not in ourselves, but in product design that ignores the needs of users and the principles of cognitive psychology. The problems range from ambiguous and hidden controls to arbitrary relationships between controls and functions, coupled with a lack of feedback or other assistance and unreasonable demands on memorization.   The Design of Everyday Things shows that good, usable design is possible. The rules are simple: make things visible, exploit natural relationships that couple function and control, and make intelligent use of constraints. The goal: guide the user effortlessly to the right action on the right control at the right time.   The Design of Everyday Things is a powerful primer on how -- and why -- some products satisfy customers while others only frustrate them.

Don Norman is an accomplished writer whose work has resonated with readers around the world. Don Norman has published several books that explore a range of topics, from fiction to nonfiction, and has received critical acclaim for the ability to weave compelling narratives. Don Norman's writing style is known for its depth and authenticity, and has earned quite a loyal following of readers.