---
title: "Tooltips Workflow"
canonical: "https://documentation.chaos.com/space/DOCSGUIDE/212467715/Tooltips%20Workflow"
format: markdown
---
There are three types of tooltip writing workflows: the Envision workflow, the Enscape workflow for new features, and the Enscape workflow for existing features.


## **Envision Workflow**

---

1. The Product Manager creates a story in the Aha! portal with a detailed description of the feature to be developed.
2. Once the feature is selected for development, a Jira work item is created in the UX project and UX designers begin designing the feature. At this stage, meetings are held with the Information Experience Specialist, during which the feature is presented.
3. A UX Designer creates a Jira work item in the Documentation project for the tooltip task.
4. The Information Experience Specialist writes tooltip suggestions in the Figma prototype provided by the UX designers.
5. After preparing the tooltips and labels, the Information Experience Specialist requests a review from the Product Managers.


## **Enscape New Features Workflow**

---

1. The Product Manager creates a story in the Aha! portal with a detailed description of the feature to be developed.
2. Once the feature is selected for development, a Jira work item is created in the UX project and UX designers begin working on the feature design. At this stage, meetings are held with the Information Experience Specialist, during which the feature is presented.
3. When the design is ready, the UX designers reassign the UX work item to the Information Experience Specialist.
4. The Information Experience Specialist contacts the UX designers and Product Managers, reviews comments in the Jira ticket, familiarizes themselves with the feature, and confirms with UX and Product Managers which components require documentation support.
5. After preparing the tooltips and labels, the Information Experience Specialist requests a review from the Product Managers.


## **Enscape Existing Features Workflow**

---

1. Developers, QAs, or other specialists notice a missing or incorrect tooltip and create a Jira work item in the respective product's Jira project.
2. The ticket is assigned to an Information Experience Specialist.
3. The Information Experience Specialist reviews the issue and adds or corrects the tooltip.
4. Once the tooltip is ready, the Information Experience Specialist notifies the Product Manager to review and approve the tooltip text.
5. After the Product Manager approves the tooltip, a Developer reassigns the ticket and begins implementing the tooltip in the product.