> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/create-your-first-experience/first-experience-by-goal.md).

# First experience by goal

[Choose your first use case](/docs/intro/what-is-jimo/choose-your-first-use-case.md) says which family your goal belongs to. This page says, for each goal, what to build in the builder first, in how many steps, and what to leave for the next level. The rule behind every row: one experience, short, no element targeting unless the goal requires it.

***

## Pick by goal

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FGRbxL5pr1IUsCP0v96hL%2Fn13-goal-to-experience.png?alt=media&amp;token=68c63104-1696-476c-9269-153b92b59d6d" alt="Six goals, each with the experience to start with"><figcaption></figcaption></figure>

#### Onboard new users

**Finish:** the generated Welcome tour. Keep three to five steps: a modal that says what the product is for, two or three tooltips on the controls a new user touches first, a last modal that points to what to do next. Attach steps only to elements with stable selectors.

**Create it from scratch if needed:** Tours & Modals > New Tour, Flow Builder, drag a Modal step then Tooltip steps. See [Tours & Modals](/docs/experiences/tours-and-modals.md).

**Next level:** the Checklist, with each task launching a tour. See [Checklist and tours together](/docs/getting-started/create-your-first-experience/checklist-and-tours-together.md).

#### Get a feature used

**Finish:** one modal or one hint on the feature, no sequence. A modal when the feature is new to everyone (shown once), a hint when it sits on a control users keep missing (always there). Hints > New Hint, pick Tooltip or Hotspot, attach it to the control. See [Hints](/docs/experiences/hints.md).

**Next level:** a short tour launched from the hint's button, and a [Goal](/docs/publish/mesure-outcomes-goal.md) on the feature's event to measure the lift.

#### Announce a release

**Finish:** a changelog post, then a banner that links to it. Changelog > Posts > New Post for the content; Banners > New Banner with a single line and a button to the post. Neither needs a selector. See [Posts](/docs/experiences/changelog/posts.md) and [Banners](/docs/experiences/banners.md).

**Next level:** a modal for a subset (admins, a plan) once identify is in place, and a "has not seen" condition in Who to stop repeating.

#### Give help in context

**Finish:** a Resource Center with three to five links to your existing docs and a contact block. Resource Centers > New Resource Center. It floats in a corner, so it needs no selector, and it is the one experience users come back to on their own. See [Resource Center](/docs/experiences/resource-center.md).

**Next level:** blocks that change per page and per audience, a checklist embedded in it, the Ask Agent block.

#### Collect feedback

**Finish:** one NPS or one single-question survey, triggered on a page your users reach after they have done something (not on login). Surveys > New Survey, pick the NPS template or a single Choice step. See [Surveys](/docs/experiences/surveys.md).

**Next level:** a survey as a branching point that sends each answer to a different checklist, and Slack notifications on new answers.

#### Replace another tool

**Finish:** the one flow your users see most in the tool you are leaving, rebuilt as is, in the same place. Not the whole library. Appcues, Intercom, Userpilot and WalkMe flows map to tours, modals, hints and checklists one for one.

**Next level:** parity, flow by flow, then what the old tool could not do: the Resource Center, the Agent, goals.

## What needs a selector and what does not

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FaiaoRC3OOx0FgRI3989E%2Fn14-anchored-vs-floating.png?alt=media&amp;token=a5cfd951-03ea-4d46-9faa-7ef06b9be734" alt="Anchored experiences need a selector, floating ones do not"><figcaption></figcaption></figure>

| Needs a CSS selector                                                                          | Needs none                                                                                                |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Tooltip and hotspot steps in a tour, hints, a checklist task's progress trigger on an element | Modals, banners, surveys, changelog posts, the Resource Center, the Agent Launcher, checklists themselves |

If your front-end is unstable or you have no developer to add `data-testid` attributes, start in the right column and bring your developer in before the first tour. See [Stable selectors on a dynamic front-end](/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md).

## Related

* [Create your first experience](/docs/getting-started/create-your-first-experience.md)
* [What to build next](/docs/getting-started/what-to-build-next.md)