A user flowchart helps the designer visualize the experience a user will take to complete a task or meet a goal on a site or app. Understanding how a user will navigate a site will help you identify their needs. Flowcharts are made up of a set of basic symbols that show the decision process to the users final destination.
To begin designing a flowchart, you must first identify who the user is. This can be done though user research or designing personas. This will help define the target audience and what the needs are. Next you will need to identify the entry point by understanding how the user will access the site or app. The entry point is where the user is when they first arrive on the site/app.
There are several people that are involved in UX that will bring a product to a successful completion. These can include UI designers, information architects, programmers and developers. They all have a large part in a successful UX experience. But getting everyone on the same page can be a battle, as each one will need different types of information in order to reach different goals within the product development. For example, a UI designers main concern is user and how they can create something that fits the user. They will focus on the user’s needs, wants and preferences. While a developer will have a different view of the product in order to understand the inner workings of the system.
Using your UX flowchart as a communication tool can be successful in helping to illustrate the product in a way everyone on the team can understand. To keep everyone on the team involved in the user flowchart, you want to stay away from the visual design and focus on how the system will react with the user’s experience within the site.
Information architecture (IA) is found in websites, apps and software we download. It is the structural design of information in a shared environment as well as the organization and labeling of a website. The IA supports usability and a connection of design principles for the digital space. It takes information that is being used and applies it to activities which require complex detail.
Information architecture creates a structure for a website, app, or other project, that allows you to understand the user’s actions and where the information we want to be used lives. Information architecture involves the creation of site maps, categories, navigations, and metadata. For example when a designer puts together a top navigation to help users understand where they are on a site, they are exercising IA architecture. IA helps people to understand what they are looking at and where to find it in the real world as well as online. Practicing information architecture helps others understand the importance of site structure and content.
For some information architects, wireframes are the best way to start the process to make connections and identify how the site will work from a user’s perspective. After researching, an IA will be designed around certain screens in order to show how a user will interact with the information before them. Designers tend to think visually and will often use this visual technique to show the structure of information. Wireframes are also a valuable deliverable to share with clients, developers and visual designers as they build mockups, prototypes, and final products.
Ideation sessions challenge you to think outside the box. These sessions encourage you to explore as many ideas as possible to find solutions. The focus is on quantity of ideas rather than quality. In a judgement free zone, you are free to uncover, sometimes unconventional, ideas to build upon. This ideation phase transitions you from learning about the users to finding a solution to the problem. This is where innovation grows and you find what the users has been missing.
The ideation session should be focused on the users to get their perspective.
The more user views you have, the more diverse the ideas will be.
The ideation process can be done several different ways depending on the needs of the user and the problem you need to find a solution for. The session can be done alone or in a group and short or over several hours. It could be a one-time session or over several sessions, as well as being formal or informal as needed. Use the research you have gathered to define the ideation problem that you want to solve. Be clear about the needs of the users. Ensure that the focus in the ideation session is on improving the user experience. Set aside any technical constraints or business viability. At this stage, no idea is too farfetched. It is much easier to scale back a crazy idea that addresses a true user need, than to try to make a very simply idea desirable.
Ideation is the process of generating a broad set of ideas on a given topic,
with no attempt to judge or evaluate them.