Framework

Service Design

A comprehensive view of service design maturity across 10 domains, drawing on IDEO, Service Design Network, Fjord, Gov.uk Service Manual, ISO 23592.

Each domain includes assessment questions mapping to five maturity levels, along with key strategy elements.

Maturity Scale

1
Initial

Ad hoc and reactive. No formal processes, reliant on individual effort.

2
Developing

Basic awareness and some repeatable processes emerging.

3
Defined

Documented standards and processes applied consistently.

4
Managed

Measured, monitored and controlled with quantitative targets.

5
Optimizing

Continuous improvement driven by data and innovation.

πŸ“

Service Blueprinting

Service Design Network, This is Service Design Doing

Mapping front-stage and back-stage service interactions, visualizing end-to-end processes, support actions, and physical evidence to reveal dependencies and improvement opportunities.

Strategy Elements

Service Blueprint Standards and Templates
Front-Stage / Back-Stage Interaction Mapping
Support Process and System Dependency Documentation
Physical Evidence and Touchpoint Inventory
Fail Point and Wait Point Identification Process
Blueprint Governance and Update Cadence
Integration with Service Design Tooling and Repositories

Assessment Questions

1. How does your organization use service blueprints to visualize service delivery?

L1No service blueprints exist; service processes are undocumented
L2Some informal process diagrams exist but do not distinguish front-stage from back-stage
L3Service blueprints are created for key services showing customer actions, front-stage, back-stage, and support processes
L4Blueprints are actively maintained, linked to operational metrics, and used to drive improvement initiatives
L5Living blueprints are continuously updated with real-time data, integrated into design tools, and inform strategic service evolution

2. How well are front-stage and back-stage dependencies mapped and managed?

L1Dependencies between customer-facing and internal processes are unknown
L2Some awareness of dependencies exists but they are not formally documented
L3Key dependencies are mapped and documented with clear ownership for each layer
L4Dependencies are actively monitored with alerts when back-stage failures impact front-stage experience
L5Predictive modeling identifies dependency risks before they impact customers, enabling proactive resolution

3. How are service blueprints used to identify and eliminate pain points in service delivery?

L1Pain points are only discovered through customer complaints after the fact
L2Ad-hoc reviews sometimes identify friction points but without a systematic approach
L3Blueprints are reviewed periodically to identify fail points, waits, and bottlenecks
L4Blueprint analysis is integrated into continuous improvement cycles with measurable impact tracking
L5AI-assisted analysis of blueprints combined with real-time data proactively surfaces optimization opportunities
πŸ—ΊοΈ

Journey Mapping

Nielsen Norman Group, IDEO

Analyzing end-to-end customer journeys, identifying pain points, emotional highs and lows, and moments of truth to drive experience improvements.

Strategy Elements

Journey Mapping Methodology and Standards
Customer Research and Persona Integration
Moments of Truth Identification Framework
Pain Point Cataloging and Prioritization Process
Emotional Journey and Sentiment Tracking
Cross-Functional Journey Improvement Governance
Journey Analytics and Measurement Dashboard

Assessment Questions

1. How does your organization create and use customer journey maps?

L1No journey maps exist; customer experience is not systematically understood
L2Some journey maps have been created for individual projects but are not maintained
L3Journey maps are created for all major services, documenting stages, emotions, and pain points
L4Journey maps are living documents updated with real customer data, research findings, and analytics
L5Journey maps are dynamic, data-driven, and automatically enriched with behavioral analytics and sentiment data

2. How effectively does your organization identify and act on moments of truth?

L1Moments of truth are not identified or understood
L2Some critical moments are anecdotally known but not formally mapped or prioritized
L3Key moments of truth are identified, documented, and have defined experience standards
L4Moments of truth are measured with specific KPIs and have dedicated improvement programs
L5Real-time monitoring of moments of truth enables immediate intervention and continuous optimization

3. How well are pain points and friction in customer journeys systematically addressed?

L1Pain points are only known through individual complaints with no systematic tracking
L2Pain points are collected informally but resolution is ad hoc and inconsistent
L3A structured process exists for cataloging pain points and prioritizing remediation
L4Pain points are quantified by business impact, tracked in backlogs, and resolved through cross-functional teams
L5Predictive analytics identify emerging friction before customers experience it, enabling preemptive design changes
🎯

Touchpoint Orchestration

Fjord/Accenture, Service Design Network

Designing and managing individual customer touchpoints for consistency, quality, and coherence across all channels and interactions.

Strategy Elements

Touchpoint Inventory and Classification
Touchpoint Design Standards and Guidelines
Channel-Specific Quality Criteria
Touchpoint Governance and Ownership Model
Consistency Audit and Review Cadence
Customer Context and Personalization Strategy
Touchpoint Performance Measurement Framework

Assessment Questions

1. How does your organization manage consistency across customer touchpoints?

L1Touchpoints are designed independently with no consistency standards
L2Some guidelines exist but touchpoint quality varies significantly across channels
L3Touchpoint design standards are documented and applied across major channels
L4A centralized touchpoint governance model ensures consistency with regular audits and quality reviews
L5Touchpoints are orchestrated as a unified system with real-time personalization and adaptive consistency

2. How effectively are touchpoints designed to support end-to-end customer goals?

L1Touchpoints are designed in isolation without considering the broader journey
L2Some touchpoints consider adjacent steps but end-to-end alignment is limited
L3Touchpoints are designed with awareness of the full journey and customer goals at each stage
L4Touchpoint design is informed by journey analytics and optimized for goal completion rates
L5Touchpoints dynamically adapt based on customer context, history, and predicted needs

3. How does your organization inventory and evaluate the quality of existing touchpoints?

L1No inventory of touchpoints exists; the full landscape is unknown
L2An informal list of touchpoints exists but quality is not systematically evaluated
L3A comprehensive touchpoint inventory is maintained with defined quality criteria
L4Touchpoints are regularly evaluated against quality benchmarks with improvement plans for underperformers
L5Automated quality monitoring across all touchpoints with real-time scoring and proactive optimization
🌐

Service Ecosystem Design

This is Service Design Doing, IDEO

Designing the broader service ecosystem including stakeholder networks, value exchange between actors, partnerships, and platform-level service thinking.

Strategy Elements

Service Ecosystem Mapping and Visualization
Stakeholder Identification and Role Definition
Value Exchange Design and Measurement
Partnership Strategy and Governance Framework
Platform and API Integration Standards
Ecosystem Co-Creation and Innovation Programs
Ecosystem Health Monitoring and Reporting

Assessment Questions

1. How well does your organization map and manage its service ecosystem and stakeholder network?

L1The service ecosystem is not understood; stakeholder relationships are informal and ad hoc
L2Key stakeholders are known but the broader ecosystem and interdependencies are not mapped
L3The service ecosystem is mapped with identified actors, roles, and value exchanges
L4Ecosystem maps are actively used to optimize partnerships, identify gaps, and manage dependencies
L5The ecosystem is dynamically managed as a platform, with real-time visibility into value flows and adaptive partnership models

2. How effectively does your organization design value exchange between service ecosystem actors?

L1Value exchange is not considered; relationships are transactional and unstructured
L2Some value propositions exist for key partners but mutual value is not systematically designed
L3Value exchange is defined for major ecosystem relationships with clear mutual benefits
L4Value exchange is measured and optimized across the ecosystem with balanced scorecards
L5Value exchange is continuously evolved through co-creation, with ecosystem-level innovation generating new shared value

3. How does your organization leverage partnerships and external actors in service delivery?

L1Services are delivered entirely in-house with no partner integration
L2Some services involve partners but integration is manual and inconsistent
L3Partner services are formally integrated with defined SLAs and interface standards
L4An ecosystem orchestration approach actively manages partner contributions with shared metrics and governance
L5A platform model enables seamless partner participation with API-driven integration, shared data, and co-innovation programs
πŸ‘₯

Employee Experience Design

Gov.uk Service Manual, Fjord/Accenture

Designing internal services and tools that enable staff to deliver excellent customer experiences, including onboarding, knowledge management, and workplace service design.

Strategy Elements

Employee Journey Mapping and Research Program
Internal Service Design Standards
Frontline Enablement and Empowerment Framework
Knowledge Management Strategy and Platform
Employee Onboarding and Training Design
Internal Tool and System Usability Standards
Employee Experience Measurement and Feedback Loops

Assessment Questions

1. How does your organization design internal services and tools to support employee effectiveness?

L1Internal tools and services are an afterthought; employees work around broken processes
L2Some internal tools are improved reactively when major issues arise
L3Employee-facing services are designed using service design principles with user research input
L4Internal service design is a formal practice with employee journey maps, metrics, and continuous improvement
L5Employee experience is treated as strategically important as customer experience, with parity in design investment and innovation

2. How well does your organization enable frontline staff to deliver excellent service?

L1Frontline staff lack adequate tools, training, and authority to resolve customer issues
L2Basic training exists but staff frequently need to escalate due to limited empowerment
L3Staff have clear guidelines, adequate tools, and defined autonomy to handle common scenarios
L4Staff are empowered with real-time customer context, decision support tools, and clear escalation paths
L5Staff are fully empowered with AI-augmented tools, personalized coaching, and the autonomy to innovate service delivery

3. How effectively does your organization capture and share service knowledge among employees?

L1Knowledge is siloed in individuals; no formal knowledge management exists
L2Some documentation exists but is outdated and hard to find
L3A structured knowledge base is maintained and accessible, with defined update processes
L4Knowledge management is integrated into workflows with search, tagging, and contribution incentives
L5AI-powered knowledge systems provide contextual answers, auto-update from interactions, and identify knowledge gaps proactively
πŸ”—

Omnichannel Integration

Fjord/Accenture, Nielsen Norman Group

Ensuring seamless, consistent customer experiences across all channels and enabling smooth transitions between digital, physical, and human-assisted service delivery.

Strategy Elements

Omnichannel Strategy and Vision
Channel Transition Design and Context Handoff Standards
Unified Customer Profile and Data Integration
Cross-Channel Consistency Standards and Audits
Channel-Specific Capability and Strength Mapping
Customer Channel Preference and Routing Logic
Omnichannel Performance Measurement Framework

Assessment Questions

1. How seamlessly can customers transition between channels during a service interaction?

L1Channels operate in silos; customers must restart interactions when switching channels
L2Some context is shared between channels but transitions are often disjointed
L3Major channel transitions are supported with context handoff for common scenarios
L4Customers can move fluidly between channels with full context preservation and proactive handoff suggestions
L5Channel transitions are invisible to customers, with AI-driven routing to the optimal channel based on context and preference

2. How consistent is the service experience across your digital, physical, and human-assisted channels?

L1Each channel delivers a different experience with no shared standards
L2Some shared branding exists but service quality and capabilities vary widely by channel
L3Core service experiences are consistent across channels with shared design principles
L4Channel-specific strengths are leveraged while maintaining consistent quality, tone, and capability standards
L5A unified experience platform ensures consistency while enabling channel-specific innovation and personalization

3. How effectively does your organization use customer data to deliver unified cross-channel experiences?

L1Customer data is fragmented across channels with no unified view
L2Some customer data is shared but a complete cross-channel view is not available
L3A unified customer profile exists and is accessible across major channels
L4Real-time customer data drives personalized experiences across all channels with consent management
L5Predictive customer intelligence anticipates needs across channels, enabling proactive and hyper-personalized service
πŸ›‘οΈ

Service Recovery & Resilience

ISO 23592, Gov.uk Service Manual

Designing for service failure, including recovery processes, complaint handling, resilience planning, and turning service failures into opportunities for trust building.

Strategy Elements

Service Failure Mode Identification and Analysis
Recovery Process Design and Playbooks
Complaint Management Framework and SLAs
Staff Empowerment for Service Recovery
Resilience and Business Continuity Planning
Service Paradox and Trust Rebuilding Strategy
Failure Data Analysis and Systemic Improvement Process

Assessment Questions

1. How does your organization design for and handle service failures?

L1Service failures are handled reactively with no pre-designed recovery processes
L2Some recovery scripts exist for known failure modes but coverage is limited
L3Service recovery processes are designed proactively for all major failure scenarios with clear escalation paths
L4Recovery processes are tested regularly, measured for effectiveness, and staff are trained and empowered to recover
L5Intelligent failure detection triggers automated recovery workflows, with service paradox principles turning failures into loyalty opportunities

2. How effectively does your organization manage customer complaints and feedback after service failures?

L1Complaints are handled inconsistently with no formal process or tracking
L2A complaint process exists but response times are slow and resolution is inconsistent
L3Complaints are tracked, categorized, and resolved within defined SLAs with root cause analysis
L4Complaint data drives systematic service improvements with closed-loop feedback to affected customers
L5Proactive outreach addresses potential dissatisfaction before formal complaints arise, with predictive churn models guiding intervention

3. How resilient are your services to disruptions and unexpected demand?

L1Services have no resilience planning; disruptions cause extended outages
L2Basic continuity plans exist for critical services but are rarely tested
L3Resilience is designed into major services with documented failover, capacity buffers, and regular testing
L4Services are designed for graceful degradation with automated failover, load management, and rapid recovery capabilities
L5Antifragile service design improves under stress, with chaos engineering practices and self-healing systems
πŸ“Š

Service Performance Metrics

Nielsen Norman Group, ISO 23592

Measuring service quality and performance through customer satisfaction scores, Net Promoter Scores, customer effort scores, and operational service KPIs.

Strategy Elements

Service Metrics Framework (CSAT, NPS, CES)
Measurement Collection Methods and Cadence
Real-Time Service Dashboard and Reporting
Leading and Lagging Indicator Balance
Metrics-to-Action Improvement Process
Service Benchmarking and Target Setting
Predictive Service Health Modeling

Assessment Questions

1. How does your organization measure customer satisfaction and service quality?

L1No formal measurement of customer satisfaction or service quality exists
L2Occasional surveys are conducted but results are not systematically analyzed or acted upon
L3Regular CSAT, NPS, and CES measurements are in place with defined collection methods and reporting
L4Service metrics are tracked in real-time dashboards, segmented by journey stage, and linked to operational KPIs
L5Advanced analytics combine satisfaction, effort, sentiment, and behavioral data into predictive service health models

2. How effectively are service metrics used to drive improvement decisions?

L1Metrics, where they exist, are reported but not used to drive decisions
L2Some metrics inform ad-hoc improvements but there is no systematic link to action
L3Service metrics are reviewed regularly and directly inform improvement backlogs and priorities
L4Metrics-driven improvement cycles are embedded in operations with clear accountability and impact tracking
L5Automated insight generation identifies improvement opportunities and triggers optimization workflows in near real-time

3. How well does your organization balance leading and lagging service performance indicators?

L1Only lagging indicators like complaints are tracked, if anything
L2Some leading indicators are monitored informally but the focus remains on lagging metrics
L3A balanced set of leading and lagging indicators is defined and tracked for major services
L4Leading indicators are used to predict service performance and trigger proactive interventions
L5A comprehensive service health scorecard with predictive and prescriptive analytics drives strategic and operational decisions
πŸ’‘

Service Innovation

IDEO, This is Service Design Doing

Developing new services and improving existing ones through experimentation, co-creation with customers, prototyping, and systematic innovation practices.

Strategy Elements

Service Innovation Strategy and Portfolio
Ideation and Concept Development Process
Service Prototyping Methods and Tooling
Co-Creation and Participatory Design Programs
Experimentation Framework and Kill Criteria
Pilot-to-Scale Governance and Decision Gates
Innovation Metrics and Learning Capture

Assessment Questions

1. How does your organization approach new service development and experimentation?

L1New services are developed based on internal assumptions with no structured innovation process
L2Some experimentation occurs but it is informal and not resourced or governed
L3A structured service innovation process exists with ideation, prototyping, and pilot phases
L4Service innovation is resourced, governed, and uses lean experimentation with defined success criteria and kill metrics
L5A portfolio approach to service innovation balances incremental and radical experiments, with rapid scaling of validated concepts

2. How effectively does your organization involve customers and stakeholders in co-creating services?

L1Services are designed without customer input beyond basic market research
L2Customer feedback is collected but true co-creation is rare
L3Co-creation workshops and participatory design sessions are conducted for major service initiatives
L4Customer and stakeholder co-creation is embedded in the service development lifecycle with diverse participant panels
L5An ongoing co-creation ecosystem engages customers, employees, and partners in continuous service evolution

3. How does your organization prototype and validate new service concepts before full-scale launch?

L1New services are launched without prototyping or validation
L2Some informal testing occurs but prototyping is not a standard practice
L3Service prototyping methods (role-play, desktop walkthroughs, pilot programs) are used for major initiatives
L4Rapid prototyping and iterative testing are standard practice with clear validation criteria before scaling
L5Digital twins and simulation enable continuous prototyping, with automated A/B testing validating service variations at scale
βš™οΈ

Service Operations Design

Gov.uk Service Manual, ISO 23592, Fjord/Accenture

Designing operational service delivery systems including capacity management, scheduling, resource allocation, and ensuring consistent service execution at scale.

Strategy Elements

Service Operations Design Principles
Capacity Planning and Demand Forecasting Model
Resource Allocation and Scheduling Framework
Service Execution Standards and Quality Checks
Operational Workflow Automation Strategy
Performance Monitoring and Real-Time Dashboards
Continuous Operational Improvement Program

Assessment Questions

1. How does your organization design and manage service delivery operations?

L1Service operations are ad hoc with no formal design or management approach
L2Basic operational processes exist but are inconsistently followed and poorly documented
L3Service operations are formally designed with documented processes, roles, and performance standards
L4Operations are optimized using data-driven capacity planning, workload management, and continuous process improvement
L5Intelligent operations use predictive analytics, automation, and self-optimizing systems to deliver consistent service at scale

2. How effectively does your organization manage service capacity and demand?

L1Capacity is not planned; demand spikes regularly overwhelm service delivery
L2Basic capacity planning exists but demand forecasting is inaccurate and reactive
L3Capacity planning uses historical data to forecast demand and allocate resources for key services
L4Dynamic capacity management adjusts resources in near real-time based on demand signals and predictive models
L5AI-driven demand sensing and elastic capacity management ensure optimal resource utilization with minimal customer impact

3. How does your organization ensure consistent service execution across locations, teams, and time?

L1Service quality varies widely depending on which team, location, or time of day
L2Some training and guidelines exist but execution consistency is a known challenge
L3Standardized processes, training programs, and quality checks ensure baseline consistency
L4Real-time monitoring, coaching, and performance feedback maintain high consistency across all delivery points
L5Automated quality assurance, adaptive workflows, and continuous calibration deliver consistently excellent service everywhere

Strategy Checklist

A comprehensive strategy should address all of the following:

πŸ“ Blueprinting

  • ☐Service Blueprint Standards and Templates
  • ☐Front-Stage / Back-Stage Interaction Mapping
  • ☐Support Process and System Dependency Documentation
  • ☐Physical Evidence and Touchpoint Inventory
  • ☐Fail Point and Wait Point Identification Process
  • ☐Blueprint Governance and Update Cadence
  • ☐Integration with Service Design Tooling and Repositories

πŸ—ΊοΈ Journey Mapping

  • ☐Journey Mapping Methodology and Standards
  • ☐Customer Research and Persona Integration
  • ☐Moments of Truth Identification Framework
  • ☐Pain Point Cataloging and Prioritization Process
  • ☐Emotional Journey and Sentiment Tracking
  • ☐Cross-Functional Journey Improvement Governance
  • ☐Journey Analytics and Measurement Dashboard

🎯 Touchpoints

  • ☐Touchpoint Inventory and Classification
  • ☐Touchpoint Design Standards and Guidelines
  • ☐Channel-Specific Quality Criteria
  • ☐Touchpoint Governance and Ownership Model
  • ☐Consistency Audit and Review Cadence
  • ☐Customer Context and Personalization Strategy
  • ☐Touchpoint Performance Measurement Framework

🌐 Ecosystem

  • ☐Service Ecosystem Mapping and Visualization
  • ☐Stakeholder Identification and Role Definition
  • ☐Value Exchange Design and Measurement
  • ☐Partnership Strategy and Governance Framework
  • ☐Platform and API Integration Standards
  • ☐Ecosystem Co-Creation and Innovation Programs
  • ☐Ecosystem Health Monitoring and Reporting

πŸ‘₯ Employee EX

  • ☐Employee Journey Mapping and Research Program
  • ☐Internal Service Design Standards
  • ☐Frontline Enablement and Empowerment Framework
  • ☐Knowledge Management Strategy and Platform
  • ☐Employee Onboarding and Training Design
  • ☐Internal Tool and System Usability Standards
  • ☐Employee Experience Measurement and Feedback Loops

πŸ”— Omnichannel

  • ☐Omnichannel Strategy and Vision
  • ☐Channel Transition Design and Context Handoff Standards
  • ☐Unified Customer Profile and Data Integration
  • ☐Cross-Channel Consistency Standards and Audits
  • ☐Channel-Specific Capability and Strength Mapping
  • ☐Customer Channel Preference and Routing Logic
  • ☐Omnichannel Performance Measurement Framework

πŸ›‘οΈ Recovery

  • ☐Service Failure Mode Identification and Analysis
  • ☐Recovery Process Design and Playbooks
  • ☐Complaint Management Framework and SLAs
  • ☐Staff Empowerment for Service Recovery
  • ☐Resilience and Business Continuity Planning
  • ☐Service Paradox and Trust Rebuilding Strategy
  • ☐Failure Data Analysis and Systemic Improvement Process

πŸ“Š Metrics

  • ☐Service Metrics Framework (CSAT, NPS, CES)
  • ☐Measurement Collection Methods and Cadence
  • ☐Real-Time Service Dashboard and Reporting
  • ☐Leading and Lagging Indicator Balance
  • ☐Metrics-to-Action Improvement Process
  • ☐Service Benchmarking and Target Setting
  • ☐Predictive Service Health Modeling

πŸ’‘ Innovation

  • ☐Service Innovation Strategy and Portfolio
  • ☐Ideation and Concept Development Process
  • ☐Service Prototyping Methods and Tooling
  • ☐Co-Creation and Participatory Design Programs
  • ☐Experimentation Framework and Kill Criteria
  • ☐Pilot-to-Scale Governance and Decision Gates
  • ☐Innovation Metrics and Learning Capture

βš™οΈ Operations

  • ☐Service Operations Design Principles
  • ☐Capacity Planning and Demand Forecasting Model
  • ☐Resource Allocation and Scheduling Framework
  • ☐Service Execution Standards and Quality Checks
  • ☐Operational Workflow Automation Strategy
  • ☐Performance Monitoring and Real-Time Dashboards
  • ☐Continuous Operational Improvement Program