background preloader

UX Design

Facebook Twitter

Changer le(s) système(s) : La Gamification [1] Être contre ne suffit pas. Être anti ne suffit pas. Dénoncer ne suffit pas. S’insurger ne suffit pas. Imaginer, créer, construire, bidouiller, tester, expérimenter… Voilà des mots qui nous plaisent plus à Hacking Social,et qu’on essaye de ne pas oublier quand on dénonce quelque chose : toujours donner d’autres pistes, des idées.

Au moins, essayer d’en donner. Aujourd’hui, nous allons explorer une piste. Tout le dossier en ebooks : L’epub : Changer les systemes _ La gamification – Hacking Social Le PDF :Changer les systèmes gamification 1.5 « Et si on décidait d’utiliser tout ce qu’on connaît du game design pour réparer ce qui ne va pas dans la réalité ? Autrement dit, et si on gamifiait nos institutions ?

La définition la plus simple est que la gamification (ou ludification) est un transfert des mécaniques de jeu à un domaine qui n’est pas un jeu. En français : « jeu sérieux ». On pourrait parler ici de gamification de la formation, de l’information, de l’apprentissage. Workflows and User Processes. UI/UX Principle #48: Document Process and Observe Workflows - Fresh Consulting.

You might think you understand a workflow or process – whether it’s a person using an application, a website, or completing a task manually – but truly understanding how the process works requires careful study and documentation of data. Improving a process necessitates understanding how it works. Documenting process and observing workflow involves getting to the bottom of the question: “What should we design that solves the user’s problem?” Rolling into UX design without first understanding process and workflows risks creating a product that doesn’t allow users to accomplish their goals. It’s about building the right product before building the product right. In this post, we’ll discuss an example of documenting process and observing workflows, then delve into why it matters and how the process is done. Some examples of documenting process and observing workflows include: Multiply that by 100 people taking 30 phone calls per day.

When you’re documenting the process, it’s helpful to know: Creating User Workflows | Cross. A Discussion: Creating User Workflow Level: Beginner By: Laura Betz We need to get things done. All of us. No exceptions. So, how does this get accomplished? When building applications there is always a purpose that needs to be fulfilled and applications may help facilitate this process. After collecting information and brainstorming with your team you can decide on the final process flow chart and a wireframe will solidify the structure for the programming. Efficiency rises when a workflow is properly implemented and may continue to occur as the solution is further streamlines / customized.

Wireframing Process Flow Chart Software. Disruptive Workflow Design. Share: Twitter LinkedIn Facebook Email Share this article: TwitterLinkedInFacebookEmail Workflow is one of the most important elements of application design. Can users proceed through their tasks with ease or are they subjected to irritating detours and burdensome extra steps? A workflow's usability can be lowered in many ways, such as when you require users to remember anything from one step to the next. (Lower the burden on short-term memory — there's a useful guideline to remember :-) Here, I want to focus on a common problem: users being disrupted from proceeding with their natural task flow.

To see the difference between bad user interface design and a bad system, let's consider two examples of user-unfriendly account updating. Bad Workflow: Apple iTunes Application Apple's iTunes application for Windows is riddled with lousy user interface design, but my current example relates to updating the user agreement. Select "Apps" in menu of data types. Bugs vs. Bugs can happen to anybody. Wireflows: A UX Deliverable for Workflows and Apps. Share: Twitter LinkedIn Facebook Email Share this article: TwitterLinkedInFacebookEmail Introduction In the UX field, wireframes are a common deliverable to show page-level layout ideas, whereas flowcharts are useful for documenting complex workflows and user tasks.

However, despite the fact that both of these deliverables remain in common use among UX professionals, there are situations in which they are suboptimal tools for communicating design ideas, particularly when documenting mobile, desktop, or web apps that don't have many unique pages, but instead feature a few core pages which change content (or layout) dynamically based on user interaction. In the last few years, an alternative deliverable called wireflow has emerged as a solution to these issues, used to show designs in the context of common user tasks. Wireflows as a Deliverable for Workflows Why We Need Something New: Flowcharts and Wireframes Don't Document Complex Apps Well Wireflows Document Interactions Conclusion. User Journey Maps or User Flows, what to do first? - Design + Sketch - Medium. UX Design is a complex process. There are lots of deliverables that may help to create a solution that will be useful and joyful for customers.

This article focuses on two ones that visualize the path that user has to pass to accomplish tasks in the designed product. Let’s try to answer following questions:What are differences between User Journey Maps and User Flows? What is their purpose? How they complement each other? Finally, which one we should focus first when we design a product? I will start with the explanation of basic terms we cover in this Story. Journey Maps try to capture the experience of a user during the interaction with the products. User Journey Maps may have several layers, they do not focus only on a particular element that triggers action. Journey maps are usually linear because they describe various aspects of accomplishing particular tasks.

UX Flows are hybrid between traditional flow charts with some visual interfaces included in them. In just a few words: My 10 Step UX+UI workflow: 2019 - UX Planet. It’s been a year that I’ve shifted from working on projects to working on a product. This is my ‘10 step UX workflow’ after learning from both the models that ensure you create products that are loved by the users.

Why is it important? : To understand the impact of the research insights on the UX that enables user-centricity. How I do it? : I like to immerse myself in co-creating personas and user journeys and/or service blueprint with the research team. Tools I use: Whiteboard, Trello, Dropbox Paper, Slack, etc Why is it important? A good navigation model helps people to move easily throughout the product and hierarchy helps to define the structure of the content. How I do it? Tools I use: Whiteboard, Post-its & Sketch App or Adobe XD Why is it important? How I do it? Tools I use: Sketch App or Adobe XD Why is it important? UX flows makes it easy for developers to get a perspective of the system. How I do it? Tools I use: Whiteboard & Sketch App or Adobe XD Why is it important? How I do it? UX Glossary: Task Flows, User Flows, Flowcharts and some new-ish stuff. Updated definitions, examples and free resources UX has a long list of terms and deliverables.

The list is even more apparent when viewing job descriptions that seem to throw in the full UX glossary of terms. Factor in that these deliverables have been evolving and many terms overlapping, I thought it was time to revisit. Task Flow Analysis and User Flows are terms I have heard for years. I decided to find out their ‘official’ definitions. In either case, flow depicts movement. Flowcharts Flowchart is a diagram of the sequence of movements or actions of people or things involved in a complex system or activity. Task flows and user flows are not that different. Task Flow Task flow is a single flow completed similarly by all users for a specific action. User Flow User Flow is the path a user follows through an application. User flows can start off simple and help determine ‘red routes’ — key user journeys. 37 Signals has a shorthand for User Flows.

You may want to give UI flows a try. Terminology - What are the differences between user flows, task flows and workflows? - User Experience Stack Exchange.