Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Relationship types and engagement levels

  • Relationship history and current status

  • Value assessment (current and potential)

  • Risks and growth opportunities

  • Engagement models and management approaches

Implementation Guidelines

Getting Started

  1. Begin by identifying and documenting key customer segments

  2. Select a high-priority segment and develop a detailed persona

  3. Map the primary customer journey for this segment

  4. Link this journey to relevant capabilities and value streams

  5. Define performance metrics for measuring success

Best Practices

  • Ensure customer segments have clear, measurable differentiators

  • Base personas on actual customer research, not assumptions

  • Map customer journeys from the outside-in perspective

  • Connect customer attributes to organizational capabilities

  • Involve multiple departments in customer domain development

  • Regularly update customer model elements based on new insights

Common Pitfalls to Avoid

  • Creating too many segments or personas, diluting focus

  • Designing journeys based on internal processes rather than customer perspectives

  • Failing to connect customer elements to operational domains

  • Not updating customer models as markets and behaviors evolve

  • Focusing exclusively on transactional data rather than emotional aspects of customer experience

Schema Evolution Guidance

The Customer Domain schema is expected to evolve with emerging practices in customer experience management. Future extensions may include:

  • Enhanced digital behavior modeling

  • Emotion and sentiment tracking

  • Real-time personalization frameworks

  • Predictive customer analytics integration

  • Ecosystem journey mapping (beyond organizational boundaries)

  • Customer data ethics and governance

Organizations should plan for these evolutions by maintaining clean taxonomies and clear relationship models in their current implementation.

Example Implementation

Example: Retail Banking Customer Segment

...

Attribute

Description

Example

relationshipID

Unique identifier for this relationship

"REL-CUST-STRAT-002"

customerSegmentID

ID of the customer segment

"CUST-SEG-001"

title

Name of the strategy

"Affluent Client Growth Strategy"

strategicImportance

Strategic importance of this segment (1-5)

5

growthTarget

Growth target for this segment

"35% growth in assets under management by 2027"

strategicInitiatives

Initiatives targeting this segment

["Digital wealth platform", "Family office services"]

competitivePositioning

Competitive positioning for this segment

"Premium service with integrated banking and investment capabilities"

investmentPriority

Investment priority for this segment

"High - tier 1 strategic focus"

strategicThemes

Strategic themes relevant to segment

["Digital transformation", "Advisory excellence"]

strategicRisks

Strategic risks related to segment

"Emerging fintech competition targeting affluent professionals"

targetValueProposition

Strategic value proposition for segment

"Seamless integration of banking, investing, and advisory services"

futureStateVision

Vision for future relationship with segment

"Trusted primary financial partner for all wealth management needs"

Schema Evolution Guidance

The Customer Domain schema is expected to evolve with emerging practices in customer experience management. Future extensions may include:

  • Enhanced digital behavior modeling

  • Emotion and sentiment tracking

  • Real-time personalization frameworks

  • Predictive customer analytics integration

  • Ecosystem journey mapping (beyond organizational boundaries)

  • Customer data ethics and governance

Organizations should plan for these evolutions by maintaining clean taxonomies and clear relationship models in their current implementation.