Get AI summaries of any video or article — Sign up free
How To Create Customer Journeys That Actually Convert [In Notion + Template] thumbnail

How To Create Customer Journeys That Actually Convert [In Notion + Template]

Landmark Labs·
5 min read

Based on Landmark Labs's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use the template’s pre-filled stages only as a starting hypothesis, then reorder or rename stages to match the real conversion path (e.g., add purchase conversion after mailing-list signup).

Briefing

Customer journey mapping often fails because the details that matter—button placement, announcement timing, and contextual cues—are hard to predict and even harder to track. A Notion-based workflow is presented as a way to capture those moving parts, connect them to real user goals, and refine the journey over time using feedback, research, and measurable KPIs.

The setup starts with a template built around an “infinite canvas” in Notion, organized so the left-hand menu moves through workspaces while a central map hosts the databases that power the journey. The home dashboard provides an overview of key journey stages, pre-filled with five stages and dummy data meant to show structure rather than final content. The first practical step is deciding whether those default stages fit the business at hand. For an athletic apparel example, the stages are adjusted to reflect a likely conversion path: sign up (e.g., joining a mailing list) followed by a purchase conversion, then a second purchase or reconversion, and finally a referral/affiliate-style stage.

Next comes persona work, where the template uses a personas database to store demographics and psychographics along with pain points, outcomes, and use cases. Personas can be created from scratch or informed by purchase data, then linked into goals and pain points so the journey stays grounded in who the customer actually is. The example persona “Jessica” drives the brainstorming: her goal is getting in better shape and updating her athletic wardrobe. Pain points are identified as obstacles such as competing brands being too expensive or mismatching her aesthetic and personality. The “win condition” becomes an endpoint tied to the journey—signing up to a health and fitness publication—positioned as a way to deliver engaging content that supports her goal.

From there, the template connects endpoints to key actions, and key actions to projects and touchpoints. For Jessica’s publication signup, actions include making the signup easy, ensuring she can find the option, and potentially improving signup UX or experimenting with where the signup button appears. The workflow also supports additional post-purchase goals, such as encouraging customers to share photos of new outfits on social media, with the journey stage and related sentiment tracked more precisely.

The system then becomes more actionable through use cases and content planning. A use case like “John’s new year fitness resolution” triggers keyword brainstorming and content ideas. Keywords are researched using a tool called Keywords Everywhere to estimate volume, difficulty, and cost per click, then turned into content items (articles) that appear in the content database once assigned a date or status. Products and features can be linked to these scenarios to keep messaging tied to what’s actually sold.

Finally, the template adds measurement and learning loops through surveys, sentiment, targets, and KPIs. After key moments like the first purchase, teams can run feedback surveys, store responses and results, and set clear objectives such as signup counts. The workflow is framed as never truly finished: customer activity and feedback continuously refine stages, actions, content, and research assumptions so the journey becomes more precise and more effective over time.

Cornell Notes

The workflow centers on building a customer journey in Notion that’s detailed enough to matter and flexible enough to improve. Instead of treating journey maps as static grids, it links journey stages to personas, goals, pain points, endpoints, key actions, projects, touchpoints, and content. The example athletic apparel journey adds purchase conversion after mailing-list signup, then reconversion and a referral/affiliate stage. Personas like “Jessica” drive specific endpoints (health and fitness publication signup), which translate into concrete actions (e.g., improve signup UX and button placement) and projects. Use cases such as “John’s new year fitness resolution” generate keyword research and article ideas, while surveys, sentiment, targets, and KPIs keep the map measurable and continuously updated.

Why are default journey stages often insufficient, and how does the template handle that?

Default stages are treated as a starting point, not a final structure. The workflow begins by checking whether the pre-filled five stages match the business’s actual conversion path. In the athletic apparel example, the stages are revised to include a purchase conversion after mailing-list signup, followed by a second purchase/reconversion stage, and then a referral/affiliate-style stage. This keeps the map aligned with where customers truly convert rather than forcing every business into a generic funnel.

How do personas connect to journey outcomes instead of staying as standalone profiles?

Personas feed directly into goals and pain points, which then link to endpoints and key actions. The example uses “Jessica” with a goal of getting in better shape and updating her athletic wardrobe. Pain points like high prices or an aesthetic mismatch are tied to what blocks purchase decisions. The endpoint becomes signing up to a health and fitness publication, which then maps to specific key actions and projects (e.g., making the signup option easy to find and improving signup UX).

What’s the practical chain from “endpoint” to “project” in this system?

Endpoints (what the customer should do) break down into key actions (what the customer experiences) and then into projects (what the business must build or change). For the publication signup endpoint, key actions include spending enough time on the site to feel comfortable and ensuring the signup is easy to locate. Those actions can translate into projects like improving mailing list signup UX or experimenting with where the signup button appears.

How does the template turn journey thinking into content planning?

Use cases create scenarios that generate keywords and content ideas. For example, “John” has a new year fitness resolution, which leads to content themes tied to athletic apparel. Keywords are researched using Keywords Everywhere for volume, difficulty, and cost per click, then converted into content items (articles) in the content database. Content appears in the content section once it’s assigned a date or status, making the brainstorming operational.

How are measurement and learning integrated into the journey map?

Surveys, sentiment, targets, and KPIs are stored in a dedicated database and linked to journey planning. After key moments like the first purchase, teams can run a feedback campaign and store survey results. Sentiment can be tracked at stages or even more granularly at key actions using selection properties (e.g., “comfortable” at the moment a user completes a signup). Targets connect business metrics—like signup counts—to specific journey stages and actions.

Review Questions

  1. When deciding whether to keep or change the template’s default journey stages, what criteria should determine the final stage order?
  2. Describe how a persona goal becomes an endpoint, then becomes key actions and projects. Use the Jessica example as a model.
  3. What information must be added to a content idea (e.g., an article) so it appears in the content section, and why does that matter for execution?

Key Points

  1. 1

    Use the template’s pre-filled stages only as a starting hypothesis, then reorder or rename stages to match the real conversion path (e.g., add purchase conversion after mailing-list signup).

  2. 2

    Build personas with goals and pain points, then link those directly to journey endpoints so messaging stays grounded in customer motivations.

  3. 3

    Translate endpoints into concrete key actions (what users do and feel), and convert those actions into projects (what the business changes or tests).

  4. 4

    Use use cases to generate keyword-driven content ideas, and research competitiveness with Keywords Everywhere before committing to topics.

  5. 5

    Assign dates or statuses to content items so they surface in the content database and become actionable planning tasks.

  6. 6

    Track sentiment and customer feedback through surveys and store results so the journey map improves with real data.

  7. 7

    Set explicit targets and KPIs tied to specific journey stages and actions to ensure the map supports measurable outcomes.

Highlights

Journey maps fail when they’re treated as static grids; the workflow emphasizes tracking details that are hard to predict and refining them over time.
In the athletic apparel example, the journey is reshaped around a likely path: mailing-list signup → purchase conversion → reconversion → referrals/affiliate behavior.
Persona-driven endpoints turn abstract marketing ideas into specific actions and projects, such as improving mailing list signup UX and testing signup button placement.
Use cases like “new year fitness resolution” feed keyword research and article planning, connecting journey moments to actual content production.
Surveys, sentiment, targets, and KPIs create a measurement loop so the journey keeps getting more accurate after customer feedback.

Topics