[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C3VDYCPAS6YDPBS11RZ40":3,"skill-same:01M73C3VDYCPAS6YDPBS11RZ40":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":70},"01M73C3VDYCPAS6YDPBS11RZ40","service-design",null,"Designs end-to-end service experiences including customer journeys, service blueprints, and operational processes. Use when: mapping customer experiences, optimizing touchpoints, aligning frontstage and backstage operations, or improving service delivery.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fservice-design\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: service-design\ndescription: >\n  Designs end-to-end service experiences including customer journeys, service blueprints,\n  and operational processes. Use when: mapping customer experiences, optimizing touchpoints,\n  aligning frontstage and backstage operations, or improving service delivery.\nversion: 1.1.0\nscope: common\nl2_propagate: true\nstatus: active\nowner: pm\nlast_reviewed: 2026-09-27\nprerequisites: none\nrelates_to:\n  - skill: accessibility-audit\n    type: follows\n  - skill: ui-ux-design-intelligence\n    type: follows\n  - skill: token-usage-lint\n    type: follows\ngemini-parity: skip\nmetadata:\n  type: process\n  triggers:\n    - service design\n    - customer journey\n    - service blueprint\n    - touchpoint design\n    - customer experience\n    - service innovation\n    - operational alignment\n---\n\n## Context\n\nThis skill provides comprehensive service design capabilities, focusing on the entire service ecosystem beyond digital interfaces. It connects customer experiences with operational processes, ensuring holistic, consistent service delivery across all touchpoints.\n\n## When to Use\n\n**Customer Experience Design**:\n- Trigger: \"Design customer journey\" or \"Map service experience\"\n- Use Case: Understanding and improving end-to-end customer experiences\n\n**Service Innovation**:\n- Trigger: \"Design new service\" or \"Improve service delivery\"\n- Use Case: Creating new service offerings or improving existing ones\n\n**Operational Alignment**:\n- Trigger: \"Align operations with customer needs\" or \"Optimize service delivery\"\n- Use Case: Connecting frontstage experiences with backstage processes\n\n**Touchpoint Optimization**:\n- Trigger: \"Improve touchpoint\" or \"Design service interaction\"\n- Use Case: Enhancing specific customer interaction points\n\n---\n\n## Execution Steps\n\n## Step 1: Service Discovery\n\n**Purpose**: Understand current service ecosystem and identify opportunities.\n\n**Discovery Activities**:\n1. **Stakeholder Interviews**:\n   - Customer interviews (current, prospective, churned)\n   - Frontline staff interviews (sales, support, service)\n   - Management interviews (strategy, constraints, goals)\n   - Partner interviews (if applicable)\n\n2. **Service Mapping**:\n   - Current customer journey mapping\n   - Touchpoint inventory (all channels)\n   - Service blueprints of existing processes\n   - Pain point identification\n\n3. **Competitive Analysis**:\n   - Competitor service experiences\n   - Industry best practices\n   - Innovation benchmarks\n   - Technology enablers\n\n**Discovery Outputs**:\n- Customer personas and scenarios\n- Current state journey maps\n- Pain point documentation\n- Opportunity identification\n\n---\n\n## Step 2: Customer Journey Mapping\n\n**Purpose**: Visualize end-to-end customer experiences across time and channels.\n\n**Journey Mapping Process**:\n1. **Define Journey Scope**:\n   - Journey start and end points\n   - Customer persona(s)\n   - Service scenario(s)\n   - Timeframe covered\n\n2. **Map Journey Stages**:\n   - Awareness → Consideration → Purchase → Usage → Support → Renewal\n   - Or custom stages for specific service\n   - Include pre-purchase and post-purchase phases\n\n3. **Identify Touchpoints**:\n   - Digital channels (website, app, email)\n   - Physical channels (store, phone, mail)\n   - Human interactions (sales, support, service)\n   - Third-party touchpoints (partners, platforms)\n\n4. **Capture Customer Experience**:\n   - Actions taken at each stage\n   - Emotional highs and lows\n   - Pain points and frustrations\n   - Needs and expectations\n\n5. **Diversity-Profile Review** (ADR-0068 — mandatory):\n   - Walk the mapped journey once for each diversity profile: **aging** (reduced\n     vision\u002Fdexterity, smaller working memory for new UI conventions), **cognitive**\n     (attention load, language complexity, multi-step comprehension), **situational**\n     (one-handed, noisy\u002Fbright environments, interruptions), and **motor-constrained**\n     (precision, reach, timing pressure).\n   - Log every friction point found in those walks as design requirements in the\n     journey map's Opportunities row — they are design inputs, not acceptable losses.\n   - WCAG conformance alone does not satisfy this step; it evaluates design-stage\n     coverage of user diversity (Universal Design), not technical compliance.\n\n**Journey Map Structure**:\n```\nStage: [Stage Name]\nTouchpoints: [List all touchpoints]\nCustomer Actions: [What customer does]\nEmotional Arc: [😊 → 😐 → 😞 → 😊]\nPain Points: [Specific frustrations]\nDiversity-Profile Friction: [Aging\u002FCognitive\u002FSituational\u002FMotor findings]\nOpportunities: [Improvement areas]\n```\n\n---\n\n## Step 3: Service Blueprinting\n\n**Purpose**: Document frontstage interactions and backstage processes.\n\n**Service Blueprint Components**:\n1. **Frontstage (Customer-Visible)**:\n   - Customer actions\n   - Touchpoint interactions\n   - Line of visibility\n   - Physical evidence\n\n2. **Backstage (Internal Processes)**:\n   - Support processes\n   - Employee actions\n   - Systems and tools\n   - Internal dependencies\n\n3. **Support Systems**:\n   - Policies and procedures\n   - Technology infrastructure\n   - Training requirements\n   - Performance metrics\n\n**Blueprint Creation Process**:\n1. **Map Customer Actions**:\n   - What customer does step-by-step\n   - Decisions customer makes\n   - Information customer needs\n\n2. **Link to Frontstage Interactions**:\n   - Employee responses and actions\n   - Systems that support interactions\n   - Processes triggered by customer actions\n\n3. **Document Backstage Processes**:\n   - Internal workflows\n   - Support systems needed\n   - Decision points and handoffs\n\n4. **Identify Dependencies**:\n   - Process dependencies\n   - System dependencies\n   - Staff dependencies\n   - Third-party dependencies\n\n**Service Blueprint Structure**:\n```\nTime: [Stage duration]\nFrontstage:\n  Customer Action: [What customer does]\n  Touchpoint: [Channel used]\n  Employee Action: [Staff response]\nBackstage:\n  Process: [Internal workflow]\n  System: [Technology used]\n  Support: [Policies, training]\n```\n\n---\n\n## Step 4: Touchpoint Design\n\n**Purpose**: Design consistent, high-quality service interactions.\n\n**Touchpoint Design Process**:\n1. **Define Touchpoint Purpose**:\n   - What customer goal does it serve?\n   - What business outcome is needed?\n   - What constraints exist?\n\n2. **Design Interaction**:\n   - Service script or guideline\n   - Employee behaviors and actions\n   - System interfaces and tools\n   - Physical environment (if applicable)\n\n3. **Ensure Consistency**:\n   - Brand alignment\n   - Cross-channel consistency\n   - Quality standards\n   - Service level agreements\n\n4. **Design for Edge Cases**:\n   - Error scenarios\n   - Peak demand handling\n   - System failure procedures\n   - Escalation paths\n\n**Touchpoint Categories**:\n- **Digital**: Website, app, email, chat, social media\n- **Physical**: Store, office, event, mail\n- **Human**: Sales, support, service, consultant\n- **Automated**: IVR, chatbot, self-service\n\n**Quality Dimensions**:\n- **Efficiency**: How quickly is service delivered?\n- **Effectiveness**: Does it solve the customer's problem?\n- **Reliability**: Is service consistent and dependable?\n- **Empathy**: Is the interaction respectful and caring?\n- **Personalization**: Is it tailored to customer needs?\n\n---\n\n## Step 5: Process Optimization\n\n**Purpose**: Align operational capabilities with customer experience goals.\n\n**Optimization Analysis**:\n1. **Identify Operational Constraints**:\n   - Resource limitations\n   - Process bottlenecks\n   - System constraints\n   - Policy restrictions\n\n2. **Analyze Process Efficiency**:\n   - Cycle time analysis\n   - Handoff optimization\n   - Parallel vs. sequential processing\n   - Automation opportunities\n\n3. **Design Future State**:\n   - Ideal customer journey\n   - Required operational changes\n   - Technology investments\n   - Process improvements\n\n4. **Create Implementation Roadmap**:\n   - Short-term improvements (quick wins)\n   - Medium-term process changes\n   - Long-term transformation\n   - Resource requirements\n\n**Optimization Techniques**:\n- **Lean Service**: Remove waste, improve flow\n- **Service Standardization**: Consistent quality\n- **Automation**: Self-service, chatbots, AI\n- **Process Redesign**: Simplify handoffs\n- **Capacity Planning**: Match demand to supply\n\n---\n\n## Step 6: Service Validation\n\n**Purpose**: Test and validate service designs with real customers.\n\n**Validation Methods**:\n1. **Journey Testing**:\n   - Walk through service with real customers\n   - Observe behavior and reactions\n   - Identify pain points in real-time\n   - Gather immediate feedback\n\n2. **Prototyping**:\n   - Role-play service scenarios\n   - Walk-through simulations\n   - Service mockups\n   - Beta testing with subset of customers\n\n3. **Measurement**:\n   - Customer satisfaction (CSAT, NPS)\n   - Service metrics (cycle time, resolution rate)\n   - Operational metrics (cost, efficiency)\n   - Behavioral metrics (adoption, engagement)\n\n4. **Iteration**:\n   - Analyze feedback and metrics\n   - Identify improvement areas\n   - Design and test changes\n   - Scale successful improvements\n\n**Validation Criteria**:\n- Customer experience improved\n- Operational efficiency maintained or improved\n- Business metrics achieved\n- Service quality consistent\n- Sustainable implementation\n\n---\n\n## Output Format\n\n**For Service Design**:\n- Customer journey maps with pain points and opportunities\n- Service blueprints documenting frontstage\u002Fbackstage\n- Touchpoint designs with interaction specifications\n- Process optimization recommendations\n- Implementation roadmap with priorities\n\n**For Service Innovation**:\n- New service concepts with value propositions\n- Business model validation\n- Pilot testing results\n- Scale-up plan\n- Go-to-market strategy\n\n**For Operational Alignment**:\n- Process redesign recommendations\n- Technology requirements\n- Training needs assessment\n- Change management plan\n- Performance metrics framework\n\n---\n\n## Best Practices\n\n**Service Design Quality**:\n✅ **Do**:\n- Start with customer research and understanding\n- Consider entire service ecosystem, not just digital\n- Design for edge cases and failure scenarios\n- Include operational feasibility in design\n- Test with real customers before scaling\n- Measure and iterate based on data\n\n❌ **Don't**:\n- Design in isolation without customer input\n- Focus only on digital touchpoints\n- Ignore operational constraints\n- Assume everything will work perfectly\n- Skip validation and testing\n- Design for the \"average\" customer only\n\n**Collaboration Quality**:\n✅ **Do**:\n- Involve cross-functional stakeholders\n- Include frontline staff in design\n- Consider partner and third-party constraints\n- Get executive buy-in for changes\n- Document decisions and rationale\n- Create shared understanding\n\n❌ **Don't**:\n- Design in silo without input\n- Ignore operational reality\n- Overlook political\u002Forganizational constraints\n- Make changes without stakeholder alignment\n- Keep design rationale hidden\n- Assume others will understand \"why\"\n\n---\n\n## Common Mistakes to Avoid\n\n**Service Design Anti-Patterns**:\n1. **Channel Silos**: Optimizing channels in isolation\n2. **Frontstage-Only**: Designing customer touchpoints without operational backing\n3. **Employee Neglect**: Forgetting the employee experience\n4. **Technology First**: Starting with solutions instead of customer needs\n5. **One-Size-Fits-All**: Designing for \"average\" customer instead of segments\n\n**Process Anti-Patterns**:\n1. **Analysis Paralysis**: Over-researching without action\n2. **Design Without Validation**: Assuming design will work\n3. **Ignoring Constraints**: Designing unrealistic solutions\n4. **Short-Term Focus**: Optimizing for metrics vs. long-term value\n5. **Change Resistance**: Not preparing organization for changes\n\n---\n\n## Related Skills\n\n- **ui-ux-design-intelligence**: For digital touchpoint design\n- **research-analysis**: For customer research and validation\n- **process-improvement**: For operational process optimization\n- **change-management**: For organizational change and adoption\n\n---\n\n## Service Design Tools\n\n**Journey Mapping**:\n- **Miro**: Collaborative journey mapping\n- **Smaply**: Customer journey platform\n- **UXPressia**: Journey mapping tool\n- **Microsoft Visio**: Diagramming journey maps\n\n**Service Blueprinting**:\n- **Miro**: Service blueprint templates\n- **Lucidchart**: Service blueprint diagrams\n- **Microsoft Visio**: Professional blueprinting\n- **Custom Templates**: Tailored blueprint formats\n\n**Research & Validation**:\n- **UserTesting**: Customer research platform\n- **Maze**: User research and testing\n- **Hotjar**: Behavioral analytics\n- **Typeform**: Survey and feedback collection\n\n**Project Management**:\n- **Asana**: Project tracking\n- **Trello**: Kanban-style management\n- **Monday.com**: Work management\n- **Notion**: All-in-one workspace\n\n---\n\n## Service Design Deliverables\n\n**Core Deliverables**:\n1. **Customer Journey Map**: Visual timeline of customer experience\n2. **Service Blueprint**: Detailed frontstage\u002Fbackstage documentation\n3. **Touchpoint Inventory**: Comprehensive list of all touchpoints\n4. **Persona Profiles**: Detailed customer segment descriptions\n5. **Service Concept**: Value proposition and business model\n6. **Implementation Roadmap**: Phased delivery plan\n\n**Supporting Artifacts**:\n- Stakeholder interview summaries\n- Competitive analysis report\n- Pain point documentation\n- Opportunity assessment\n- Validation testing results\n- Metrics framework and baseline\n\n**Presentation Materials**:\n- Executive summary presentation\n- Stakeholder communication plan\n- Training materials for staff\n- Customer communication strategy\n\n---\n\n## Service Metrics Framework\n\n**Customer Experience Metrics**:\n- **CSAT** (Customer Satisfaction): Post-interaction surveys\n- **NPS** (Net Promoter Score): Likelihood to recommend\n- **CES** (Customer Effort Score): Ease of interaction\n- **Retention Rate**: Customer churn and loyalty\n- **CLV** (Customer Lifetime Value): Long-term value\n\n**Operational Metrics**:\n- **Cycle Time**: Time to complete service\n- **First Contact Resolution**: One-and-done rate\n- **Service Level Agreement** compliance\n- **Cost per Service**: Efficiency metric\n- **Employee Satisfaction**: Staff engagement\n\n**Quality Metrics**:\n- **Consistency**: Standard adherence\n- **Accuracy**: Error rates\n- **Timeliness**: Response times\n- **Completeness**: Full solution delivery\n- **Recovery**: Problem resolution success\n\n---\n\n## Service Design vs. Related Disciplines\n\n**Service Design vs. UX Design**:\n- **UX Design**: Focuses on digital interface design\n- **Service Design**: Focuses on entire service ecosystem\n\n**Service Design vs. Operations Management**:\n- **Operations**: Focuses on efficiency and cost\n- **Service Design**: Focuses on customer experience and operational alignment\n\n**Service Design vs. Product Management**:\n- **Product Management**: Focuses on feature roadmap\n- **Service Design**: Focuses on holistic experience and delivery\n\n**Integration Opportunities**:\n- UX Design: Digital touchpoint expertise\n- Operations: Operational feasibility and constraints\n- Product Management: Business viability and roadmap\n- Marketing: Customer acquisition and communication\n","## Context\n\nThis skill provides comprehensive service design capabilities, focusing on the entire service ecosystem beyond digital interfaces. It connects customer experiences with operational processes, ensuring holistic, consistent service delivery across all touchpoints.\n\n## When to Use\n\n**Customer Experience Design**:\n- Trigger: \"Design customer journey\" or \"Map service experience\"\n- Use Case: Understanding and improving end-to-end customer experiences\n\n**Service Innovation**:\n- Trigger: \"Design new service\" or \"Improve service delivery\"\n- Use Case: Creating new service offerings or improving existing ones\n\n**Operational Alignment**:\n- Trigger: \"Align operations with customer needs\" or \"Optimize service delivery\"\n- Use Case: Connecting frontstage experiences with backstage processes\n\n**Touchpoint Optimization**:\n- Trigger: \"Improve touchpoint\" or \"Design service interaction\"\n- Use Case: Enhancing specific customer interaction points\n\n---\n\n## Execution Steps\n\n## Step 1: Service Discovery\n\n**Purpose**: Understand current service ecosystem and identify opportunities.\n\n**Discovery Activities**:\n1. **Stakeholder Interviews**:\n   - Customer interviews (current, prospective, churned)\n   - Frontline staff interviews (sales, support, service)\n   - Management interviews (strategy, constraints, goals)\n   - Partner interviews (if applicable)\n\n2. **Service Mapping**:\n   - Current customer journey mapping\n   - Touchpoint inventory (all channels)\n   - Service blueprints of existing processes\n   - Pain point identification\n\n3. **Competitive Analysis**:\n   - Competitor service experiences\n   - Industry best practices\n   - Innovation benchmarks\n   - Technology enablers\n\n**Discovery Outputs**:\n- Customer personas and scenarios\n- Current state journey maps\n- Pain point documentation\n- Opportunity identification\n\n---\n\n## Step 2: Customer Journey Mapping\n\n**Purpose**: Visualize end-to-end customer experiences across time and channels.\n\n**Journey Mapping Process**:\n1. **Define Journey Scope**:\n   - Journey start and end points\n   - Customer persona(s)\n   - Service scenario(s)\n   - Timeframe covered\n\n2. **Map Journey Stages**:\n   - Awareness → Consideration → Purchase → Usage → Support → Renewal\n   - Or custom stages for specific service\n   - Include pre-purchase and post-purchase phases\n\n3. **Identify Touchpoints**:\n   - Digital channels (website, app, email)\n   - Physical channels (store, phone, mail)\n   - Human interactions (sales, support, service)\n   - Third-party touchpoints (partners, platforms)\n\n4. **Capture Customer Experience**:\n   - Actions taken at each stage\n   - Emotional highs and lows\n   - Pain points and frustrations\n   - Needs and expectations\n\n5. **Diversity-Profile Review** (ADR-0068 — mandatory):\n   - Walk the mapped journey once for each diversity profile: **aging** (reduced\n     vision\u002Fdexterity, smaller working memory for new UI conventions), **cognitive**\n     (attention load, language complexity, multi-step comprehension), **situational**\n     (one-handed, noisy\u002Fbright environments, interruptions), and **motor-constrained**\n     (precision, reach, timing pressure).\n   - Log every friction point found in those walks as design requirements in the\n     journey map's Opportunities row — they are design inputs, not acceptable losses.\n   - WCAG conformance alone does not satisfy this step; it evaluates design-stage\n     coverage of user diversity (Universal Design), not technical compliance.\n\n**Journey Map Structure**:\n```\nStage: [Stage Name]\nTouchpoints: [List all touchpoints]\nCustomer Actions: [What customer does]\nEmotional Arc: [😊 → 😐 → 😞 → 😊]\nPain Points: [Specific frustrations]\nDiversity-Profile Friction: [Aging\u002FCognitive\u002FSituational\u002FMotor findings]\nOpportunities: [Improvement areas]\n```\n\n---\n\n## Step 3: Service Blueprinting\n\n**Purpose**: Document frontstage interactions and backstage processes.\n\n**Service Blueprint Components**:\n1. **Frontstage (Customer-Visible)**:\n   - Customer actions\n   - Touchpoint interactions\n   - Line of visibility\n   - Physical evidence\n\n2. **Backstage (Internal Processes)**:\n   - Support processes\n   - Employee actions\n   - Systems and tools\n   - Internal dependencies\n\n3. **Support Systems**:\n   - Policies and procedures\n   - Technology infrastructure\n   - Training requirements\n   - Performance metrics\n\n**Blueprint Creation Process**:\n1. **Map Customer Actions**:\n   - What customer does step-by-step\n   - Decisions customer makes\n   - Information customer needs\n\n2. **Link to Frontstage Interactions**:\n   - Employee responses and actions\n   - Systems that support interactions\n   - Processes triggered by customer actions\n\n3. **Document Backstage Processes**:\n   - Internal workflows\n   - Support systems needed\n   - Decision points and handoffs\n\n4. **Identify Dependencies**:\n   - Process dependencies\n   - System dependencies\n   - Staff dependencies\n   - Third-party dependencies\n\n**Service Blueprint Structure**:\n```\nTime: [Stage duration]\nFrontstage:\n  Customer Action: [What customer does]\n  Touchpoint: [Channel used]\n  Employee Action: [Staff response]\nBackstage:\n  Process: [Internal workflow]\n  System: [Technology used]\n  Support: [Policies, training]\n```\n\n---\n\n## Step 4: Touchpoint Design\n\n**Purpose**: Design consistent, high-quality service interactions.\n\n**Touchpoint Design Process**:\n1. **Define Touchpoint Purpose**:\n   - What customer goal does it serve?\n   - What business outcome is needed?\n   - What constraints exist?\n\n2. **Design Interaction**:\n   - Service script or guideline\n   - Employee behaviors and actions\n   - System interfaces and tools\n   - Physical environment (if applicable)\n\n3. **Ensure Consistency**:\n   - Brand alignment\n   - Cross-channel consistency\n   - Quality standards\n   - Service level agreements\n\n4. **Design for Edge Cases**:\n   - Error scenarios\n   - Peak demand handling\n   - System failure procedures\n   - Escalation paths\n\n**Touchpoint Categories**:\n- **Digital**: Website, app, email, chat, social media\n- **Physical**: Store, office, event, mail\n- **Human**: Sales, support, service, consultant\n- **Automated**: IVR, chatbot, self-service\n\n**Quality Dimensions**:\n- **Efficiency**: How quickly is service delivered?\n- **Effectiveness**: Does it solve the customer's problem?\n- **Reliability**: Is service consistent and dependable?\n- **Empathy**: Is the interaction respectful and caring?\n- **Personalization**: Is it tailored to customer needs?\n\n---\n\n## Step 5: Process Optimization\n\n**Purpose**: Align operational capabilities with customer experience goals.\n\n**Optimization Analysis**:\n1. **Identify Operational Constraints**:\n   - Resource limitations\n   - Process bottlenecks\n   - System constraints\n   - Policy restrictions\n\n2. **Analyze Process Efficiency**:\n   - Cycle time analysis\n   - Handoff optimization\n   - Parallel vs. sequential processing\n   - Automation opportunities\n\n3. **Design Future State**:\n   - Ideal customer journey\n   - Required operational changes\n   - Technology investments\n   - Process improvements\n\n4. **Create Implementation Roadmap**:\n   - Short-term improvements (quick wins)\n   - Medium-term process changes\n   - Long-term transformation\n   - Resource requirements\n\n**Optimization Techniques**:\n- **Lean Service**: Remove waste, improve flow\n- **Service Standardization**: Consistent quality\n- **Automation**: Self-service, chatbots, AI\n- **Process Redesign**: Simplify handoffs\n- **Capacity Planning**: Match demand to supply\n\n---\n\n## Step 6: Service Validation\n\n**Purpose**: Test and validate service designs with real customers.\n\n**Validation Methods**:\n1. **Journey Testing**:\n   - Walk through service with real customers\n   - Observe behavior and reactions\n   - Identify pain points in real-time\n   - Gather immediate feedback\n\n2. **Prototyping**:\n   - Role-play service scenarios\n   - Walk-through simulations\n   - Service mockups\n   - Beta testing with subset of customers\n\n3. **Measurement**:\n   - Customer satisfaction (CSAT, NPS)\n   - Service metrics (cycle time, resolution rate)\n   - Operational metrics (cost, efficiency)\n   - Behavioral metrics (adoption, engagement)\n\n4. **Iteration**:\n   - Analyze feedback and metrics\n   - Identify improvement areas\n   - Design and test changes\n   - Scale successful improvements\n\n**Validation Criteria**:\n- Customer experience improved\n- Operational efficiency maintained or improved\n- Business metrics achieved\n- Service quality consistent\n- Sustainable implementation\n\n---\n\n## Output Format\n\n**For Service Design**:\n- Customer journey maps with pain points and opportunities\n- Service blueprints documenting frontstage\u002Fbackstage\n- Touchpoint designs with interaction specifications\n- Process optimization recommendations\n- Implementation roadmap with priorities\n\n**For Service Innovation**:\n- New service concepts with value propositions\n- Business model validation\n- Pilot testing results\n- Scale-up plan\n- Go-to-market strategy\n\n**For Operational Alignment**:\n- Process redesign recommendations\n- Technology requirements\n- Training needs assessment\n- Change management plan\n- Performance metrics framework\n\n---\n\n## Best Practices\n\n**Service Design Quality**:\n✅ **Do**:\n- Start with customer research and understanding\n- Consider entire service ecosystem, not just digital\n- Design for edge cases and failure scenarios\n- Include operational feasibility in design\n- Test with real customers before scaling\n- Measure and iterate based on data\n\n❌ **Don't**:\n- Design in isolation without customer input\n- Focus only on digital touchpoints\n- Ignore operational constraints\n- Assume everything will work perfectly\n- Skip validation and testing\n- Design for the \"average\" customer only\n\n**Collaboration Quality**:\n✅ **Do**:\n- Involve cross-functional stakeholders\n- Include frontline staff in design\n- Consider partner and third-party constraints\n- Get executive buy-in for changes\n- Document decisions and rationale\n- Create shared understanding\n\n❌ **Don't**:\n- Design in silo without input\n- Ignore operational reality\n- Overlook political\u002Forganizational constraints\n- Make changes without stakeholder alignment\n- Keep design rationale hidden\n- Assume others will understand \"why\"\n\n---\n\n## Common Mistakes to Avoid\n\n**Service Design Anti-Patterns**:\n1. **Channel Silos**: Optimizing channels in isolation\n2. **Frontstage-Only**: Designing customer touchpoints without operational backing\n3. **Employee Neglect**: Forgetting the employee experience\n4. **Technology First**: Starting with solutions instead of customer needs\n5. **One-Size-Fits-All**: Designing for \"average\" customer instead of segments\n\n**Process Anti-Patterns**:\n1. **Analysis Paralysis**: Over-researching without action\n2. **Design Without Validation**: Assuming design will work\n3. **Ignoring Constraints**: Designing unrealistic solutions\n4. **Short-Term Focus**: Optimizing for metrics vs. long-term value\n5. **Change Resistance**: Not preparing organization for changes\n\n---\n\n## Related Skills\n\n- **ui-ux-design-intelligence**: For digital touchpoint design\n- **research-analysis**: For customer research and validation\n- **process-improvement**: For operational process optimization\n- **change-management**: For organizational change and adoption\n\n---\n\n## Service Design Tools\n\n**Journey Mapping**:\n- **Miro**: Collaborative journey mapping\n- **Smaply**: Customer journey platform\n- **UXPressia**: Journey mapping tool\n- **Microsoft Visio**: Diagramming journey maps\n\n**Service Blueprinting**:\n- **Miro**: Service blueprint templates\n- **Lucidchart**: Service blueprint diagrams\n- **Microsoft Visio**: Professional blueprinting\n- **Custom Templates**: Tailored blueprint formats\n\n**Research & Validation**:\n- **UserTesting**: Customer research platform\n- **Maze**: User research and testing\n- **Hotjar**: Behavioral analytics\n- **Typeform**: Survey and feedback collection\n\n**Project Management**:\n- **Asana**: Project tracking\n- **Trello**: Kanban-style management\n- **Monday.com**: Work management\n- **Notion**: All-in-one workspace\n\n---\n\n## Service Design Deliverables\n\n**Core Deliverables**:\n1. **Customer Journey Map**: Visual timeline of customer experience\n2. **Service Blueprint**: Detailed frontstage\u002Fbackstage documentation\n3. **Touchpoint Inventory**: Comprehensive list of all touchpoints\n4. **Persona Profiles**: Detailed customer segment descriptions\n5. **Service Concept**: Value proposition and business model\n6. **Implementation Roadmap**: Phased delivery plan\n\n**Supporting Artifacts**:\n- Stakeholder interview summaries\n- Competitive analysis report\n- Pain point documentation\n- Opportunity assessment\n- Validation testing results\n- Metrics framework and baseline\n\n**Presentation Materials**:\n- Executive summary presentation\n- Stakeholder communication plan\n- Training materials for staff\n- Customer communication strategy\n\n---\n\n## Service Metrics Framework\n\n**Customer Experience Metrics**:\n- **CSAT** (Customer Satisfaction): Post-interaction surveys\n- **NPS** (Net Promoter Score): Likelihood to recommend\n- **CES** (Customer Effort Score): Ease of interaction\n- **Retention Rate**: Customer churn and loyalty\n- **CLV** (Customer Lifetime Value): Long-term value\n\n**Operational Metrics**:\n- **Cycle Time**: Time to complete service\n- **First Contact Resolution**: One-and-done rate\n- **Service Level Agreement** compliance\n- **Cost per Service**: Efficiency metric\n- **Employee Satisfaction**: Staff engagement\n\n**Quality Metrics**:\n- **Consistency**: Standard adherence\n- **Accuracy**: Error rates\n- **Timeliness**: Response times\n- **Completeness**: Full solution delivery\n- **Recovery**: Problem resolution success\n\n---\n\n## Service Design vs. Related Disciplines\n\n**Service Design vs. UX Design**:\n- **UX Design**: Focuses on digital interface design\n- **Service Design**: Focuses on entire service ecosystem\n\n**Service Design vs. Operations Management**:\n- **Operations**: Focuses on efficiency and cost\n- **Service Design**: Focuses on customer experience and operational alignment\n\n**Service Design vs. Product Management**:\n- **Product Management**: Focuses on feature roadmap\n- **Service Design**: Focuses on holistic experience and delivery\n\n**Integration Opportunities**:\n- UX Design: Digital touchpoint expertise\n- Operations: Operational feasibility and constraints\n- Product Management: Business viability and roadmap\n- Marketing: Customer acquisition and communication\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":37,"description":45,"l2_propagate":46,"gemini-parity":47,"last_reviewed":48,"prerequisites":49},"pm","common","active","1.1.0",{"type":28,"triggers":29},"process",[30,31,32,33,34,35,36],"service design","customer journey","service blueprint","touchpoint design","customer experience","service innovation","operational alignment",[38,41,43],{"type":39,"skill":40},"follows","accessibility-audit",{"type":39,"skill":42},"ui-ux-design-intelligence",{"type":39,"skill":44},"token-usage-lint","Designs end-to-end service experiences including customer journeys, service blueprints, and operational processes. Use when: mapping customer experiences, optimizing touchpoints, aligning frontstage and backstage operations, or improving service delivery.\n",true,"skip",1790467200000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883",".gemini\u002Fskills\u002Fservice-design",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":46},[60,63,66],{"tool":61,"command":62},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill service-design",{"tool":64,"command":65},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill service-design",{"tool":67,"command":68},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill service-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fservice-design\u002FSKILL.md",[],[72,80,85,90,95,100],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":81,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":79},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":86,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":79},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":91,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":79},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":96,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":79},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":101,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":79},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]