Product Requirements Document

Mission

Enterprise Chat User Onboarding is meant to automatically onboard users to their discipline, teach prompts interactively, and simplify of the app’s core concepts. After onboarding, a user should feel enabled within Enterprise Chat and be equipped to become an intermediate user.

Background

Beginner-level users with Enterprise Chat (or really having no any LLM experience) don't fully understand or explore the capabilities of the platform. We want to assist them by onboarding them efficiently and automatically into the system, so they can be more comfortable with the tools available to them. To that end, we want them to have prompt-access enabled (auto-join) for their self-reported discipline within the first minute of using the tool. We want users to learn how to build prompts soon after that, with educational examples. We also want to give them a brief tour of the platform, with an option to replay the tour at any time.

Targeted Personas

A full list of personas can be found https://lucid.app/lucidspark/ed334dc2-724c-4bef-b653-afa71ff82de9/edit?viewport_loc=1988%2C-73%2C6244%2C3461%2C0_0&invitationId=inv_29b7c156-cc1c-4a12-8033-455d3585c8d2here.

• Angela Analyst: who may not have ever used an LLM before. They may need lots of handholding.
• Dario Data Professional: who may have some LLM experience. They will still need a general overview of the existing platform capabilities to know what is where.

Current Behavior

There is no onboarding process today. Users are given some minimal direction using helper text within "Create New Prompt", but nothing outside of that.

Outcomes / Goals

• A user logs into Enterprise Chat for the first time and is immediately lead through an intuitive onboarding process. At the end of the process, the user will be added to a team matching their affinity group (engineering, sales, etc).
• Users should be taught basic prompt engineering, and have a brief tour of the platform to understand where basic features are located and how they work.
  • Prompt creation and sharing
  • Back-and-forth with the chat model
• This will be a singular release. New onboarding capabilities will appear in subsequent feature PRDs

User Stories

Onboarding a User Onto a Team

• As a new user, immediately after login a chat window appears which begins onboarding me. Throughout the subsequent chat conversation, I answer some basic questions about myself which helps the system autojoin certain teams and groups for me.

Helper Text

• As a new user or regular user , I'm given plenty of helper text which can guide me through the platform incase I don't know what something does OR I forget how it works.

Prompt Library

• As a new user, I'm quickly directed to the prompt library and taught how to use it in an intuitive manner.

Use cases

First-time Onboarding

1. Team Assignment
   1. Primary Actor: Any First-time User
   2. Description: From the moment a first time user logs in, a chat screen is displayed for them, asking them where in the org they sit.
   3. Preconditions:
      1. User is authorized to use Enterprise Chat.
      2. User has never before logged into Enterprise Chat OR has ever gone through the onboarding process OR User has manually triggered the onboarding process.
   4. Postconditions:
      1. User is added to and can see the prompt libraries for their self-designated team.
   5. Flow:
      1. User logs into Enterprise Chat
      2. User is given a single chat session called Onboarding. Within this chat session they see the following message: "Hello, [name]! Happy to see that you've joined. Let's start off by personalizing your chat experience.
         What is your role at [Enterprise].inc?"
      3. The user is provided a dynamic list of groups in Enterprise Chat (configured by the EC Administrator). The user is able to select one or more groups.
      4. After clicking the continue arrow ">", the next chat message will display: "Great, we've just added your team to the left navigation bar for you. You can see all prompts within that team." (later this will be used to display live users)
      5. Outcome: User is now assigned a team and can see all team shared prompts.

Novice User Training

1. Prompt Engineering Walkthrough - Can be built with Intercom
   1. Primary Actor: Any first-time or novice user who triggers the walkthrough
   2. Description: Auser should be guided through the process of writing a prompt. They should be pushed to create a new prompt for the first time, and taught how to share that with the rest of the team. This process should be skippable if needed.
   3. Preconditions: (User has finished team assignment AND back-and-forth chat walkthrough) OR user has manually triggered this through the walkthrough menu.
   4. Postconditions: User has sufficient understanding to design their own prompts.
   5. Flow:
      1. After a user has finished the team assignment onboarding flow OR the user has manually triggered this walkthrough in the settings menu, the "Prompt Library" menu item should be highlighted with some text "Learn how to prompt engineer!"
      2. The user should click on this to continue the walkthrough. Alternatively, they can press the skip button to bypass this completely at any time.
      3. Next the user should be guided through basic prompt engineering, with tooltips displaying above each of the fields (step by step) to be filled in by the user. Provide examples in these tool tips
      4. When the user completes their prompt, they should be shown how to optionally share this prompt to their team.
      5. Outcome: The user has created a new prompt and has optionally shared it with their team.
2. Back-and-Forth Chat Walkthrough - Can be built with Intercom
   1. Primary Actor: Any first-time or novice user who triggers the walkthrough
   2. Description: There are user personas who have never used ChatGPT or anything remotely similar to it. They will need to be handheld to understand how to operate an AI chat agent.
   3. Preconditions: User has just finished team assignment OR user has manually triggered this through the walkthrough menu.
   4. Postconditions: User has understanding on how to create a new chat, use the chat window, and has some experience chatting with the model.
   5. Flow:
      1. User is given another single chat session called AI-Chat Tutorial (or something else fun). Intercom will draw the user's eye to this chat session for them to click or skip it.
      2. When clicked on, this intercom window will display the following message: "Welcome to the AI-Chat Tutorial. Here you will learn how to chat with an AI-powered agent. Let's begin by asking a question. You can ask one-off questions like 'What is an AI-powered chat agent good at doing?'"
      3. Intercom will highlight the text field and wait for the user to write a question and press ">". When the agent responds, the intercom message will display "The AI-powered agent will then respond. You can continue asking questions on this topic, or switch to an entirely new topic altogether! You can ask a followup question like "What is an AI-powered agent not good at doing?"
      4. Intercom will again highlight the text field and wait for the user to write a question and press ">". When the agent responds, intercom will display "Agents can also be used in back-and-forth conversation, where they ask you questions to better refine their answer to your query. Try asking the agent to personalize by asking you questions: "Please refine your next answer by asking me questions about my job role. How can an AI-powered agent help me achieve my job role's objectives?"
      5. At this point the demo will end, intercom will display no more messages and the user will be free to explore the chat as they wish.

Requirements

Functional

• List of functional description of the feature

Non-functional requirements

• Simple for first-time users to understand. All text and explanations should point to more detailed documentation in case a user wants to Learn More.

Out of Scope

• Vector DBs and explaining how they work
• Any kind of onboarding for features that dont yet exist or that a non-admin user wouldn't have access to (agent systems, user/group management, anything admin related, etc)

Dependencies & Constraints

• Any kind of dependency

Assumptions

• Work can begin on this near immediately, as it faces no dependency from an infrastructure/functional perspective. Teams/user groups already exists

Risks

• The above assumption about lack of prerequisites is wrong and there is substantial work involved to even have teams/user groups.

Timeline and Milestones

Phase I

• Release 1.01
  • Users get a team-assignment onboarding experience
  • Intercom walkthrough for prompt engineering
  • Intercom walkthrough for model back-and-forth

Questions?