> 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/what-to-build-next/patterns-that-work.md).

# Patterns that work

Combinations of experiences that come back account after account, with the settings that make them work. Each one is a few hours once the first experience is live.

***

## The patterns

Eight combinations, each with the settings that make it work.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FmIGUauVKj0EOIFnqd4zp%2Fn26-patterns.png?alt=media&amp;token=47866d3a-0e0a-4dc6-ac3f-be7603b1c77a" alt="Eight patterns as chains of experiences"><figcaption></figcaption></figure>

### Welcome tour, checklist, Resource Center

The onboarding backbone. A three-step welcome tour on first login whose last button launches a checklist. Five tasks, each launching a short tour, each completed by an event or the tour's completion. A Resource Center with the checklist embedded, so the user finds it again after closing it, plus links and a contact.

#### Settings

Tour on page load, Who = new users (signup date in the last 7 days, once `created_at` is sent), show once. Checklist: Dismissible on, so users can close it and reopen it from the Resource Center. See [Checklist and tours together](https://help.usejimo.com/docs/getting-started/create-your-first-experience/checklist-and-tours-together.md) and [Checklist behavior](https://help.usejimo.com/docs/experiences/checklists/behavior.md).

### A survey as a branching point

One question on first login ("What brings you here?" with three answers), and each answer launches a different checklist. Users get the onboarding that matches their intent, and you learn the split. Build the three checklists first, then the survey with a Choice step whose each option has a Launch experience action. See [Surveys](https://help.usejimo.com/docs/experiences/surveys.md) and [Available actions](https://help.usejimo.com/docs/build/actions/available-actions.md).

### Modal, then hint, then tour

For feature adoption, in this order over three weeks. A modal announces the feature once. A hint stays on the feature's control for the users who missed it. A tour, launched from the hint's button, walks through it for those who want the detail. Each step reaches fewer users with more depth, and none of them interrupts twice.

### One Resource Center per product or per role

When your app serves several products or roles with the same login, one Resource Center per audience beats one with twenty links. Create them with the same theme, and target each with Who on the role attribute and Where on the product's pages. Users see one, the right one.

### Resource Center blocks per page

A single Resource Center whose blocks change with the page: the links for Reports on the Reports pages, the links for Billing on Billing. Each block carries its own Where and Who. See [Resource Center components](https://help.usejimo.com/docs/experiences/resource-center/components.md).

### Re-show to users who did not finish

A tour or a checklist that comes back after a few days for the users who started it without completing it. Who: a "has not completed" condition on the experience. When: a recurrence instead of show once. Keep rate limiting on so it does not stack with other experiences. See [Who](https://help.usejimo.com/docs/publish/target-right-people-who.md) and [When](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when.md).

### Internal announcements

A banner for maintenance windows or incidents, targeted at internal users through a segment on your email domain, published to Production with a scheduled end date. Cheaper than a Slack message nobody reads, and gone on its own. See [Banners](https://help.usejimo.com/docs/experiences/banners.md) and [Planning](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/planning-your-experience.md).

### Chain two checklists

When the first checklist is completed, launch the second (advanced setup, a second product). The last task's completion, or a Goal on the checklist, triggers the next one through a Launch experience action. See [Checklists](https://help.usejimo.com/docs/experiences/checklists.md).

## Related

* [What to build next](https://help.usejimo.com/docs/getting-started/what-to-build-next.md)
* [Bring in the Agent](https://help.usejimo.com/docs/getting-started/what-to-build-next/bring-in-the-agent.md)
