UX Design Interview Questions and Answers

The elements of design are: LINE – The linear marks made with a pen or brush or the edge created when two shapes meet. SHAPE – A shape is a self contained defined area of geometric (squares and circles), or organic (free formed shapes or natural shapes). A positive shape automatically creates a negative shape. DIRECTION – All lines have direction – Horizontal, Vertical or Oblique. Horizontal suggests calmness, stability and tranquillity. Vertical gives a feeling of balance, formality and alertness. Oblique suggests movement and action SIZE – Size is simply the relationship of the area occupied by one shape to that of another. TEXTURE – Texture is the surface quality of a shape – rough, smooth, soft hard glossy etc. COLOUR – Colour is light reflected off objects. Color has three main characteristics: hue or its name (red, green, blue, etc.), value (how light or dark it is), and intensity (how bright or dull it is).

The elements of design are: LINE – The linear marks made with a pen or brush or the edge created when two shapes meet. SHAPE – A shape is a self contained defined area of geometric (squares and circles), or organic (free formed shapes or natural shapes). A positive shape automatically creates a negative shape. DIRECTION – All lines have direction – Horizontal, Vertical or Oblique. Horizontal suggests calmness, stability and tranquillity. Vertical gives a feeling of balance, formality and alertness. Oblique suggests movement and action SIZE – Size is simply the relationship of the area occupied by one shape to that of another. TEXTURE – Texture is the surface quality of a shape – rough, smooth, soft hard glossy etc. COLOUR – Colour is light reflected off objects. Color has three main characteristics: hue or its name (red, green, blue, etc.), value (how light or dark it is), and intensity (how bright or dull it is).

Here are some examples of the types of user research performed at each phase of a project. Card Sorting: Allows users to group and sort a site’s information into a logical structure that will typically drive navigation and the site’s information architecture. This helps ensure that the site structure matches the way users think.

Contextual Interviews: Enables the observation of users in their natural environment, giving you a better understanding of the way users work. First Click Testing: A testing method focused on navigation, which can be performed on a functioning website, a prototype, or a wireframe. Focus Groups: Moderated discussion with a group of users, allowing insight into user attitudes, ideas, and desires. Heuristic Evaluation/Expert Review: A group of usability experts evaluating a website against a list of established guidelines. Interviews: One-on-one discussions with users show how a particular user works. They enable you to get detailed information about a user’s attitudes, desires, and experiences. Parallel Design: A design methodology that involves several designers pursuing the same effort simultaneously but independently, with the intention to combine the best aspects of each for the ultimate solution. Personas: The creation of a representative user based on available data and user interviews. Though the personal details of the persona may be fictional, the information used to create the user type is not. Prototyping: Allows the design team to explore ideas before implementing them by creating a mock-up of the site. A prototype can range from a paper mock-up to interactive HTML pages. Surveys: A series of questions asked to multiple users of your website that help you learn about the people who visit your site. System Usability Scale (SUS): SUS is a technology-independent ten-item scale for subjective evaluation of the usability. Task Analysis: Involves learning about user goals, including what users want to do on your website, and helps you understand the tasks that users will perform on your site. Usability Testing: Identifies user frustrations and problems with a site through one-on-one sessions where a “real-life” user performs tasks on the site being studied. Use Cases: Provide a description of how users use a particular feature of your website. They provide a detailed look at how users interact with the site, including the steps users take to accomplish each task.

There are two main types of user research: quantitative (statistics: can be calculated and computed; focuses on numbers and mathematical calculations) and qualitative (insights: concerned with descriptions, which can be observed but cannot be computed). Quantitative research is primarily exploratory research and is used to quantify the problem by way of generating numerical data or data that can be transformed into usable statistics. Some common data collection methods include various forms of surveys – online surveys, paper surveys, mobile surveys and kiosk surveys, longitudinal studies, website interceptors, online polls, and systematic observations. Qualitative user research is a direct assessment of behavior based on observation. It’s about understanding people’s beliefs and practices on their terms. It can involve several different methods including contextual observation, ethnographic studies, interviews, field studies, and moderated usability tests.

User Experience (UX) research is the process of discovering the behaviors, motivations and needs of your customers through observation, task analysis, and other types of user feedback. Understand the user experience for new products, websites, mobile apps and prototypes. UX research helps brands and organisations accomplish the following: Understand the user experience for new products, websites, mobile apps and prototypes Make informed decisions through the product development process by testing various aspects of product designs Discover, optimise and evaluate the genuine user experience Understand each user interaction prior to conversion Nail the design and experience early in a product’s life cycle

There are many advantages of usability testing including: feedback direct from the target audience to focus the project team internal debates can be resolved by testing the issue to see how users react to the different options being discussed issues and potential problems are highlighted before the product is launched The business advantages of usability testing can be seen at the end of the project: it increases the likelihood of usage and repeat usage it minimises the risk of the product failing users are better able to reach their goals, which results in the business meeting its targets Disadvantages*.Usability testing provides many benefits, but there are a few disadvantages in using this methodology, which should be noted. Firstly, testing is not 100% representative of the real life scenario, e.g. a mother will not have her two young children running around like she might have at home. Also, usability testing is mainly qualitative, so does not provide the large samples of feedback that a questionnaire might, but the feedback can be far more accurate and insightful.

There are a few different types of usability testing or reasons to conduct usability research:

Comparative Usability Testing. Used to compare the usability of one website with another. Comparative tests are commonly used to compare a website against peer or competitor sites, however it can also be used to compare two designs to establish which provides the best user experience. Explorative Usability Testing. Before a new product is released, explorative usability testing can establish what content and functionality a new product should include to meet the needs of its users. Users test a range of different services where they are given realistic scenarios to complete which helps to highlight any gaps in the market that can be taken advantage of and illustrate where to focus design effort.

UX researchers have developed many techniques over the years for testing and validating product hypothesis and particular design decisions. The methods range from well-known lab-based usability studies to those that have been more recently developed. In this article, we will explore seven different usability testing methods when you should use them and why.Before you pick a particular testing method, you should have a clear understanding of your target audience, available resources (time and money), and research objectives. This information not only will help you select the relevant testing method but also adjust the questions and tasks for your test participants: Guerilla testing is the simplest form of usability testing. Basically, guerrilla testing means going into a public place such as a coffee shop to ask people about your prototype. Test participants are chosen randomly.Guerilla testing works best in the early stages of the product development process. Unmoderated remote usability testing occurs remotely without a moderator. It offers quick, robust, and inexpensive user testing results to be used for further analysis. Test participants are asked to complete tasks in their own environment using their own devices and without a moderator present, which leads to the product being used naturally. The cost of unmoderated testing is lower; however, this type of testing offers less detailed testing results. Unmoderated remote usability testing works the best when you need to obtain a large sample to prove critical findings from your initial moderated research. Contextual inquiry is less a usability testing method and more like an interview/observation method that helps a product team obtain information about the user experience from the real users.This technique is useful for getting rich information about users— their workspace, personal preferences, and habits. Card sorting is an excellent method for prioritizing content and features in user interface. The technique is relatively simple—all you need to do is place concepts (content, features) on cards and allow test participants to manipulate the cards into groups and categories.Card sorting is great when you want to optimize your product’s information architecture.

Usability testing is a method used to evaluate how easy a website is to use. The tests take place with real users to measure how ‘usable’ or ‘intuitive’ a website is and how easy it is for users to reach their goals.The key difference between usability testing and traditional testing (bug testing, acceptance testing etc.) is that usability testing takes place with actual users or customers of the product. Whilst traditional testing might be undertaken by a developer, designer or project manager, usability testing removes any bias by collecting feedback direct from the end user. Usability testing can be used in a variety of ways during your project lifecycle. Despite not being able to mimic real life usage, usability testing is still the best method of ensuring your website supports users in achieving their

goals quickly and easily. When businesses meet the needs and expectations of their users, they are more likely to develop a successful service.

Prototyping is the 4th step of the design thinking process.Before you determine how you should go about the prototyping process, you have to have identified the users, defined their problem, and brainstormed and selected a proper solution in the form of a product or service. Listed below are the steps in the prototyping methodology: Identify Obstacles .Start by brainstorming with your team to identify any obstacles that may delay or block your prototyping or product designing process. Having these identified prior to designing will allow you to take precautions. Select the Features.You prototype won’t be able to represent all the product features, therefore you might want to select the key features that will help you gather as much feedback from the user as possible. Sketch Your Design .You can do this on a piece of paper or a diagramming tool like Creately which provides complete libraries for wireframes, UI mockups, flowcharts, mind maps etc. Share Your Design .Share your design with partners, stakeholders etc. Ask for their feedback and mark where you need to make modifications to the design based on their requirements. Continue to Develop .Apply changes and develop your prototype by adding more features. Once it’s ready, you can share it with your stakeholders, partners, users etc. again for their feedback.

A prototype is a basic working model, mock-up or a simple simulation of the product which leads us to create a minimal viable product to final product and variations. The main reason for prototyping is to validate the idea and this is the step in converting an idea to a real product. A prototype could be a working model,

representational (non-working) model, miniature or a scale model, video or a photo demonstration based on the

factors like a problem to be solved, the mandate of the end customer. A prototype can be in the following forms paper, 3D printing, digital, small model or limited usage product.Here a prototype is made using video just to show others the idea in a graphical/visual format: Feasibility Prototype Horizontal Prototype Rapid Prototyp Simulations Storyboard Vertical Prototype Wireframe Animations Mock-up

The prototype is an important draft design that precedes the development of the original design layout. It is intended not only to show the structure of the future site, but also the site map, the interrelation of its main pages. Prototyping is a process designed to significantly reduce the time to develop a site, due to the focus of the designer on the main functional and marketing factors: The prototype gives the customer a complete idea of how the site will look like in the final result; Prototyping allows you to streamline the design development process, focusing on important interface

elements;

A site’s sketch is an irreplaceable thing if the client still does not fully understand what he expects from the site, what functions each page will carry. Careful planning at the prototyping stage makes it possible to avoid global changes in the finished layout; At the prototyping stage, it is possible to identify unnecessary elements that are best abandoned; This process significantly reduces the workload of the designer in developing the project, and thus saves the

customer’s money;
Having a prototype in hand, the designer and customer more clearly represent the final result;

Prototype development involves the involvement of the customer, contributes to more productive work, process consistency. Having a prototype makes it easier to understand the tasks for each team member. It gives them the opportunity to do more realistic planning of development deadlines and more accurately determine the cost of work. Website development in strict accordance with the prototype allows not taking into account the cost of changes and modifications.

User-centered design is an iterative design process in which designers focus on the users and their needs in each phase of the design process. UCD calls for involving users throughout the design process via a variety of research and design techniques so as to create highly usable and accessible products for them. User-centered design demands that designers employ a mixture of

investigative (e.g., surveys and interviews)

and generative (e.g., brainstorming) methods and tools to develop an understanding of user needs.

Data may be grouped into four main types based on methods for collection: observational, experimental, simulation, and derived. The type of research data you collect may affect the way you manage that data. For example, data that is hard or impossible to replace (e.g. the recording of an event at a specific time and place) requires extra backup procedures to reduce the risk of data loss. Or, if you will need to combine data points from different sources, you will need to follow best practices to prevent data corruption: Observational Data.Observational data are captured through observation of a behavior or activity. Experimental data are collected through active intervention by the researcher to produce and measure change or to create difference when a variable is altered. Simulation Data are generated by imitating the operation of a real-world process or system over time using computer test models. Derived data involves using existing data points, often from different data sources, to create new data through some sort of transformation, such as an arithmetic formula or aggregation.

User research helps us to understand how people go about performing tasks and achieving goals that are important to them. User research focuses on understanding user expectations, behaviors, needs, and motivations through methodical, investigative approaches.It helps us identify unarticulated needs and to fill in any gaps in our knowledge about our users, context of use, challenges, and opportunities. It also helps us to align our product and business strategy with the core needs and goals of our users.

Whether you're new usability testing or want to improve your know-how, we want to share with you our best tips for creating usability tasks. Tasks are the backbone of usability testing: Define user goals.Before you conduct usability testing, and preferably before you design anything—you should always start by understanding your users' goals. If you define user goals from the start, it will help you draft tasks for usability testing. Start with a simple task.For users to become accustomed to the testing experience and your product, start your test with one simple task. Give users one task at a time.Avoid grouping tasks together—this will create lengthy and complicated instructions, and users will have to be reminded about what they have to do. Split tasks up to create the focus on a single 'to-do' activity for your users. Follow your design's flow.When a new user arrives on your website, they do certain actions first, e.g., sign up or log in. To create a realistic user test, follow the same flow users take in your live website or product. Make tasks actionable.The premise of usability testing is to learn if users can complete tasks using your product. For this, you have to create similar tasks to those users do in real life in your app or website. Set a scenario. Such a description gives users the task (purchase plane tickets) while being clear on why they need to do it (holidays are coming up). This scenario also shares the details they need to know to be able to complete the task. Avoid giving precise instructions.One of the most important rules for writing usability tasks is to avoid giving precise instructions for completing the tasks or using leading words in your phrasing.

Extreme Prototyping is employed mainly for web applications and usually in three phases: Static HTML/CSS/JS is created — this gives users an instant tangible feel for the product. Thereafter, the service layer is simulated — this includes business rules and logic. Lastly, the actual service layer is developed — this involves integrating with real-world systems and plugging that into the front end HTML/CSS/JS views. This gives users an early view of the application without having actual functionality behind it. The backend will gradually come together as the process moves along.

Fast prototyping is a course of whereby a working mannequin or prototype is developed for the aim of testing the assorted product options like design, concepts, options, performance, efficiency and output. This strategy of improvement of working mannequin is kind of fast. The person can provide an early suggestions relating to the prototype. Fast prototyping is, usually, a major and important a part of the system designing course of and it’s believed to lower the venture value and danger. Disadvantages of fast prototyping: Some individuals are of the opinion that fast prototyping isn’t efficient as a result of, in precise, it fails in replication of the true product or system. It might so occur that some essential developmental steps may very well be omitted to get a fast and low-cost working mannequin. This may be one

of many biggest disadvantages of fast prototyping. One other drawback of fast prototyping is one through which many issues are ignored leading to limitless rectifications and revisions. Another drawback of fast prototyping is that it is probably not appropriate for big sized functions.

Prototypes are at their best, when they are seen as a tool for tinkering. When using them as the standard method for visualizing possible solutions to a problem, they let you discover ideas that you wouldn't have come to mind when working solely on isolated application states.There are three essentials of successful prototyping: Speed is everything. In order not to fall for the temptation of seeing whatever first comes out of the prototyping process as the ideal solution, you need to get comfortable with throwing away your work; Keep it small. It is often easier to create a series of small feature prototypes than one big demo; It's not for production. Trying to force the code into that system results in lots of workarounds that wouldn't even be needed when not starting from prototype code.Your code should be at least written nicely enough so that you still understand it the next day. .

Just to name a few: Adobe XD, Figma, Invision studio Sketch Balsamiq

User Interface (UI) design is the design of software or websites with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible. Good user interface design puts emphasis on goals and completing tasks, and good UI design never draws more attention to itself than enforcing user goals.

Graphic designers work with graphical images, whether they be illustrations, typography, or images, and on a variety of media including print and web. Graphic design is typically rendered in 2D — printed on a physical surface or displayed on a screen but not limited to 2D. As a graphic designer, you can specialize in the following Logo design Brand design Print Designer

User interface (UI) design is not the same as UX design. A seasoned UX design pro understands the vital difference and is able to articulate it clearly. Designing for the user interface often plays an important role in the work of a UX designer, but it is not the only function. Whereas UI design is concerned with the effective layout of visual elements on a user interface, UX design is ‘people first.’ It’s about what motivates them—how they think and behave. A great UX designer should be able to demonstrate knowledge describing the differences, in particular how UI design is only one slice of the UX design process ‘pie’, and only one of many different disciplines that reside under the UX banner. These include, but are not limited to: a user-centered design strategy, core user demographic definition, persona creation, user research, information architecture, content strategy, interaction design, visual design and usability testing.

Prototype model should be used when the desired system needs to have a lot of interaction with the end users.

Typically, online systems, web interfaces have a very high amount of interaction with end users, are best suited for Prototype model. It might take a while for a system to be built that allows ease of use and needs minimal training for the end user. Prototyping ensures that the end users constantly work with the system and provide a feedback which is incorporated in the prototype to result in a useable system. They are excellent for designing good human computer interface systems.

Many UX specialists consider A/B testing as a usability testing method. It’s vital to understand that usability is all about having individuals experience a product’s functionality. And as we know, A/B testing is about experimenting with two or more versions of a page/screen to see which is most effective. The goal of A/B testing is to find the page that will convert better, while the purpose of usability testing is finding usability issues that prevent users from having great user experience.

Remember to budget for more than one usability test. Building usability into a Web site (or any product) is an iterative process. Consider these elements when budgeting for usability testing: Time: You will need time to plan the usability test. It will take the usability specialist and the team time to become familiar with the site and pilot test the test scenarios. Be sure to budget in time for this test prep as well as running tests, analyzing the data, writing the report, and presenting the findings. Recruiting Costs: Consider how or where you will recruit your participants. You will either need to allow for staff time to recruit or engage a recruiting firm to schedule participants for you based on the requirements. Participant Compensation: If you will be compensating participants for their time or travel, factor that into your testing budget. Rental Costs: If you do not have monitoring or recording equipment, you will need to budget for rental costs for the lab or other equipment. You may also need to secure a location for testing, a conference room for example, so consider this as well. It’s important to keep in mind that usability testing is not just a milestone to be checked off on the project schedule. The team should have a goal for why they are testing and then implement the results.

Here are 5 key principles of good website usability: Availability and Accessibility. Let’s start with a basic, yet central aspect of usability: the availability and accessibility of your site. If people try to access your website and it doesn’t work — for whatever reason –

your website becomes worthless. Clarity. If you distract or confuse your visitors, they will either need more time to find what they came for, or they might forget their initial goal all together.It is your job to help them reach these goals as quickly as possible. If you can manage to do that, your visitors will be pleased and you have laid the groundwork for a positive experience. Learnability. It should be your goal to design intuitive interfaces — interfaces that don’t require instructions, or even a long process of trial and error to figure them out. Key to intuitive design is to make use of what people already know, or create something new that is easy to learn. Credibility.It is important that people know you are a real company with real people. Offer a clear “About Us” page together with your contact details and if possible a physical address. Relevancy.It is not enough that your website is clear, your content must also be relevant. Again, it is essential that you know your users and why they visit your site.

Interaction designers, focus on digital products and interactive software design. Interaction design helps humans experience or manipulate software or interface with screen-based hardware in order to achieve specific goals — checking email, withdrawing money from an ATM, or “Liking” a webpage. Interaction design is heavily focused on satisfying the needs and desires of the people who will use the product. Interaction design can be broken down into two parts or the same whole UI Design — User interface design UX Design — User experience design

User research is conducted so as to understand users’ characteristics, aims, and behaviors towards achieving these aims. Its purpose is to produce designs that improve their working practices and lives. User research also involves the continuous evaluation of the impact of designs on the users, not only during the design and development phase but after long-term use, too.

Usability testing can be broken down into a few major steps: Identify what needs to be tested and why (e.g. a new product, feature, etc.) Identify the target audience (or your desired customers). Create a list of tasks for the participants to work through. Recruit the right participants for the test. Involve the right stakeholders.

Apply what you learn. One of usability’s most hard-earned lessons is that ‘you are not the user.’ If you work on a development project, you’re atypical by definition. Design to optimize the user experience for outsiders, not insiders.

UX research is the starting point for a project. Research helps us learn about the users and their behavior, goals, motivations, and needs. It also shows us how they currently navigate a system, where they have problems and, most importantly, how they feel when interacting with our product. UX research comes first in the UX design process because without it, our work can only be based on our own experiences and assumptions, which is not objective. As Neil Turner, founder of UX for the Masses told us, a good foundation is key to successful design: “Good user research is key to designing a great user experience. Designing without good user research is like building a house without solid foundations—your design will soon start to crumble and eventually fall apart.”

The fundamental principles of design are: BALANCE — Balance in design is similar to balance in physics. A large shape close to the center can be balanced by a small shape close to the edge. Balance provides stability and structure to a design. It’s the weight distributed in the design by the placement of your elements. PROXIMITY — Proximity creates a relationship between elements. It provides a focal point. Proximity doesn’t mean that elements have to be placed together, it means they should be visually connected in some way. ALIGNMENT — Allows us to create order and organization. Aligning elements allows them to create a visual connection with each other. REPETITION — Repetition strengthens a design by tying together individual elements. It helps to create association and consistency. Repetition can create rhythm (a feeling of organized movement). CONTRAST — Contrast is the juxtaposition of opposing elements (opposite colors on the color wheel, or value light/dark, or direction — horizontal/vertical). Contrast allows us to emphasize or highlight key elements in your design. SPACE — Space in art refers to the distance or area between, around, above, below, or within elements. Both positive and negative space are important factors to be considered in every design.

User Experience (UX) design incorporates aspects of: psychology, anthropology, sociology, computer science, graphic design, industrial design cognitive science. The goal of UX design is to create a seamless, simple, and useful interaction between a user and a product, whether it be hardware or software.

Industrial designers create physical products designated for mass-consumption by millions of people. Motorcycles, iPods, toothbrushes, and nightstands are all designed by industrial designers. These people are masters of physical goods and innovation within the constraints of production lines and machines.

Here are some tips most important for presenting UX research findings, so that you don't leave the results to fend for themselves in an inbox. Don't only deliver a long report.No one is going to read the whole thing if that’s the only deliverable you present. Don't forget visuals.The people in these roles tend to be well versed in deciphering trend lines, graphs and charts Don't just email your findings out.Set up a “report out” meeting, either in person or using your favorite teleconferencing software. Don't undermine your qualitative findings.When a survey comes back with 50 responses with open- ended feedback comments, often the counter is that those comments are not statistically significant. Don't report only hyped up metrics.If you do not also ask users the question, “how valuable is this” design, then the metric measuring usability won’t matter if it’s not valuable to the user.

Program Management 5 Steps in the Reasearch Process: Locating and Defining Issues or Problems.This step focuses on uncovering the nature and boundaries of a situation or question related to marketing strategy or implementation. In defining the issues or problems, the researcher should take into account the purpose of the study, the relevant background information, what information is needed, and how it will be used in decision making Designing the Research Project.This step is focused on created a research plan or overall approach on how you are going to solve the issue or problem identified. Collecting Data.This step revolved around obtaining the information that you will need to solve the issue or problem identified. Interpreting Research Data.This step is focuses on examining the data and coming up with a conclusion that solves the problem. Report Research Findings.The final step is to report the research findings to those who need the data to make decisions.

Restate your research problem. Begin your research methodology section by listing the problems or questions you intend to study. Include your hypotheses, if applicable, or what you are setting out to prove through your research.

Establish your overall methodological approach. Your overall approach will be either qualitative or quantitative. Occasionally, you may also use a mix of both approaches. Briefly explain why you chose your approach. Define how you collected or generated data. This portion of your methodology section tells your readers when and where you conducted your research, and what basic parameters were put into place to ensure the relative objectivity of your results. Provide background for uncommon methods. Particularly in the social sciences, you may be using methods that aren't typically used, or that don't seem to fit with your research problem. Cite any sources that contributed to your choice of methodology. If you used anyone else's work to help you craft or apply your methodology, discuss those works and how they contributed to your own work, or how your work is building on theirs. Explain your selection criteria for data collection. If you're collecting primary data, you likely set eligibility parameters. Distinguish your research from any weaknesses in your methods. Every research method has strengths and weaknesses. Describe how you overcame obstacles. Overcoming obstacles in your research can be one of the most important parts of your methodology. Evaluate other methods you could have used. Particularly if you're using a method that seems unusual for your particular subject matter, include a discussion of other methods that are more typically used for your type of research. Describe how you analyzed your results. Your analysis generally depends on whether your approach is qualitative, quantitative, or a mixture of the two. Explain how your analysis suits your research goals. Identify how your analysis answers your research questions. Relate your methodology back to your original research questions and present a proposed outcome based on your analysis. Assess whether your findings can be transferred or generalized. You may be able to transfer your findings to other contexts, or generalize them to broader populations

The biggest sign of an amateur UX designer is excluding end users from the design process. At the very start of my career I held the attitude that I could test any app, website, or product on myself, replacing the act of speaking with users. Never a good idea. It took time for me to learn a more professional approach, which is to start the design process by listening to the end user. Overall, UX research helps us avoid our biases since we are required to design solutions for people who are not like us. “Insights that are received directly from user experience research are like muscle memory; the more you do research, the more insights you build up. But just like muscle memory, YOU have to be a part of the hard work in order to enjoy the lasting benefits of it that are specific to you. While it may be tempting to outsource research to a specialized team (and sometimes you can’t avoid it), you should try your utmost best to engage in at least a little bit of the research so that the insights grow under your skin instead of being handed to you from someone else who has sweated it.”

As Tim Brown, president, and CEO of IDEO, a famed global design consultancy describes it: “‘Design thinking’ is a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Design thinking is a method for the generation of solutions and a practical, creative resolution of problems. It’s about uncovering insights into the unmet needs of your target audience. It’s a form of solution-based, or solution-focused thinking, with the intent of producing a constructive future result. Most of all it’s a ‘people first’ approach—a design process mindset that designs products around people’s needs, motivations, and behaviors.

Leads to implementing and then repairing way of building systems; Practically, this methodology may increase the complexity of the system as scope of the system may expand

beyond original plans;
Incomplete application may cause application not to be used as the full system was designed;
Incomplete or inadequate problem analysis.

Prototyping tools are the tools to help you make product creation faster and much more effective. Prototypes demonstrate your ideas, and in doing so can change the way you design. Today's clients are looking for interactive prototypes. These prototypes give you an overview of your design, interactions and ideas: Sketch Zeplin Figma

Framer X Mockplus iDoc MockFlow Balsamiq Webflow Flinto Framer

In general the large portion of the costs of a project goes into the design and engineering work, the tooling and equipment and product testing. Prototyping in many companies today represents a small amount of the overall costs (well below 5–10% in most cases) but the effects are huge. In particular, the effects of NOT doing enough prototyping to validate the main or riskiest aspects of your product can lead to severe design and tooling modifications (if not complete retooling), repetitions of tests and increase in engineering hours. That could easily make the project go 2 or 3 times over the initial budget, not to mention delays to market that can be catastrophic in some cases.

A mobile app prototype is an preliminary visual mock-up that looks like a real app, and that demonstrates an app’s fundamental design and function, but does not contain working code. An app prototype can be as basic as sketches on paper or as high-fidelity as a clickable, digital model that works on your phone. Prototypes convey the look and feel of your app, but they are usually not working software. They set the stage for the first functioning version of your app, often referred to as the minimum viable product. Types of Mobile App Prototypes: Hand-sketched prototype: The most basic prototype is a simple series of hand sketches on paper. Each sketch represents a different screen and you can cycle through the sketches to show the app’s flow. Black and white digital prototype: The first digital phase of app design involves creating black and white “wireframes” representing each screen of the app. These wireframe designs can then be set up with a prototyping tool, such as Invision. High-fidelity digital prototype: Your high-fidelity digital prototype looks like a real mobile app. Even though the screens are just images—so you can’t type in fields, use the GPS or camera, etc.—the images reflect the intended design, are clickable, and are viewable on your mobile device just like a real app.

Organize project details . Mockups can help the designer to uncover visual elements that clash, before you arrive at the final, end design. Visual hierarchies, that show the difference between design elements such as font and color, should be determined at the mockup phase of the design process.With the visual elements more refined than with wireframes, mockups allow stakeholders to actually review the visual side of the project. Find errors early on. Mockups are flexible and this makes it easy to iterate. Much like working with a wireframe, mockups allow for easy and quick revisions that can stack up pretty quickly, as they do not require code or programming. Translate ideas into a stakeholder language.For clients and stakeholders, presenting a digital mockup can be best the way to go, as simply using a flat design might not be enough in terms of visualization and translating ideation. Communicate ideas between team members.Not only can the mockup serve as a discussion medium between the designer and user or stakeholder, it can also act as a communication device between the members of the design teams.Mockups may help facilitate work across disciplinary borders, bringing together teams who are working on different objectives. Design implementation .How does your initial design flow and perform? By looking at a mockup, you should have a good idea of how the final product will look and a rough idea of how it might function (even if the functionality isn’t yet in place). The user’s perspective .Paper and low-fidelity mockups get a lot of stick from users because they are low- cost. But if a user is presented with an early version of a system – a mid-fidelity digital UI mockup – that required substantial work, they may be more inclined to focus on the value of the design.

Gathering feedback from your users is a crucial part of any design process. The way in which you can gather this feedback varies depending on what kind of questions you are trying to answer, the resources you have available for user research and what phase of product development you are currently in. Qualitative usability testing is widely considered to be one of the most effective user research methods for gathering feedback, due to the great amount of insight you can gather from such a small group of users.Here's an example scenario that will give you some context for the steps ahead: Create categories to group insights under.Before you start listening to the recordings, you need to prepare your workspace. Think of distinct stages the user went through when using your prototype and divide your whiteboard (or wall) space accordingly. This will make insights easier to group later on and give you a snapshot of which areas received the most feedback. Listen to your recordings and write down insights.Get your post-it notes at the ready;Start playing back the recordings, one user at a time; Begin noting down insights . Stick insights under their correct heading.Stick each post-it in its corresponding space on the whiteboard. Group similar insights.Grouping similar insights will help you visualise how often they occur and give them the correct level of priority when it comes to addressing them. If you’re able to show that all five users grew frustrated at the length of the login process, then it shouldn’t take much convincing to make addressing this a high priority. Adjust for perceived impact if solved.You should now have a whiteboard covered in post-its that are categorised into practical headings and prioritised based on number of occurrences. The last step is to adjust the priority of the insights based on the potential impact if solved.

From the user’s point of view, usability is important because it can make the users complete the task accurately, and users can operate it with a pleasant mood rather than feeling stupid. From the developer’s aspect, usability is an important principle to determine the success of a system. From the manager’s point of view, the poor usability of products will greatly reduce productivity, people will not buy your products. Any product that lacks usability will waste more time and energy.em

Efficiency- the degree that users can finish a particular task and achieve a specific goal correctly and

completely in a short time;

Satisfaction — User’s subjective satisfaction and acceptance degree in the process of using a product. A site with good usability has to follow these factors: fast connection, well designed, completely description and testing, simple operations, friendly and meaningful information interaction, unique style.

In general, your report should include a background summary, your methodology, test results, findings and recommendations. There are a number of report templates that you may adapt to assist you in reporting your findings: Background Summary: Include a brief summary including what you tested (website or web application), where and when the test was held, equipment information, what you did during the test (include all testing materials as an appendix), the testing team, and a brief description of the problems encountered as well as what worked well. Methodology: Include the test methodology so that others can recreate the test. Explain how you conducted the test by describing the test sessions, the type of interface tested, metrics collected, and an overview of task scenarios. Describe the participants and provide summary tables of the background/demographic questionnaire responses (e.g., age, professions, internet usage, site visited, etc.). Provide brief summaries of the demographic data, but do not include the full names of the participants Test Results: Include an analysis of what the facilitator and data loggers recorded. Describe the tasks that had the highest and lowest completion rates. Provide a summary of the successful task completion rates by participant, task, and average success rate by task and show the data in a table. Follow the same model for all metrics. Depending on the metrics you collected you may want to show the: Number and percent of participants who completed each scenario, and all scenarios (a bar chart often works well for this) Average time taken to complete each scenario for those who completed the scenario Satisfaction results Participant comments can be included if they are illustrative. Findings and Recommendations: List your findings and recommendations using all your data (quantitative and qualitative, notes and spreadsheets). Each finding should have a basis in data—in what you actually saw and heard. You may want to have just one overall list of findings and recommendations or you may want to have findings and recommendations scenario by scenario, or you may want to have both a list of major findings and recommendations that cut across scenarios as well as a scenario-by-scenario report.

The most used models are Waterfall models used for generally small scale projects and single release based software products, whereas the Prototyping Model is used for developing large scale products generally developed in multiple parts rather than single release also called version of release.The software developments strategy I prefer is Prototyping Model. The reason for selecting the Prototyping Model encourages progressive strategic development with course of time.With prototyping model, I am also using non-agile approach and USDP methodology as active part of the development process. A Waterfall method of software development has to pass through every phase once, and not meant to go back to previous phase again. Once the requirements request made freeze, changes can’t be done during any phase. That is why, it is used rarely now a days. Due to this If there is any change in requirements, and then it becomes difficult as well as costly affair. Prototyping Model is a technique that uses the technique of replication of few aspects or feature of expected product and it is then developed upon it to obtain the full software. It can be called designing of software prototypes or temporary versions of software program being developed for full edition deliverables.

Prototype Testing is conducted with the intent of finding defects before the website goes live. Online Prototype Testing allows seamlessly to collect quantitative, qualitative, and behavioural data while evaluating the user experience. Characteristics of Prototype Testing: To evaluate new designs prior to the actual go live to ensure that the designs are clear, easy to use and meet

users requirements;

Is best when iterative testing is built into the development process, so that changes can be easily made often to ensure that major issues do not arise well before going live; Provides confirmation about the new design direction, branding and messaging are going in the right direction.

A prototype attempts to test the critical aspects of the full system. It intends to describe how an idea or feature will work whereas a PoC simply shows that it can be done. The prototype it is a working interactive model of the end product that gives an idea of the design, navigation and/or layout. It would allow a project team to understand the steps that the Chatbot takes to process the query and to develop a response.A pilot is the testing of a fully functional product that is offered to a portion of your target users. The purpose of running a pilot is to get a good understanding if the client would use certain functionality and how it is used with actual clients. Using our example, a pilot would test whether and how taxpayers actually use the Chatbot in addition to what it is being asked. The feedback collected during a pilot should be used to tweak the product before it is released to your entire user-base. A second pilot may be warranted depending on the extent of the pilot. To summarize, a proof of concept tells you whether a product can be developed and tests the technical feasibility, a prototype shows how the product can be developed, and a pilot informs you about whether clients will use the product.

User interface (UI) prototyping is an iterative development technique in which users are actively involved in the mocking-up of the UI for a system. UI prototypes have several purposes: As an analysis artifact that enables you to explore the problem space with your stakeholders. As a design artifact that enables you to explore the solution space of your system. A basis from which to explore the usability of your system. A vehicle for you to communicate the possible UI design(s) of your system. A potential foundation from which to continue developing the system (if you intend to throw the prototype away and start over from scratch then you don't need to invest the time writing quality code for your prototype).

Different UX designers approach the task of wireframing in different ways. Some like to draw by hand, while others like to use apps or tools found online. But more often than not, the decision to use online tools or to wireframe by hand, and the process used to get to from wireframe to code, is less related to the individual preference of the UX Designer, and much more related to what approach the particular situation requires. It depends largely on how much emphasis there is on visual design in a project, and how much uncertainty there is with respect to what is being designed. In the bullet points below are a number of ways different designers can structure the process from design to implementation: Wireframe > Interactive Prototype > Visual > Design Sketch > Code Sketch > Wireframe > Hi-Def Wireframe > Visual > Code Sketch > Wireframe > Visual > Code If the task is very narrow and the visual design is either set or considered unimportant (such as with many backend administrative interfaces), then sketch > code makes sense, whereas if the time and resources and the

business value are all high, then spending the time to make a high-definition wireframe and going through a cycle of testing with a fully realized interactive prototype makes better sense.

Do your research.Remember: UX design is a process, and wireframing isn’t the first step in this process. Before you even think about picking up a pen and paper, you need to have covered the first two steps; namely understanding who your audience is by way of user research, detailing requirements, creating user personas and defining use cases, and complementing this with further competitor and industry research; Prepare your research for quick reference. If you’re a mere mortal, you might struggle to both retain and recall all of that, so I recommend scribbling a cheatsheet with your business and user goals (your requirements), your personas, use cases, and perhaps some reminders of the coolest features you stumbled

across in your competitor research;

Make sure you have your user flow mapped out.It’s important to have a watertight concept of where your users will be coming from (which marketing channel, for example, and off the back of what messaging), and where you need them to end up; Draft, don’t draw. Sketch, don’t illustrate.Remember: you’re outlining and representing features and formats, not illustrating in mighty fine detail; Add some detail and get testing.Add detail in the way you would naturally process a screen, or the page of a book: from top-to-bottom and left-to-right. Remember: Your wireframe is the skeleton of your site. You’re not adding the muscle just yet—the content and the copy; Start turning your wireframes into prototypes.Once you’ve documented and acted upon the feedback from your first prototype, you can start developing your high-fidelity prototypes. There are lots of slick tools out there for this, from Proto.io to Adobe XD and Framer, but the most well-known are Sketch and the browser-based, new(ish) kid-on-the-block, Figma. Once you’ve developed your wireframes in Sketch, you can import them into the industry-leading prototyping tool InVision.

Fail Early: A business might prototype their mobile app and discover that what they envisioned is not practical or what their users or stakeholders want. Far from being a waste of time and money, in this case beginning with a prototype saved a great deal in development costs and provides peace of mind and proof to executive teams that a digital solution won’t work. Get Clarity: More often, prototypes give clarity regarding precisely what you need, and how a mobile app can fulfill on it. They allow you to play with ideas and solicit feedback before investing in developing the software. Sell Early: Prototypes also perform a significant role in obtaining funding by demonstrating the product to investors, executive boards, or even prospective customers. Iterate Quickly: Prototypes even benefit businesses that already have a clear mobile app concept in mind by allowing you to cycle through multiple drafts before developing software. You create a better product, with less time and money, by putting effort into the planning stages of developing a mobile app with a prototype, and that’s smart business.

Mobile app investors are met with a plethora of pitches in their inboxes every day. Understanding how to build an app and launch a prototype for your mobile app can help differentiate your startup from the rest and give you a competitive advantage when pitching your app to potential investors. Understand The Problem.One of the first steps in creating a quality app is ensuring you have a problem worth solving. The problem could range from a corporate requirement, if you’re going after the B2B market, to something as simple as boredom Identify Key Functionality Requirements.Once you’ve identified the problem, start brainstorming product requirements. It’s easy—and quite fun—to list the hundreds of different features your app should have. And that’s exactly what you should do! Create Sketches Of The Primary Screens.After you figure out the highest priority features, start thinking through the user experience. One of the best ways to craft the user experience is to begin with a few rough sketches of how the primary screens should look and feel. Turn Your Sketches Into Wireframes.A wireframe is a low-fidelity, simplified outline of your product consisting of boxes, words, lines and sometimes descriptions. It’s meant to lay the framework of where your app will go rather than the final look and feel of the app. Turn Wireframes Into A Prototype.Prototyping not only makes your product more real for investors, but it also gives your testers the ability to get a real feel for what it would be like to use the app, and arms your developers with a better sense of the intended UX before finalizing the design. Translate Wireframes Into Final Designs.In each scenario, you will want to spend time talking to these people about your vision and gauge their ability to execute by reviewing their past work. Some designers use Sketch to create their app designs; others use Illustrator. When you have the final files, update your Invision or Xcode prototype to make it look and feel like it’s live.

A mockup is a visual way of representing a product. While a wireframe mostly represents a product’s structure, a mockup shows how the product is going to look like. But still, a mockup is not clickable (just like the wireframe). As opposed to a wireframe, a mockup is either a mid or high-fidelity display of design. A mockup helps you make final decisions regarding a product’s color schemes, visual style, typography. With a mockup, you can allow yourself to experiment with the visual side of the product to see what looks the best. Here again, you can ask your potential users for feedback and make the necessary changes right away. This will save you way more time than getting back and making adjustments to the UI after you have launched the product.s opposed to a wireframe, you cannot sketch the mockup. You might need to use a mockup tool. There are plenty of them, too. You might want to try Marvel, InVision, or Moqups.

Usability testing offers a variety of benefits for both future users of a product as well as the company or developers creating that product. A few of these include:

Saves time for both the company and users. Provides a better user experience. Offers insight into how satisfied users are with the product. Identifies problem areas within the product which may not have been obvious otherwise. Provides an unbiased examination of the product. The return on investment of having a product which offers an excellent user experience can be massive. For example, according to Forbes, Jeff Bezos invested 100 times more into customer experience than advertising during the first year of Amazon. Today, Amazon is one of the world's largest companies.

Visibility of system status Match between system and the real world User control and freedom Consistency and standards Error prevention Recognition rather than recall Flexibility and efficiency of use Aesthetic and minimalist design Help users recognize, diagnose, and recover from errors Help and documentation

Typically, usability is measured relative to users' performance on a given set of test tasks.The most basic measures are based on the definition of usability as a quality metric: success rate (whether users can perform the task at all), the time a task requires, the error rate, and. users' subjective satisfaction.

There are many types of usability testing to evaluate how your customers experience your website. Which test you use will depend on the purpose and goals of your research.While web analytics provides an insight into various interactions on your website, it doesn’t delve deeper into the bug testing process. The more methods and techniques you use to gather evidence, the more likely you will be able to identify and solve your problems:

Moderated In-Person Moderated Remote Unmoderated Remote Problem Discovery Benchmark Eye Tracking Learnability

User personas — Once you have adequate data on your users, you can build fictional user personas. These act as stand-ins for the actual user during the design process, focusing more on behaviors rather than demographics. At UXPin, we use lightweight personas informed by user interviews and in-app data. We define the person’s role, daily responsibilities, and motivations. User scenarios — These logic exercises take personas a step further — they outline how a persona would act in a specific situation, including what pages they visit and why. In the below example created during our redesign process, you can see how we tried to imagine a realistic scenario for a marketer collaborating with a designer in UXPin. The thought exercise helps us understand that speed and ease-of-use are the top priorities when commenting on designs. For fast user scenarios, Google spreadsheets works quite well since you can also collaborate with other product team members. Customer journey maps — The ultimate document for understanding your user, journey map out the personas and user scenarios at each step of the experience. User emotions, quality of experience, product weaknesses, and other factors can all be documented. Moreover, they cover customer touchpoints before, during, and after service so so you can gauge the lasting effect of your design. Product documentation — While optional in the age of prototyping, documentation like product requirement documents and functional spec documents consolidate market and user research into a unified vision.

User Research Tools: Slack Channels UX Artifact Templates Competitive analysis Research Platforms/Databases Research Artifact Templates Recruiting Prototyping Synthesis & Sharing

Follow these five tips, and you will reap the rewards of your UX research efforts: Conduct UX research right at the beginning.The earlier you do it, the more impact it will have on the final product. Define Concrete Goals.To extract the most value from this research, you need to define a clear mission with concrete goals. This means formulating the right questions and setting up the scope for your work. Choose your UX research methods wisely.Do not just stick to a few tried-and-tested tricks that you use every time; choose wisely based on the context of your project. Share Your Findings . It is one thing to conduct user research and gather everything you need to know about your target audience. The next challenge lies in communicating these findings and ensuring they provide value to key stakeholders, including fellow designers, product managers and developers. Remember: User Research Never Stops.You should never stop learning from your users; as the market evolves and technology changes, the product also needs to keep up. Even your audience might change over time, so it is crucial to ensure that you are not relying on outdated insights that are no longer relevant. Maintain constant dialogue with your users and make UX research a part of your long-term design strategy.

UX researchers and other project stakeholders often fervently debate the number of participants that are necessary for usability studies. At the core of this debate is often the tension between the usability professional’s desire for the best possible study and the business team's desire to reduce time and expense.In summary, research suggests that from three to twenty participants can provide valid results, and a good baseline is between five and ten participants. In general, there should be more participants for more complex, highly critical projects; while fewer participants are necessary when testing more novel designs.

Wireframing is a practice used by UX designers which allows them to define and plan the information hierarchy of their design for a website, app, or product. This process focuses on how the designer or client wants the user to process information on a site, based on the user research already performed by the UX design team. When designing for the screen you need to know where all the information is going to go in plain black and white diagrams before building anything with code. Wireframing is also a great way of getting to know how a user interacts with your interface, through the positioning of buttons and menus on the diagrams.

Without the distractions of colors, typeface choices or text, wireframing lets you plan the layout and interaction of your interface. A commonly-used argument for wireframing is that if a user doesn’t know where to go on a plain hand-drawn diagram of your site page, then it is irrelevant what colors or fancy text eventually get used. A button or call to action needs to be clear to the user even it’s not brightly colored and flashing.

Time seems to fly by on a project, especially with agile development methods being so prevalent these days. If you miss a deadline by even a whisker, things can turn ugly. If time is so tight that you cannot do UX research before the launch of a product, do it post launch, then quickly fix the issues you discover as the project progresses. If a stakeholder or client isn’t allowing you time to plan for research, be smart and analyze whatever research data is already available. Be prepared to run usability tests and make adjustments to the design later on. However, rather than skipping UX research altogether because of time and budgetary constraints, consider employing the following research methods instead: Lean UX Guerrilla research Minimum viable research Heuristic evaluation Expert review Hypothetical personas

Remote usability testing allows you to conduct user research with participants in their natural environment by employing screen-sharing software or online remote usability vendor services. In general, tests should be about 15–30 minutes long made up of about 3-5 tasks. Remote usability tests can be “Moderated” in the same manner you would for an in-person lab test or, “Un-moderated” where participants complete the tasks independently. When to Consider Remote Testing There are certain conditions when it makes sense to consider remote usability testing. Some of those conditions include: Timelines might prevent in-person testing due to scheduling issues The target audience/participants are geographically dispersed making travel for them or the experimenters difficult The participants need to use a particular work machine due to software or security requirements The participants have accessibility issues which require that they use their own software or equipment You can potentially run multiple tests at once Although this method is flexible, as with any test, you must consider the benefits and cost of this methodology.

User research provides an essential foundation for design strategy. It helps you to create an optimal product for users. Most importantly, you'll have the data to back your strategy and design decisions. User research also helps you to identify early adopters who would use your product.User research helps you to discover people who can give you valuable contextual feedback on your product.

Functional testing is carried out to ensure that the product behaves according to the functional requirements without taking design principles into consideration. This entails a series of tests which perform a feature-by- feature validation of behavior, using a wide range of normal and erroneous input data. In contrast, usability testing focuses on customer acceptance and how well the customer can use the product to complete the required task. Usability testing investigates all aspects of the usability of a product, including overall structure, navigational flow, layout of elements on a page, clarity of content, and overall behavior. The relationship between functional and usability testing: usability testing needs to come after functional testing, once functional problems have been fixed. Performing usability testing on functionally-flawed products only unearths functional problems, which leads to frustration for the participants who are struggling with bugs when trying to complete a task. It hinders the participants, it negatively influences their perception (and hence their feedback), and it invalidates the usability aspect of the results. Both functional and usability testing require very different mindsets from the person testing and ideally should not be carried out by anyone involved in the development of the product. Functional testing requires the mindset of “CAN I do what I need to do; does this product work?” Usability testing is more about ‘usability’ than it is about ‘testing’ (given that the latter term inevitably seems to bring about visions of functional testing first and foremost) and needs to have the mindset “HOW can I do what I need to do; does this make sense?”

The 9 Phases of a Usability Study: Decide which part of your product or website you want to test.Do you have any pressing questions about how your users will interact with certain parts of your design, like a particular interaction or workflow? Pick your study's tasks.Your participants' tasks should be your user’s most common goals when they interact with your product or website, like making a purchase. Set a standard for success.Once you know what to test and how to test it, make sure to set clear criteria to determine success for each task. Write a study plan and script.At the beginning of your script, you should include the purpose of the study, if you’ll be recording, some background on the product or website, questions to learn about the participants’ current knowledge of the product or website, and, finally, their tasks. Delegate roles.During your usability study, the moderator has to remain neutral, carefully guiding the participants through the tasks while strictly following the script. Find your participants.Screening and recruiting the right participants is the hardest part of usability testing. Most usability experts suggest you should only test five participants during each study, but your participants should also closely resemble your actual user base. Conduct the study.During the actual study, you should ask your participants to complete one task at a time, without your help or guidance. If the participant asks you how to do something, don’t say anything. You want to see how long it takes users to figure out your interface. Analyze your data.Analyzing it will help you discover patterns of problems, gauge the severity of each usability issue, and provide design recommendations to the engineering team. Report your findings.After extracting insights from your data, report the main takeaways and lay out the next steps for improving your product or website’s design and the enhancements you expect to see during the next round of testing.

5 Factors of Usability: Learnability. How quickly can a new visitor learn the user interface to accomplish basic tasks? Is the design of the site intuitive? Efficiency. How quickly can users perform tasks, find products etc? Memorability. Can a returning visitor remember how to effectively use your site or application or are they forced to relearn everything from the beginning? Errors & Error Frequency. How often does a visitor make errors while using your website? How serious are these errors? Why are they making them and can they easily recover from these mistakes? Satisfaction. After completing their task does the user have a good feeling about your company? Focusing on these five points will give you a good start on fixing basic usability issues.

You’re bringing ideas to life.But when you translate that idea into a prototype, you’re breathing life into your design. It’s no longer just some idea you had in the shower; now it’s an actual design that exists in the

world;

You’re working toward the best solutions.Every prototype starts as a blank page, and you should use it to experiment with different ideas, discard what doesn’t work, and refine what does; You’re iterating toward a better product.UX design is a practice of both ingenuity and evidence. When you get feedback on your prototype from users, you’re building a body of knowledge about what your

audience wants;

You’re uncovering usability issues and reducing risk.By catching changes earlier in the process, you can optimize the experience design while the cost is still relatively low. This will save your company or your client lots of money, and they’ll love you for it; You’re avoiding doing things that don’t make sense.You still have to invest a little time in creating the prototype, but you’ll avoid building something you know will fail.

This word has a broad usage in the design industry but put simply, a prototype is an early version of your product that’s used for testing. Prototypes are the gateways to insight. By testing your design with your audience, you’re discovering which solutions work and which don’t. With that knowledge in hand, you can evolve your design to better suit the needs of your end users. In many ways, the exchange of knowledge through a prototype forms the foundation of human-centered design. Users get to help shape the products they interact with every day, and designers learn how to build stuff their audience actually wants.

Prototyping is the Design Verification phase of Product Development because it demonstrates or proves the design. Think of a Prototype as simply taking a design from the virtual, imaginary realm into the physical world. Of course there are lots of reasons we want to touch and feel and try our new widget, and a prototype is the way to do that. But, there are some specific reasons to prototype. Some of the most common are: Display or Show the new product — maybe at a show or for investors Test an idea to see if it really works Test the design to see if it passes certain requirements Use it to evaluate where improvements are necessary Get customer feedback

UX design helps users accomplish meaningful tasks across platforms and services UI design makes compelling and aesthetically pleasing interfaces that connect with humans or in other words: UX Makes Interfaces Useful UI Makes Interfaces Beautiful