用戶體驗/概念證明/第1部分 (USER EXPERIENCE / PROOF OF CONCEPT / PART 1)

This is the first article of a four-part series. Please read Part 2 and Part 3.

這是由四個部分組成的系列文章的第一篇。 請閱讀 第2 部分 和 第3部分 。

How do today’s top UX designers create the best mobile experiences for apps like Lyft, Airbnb, and Mint? They start with an inspiration and then follow a clear and repeatable User Experience process. Sounds simple right? But what is this process? And how can you learn it and apply it to your projects?

當今的頂級UX設計師如何為Lyft，Airbnb和Mint等應用程序創造最佳的移動體驗？ 他們從靈感開始，然后遵循清晰可重復的用戶體驗過程。 聽起來很簡單吧？ 但是這個過程是什么？ 以及如何學習并將其應用于您的項目？

UX process is a complex topic for sure, and there is no single answer. However, in my twenty-plus years of teaching, studying, and refining the UX process, it’s now crystal-clear to me that the key to creating any successful interactive experience is building an accurate and flexible Proof of Concept (a step-by-step sequence of images representing how a user moves through a particular interactive experience).

UX過程無疑是一個復雜的主題，沒有一個答案。 但是，在我二十多年的教學，研究和完善UX流程的過程中，對我來說，現在已經非常清楚，創建任何成功的交互體驗的關鍵是構建準確而靈活的概念證明(逐步代表用戶如何在特定的互動體驗中移動的圖像的逐步步驟)。

So… You’re thinking: “Okay. I need a Proof of Concept. Simple, let’s open up Sketch and start designing screens!” Whoa! Hold on now. You can’t just go willy-nilly building screens and mock-ups without some strategic planning and core setup elements that will make your Proof of Concept a success.

所以……您在想：“好吧。 我需要概念證明。 簡單，讓我們打開Sketch并開始設計屏幕！” 哇！ 等一下 如果沒有一些戰略計劃和核心設置要素，這將使您的概念證明獲得成功，那么您將無法隨意制作屏幕和模型。

Over the years, I’ve helped hundreds of students develop app redesigns, interactive projects, mobile applications, and interactive art installations. Based on this extensive history, I have arrived at a successful User Experience design process for building a Proof of Concept.

多年來，我已經幫助數百名學生開發了應用程序重新設計，交互式項目，移動應用程序和交互式藝術作品。 基于這段悠久的歷史，我已經成功構建了用于概念驗證的用戶體驗設計過程。

Assuming you know what your project is — a big assumption, I know — and you have basic goals in mind, setting up a successful Proof of Concept requires a rock-solid user persona, user scenario, user task, and user flow diagram. You must build these core elements first before tackling the Proof of Concept.

假設您知道您的項目是什么-我知道這是一個很大的假設-并且您已牢記基本目標，因此要成功建立概念證明，需要堅實的用戶角色 ， 用戶場景 ， 用戶任務和用戶流程圖 。 在解決概念驗證之前，您必須首先構建這些核心元素。

In this article we will cover:

在本文中，我們將介紹：

1. What is a Proof of Concept?

   什么是概念證明？

2. Defining design goals

   定義設計目標

3. Why you need a user persona and what it looks like

   為什么需要用戶角色及其外觀

4. A user story (scenario) provides context for the Proof of Concept

   用戶案例(場景)為概念驗證提供了上下文

5. Defining a clear user task with a measurable outcome

   定義清晰的用戶任務并獲得可衡量的結果

6. Creating a user flow diagram

   創建用戶流程圖

In this article, I detail what these core setup elements look like, how to create them and reveal time-tested tips and tricks forged over years of trial-and-error.

在本文中，我將詳細介紹這些核心設置元素的外觀，如何創建它們以及揭示經過數年反復試驗而經過時間考驗的技巧和竅門。

1.什么是概念證明？ (1. What is a Proof of Concept?)

A Proof of Concept is a Blueprint. Like buildings and cities, interactive experiences need planning and a clear process for execution. And in the same way that buildings need blueprints, mobile apps need a Proof of Concept.

概念證明是一個藍圖。 像建筑物和城市一樣，交互式體驗需要規劃和明確的執行流程。 就像建筑物需要藍圖一樣，移動應用程序也需要概念證明。

In a general sense, a Proof of Concept is any representation that demonstrates how an interactive project will work. This can include sketches, diagrams, wireframes, prototypes, and coded experiments.

在一般意義上，概念證明是表示交互式項目將如何工作的任何表示形式。 這可以包括草圖，圖表，線框，原型和編碼實驗。

For the purpose of this article, I define a Proof of Concept as a step-by-step sequence of images that represents how a user moves through a particular interactive experience.

出于本文的目的，我將概念證明定義為逐步的圖像序列，代表用戶如何在特定的交互體驗中移動。

The benefit of using a Proof of Concept is that it provides a blueprint for the actual development, coding, and launch of a mobile app. You wouldn’t start pouring concrete before you had a very clear idea of what you’re building.

使用概念驗證的好處在于，它為移動應用程序的實際開發，編碼和啟動提供了一個藍圖。 在您非常清楚自己要構建的內容之前，您不會開始澆注混凝土。

Here is an example of a high-fidelity Proof of Concept designed by one of my previous students Alex Kim.

這是 我以前的一位學生 Alex Kim 設計 的高保真 概念驗證 的示例 。

A Proof of Concept can be used to model a completely new app from scratch or redesign an existing app. Design firms and tech companies develop Proof of Concepts to create new apps, improve existing apps, or propose new features. Many of my students propose and create a unique app for their portfolios or redesign an existing app in order to demonstrate their understanding of UX process and design.

概念驗證可用于從頭開始為全新的應用程序建模或重新設計現有應用程序。 設計公司和科技公司開發概念驗證以創建新應用，改進現有應用或提出新功能。 我的許多學生為自己的作品集提議并創建一個獨特的應用程序，或者重新設計一個現有的應用程序，以展示他們對UX流程和設計的理解。

There is no single way to build a Proof of Concept. Over my years of teaching, I have developed a model for creating a Proof of Concept. This model represents a minimum viable product with the least amount of elements possible to achieve actionable results.

沒有建立概念證明的單一方法。 在多年的教學中，我已經開發了用于創建概念證明的模型。 該模型代表了一種最小可行的產品，其元素數量最少，可以達到可行的結果。

This is a very simple model. I always stress to my students (and anyone I can convince) that starting out simple is the best way to achieve early success. These early successes will point you in the right direction. Try this process once, see how it fits. At any step, you can perform more testing, apply different types of testing, and create additional personas, scenarios, and flows.

這是一個非常簡單的模型。 我總是向我的學生(以及我能說服的所有人)強調，從簡單開始是取得早期成功的最好方法。 這些早期的成功將為您指明正確的方向。 嘗試一次此過程，看看它如何適合。 在任何步驟，您都可以執行更多測試，應用不同類型的測試以及創建其他角色，場景和流程。

2.定義設計目標。 (2. Defining design goals.)

The first thing you need to do when creating a Proof of concept is to define your design goals. You need to know what you want to accomplish before you start designing. The design goals become a touchstone that you go back to and use to evaluate your progress.

創建概念證明時，您要做的第一件事就是定義設計目標。 在開始設計之前，您需要知道要完成的工作。 設計目標成為您重新評估進度的試金石。

Where do you get your design goals from? This starts with sitting down, reflecting, and taking notes about your goals for the project. If you’re working on a client project, your discussions with the client, your own heuristic evaluation, and experience will provide your goals. If you’re working on a personal or student project you’ll have to rely on your own research, suggestions from your instructor and peers, and your heuristic evaluation of the app.

您從哪里獲得設計目標？ 首先，請坐下，進行反思，并記下項目目標。 如果您正在處理客戶項目，則與客戶的討論，自己的啟發式評估和經驗將為您提供目標。 如果您正在從事個人或學生項目，則必須依靠自己的研究，老師和同伴的建議以及對應用程序的啟發式評估。

When you start, write everything out no matter how big or small the goals are. Large goals could be something like “Increase click-through rates by 50%”. A small goal could be something like “Move the main menu from left to right”

開始時，無論目標有多大，都應將所有內容寫下來。 大型目標可能類似于“將點擊率提高50％”。 一個小的目標可能是“將主菜單從左移到右”

Here’s a good technique. Open up a spreadsheet and list every goal you can think of for the project large and small. Then go back through the list and make a new column and categorize each goal with either an “A”, “B”, or a “C”. Sort your “A” goals to the top and identify the top three “A” goals.

這是個好技術。 打開電子表格，列出您可以為該項目大大小小的每個目標。 然后返回列表，新建一個列，并用“ A”，“ B”或“ C”對每個目標進行分類。 將您的“ A”目標排序到頂部，并確定前三個“ A”目標。

It’s important to narrow down to the top three design goals so that you don’t get overwhelmed. Don’t worry, all your other goals are still there and you can go back and reprioritize them at any time. Print out your three goals and keep them close to you whenever you’re working on the project so that you can reference them.

重要的是縮小最重要的三個設計目標，以免使您不知所措。 別擔心，您的所有其他目標仍然存在，您可以隨時返回并重新排列它們的優先級。 打印出您的三個目標，并在您進行項目時使它們離您很近，以便您可以參考它們。

Before you can actually get started designing your Proof of Concept you need to create the following elements: a user persona, user scenario, user task, and a user flow diagram.

在真正開始設計概念驗證之前，您需要創建以下元素：用戶角色，用戶場景，用戶任務和用戶流程圖。

3.為什么需要用戶角色及其外觀。 (3. Why you need a User Persona and what it looks like.)

A user persona is an imagined representation of a primary target user. Think of the user persona as an aggregate of the most important needs and characteristics of your primary target audience. In the beginning, focus on creating up to three of these personas. Later you can move on to other personas that have different needs from your primary target audience (including some personas that have outlier characteristics).

用戶角色是主要目標用戶的想象表示。 將用戶角色視為主要目標受眾最重要的需求和特征的總和。 在開始時，重點是最多創建三個這樣的角色。 稍后，您可以轉到與主要目標受眾有不同需求的其他角色(包括一些具有異常特征的角色)。

The persona is a fictitious character. It’s a common mistake to use a real person for your persona. This can cause confusion as this person often has specific characteristics, or needs, that fit outside of the model persona you’re trying to create.

角色是虛構的角色。 使用真實人物作為您的人物形象是一個常見的錯誤。 這會引起混亂，因為此人通常具有特定的特征或需求，這些特征或需求適合您要創建的模型角色的外部。

I recommend including the persona as one of the first slides in your Proof of concept. This provides the context for the user scenario and flow.

我建議將該角色作為概念證明中的第一張幻燈片之一。 這為用戶方案和流程提供了上下文。

4.用戶故事(場景)為概念驗證提供了上下文。 (4. A user story (scenario) provides context for the Proof of Concept.)

Once you have your persona, next you want to create a user scenario for that persona. The scenario is a short story that sets up the background and the current context. The scenario should say why your user is interacting with your project.

擁有角色之后，接下來您要為該角色創建一個用戶場景。 該場景是一個簡短的故事，它設置了背景和當前上下文。 該方案應說明您的用戶為何與您的項目進行交互。

Write 3 to 5 sentences of backstory and provide the current context — in terms of time and place, and the reason (or rationale) for using your project. Remember to keep it short, and pick your words wisely. From reading the user scenario, your audience should understand who the persona is, why they want to use the project, and what the context is for using it.

寫3到5個背景故事，并提供當前的上下文-在時間和地點以及使用項目的原因(或理由)方面。 記住要簡短，并明智地選擇你的話。 通過閱讀用戶場景，您的聽眾應該了解角色是誰，他們為什么要使用該項目以及使用該項目的上下文。

5.定義清晰的用戶任務，并得出可衡量的結果。 (5. Defining a clear user task with a measurable outcome.)

For a Proof of Concept to be effective, it must be based on a user task. For instance, a user may want to search a list of restaurants, or check a balance on an account, or update their profile information. Whatever the goal they have in mind is, that is the task. Ultimately the Proof of Concept is the visual representation of the achievement of the task. It shows a step-by-step sequence of how the user accomplishes a particular task.

為了使概念證明有效，它必須基于用戶任務。 例如，用戶可能想要搜索餐館列表，或檢查帳戶余額，或更新其個人資料信息。 他們想到的目標是任務。 最終，概念證明是任務完成情況的視覺表示。 它顯示了用戶如何完成特定任務的分步序列。

It is important to connect the scenario to the tasks. Therefore your scenario should set up the context of the tasks, and the tasks should reflect the scenario.

將方案連接到任務上很重要。 因此，您的方案應設置任務的上下文，并且任務應反映方案。

When starting a new Proof of Concept, it helps to define a small number of core tasks. I start students off by having them define only three tasks. I ask them to focus on identifying the most important three tasks based on the user’s goals.

在開始新的概念驗證時，它有助于定義少量核心任務。 首先，讓學生定義三個任務。 我要求他們專注于根據用戶目標確定最重要的三個任務。

One of the best ways to capture tasks is to write them down in the form of a flowchart, or write each step in sharpie marker on a separate sticky note and then combine them to create a sequence of steps.

捕獲任務的最佳方法之一是將它們以流程圖的形式記錄下來，或者將每個步驟寫在單獨的便箋上的沙皮紙標記中，然后將它們組合起來以創建一系列步驟。

Defining “The Task”Now that you have defined your three core user tasks, you want to write them down in simple statements. For instance, you might write out the first task as “Task 1: search internships in my city,” the second task as “Task 2: select design internship, $25 dollars an hour,” and the third task as “Task 3: tap the more info button.” Notice that the wording of these tasks is very clear.

定義“任務”現在，您已經定義了三個核心用戶任務，您想用簡單的語句將它們寫下來。 例如，您可以將第一個任務寫為“任務1：在我所在的城市搜索實習”，將第二個任務寫為“任務2：選擇設計實習，每小時25美元”，而將第三個任務寫為“任務3：點擊更多信息按鈕。” 請注意，這些任務的措辭非常清楚。

Avoid any vague task statements, as these will confuse your audience, or send them down complex paths without a clear goal in mind. Examples of unclear task statements include “Login and complete the first level,” or “Search for restaurants close to you.” While these statements seem reasonable at first glance if you think deeply you’ll notice that they leave a lot of information unexplained.

避免使用任何含糊的任務陳述，因為這會使您的聽眾感到困惑，或者使他們沿著復雜的道路前進，而沒有明確的目標。 任務說明不明確的示例包括“登錄并完成第一級”或“搜索您附近的餐館”。 盡管乍一看這些陳述似乎很合理，但您會注意到它們留下了許多無法解釋的信息。

A Proof of Concept is a primary tool for user testing, so clear tasks will help your user testers understand exactly what you want them to do. The more clear you are about the tasks the easier it is for you to define, and visually represent, the step-by-step screens in your Proof of Concept.

概念驗證是用戶測試的主要工具，因此清晰的任務將幫助您的用戶測試人員準確了解您希望他們做的事情。 您對任務越清楚，就越容易定義和直觀地表示概念證明中的逐步屏幕。

Every user task needs a “Measurable Outcome”I use the term “measurable outcome” to mean a clear form of completion criteria. You can also call this the result of the task. It must be something that can be unequivocally proven to have either been met or not through testing. For instance, the measurable outcome could be “closes confirmation pop-up window.” This example is testable because we can observe the user actually tapping on the close icon. Something that’s not measurable is generally passive and/or open-ended.

每個用戶任務都需要一個“可衡量的結果” 我用“可衡量的結果”一詞來表示完成標準的明確形式。 您也可以將其稱為任務的結果。 它一定是可以通過測試明確證明已經達到或未達到要求的東西。 例如，可測量的結果可能是“關閉確認彈出窗口”。 此示例是可測試的，因為我們可以觀察到用戶實際上點擊了關閉圖標。 不可測量的東西通常是被動的和/或開放的。

There has to be a specific result for each user task. While it might seem like overkill, I require students to write a sentence underneath the task statement that defines the result of each task. This reinforces the clarity of the task and allows your audience to understand what exact results are desired for a particular task.

每個用戶任務必須有一個特定的結果。 盡管這看起來有些過分，但我還是要求學生在任務說明下寫一個句子，以定義每個任務的結果。 這增強了任務的清晰度，并使您的聽眾了解特定任務所需的確切結果。

6.創建用戶流程圖 (6. Creating a user flow diagram)

A user flow diagram is a sequential diagram or series of illustrations that describe how a user moves step-by-step through an interactive project (app, website, installation) to achieve a goal.

用戶流程圖是描述用戶如何逐步移動交互式項目(應用程序，網站，安裝)以實現目標的順序圖或一系列插圖。

Other words for user flow include task flow, user task, wire flow, flowchart, decision trees, and more. All of these have the same goal of describing the path of the user.

用戶流程的其他詞語包括詢問流程，用戶任務，電匯流程，流程圖，決策樹等。 所有這些都具有描述用戶路徑的相同目標。

A user flow is often illustrated as a flowchart with each step defined as a box with an arrow to the next step. The last step has to be the achievement of the measurable outcome of the task. A great way to present this is to create a single slide with clear labeling that includes the task number, task title, persona image, basic persona demographics, the flow chart of the steps, and a highlighted final step/measurable outcome.

用戶流程通常被圖示為流程圖，每個步驟定義為帶有指向下一步的箭頭的框。 最后一步必須是完成任務的可衡量結果。 呈現此問題的一種好方法是創建一張帶有清晰標簽的幻燈片，其中包括任務編號，任務標題，角色形象，基本角色人口統計信息，步驟流程圖以及突出顯示的最終步驟/可衡量的結果。

An effective method for creating the user flow is to write out the task and then quickly write down the steps using sticky notes until you have completed the flow. If you have over 7–10 steps, that’s a good sign that you need to either improve the user experience by eliminating steps or subdivide it into multiple user flows. Now that you have your user flows you’re ready to start designing screens in low-fidelity.

創建用戶流的一種有效方法是寫出任務，然后使用便箋快速記下步驟，直到完成該流。 如果您的步驟超過7–10，則表明您需要通過消除步驟或將其細分為多個用戶流程來改善用戶體驗。 有了用戶流之后，您就可以開始設計低保真屏幕了。

The “Proof” in the Proof of Concept

概念證明中的“證明”

In a sense, the degree to which your user task statements and results match up is the “proof” part of the Proof of Concept. When a particular task achieves the desired result it proves that the Proof of Concept is accurate.

從某種意義上說，用戶任務陳述和結果的匹配程度是概念證明的“ 證明 ”部分。 當特定任務達到期望的結果時，它證明概念證明是準確的。

User testing your Proof of Concept will reveal if your user testers can actually achieve the results you have defined for each task. It is almost never the case that your tasks achieve the correct results the first time, or the second, or the third! And of course, it should be like this. You create a Proof of Concept for this exact reason: so that you can test the tasks and results over and over until they prove your concept.

對概念驗證的用戶測試將揭示您的用戶測試員是否可以真正實現您為每個任務定義的結果。 幾乎永遠不會在您的任務第一次，第二次或第三次獲得正確結果的情況下 ！ 當然，應該是這樣。 出于這個確切的原因，您創建了概念證明：以便您可以反復測試任務和結果，直到它們證明您的概念為止。

摘要 (Summary)

We defined the Proof of Concept as a blueprint for your interactive project. It starts with defining your design goals. Then you create an example person (or user persona) in your primary target audience. This persona needs a user scenario that sets up the background story and the current context. And every Proof of Concept needs a series of user tasks defining the desired outcomes for the user. The path a user takes to complete a task is illustrated with a user flow diagram.

我們將概念驗證定義為您的交互式項目的藍圖。 首先要定義您的設計目標。 然后，在主要目標受眾中創建一個示例人物(或用戶角色)。 該角色需要一個設置背景故事和當前上下文的用戶場景。 每個概念證明都需要一系列用戶任務，這些任務定義了用戶所需的結果。 用戶流程圖說明了用戶完成任務所采用的路徑。

In the next article, we will cover starting your Proof of Concept design in low-fidelity, clearly labeling and formatting the Proof of Concept, conducting a paper prototype test, and documenting the results.

在下一篇文章中 ，我們將介紹以低保真度開始您的概念證明設計，清楚地標記和格式化概念證明，進行紙質原型測試并記錄結果。