フローチャートは、ユーザーの Chat アプリでのすべての操作を可視化および検討する際に役立つツールです。Chat アプリが他の Google サービスや Google 以外のサービスと連携している場合は、それらのインタラクションも含めてください。フローチャートには、考えられるすべてのインタラクションを表すようにします。ワークフローが複雑な場合は、すべてのユーザー ジャーニーのフローチャートを作成します。
次のフローチャートは、Chat から Google カレンダーを管理できる Chat アプリのユーザー ジャーニーを示しています。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-03-06 UTC。"],[[["\u003cp\u003eDefine user journeys with flowcharts to visualize user interactions and potential pain points within your Google Chat app.\u003c/p\u003e\n"],["\u003cp\u003eUtilize user stories (As a \u003cem\u003euser\u003c/em\u003e, I want to \u003cem\u003edo a task\u003c/em\u003e, so I can \u003cem\u003eachieve a goal\u003c/em\u003e) to guide the development of user journeys and ensure alignment with user needs.\u003c/p\u003e\n"],["\u003cp\u003eAccount for all error scenarios within user journeys, crafting actionable error messages to help users recover and continue their workflow.\u003c/p\u003e\n"],["\u003cp\u003eEnsure each user interaction within the journey concludes with a message from the Chat app, providing feedback or guidance to the user.\u003c/p\u003e\n"],["\u003cp\u003eInclude a legend with your user journey flowcharts to clarify the meaning of different shapes and symbols, making them easier to understand.\u003c/p\u003e\n"]]],["Define user journeys as sets of actions between users and a Chat app to achieve goals. Create flowcharts to visualize all interactions, including those with external services. Write user stories in the format: \"As a *user*, I want to *do a task*, so I can *achieve a goal*.\" Include a legend for the flowchart. Map out error scenarios, defining the error, message, and user response. Detail each interaction with a message from the Chat app.\n"],null,["# Define all user journeys\n\nThis page describes how to define and map the user journeys of your\nGoogle Chat app. A *user journey* is a set of actions and\ninteractions between a user and a Chat app that helps\nthe user achieve a goal. Define these journeys before building the\nChat app to identify the following:\n\n- When to provide error messages.\n- When to suggest commands to help users use the Chat app.\n- Where the user flow might be simplified.\n\nCreate a flowchart of all user journeys\n---------------------------------------\n\nFlowcharts are useful tools for both visualizing and thinking through all user\nChat app interactions. If your\nChat app works with other Google services, or\nservices outside of Google, be sure to include these interactions too. Ideally,\nyour flowchart depicts every possible interaction, or for more complicated\nworkflows, a flowchart for every user journey.\n\nThe following flowchart shows the user journey for a\nChat app that helps people manage their\nGoogle Calendar from Chat:\n\nThe preceding diagram shows the following steps of a user wanting to use a\nChat app to check their Calendar:\n\n1. A user adds the Chat app to a space.\n\n2. The Chat app sends a welcome message that prompts\n the user to [authorize access](/workspace/chat/authenticate-authorize).\n\n - If the user refuses to authorize access, the previous welcome message is resent.\n - If the user agrees to authorize access, they click **Sign in**.\n3. The user is asked to sign in from a\n [dialog message](/workspace/chat/dialogs).\n\n - If the user is unable to sign in, an error message is sent asking the user to try signing in again.\n - If the user is able to successfully sign in, an onboarding message is sent that describes how to use the Chat app.\n4. The user types the `/checkCalendar`\n [slash command](/workspace/chat/commands)\n to get today's schedule from Calendar.\n\n - If the Chat app is unable to retrieve the user's calendar, an error message is sent.\n - If successful, the Chat app sends today's schedule in a card message.\n\nWrite user stories to guide your user journeys\n----------------------------------------------\n\nA *user story* represents a user goal, and is written so that the user, task,\nand purpose of the story is clear. User stories are meant to be open-ended\nbecause there's usually more than one way to satisfy the requirements that they\ndescribe. User stories help you set paths for users to follow as they work with\nChat app.\n\nUser stories have the following format: As a *user* , I want to *do a task* , so I\ncan *achieve a goal* . In the previous example, the user story is: As a\n*cross-functional worker* , I want to *check my calendar* so I can\n*collaborate on projects with others*.\n\nMost Chat apps have multiple user stories. For example, another\nuser story for the example Chat app is: As a *manager* ,\nI want to *schedule a weekly meeting that includes all my direct reports* , so we\ncan *collaborate on projects*. For each user story, identify the users' journey\nfor your Chat app and create a flowchart to identify\nall potential interactions with your Chat app.\n\nInclude a legend\n----------------\n\nTo help others read your user journeys, include a legend that describes which\nshape represents which type of interaction. For example, identify a unique shape\nfor user decision points, user input, successful and unsuccessful results from\nyour Chat app, and any messages from the\nChat app.\n\nAccount for all error scenarios\n-------------------------------\n\nTo ensure users never get stuck while working with your\nChat app, include error scenarios in your user journey\nmap. Define how the error occurs,\n[write an actionable error message](/workspace/chat/write-error-messages),\nand identify how the user might respond to the error in order to achieve their\ngoal. For example, \"Wrong username or password. Try signing in again.\"\n\nIdentify the messages your Chat app sends to users\n--------------------------------------------------\n\nEach interaction should end with a message from your\nChat app to the user, even if it's only a message\nconfirming that the Chat app successfully completed the\nuser's request. For example, \"Welcome to the scheduling app. I can schedule,\nreschedule, or remove events from your calendar. Take a look at today's schedule\nby typing `/checkCalendar`.\"\n\nRelated topics\n--------------\n\n- [Set up slash commands to interact with Google Chat users](/workspace/chat/slash-commands)\n- [Write an actionable error message](/workspace/chat/write-error-messages)\n- [Design user interactions](/workspace/chat/interactivity)"]]
