본문으로 건너뛰기
cccskills
무료GitHub에 공개

customer-journey-map

Map the customer experience from discovering a product to recommending it. Create a table of interactions, actions, emotions, and pain points at each stage, then prioritize improvements to sign-up, initial use, and continued engagement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.

설치 방법 보기

이럴 때 유용합니다

  • Mapping the full customer experience
  • Finding friction during sign-up and initial use
  • Identifying reasons customers leave
  • Prioritizing customer experience improvements

포함된 파일(1)

  • SKILL.md3.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

Context

You are creating a customer journey map for $ARGUMENTS.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

Instructions

  1. Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

  2. Map the journey stages (adapt to the product):

    StageDescription
    AwarenessHow do they first learn about the product?
    ConsiderationWhat do they evaluate? What alternatives do they compare?
    AcquisitionHow do they sign up or purchase?
    OnboardingFirst experience with the product — time to value
    EngagementRegular usage — building habits
    RetentionWhat keeps them coming back? What might cause churn?
    AdvocacyWhen and why do they recommend the product to others?
  3. For each stage, document:

    • Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
    • User actions: What they do at this stage
    • Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
    • Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
    • Pain points: Friction, confusion, drop-off risks
    • Opportunities: How to improve the experience at this point
  4. Identify critical moments:

    • Aha moment: When the user first experiences core value
    • Moments of truth: Decision points where they commit or abandon
    • Churn triggers: Where users most commonly drop off
  5. Create the journey map table:

    StageTouchpointUser ActionEmotionPain PointOpportunity
  6. Recommend prioritized improvements:

    • Which pain points have the highest impact on conversion or retention?
    • What quick wins can improve the experience immediately?
    • What requires deeper investment but has the biggest payoff?

Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.


Further Reading

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

phuryn의 스킬 모두 보기

이 스킬의 문제 신고