Building a Customer Journey Inventory for Your Journey Portfolio
This skill teaches you how to systematically catalog every customer journey in your organization into a single, structured portfolio that becomes the foundation for ecosystem-level analysis, prioritization, and cross-journey optimization.
Start by gathering existing journey maps, process documents, and stakeholder knowledge from every department. Catalog each journey with a consistent set of attributes: name, owner, lifecycle stage, persona, channels, and current maturity. Organize entries into a centralized registry, assign hierarchy levels, and validate completeness through cross-functional review. The finished inventory becomes your single source of truth for journey management.
Outcome: You produce a comprehensive, structured registry of every customer journey in your organization, complete with ownership, hierarchy levels, and metadata, enabling you to identify gaps, overlaps, and prioritization opportunities at the ecosystem level.
Prerequisites
- Basic understanding of customer journey mapping concepts
- Familiarity with customer lifecycle stages (awareness, acquisition, onboarding, retention, advocacy)
- Access to existing journey maps, service blueprints, or process documentation across departments
- Stakeholder relationships across at least 3 functional teams (marketing, product, support, sales)
Overview
A customer journey inventory is the foundational artifact of the Ecosystem Journey Framework. It is a comprehensive catalog of every journey a customer takes with your organization, structured with consistent metadata so you can analyze, compare, and manage journeys as a connected portfolio rather than isolated maps. Without this inventory, teams operate with fragmented visibility. Marketing knows about the acquisition journey, support knows about the escalation journey, and product knows about the onboarding journey, but nobody holds the full picture. The inventory closes that gap by collecting all journeys into one place with a shared vocabulary and structure.
The specific artifact you produce is a centralized registry, typically a structured spreadsheet, database, or journey management platform, where each row represents a distinct journey and each column captures a standardized attribute. These attributes include the journey name, a brief description, the owning team, the customer persona it serves, the lifecycle stage it belongs to, the channels involved, the current documentation maturity (undocumented, mapped, measured, managed), and the hierarchy level (L0 through L3) as defined in the Ecosystem Journey Framework. A well-built inventory for a mid-size SaaS company typically contains 40 to 120 distinct journeys. An enterprise with multiple product lines may catalog 200 or more.
The value of the inventory goes beyond documentation. It is the input for nearly every downstream activity in journey management: prioritizing journeys for optimization, aligning teams around journey ownership, and identifying cross-journey insights. If the inventory is incomplete or inconsistently structured, every downstream decision inherits those gaps. Success looks like a registry that is comprehensive enough that no stakeholder can name a journey that is missing, structured enough that any entry can be compared to any other, and maintained enough that it stays current as journeys evolve. The inventory is never truly finished. It is a living document that grows and refines over time, but the initial build is the critical first step.
How It Works
The core principle behind a customer journey inventory is that you cannot manage what you have not cataloged. Most organizations have journey knowledge scattered across Miro boards, Figma files, PowerPoint decks, Confluence pages, and the heads of individual employees. Some of this knowledge is documented. Much of it is tribal. The inventory process works by systematically extracting this distributed knowledge, normalizing it into a consistent structure, and surfacing the gaps nobody knew existed.
The inventory uses a flat registry structure rather than a hierarchical tree for the initial capture. This is deliberate. Hierarchy (L0 through L3 levels) is applied after capture, not during it. If you try to organize journeys into a hierarchy while you are still discovering them, you introduce premature structure that causes people to filter their contributions. They think, "This journey doesn't fit neatly into the hierarchy, so maybe it's not a real journey." By collecting everything flat first, you capture edge cases, unofficial workarounds, and shadow journeys that often represent the biggest experience gaps.
Each journey entry uses a standardized attribute schema. The schema serves two purposes. First, it forces specificity. A journey called "onboarding" is too vague. When you require the persona, lifecycle stage, and channels, that vague label becomes "new enterprise customer onboarding via CSM-led implementation," which is distinct from "self-serve trial user onboarding via in-app guides." Second, the schema enables comparison. When every journey has a documented owner, maturity level, and lifecycle stage, you can instantly see that your retention stage has 15 journeys with 3 owners while your advocacy stage has 2 journeys with zero owners.
The process works in three phases. Phase one is divergent collection, where you cast the widest possible net through document audits, stakeholder interviews, and workshop exercises. Phase two is convergence and deduplication, where you merge overlapping entries, split entries that are actually multiple journeys, and fill in missing attributes. Phase three is validation and hierarchy assignment, where cross-functional reviewers confirm completeness and you layer on the L0 through L3 structure from the Ecosystem Journey Framework. The reason validation must be cross-functional is that no single team sees more than 30 to 40 percent of all customer journeys. Marketing sees acquisition. Product sees usage. Support sees failure. Only the combined view reveals the full portfolio.
A common question is how granular to go. The answer depends on your hierarchy levels. L0 is the entire customer lifecycle. L1 represents major phases (acquisition, onboarding, usage, renewal). L2 captures distinct journeys within a phase (trial signup, demo request, organic content discovery). L3 breaks a journey into specific scenarios or variants (trial signup via mobile, trial signup via desktop with SSO). For the initial inventory, aim to capture L1 and L2 comprehensively. L3 detail can be added later as you prioritize specific journeys for deeper analysis.
Step-by-Step
Step 1: Audit existing journey documentation
Before talking to anyone, gather every existing journey map, service blueprint, process flow, and customer experience document you can find. Search shared drives, Confluence spaces, Miro boards, Figma files, and presentation archives. Check with CX, UX, product, marketing, sales, and support teams. Create a simple log of what you find: document name, format, date created, author, and which journey it describes.
Many organizations discover they have 5 to 15 existing journey artifacts scattered across teams, some current, many outdated. This audit gives you a starting inventory of documented journeys and, equally important, reveals which teams have journey mapping habits and which do not. The absence of documentation from a team is a signal that their journeys are undocumented, not that they do not exist.
Tip: Search for common file names like 'customer journey,' 'user flow,' 'service blueprint,' 'experience map,' and 'process flow.' Also search for persona names and lifecycle stage terms. Documentation often lives under unexpected labels.
Step 2: Define your inventory attribute schema
Before you start collecting journey entries, define the exact attributes you will capture for each one. A strong starting schema includes: journey ID (a unique identifier), journey name, brief description (1-2 sentences), customer persona, lifecycle stage, primary channels involved, journey owner (person or team), documentation status (undocumented, sketched, fully mapped, measured, managed), business impact estimate (high, medium, low), and a notes field. Write a short definition for each attribute so contributors interpret them consistently. For example, define exactly what your lifecycle stages are and provide examples.
' This schema is your data contract. Every journey entry must conform to it. Resist the temptation to add too many attributes initially. Eight to twelve attributes is the sweet spot.
You can always add columns later, but asking for 25 fields up front will slow collection to a halt.
Tip: Create a one-page 'schema cheat sheet' with each attribute, its definition, and two example entries. Distribute this to every contributor before they start adding journeys. Misaligned definitions are the number one cause of inconsistent inventories.
Step 3: Conduct stakeholder collection workshops
Run 60-minute workshops with each major functional team to extract their journey knowledge. ' Capture each journey on a sticky note or spreadsheet row with just the name and a brief description. Do not try to fill in all attributes during the workshop. Focus on breadth.
A marketing team might surface 8 to 12 journeys (organic discovery, paid acquisition, webinar registration, content download, referral). A support team might surface 6 to 10 (ticket submission, escalation, knowledge base self-service, proactive outreach). Keep the energy divergent. When someone says 'I think that's the same as what James mentioned,' note it but do not merge yet.
Deduplication happens in a later step. Run separate workshops rather than one giant session so that quieter teams are not overshadowed by more vocal ones.
Tip: Ask each participant to write down their journeys silently for 5 minutes before any group discussion. This prevents anchoring, where the first person to speak defines the frame and others only add incremental variations.
Step 4: Mine quantitative sources for hidden journeys
Workshops capture journeys that people think about consciously. But many journeys exist in behavioral data that nobody has named. Pull analytics data from your website, app, CRM, and support systems. Look for distinct behavioral sequences: what are the top 10 paths users take through your product?
What are the top 5 reasons customers contact support? What are the most common sequences in your CRM pipeline stages? Each distinct pattern may represent a journey that was not surfaced in workshops. For example, analytics might reveal that 15 percent of trial users follow a path nobody mentioned: they sign up, import data, hit an error, search the knowledge base, find nothing, and abandon.
That is a real journey with real business impact, but no team 'owns' it because it spans product, documentation, and support. Add these data-derived journeys to your inventory with a flag indicating they were identified through behavioral data rather than stakeholder input.
Tip: Pay special attention to failure paths and abandonment sequences. Teams naturally think about the happy path journeys they designed. The journeys customers actually take when things go wrong are often the most impactful to optimize.
Step 5: Deduplicate and normalize entries
You now have a raw list from document audits, workshops, and data mining. This list will contain duplicates, overlaps, and inconsistent granularity. Go through the full list and identify entries that describe the same journey using different names. Marketing's 'lead nurture flow' and sales' 'prospect warming sequence' may be the same journey seen from different angles.
Merge true duplicates into single entries, noting all original names as aliases. Next, check granularity. Some entries will be too broad ('the customer experience') and need to be split. Others will be too narrow ('clicking the pricing page CTA') and need to be rolled up into a parent journey.
Apply your lifecycle stages as a sorting mechanism. Group all entries by stage and look for gaps. If you have 20 entries under acquisition and 2 under advocacy, either your advocacy journeys are genuinely sparse or you have a collection gap to investigate. Normalize all entries to your attribute schema, filling in every field.
For attributes you cannot determine yet, mark them as 'TBD' rather than leaving them blank.
Tip: Create an aliases column in your inventory. When you merge duplicates, record all the original names. This helps future contributors find existing entries instead of creating new duplicates, and it preserves the vocabulary each team uses naturally.
Step 6: Assign hierarchy levels (L0-L3)
With a clean, deduplicated list, you can now layer on the hierarchy structure from the Ecosystem Journey Framework. Start at L0, which is the entire customer lifecycle from first awareness to advocacy or churn. Your L1 journeys are the major phases: awareness, acquisition, onboarding, usage, retention, expansion, and advocacy. These should already align with your lifecycle stages.
L2 journeys are the distinct experiences within each phase. ' For the initial inventory, ensure every entry has an L1 and L2 classification. L3 detail can be added selectively for high-priority journeys. Add a 'hierarchy level' column to your schema and tag each entry.
Verify that every L1 phase has at least 3 L2 journeys. Fewer than that suggests incomplete collection.
Tip: Do not force every journey into a single L1 phase. Some journeys genuinely span multiple phases. For example, a 'proactive health check' journey might span usage and retention. Tag it with its primary phase and note the secondary phase in your notes column.
Step 7: Validate through cross-functional review
Share the complete inventory with representatives from every team that contributed, plus at least two teams that did not participate in workshops (finance, legal, and partnerships are commonly overlooked). Ask each reviewer three specific questions. First, is any journey your team touches missing from this list? Second, are any entries inaccurately described or attributed?
Third, do the ownership assignments reflect reality? Give reviewers one week to respond. Track their additions and corrections in a changelog. This review typically surfaces 10 to 20 percent more journeys, mostly in areas like billing, compliance, partner channels, and internal handoff processes.
It also catches ownership disputes, where two teams both claim (or both deny) ownership of a journey. Document these disputes rather than resolving them in this step. Ownership alignment is a separate skill. After incorporating reviewer feedback, circulate the updated inventory one more time for final confirmation.
Tip: Frame the review as 'help us find what is missing' rather than 'approve this list.' The first framing activates constructive thinking. The second framing leads to quick rubber-stamping with no real scrutiny.
Step 8: Establish a maintenance cadence
An inventory that is not maintained becomes stale within one quarter. Define who owns the inventory as a living document. This is typically a CX program manager, journey management lead, or the person coordinating the Ecosystem Journey Framework initiative. Set a quarterly review cycle where the owner checks for new journeys (launched products, new channels, organizational changes), retired journeys (deprecated features, sunset products), and attribute updates (ownership changes, maturity improvements).
Create a simple intake process so any team member can submit a new journey for inclusion. ' Tag each inventory entry with a 'last reviewed' date so you can identify stale entries. Any entry not reviewed in 6 months should be flagged for attention. The quarterly review should take 2 to 4 hours for a portfolio of 50 to 100 journeys once the initial build is complete.
Tip: Tie the inventory review to an existing organizational rhythm, like quarterly business reviews or planning cycles. Standalone review meetings get deprioritized and skipped. Piggybacking on established meetings ensures consistency.
Examples
Example: B2B SaaS company with 200 employees
A project management SaaS company serving mid-market and enterprise customers has 6 product teams, a 20-person customer success organization, and journey maps scattered across Miro, Figma, and Google Slides. They have never consolidated their journey knowledge. Their goal is to build a customer journey inventory that supports a new CX governance initiative launching next quarter.
The CX lead starts with a document audit and finds 11 existing journey maps: 4 from product (onboarding flows), 3 from marketing (acquisition funnels), 2 from support (escalation processes), and 2 from customer success (renewal and expansion). She defines a 10-attribute schema and creates a shared Google Sheet. She runs 6 workshops, one per department, over two weeks. The workshops surface 67 unique journey entries.
She then pulls data from Mixpanel (product analytics), Zendesk (support tickets), and Salesforce (sales pipeline) and identifies 14 additional journeys that nobody mentioned, including a significant 'failed data import' journey affecting 22 percent of new accounts. After deduplication, she has 58 distinct journeys. She assigns hierarchy levels: 1 L0 (full lifecycle), 6 L1 phases, 42 L2 journeys, and 9 L3 variants for high-priority areas. Cross-functional review adds 7 more journeys from finance (billing disputes, invoice management) and partnerships (co-sell handoff).
The final inventory contains 65 journeys. She assigns provisional owners to all entries and schedules quarterly reviews aligned with the company's existing QBR cadence. The inventory immediately reveals that the 'expansion' lifecycle stage has only 3 documented journeys with no clear owner, flagging it as the top priority for the CX governance initiative.
Example: Small B2C e-commerce brand
A direct-to-consumer skincare brand with 30 employees sells through their website, Amazon, and retail partners. They have one UX designer who has created a few journey maps for the website checkout flow. They want to understand the full customer experience across all channels to reduce churn and increase repeat purchases.
The UX designer defines a simplified 8-attribute schema and creates an Airtable base as the inventory. She runs three informal interviews rather than formal workshops: one with the marketing manager, one with the customer service lead, and one with the operations manager who handles Amazon and retail. These conversations surface 28 journey entries spanning online discovery, social media engagement, first purchase, subscription management, returns, and loyalty program participation. She pulls Google Analytics data to identify behavioral paths and discovers that 18 percent of first-time buyers follow a journey through Instagram to the website to an abandoned cart to a retargeting email to a purchase, a 5-step journey nobody had named.
She also mines Gorgias (support platform) and finds 4 distinct support journeys including an 'allergy concern' journey that has high emotional stakes but zero documentation. After deduplication, the inventory contains 31 journeys across 5 L1 phases. The inventory reveals that the brand has 12 acquisition journeys but only 2 retention journeys, explaining why customer lifetime value has been flat. The founder uses this insight to shift budget from acquisition campaigns toward retention journey development.
Example: Enterprise financial services firm
A bank with 5,000 employees and multiple business lines (retail banking, wealth management, commercial lending, insurance) has dozens of journey maps created by different divisions over the past 4 years. There is no central repository, no shared terminology, and no cross-divisional visibility. The Chief Customer Officer wants a unified inventory to support a digital transformation initiative.
The CCO assigns a team of 3 to the inventory project. They start with a document audit that takes two full weeks and surfaces 47 existing journey maps across 8 divisions, stored in SharePoint, Confluence, PowerPoint, and Visio. They define a 12-attribute schema that includes regulatory classification (a requirement in financial services) and build the inventory in a journey management platform (TheyDo). They run 12 workshops with 14 teams over 4 weeks.
Each workshop is 90 minutes and follows the silent-writing-first protocol. The workshops generate 189 raw journey entries. Data mining from the core banking platform, CRM, call center analytics, and digital banking app adds 31 more entries, including several cross-division handoff journeys (like when a retail customer qualifies for wealth management services). Deduplication is the most labor-intensive step, taking a full week, because different divisions use different terminology for similar journeys.
After normalization, the inventory contains 142 distinct journeys: 1 L0, 8 L1 phases, 98 L2 journeys, and 35 L3 variants. Cross-functional review with compliance and legal adds 9 regulatory journeys that were not surfaced in any workshop. The final inventory of 151 journeys reveals that 23 journeys span multiple business lines but have no cross-divisional owner, directly informing the digital transformation roadmap and the creation of 4 new cross-functional journey teams.
Example: Early-stage SaaS startup
A 12-person startup building an AI writing assistant has no formal journey maps. The CEO and head of product have the customer experience in their heads but have never documented it. They are preparing for a Series A and want to demonstrate CX maturity to investors.
The head of product blocks a single afternoon for the inventory. She creates a simple Google Sheet with 8 columns: journey name, description, persona, lifecycle stage, channels, owner, documentation status, and notes. She sits with the CEO for 45 minutes and they brainstorm every customer interaction they can think of, writing each on a separate row. They identify 22 journeys spanning awareness (content marketing discovery, Product Hunt launch, word of mouth referral), trial (signup, first document creation, template exploration), conversion (upgrade prompt, pricing page evaluation, team invite), and post-purchase (feature adoption, support request, feedback submission, cancellation).
She then spends an hour reviewing Intercom conversations and Mixpanel funnels to surface 6 more journeys, including an 'API integration' journey that 15 percent of users follow but nobody on the team had mentioned. After a quick pass to fill in all attributes, the inventory contains 28 journeys. Every entry is marked as 'undocumented' or 'sketched' because no formal maps exist. The inventory immediately shows that 19 of 28 journeys have no clear owner beyond 'the whole team,' which becomes a concrete talking point for hiring priorities.
The head of product uses the inventory to prioritize 5 journeys for detailed mapping before the Series A pitch, demonstrating to investors that the company understands its customer experience at a systemic level.
Best Practices
Use a consistent naming convention for journey names that includes the persona and the action, such as 'Enterprise Buyer: Evaluating Pricing Options' rather than just 'Pricing Journey.' Consistent naming prevents duplicates and makes the inventory scannable. Without a naming convention, you will end up with 'Onboarding,' 'New User Onboarding,' 'Customer Onboarding Flow,' and 'Getting Started Experience' as four separate entries for the same journey.
Capture journey entries at L2 granularity during initial collection and resist the urge to go deeper until you have validated the full portfolio. Going to L3 detail too early creates an inventory so large that it becomes unmanageable, and you end up spending weeks documenting micro-variations of low-priority journeys while major gaps in high-impact areas remain undiscovered.
Separate the collection phase from the evaluation phase. When gathering journeys from stakeholders, do not simultaneously ask them to rate importance, assign scores, or debate whether something qualifies as a 'real' journey. Evaluation during collection causes self-censorship, where contributors filter out journeys they assume are unimportant. Collect everything first.
Evaluate after the inventory is complete.
Include internal handoff journeys, not just customer-facing ones. The journey from 'sales closes deal' to 'CSM begins onboarding' is invisible to the customer but profoundly affects their experience. These internal transitions are where most journey friction hides, and they are almost never captured unless you explicitly ask for them.
Document the 'documentation status' attribute honestly. If a journey has never been mapped, mark it as undocumented. If it was mapped two years ago and never updated, mark it as stale. Inflating maturity levels creates false confidence and causes teams to skip journeys that desperately need attention. The inventory should reveal gaps, not hide them.
Store the inventory in a tool that supports filtering, sorting, and shared access. A static PDF or slide deck cannot function as a working inventory. Use a shared spreadsheet at minimum, or a journey management platform if available. The inventory must be queryable. Stakeholders should be able to filter by lifecycle stage, by owner, or by maturity level and instantly see the relevant subset.
Assign a provisional owner to every journey entry, even if ownership is disputed or unclear. Unowned journeys are invisible journeys. Assigning a provisional owner creates accountability for follow-up, even if the final ownership decision happens later through the team alignment process.
Common Mistakes
Treating the inventory as a one-time project rather than a living document
Correction
Organizations often invest significant effort in the initial build and then let the inventory rot. New products launch, channels are added, and teams reorganize, but nobody updates the registry. Within two quarters, the inventory no longer reflects reality and teams stop trusting it. The fix is to assign a single owner, set a quarterly review cadence, and create a lightweight intake process for new journey submissions.
Tie the review to an existing meeting rhythm so it does not get deprioritized.
Collecting journeys from only one or two departments
Correction
This is the most common structural failure. If you only talk to marketing and product, you will miss support journeys, billing journeys, partner-mediated journeys, and compliance-related journeys. The result is an inventory that covers 40 percent of the actual portfolio and creates blind spots in every downstream analysis. The signal to watch for is a lifecycle stage with fewer than 3 L2 journeys.
That almost always means incomplete collection rather than a genuinely sparse stage. Fix it by running collection workshops with every customer-touching team, including teams you might not initially consider like finance, legal, and operations.
Making the attribute schema too complex for initial collection
Correction
' This level of detail is valuable eventually but devastating during initial collection. Contributors face a 30-minute task per journey entry and either give up or fill fields with guesses. Start with 8 to 12 core attributes. You can always add enrichment columns after the initial inventory is validated.
Watch for the signal of incomplete rows. If more than 30 percent of entries have blank fields, your schema is too demanding for this stage.
Merging journeys too aggressively during deduplication
Correction
In the push to create a clean inventory, teams sometimes merge entries that share a name but serve different personas or channels. 'Onboarding' for a self-serve user and 'onboarding' for an enterprise customer with a dedicated CSM are fundamentally different journeys with different touchpoints, pain points, and owners. Merging them into a single 'onboarding' entry destroys the specificity that makes the inventory useful. Before merging, verify that the persona, lifecycle stage, and primary channels are identical.
If any of those differ, keep the entries separate and differentiate them with more specific names.
Skipping the data-mining step and relying only on stakeholder interviews
Correction
Stakeholders describe journeys they designed and journeys they know about. They rarely describe failure paths, workaround journeys, or emergent behaviors that nobody planned. These unintended journeys often represent the biggest experience gaps and the highest-impact optimization opportunities. If your inventory contains only 'happy path' journeys with clean flows and clear owners, you have likely missed the messy reality of how customers actually behave.
Supplement stakeholder input with behavioral data from analytics, support tickets, and CRM sequences to surface these hidden journeys.
Assigning hierarchy levels before completing the full collection
Correction
When you try to organize journeys into L0-L3 levels while still collecting them, contributors start self-filtering. They think a journey is 'too small' for L2 or 'too vague' for L3 and leave it out. Premature hierarchy also creates anchoring, where people only think of journeys that fit the categories already defined. Collect flat first.
Add hierarchy after you have a complete, deduplicated list. This ensures you capture everything before imposing structure.
Other Skills in This Method
Prioritizing Journeys for Optimization
How to assess and rank journeys by business impact, customer friction, and strategic alignment to decide where to focus improvement efforts.
Transitioning from Journey Mapping to Journey Management
How to evolve static journey maps into a dynamic, continuously managed journey management practice across teams.
Aligning Teams Around Journey Ownership
How to assign cross-functional ownership of journeys at each hierarchy level and establish governance for ongoing journey management.
Structuring Journey Hierarchy Levels (L0-L3)
How to define and organize customer journeys into hierarchical levels from macro (L0) to micro (L3) for scalable journey management.
Identifying Cross-Journey Insights and Patterns
Techniques for analyzing interconnected journeys to surface systemic pain points, redundancies, and optimization opportunities across the ecosystem.
Mapping Touchpoint Interconnections Across Journeys
How to visualize and document the relationships between touchpoints, channels, and journeys to create a holistic ecosystem view.
Frequently Asked Questions
How many journeys should a typical customer journey inventory contain?
The number varies significantly by organization size and complexity. A startup typically catalogs 20 to 40 journeys. A mid-size company with multiple products usually has 50 to 120 journeys. Large enterprises with multiple business lines may have 150 to 300 or more. If your inventory has fewer than 15 entries, you almost certainly have collection gaps. If it exceeds 300, consider whether you have gone too granular at the L3 level and should roll some entries up to L2.
Should I build the customer journey inventory before or after creating individual journey maps?
Build the inventory first. The inventory tells you which journeys exist across the organization and helps you prioritize which ones to map in detail. Mapping individual journeys before building the inventory is like writing chapters of a book before creating the table of contents. You will produce useful artifacts, but you will miss gaps, duplications, and dependencies that only the portfolio view reveals. Existing maps feed into the inventory as inputs, but the inventory itself should come before any new mapping effort.
How do I handle journeys that span multiple departments or lifecycle stages?
This is common and expected. Assign each journey a primary lifecycle stage and a primary owner, then use a secondary stage field and a notes column to capture the cross-cutting nature. For example, an 'enterprise renewal' journey primarily belongs to the retention stage and is owned by customer success, but it involves finance (invoicing), legal (contract terms), and sales (upsell opportunity). Document all involved teams in the entry. These cross-cutting journeys are often the most valuable to optimize because their friction comes from handoff failures between teams.
What tool should I use to store the customer journey inventory?
Start with the simplest tool your team will actually use. A shared Google Sheet or Airtable base works well for inventories under 100 entries. For larger portfolios or organizations that need role-based access, filtering, and visualization, dedicated journey management platforms like TheyDo, Milkymap, or Custellence are purpose-built for this. The critical requirement is that the tool supports filtering by any attribute, shared access for all stakeholders, and easy editing. A static document like a PDF or slide deck will fail because it cannot be queried or collaboratively maintained.
How long should building a customer journey inventory take?
The initial build typically takes 4 to 8 hours of focused work for a small organization (under 50 employees) and 2 to 4 weeks of elapsed time for a large enterprise where you need to coordinate workshops across many teams and wait for review feedback. The document audit takes 2 to 4 hours. Each stakeholder workshop takes 60 to 90 minutes. Deduplication and normalization take 2 to 6 hours depending on how many raw entries you collected. Cross-functional review adds 1 to 2 weeks of elapsed time. Do not let the timeline expand beyond a month for the initial build, or momentum dies.
How do I keep the inventory from becoming stale after the initial build?
Assign a single owner who is accountable for the inventory's accuracy. Set a quarterly review cycle tied to an existing organizational meeting like a QBR or planning session. Create a lightweight intake mechanism, such as a Slack channel or a simple form, where anyone can submit new journeys for addition. Tag every entry with a 'last reviewed' date and flag entries older than 6 months for re-review. The quarterly maintenance pass should take 2 to 4 hours for a portfolio of 50 to 100 journeys. Treat the inventory like a product backlog, something that is continuously groomed, not a report that is published and archived.
Why does my customer journey inventory keep growing uncontrollably?
Uncontrolled growth usually means you are cataloging at too fine a granularity, mixing L3 micro-variants with L2 journeys. Check whether your entries represent genuinely distinct experiences or just minor variations of the same journey. If 'signup via Google SSO' and 'signup via email' have the same touchpoints, owner, and pain points, they are L3 variants of the same L2 journey and should be consolidated. Apply the rule: if two entries would have the same journey map structure with only minor channel or input differences, they belong as variants under a single L2 entry, not as separate inventory rows. Periodically review your inventory and roll up entries that have drifted into excessive detail.