How the Enablement Hub Works
Understanding the information architecture—how Outcomes connect to showcases, guides, golden configs, playbooks, and the schema.
The Hub-of-Hubs Model
Everything in the Kaptio Enablement Hub serves Outcomes. An Outcome represents a business capability that customers want to achieve with Kaptio—like "Manage Booking Lifecycle" or "Establish Platform Foundation."
Think of Outcomes as the center of a wheel, with all other content types as spokes radiating outward. This design ensures that no matter where you enter the hub—whether exploring the data model, reading a guide, or deploying a golden config—you can always trace back to the business capability it serves.
Content Types Explained
Outcomes (The Center)
The primary organizing principle. Each Outcome includes product marketing, user journey, adoption roadmap, project plan, and links to all supporting materials.
Content for Learning
Guides
Step-by-step configuration instructions for complex setup processes. User and admin documentation.
Showcases
Feature marketing microsites that demonstrate capabilities interactively. For pre-sales and positioning.
Content for Configuring
Golden Configs
Pre-built configuration examples deployable to customer orgs. The "working software" that proves product-market fit.
Playbooks
Demo scripts and smoke tests for golden configs. Validates the happy path and provides alignment on "what good looks like."
Content for Reference
Schema Objects
Documentation of the Kaptio data model. Explains the structure that underpins Outcomes.
Open Schema Explorer →How Content Connects
All content links back to Outcomes using explicit relationship fields. These connections are bidirectional—when viewing an Outcome, you see all related content; when viewing a Guide, you see which Outcomes it supports.
| Relationship | Direction | Meaning |
|---|---|---|
| markets | Showcase → Outcome | This Showcase positions this Outcome |
| teaches | Guide → Outcome | This Guide explains how to implement |
| implements | Golden Config → Outcome | This config sets up part of this Outcome |
| validates | Playbook → Golden Config | This playbook demos/tests this config |
| underpins | Schema → Outcome | This object stores data for this Outcome |
| requires | Outcome → Outcome | This Outcome depends on another |
Navigation Patterns
Starting from an Outcome
If you know what capability you need:
- 1 Browse by layer (Core, Product Experience, Channel, Advanced)
- 2 Filter by product (Circle, Quest, Voyage)
- 3 Click into an Outcome to see all related content
Starting from Data
If you need to understand the data model:
- 1 Open the Schema Explorer
- 2 Browse objects by domain
- 3 See which Outcomes use each object
Starting from a Golden Config
If you're deploying configuration:
- 1 Find the golden config for your use case
- 2 Run the associated Playbook to validate
- 3 Navigate to the Outcome for broader context
Starting from a Playbook
If you're demoing or testing:
- 1 Find the Playbook for the feature
- 2 Ensure the golden config is deployed
- 3 Follow the demo script step by step
The Artifact Stack in Action
The content model follows a clear hierarchy that supports both pre-sales and delivery use cases:
Pre-Sales / Positioning
Outcomes → Showcases → Playbooks — demonstrate value and capabilities
Implementation
Golden Configs → Guides → Schema — deploy and configure solutions
Validation
Playbooks → Golden Configs — smoke test and validate deployments
Training
Guides → Playbooks — teach users how to operate the system
Continue Learning
Ready to Explore?
Browse outcomes by product solution, dependency order, or implementation phase.
Browse All Outcomes