📋 Content Guide
✅ Simplified Model
Outcome Template
Use this guide to create consistent, high-quality outcome content. The simplified model focuses on Features → Journey → Plan → Resources → Pitfalls.
🗺️ Outcome Page Structure
✨
Features
productMarketing
🗺️
Journey
userJourney
📋
Plan
projectPlan
📚
Resources
related* fields
⚠️
Pitfalls
pitfalls[]
⚡ Quick Reference
Required Fields
- • title
- • layer
- • description
- • userJourney (array)
Recommended Fields
- • icon (emoji)
- • personas (array)
- • productMarketing
- • projectPlan
- • pitfalls
Content Linking
- • relatedKB
- • relatedGuides
- • relatedTools
- • relatedSchema
- • relatedReports
- • goldenConfigs
🎯 Identity Fields
title
Display name of the outcome. Should be action-oriented.
title: "Know Your Customers" layer
Which platform layer this outcome belongs to.
core product-experience channel advanced
solution
For product-experience layer only. Which solution playbook this outcome belongs to.
🚢 voyage-cruise
🚂 voyage-trains
🎯 circle-sell
🏢 circle-dmc-operate
✨ quest-tailormade
🎒 quest-fit-package
complexity
Implementation complexity indicator.
simple standard complex configurable
personas
Which user personas are impacted by this outcome.
product-manager reservation-consultant operations-coordinator revenue-manager finance-admin system-admin sales-agent
requires
Dependencies on other outcomes (simple string array).
requires: ["establish-platform-foundation", "build-service-catalog"] ✨ Product Marketing
productMarketing
Marketing-focused content describing features and benefits. This populates the "Features" section on the outcome page.
productMarketing:
headline: "Know Every Customer Before They Ask"
introduction: "Build complete customer profiles that enable personalized service..."
features:
- title: "Smart Customer Search"
description: "Find existing customers in seconds with fuzzy matching."
benefits:
- "80% faster customer lookup"
- "Prevent duplicate accounts"
icon: "🔍"
- title: "Flexible Account Types"
description: "Support B2C direct customers and B2B trade partners."
benefits:
- "Single source of truth"
- "Clear segmentation"
icon: "🏢" 🗺️ User Journey
userJourney (required)
Step-by-step flow showing how users accomplish this outcome. This is a required field.
userJourney:
- step: 1
actor: "Customer"
action: "Enquires about a trip"
system: "Phone/Email/Web"
notes: "Initial contact point"
value: "Capture every opportunity"
- step: 2
actor: "Sales Agent"
persona: "reservation-consultant"
action: "Searches for existing customer"
system: "Kaptio"
value: "Prevents duplicate accounts"
- step: 3
actor: "System"
action: "Returns match or no-match"
system: "Kaptio"
notes: "Fuzzy matching on email, phone, name" 📋 Project Plan
projectPlan
Implementation plan with phases, tasks, and risks. This populates the "Plan" section.
projectPlan:
estimatedDuration: "2-3 weeks"
complexity: "medium" # low | medium | high
prerequisites:
- "Salesforce org provisioned"
- "Kaptio package installed"
phases:
- name: "Discovery"
duration: "2-3 days"
owner: "Consultant + Client Admin"
tasks:
- task: "Document Business Unit requirements"
type: "prerequisite"
- task: "Define Sales Channel structure"
type: "config"
deliverables:
- "Foundation Design Document"
- name: "Configuration"
duration: "3-5 days"
owner: "System Admin"
tasks:
- task: "Create Business Units"
type: "config"
- task: "Configure Sales Channels"
type: "config"
risks:
- risk: "Over-complicating channels"
mitigation: "Start with go-live channels only"
successCriteria:
- "All Business Units configured"
- "Test booking per channel complete" 📚 Resources & Content Linking
Content Hub Connections
Link this outcome to related content across the enablement hub. These fields connect to other content collections.
🛠️ Golden Configs
Deployable configuration examples
goldenConfigs 🔧 Tools
External applications that assist
relatedTools 📖 Knowledge Base
Troubleshooting guides and FAQs
relatedKB 📚 Guides
Step-by-step configuration guides
relatedGuides 🗂️ Schema
Salesforce object API names
relatedSchema 📊 Reports
Deployable Salesforce reports
relatedReports # Golden Configs (defined inline)
goldenConfigs:
- id: "foundation-single-entity"
title: "Single-Entity Foundation"
description: "Complete setup for a single-brand operator"
- id: "foundation-multi-region"
title: "Multi-Region Foundation"
description: "Foundation for operators across multiple regions"
# Related content (by slug/id)
relatedKB:
- business-unit-configuration
- sales-channel-setup
relatedGuides:
- currency-fx-configuration
relatedTools:
- gold-org-configurator
- core-health
- schema-explorer
relatedSchema:
- KaptioTravel__BusinessUnit__c
- KaptioTravel__SalesChannel__c
- KaptioTravel__Currency__c
relatedReports:
- foundation-health-check ⚠️ Pitfalls
pitfalls
Common mistakes and things to avoid. Simple array of strings.
pitfalls: - "Starting too simple when M&A is on the horizon" - "Mixing legal entity with Business Unit decisions" - "Over-complicating channels—start with go-live only" - "Skipping tax profile validation" - "Not testing currency conversion end-to-end"
📄 Starter Template
new-outcome.mdx
---
title: "Your Outcome Title"
layer: "core" # core | product-experience | channel | advanced
solution: "circle-sell" # Only for product-experience layer
complexity: "standard" # simple | standard | complex | configurable
personas:
- product-manager
- reservation-consultant
requires:
- establish-platform-foundation
description: "One-sentence description of what this outcome enables."
icon: "📦"
# ═══════════════════════════════════════════════════════════════
# THE VISION: Features & Journey
# ═══════════════════════════════════════════════════════════════
productMarketing:
headline: "Compelling Marketing Headline"
introduction: "Two to three sentences explaining the value proposition."
features:
- title: "Feature Name"
description: "What this feature does and why it matters."
benefits:
- "Specific benefit with metric if possible"
icon: "✨"
userJourney:
- step: 1
actor: "Actor Name"
persona: "persona-id"
action: "What they do"
system: "Where they do it"
notes: "Additional context"
value: "Why this step matters"
- step: 2
actor: "System"
action: "Automated action"
system: "Kaptio"
# ═══════════════════════════════════════════════════════════════
# THE PATH: Implementation Plan
# ═══════════════════════════════════════════════════════════════
projectPlan:
estimatedDuration: "2-3 weeks"
complexity: "medium"
prerequisites:
- "Kaptio package installed"
phases:
- name: "Discovery"
duration: "2-3 days"
owner: "Consultant"
tasks:
- task: "Task description"
type: "prerequisite"
deliverables:
- "Design Document"
- name: "Configuration"
duration: "3-5 days"
owner: "Admin"
tasks:
- task: "Configuration task"
type: "config"
risks:
- risk: "Risk description"
mitigation: "How to mitigate"
successCriteria:
- "Definition of done"
# ═══════════════════════════════════════════════════════════════
# RESOURCES: Related Content
# ═══════════════════════════════════════════════════════════════
goldenConfigs:
- id: "config-id"
title: "Configuration Title"
description: "What this configuration demonstrates"
relatedKB:
- article-slug
relatedGuides:
- guide-slug
relatedTools:
- tool-id
relatedSchema:
- KaptioTravel__Object__c
relatedReports:
- report-id
# ═══════════════════════════════════════════════════════════════
# PITFALLS
# ═══════════════════════════════════════════════════════════════
pitfalls:
- "Common mistake to avoid"
- "Another pitfall"
---
## Additional Content
Add any MDX content here. This appears in the Resources section.
💡 Live Example
See the "Establish Platform Foundation" outcome for a complete working example of this template structure.
View Example →