Customer Journey Map: See the Experience, Find What to Fix

マーケティング・営業

Customer Journey Map: See the Experience, Find What to Fix

For the team improving a service, opened when you need to find where the experience breaks down. The centre of the whiteboard is a grid of five stages, from awareness to growing use, crossed with actions, feelings, touchpoints, and fix ideas; around it sit a frame for the persona and scope, a quadrant for ranking fixes by impact and effort, and a frame for the evidence behind each cell. The task board runs from research to mapping to choosing fixes, and starts with four parent tasks - scoping, gathering input, filling the map, and acting on the gaps - each with its own subtasks.

0 いいね 0 コピー 作者: WeProcess
customer journey customer experience UX research personas touchpoints
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 Customer Journey Map: See the Experience, Find What to Fix

ホワイトボード プレビュー

1. Whose Experience, and How Much of It 2. The Journey (stage by lens) 3. Which Fix First (impact vs effort) Plan it in (hard, high impact) Do it now (easy, high impact) Leave it (hard, low impact) Batch it (easy, low impact) 4a. Where each fact came from 4b. The lowest point 4c. What we want to test 4d. Next three to start Customer Journey Map How to use: 1. Pi... Goal & scope Ground rules Pain points &... Insights & ideas PersonaExample: a director at a 30-person studio who keeps the team's projects on schedule. ScopeExample: three months, from first hearing about us to the team using it without being asked. Questions to answerExample: where do people drop off? What confuses them in the first week? Evidence we'll useExample: 5 interviews, 3 months of tickets, usage data. Don't fill cells from memory. Awareness Comparison Signing up First use Growing use Actions Ex: searches "team task tracker" and finds an article Ex: opens three pricing pages and builds a comparison table Ex: signs up on the free plan and writes an internal case Ex: creates the first project and invites two people Ex: rolls it out to another team and moves to a paid plan Feelings Hopeful ↗Ex: "this might stop things slipping" Stuck →Ex: "they all look the same to me" Nervous ↘Ex: "will this get approved, can we back out" Encouraged ↗Ex: "that came together faster than I expected" Settled →Ex: "we're probably not using half of it" Touchpoints Search results / referrals / social / review sites Pricing page / feature list / customer stories Signup form / quote / terms of service First-run guide / help docs / support Monthly summary / product news / invoices Fix ideas Ex: a three-minute overview page for people arriving from search Ex: a comparison table on the pricing page so choosing takes less time Ex: a one-pager they can hand straight to their approver Ex: a day-7 message covering the settings people trip on Ex: highlight one unused feature per month 縦軸: Impact on the... Worth doing, but not this week. Put it in the quarter plan with an owner and a date. Top priority. Assign it this week. Wording changes and better guidance usually land here. Not this round. Leave one line saying why so the debate doesn't restart later. Clear these together when there's slack. Mostly small copy and navigation fixes. Interviews: 5 people in March (notes linked on the card) Tickets: last 3 months, already grouped by stage Usage: __% create a project within 7 days Recolour any cell that is still a guess Ex: signing up - the internal case stalls and goes quiet Ex: first use - invited teammates never show up Pick one low point and stay on it Ex: an approval one-pager lifts paid conversion Metric: free to paid rate (now __%) Deadline: measure the same number in four weeks 1. ____________ (owner: ______) 2. ____________ (owner: ______) 3. ____________ (owner: ______)
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Research Backlog 16件

Set the scope
Gather real input
Fill in the map
Act on the gaps
Pick one persona
Bound the journey
List key questions
Talk to five users
Sort support tickets
Check usage data
Map steps & channels
Chart the emotions
Flag the low points
List fix ideas
Rank by effort
Set success metrics

Gathering Input 0件

Mapping 0件

Choosing Fixes 0件

Done 0件