journey-orchestration
Orchestrate the post-sale customer journey across onboarding, adoption, renewal, and expansion so experiences feel intentional rather than fragmented. Use when connecting CS, Support, Product, and Marketing touchpoints into coherent lifecycle journeys.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- journey-orchestration
- description
- Orchestrate the post-sale customer journey across onboarding, adoption, renewal, and expansion so experiences feel intentional rather than fragmented. Use when connecting CS, Support, Product, and Marketing touchpoints into coherent lifecycle journeys.
03 SKILL.md 正文
Journey Orchestration (Post-Sale)
Overview
Journey orchestration aligns timing, channels, and owners across the customer lifecycle so each stage prepares the next — without conflicting messages or gaps.
When to Use
- Mapping the full post-sale journey
- Reducing handoff gaps between teams
- Designing stage transitions (onboarding → adoption → renew)
- Unifying digital and human touchpoints
Core Practices
- Define stages, entry/exit criteria, and success metrics
- Map touchpoints by stage, channel, and owner
- Remove duplicate or conflicting outreach
- Trigger stage transitions from signals (not only time)
- Align content and plays to stage goals
- Measure stage conversion and drop-off reasons
Principles
- The customer experiences one journey; org charts are invisible to them
- Time-based journeys underperform signal-based ones
- Orchestration requires shared data and definitions
- Less coordinated noise often beats more activity
Verification
- [ ] Stages and criteria are documented
- [ ] Owners exist for each major touchpoint class
- [ ] Drop-offs between stages are measured
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.