CRO Mapping: Funnel Map to a 26-Week Testing Plan
13 min read · 2026-11-09
CRO mapping means drawing your conversion funnel and customer journey step by step. You mark where visitors drop out and why, then turn those friction points into a ranked plan of tests and fixes. The map shows you where to work. The roadmap you build from it sets the order of the work, who does it and when each result is due.
In this guide, CRO means conversion rate optimization for websites and apps. It does not mean crop mapping, bird distribution maps or clinical research organizations. The guide covers the whole process: a 26-week testing plan in six phases, a mapping method, and a worked example that scores the same six test ideas with PIE, ICE and TIR. It also gives a week-by-week plan for the first 90 days and a one-page format to win leadership buy-in.
Want this plan built around your own funnel? Generate your roadmap with AI from this guide, then drag and drop the phases, steps and milestones to fit your team and your traffic.
The roadmap at a glance
Goal: Within 26 weeks, map the funnel, build a ranked backlog of evidence-based hypotheses and run a steady testing program with clean tracking, clear owners and results leadership trusts. Duration: 26 weeks
Goals and tracking audit (Weeks 1-4)
Agree on the conversions that matter and make sure you can measure them before you map anything.
- Pick one primary conversion, such as completed purchase, demo request or trial signup, plus two or three micro-conversions on the way.
- Audit analytics: check that each key event fires once, on the right page, with the right values, on every main device and browser.
- Compare analytics totals with your order system or CRM and explain any large gap.
- Write a measurement plan listing every event, where it fires and who owns it.
- Start collecting a clean baseline. We suggest about 30 days, so it covers several full weeks and is not skewed by a single promotion.
Milestone: Measurement plan signed off, and primary conversion counts that match the source system within an agreed tolerance.
CRO mapping: funnel and journey (Weeks 3-7)
Draw the path visitors take and find where and why they leave.
- Build a funnel report by step, device and traffic source to locate the biggest drop-offs.
- Map the customer journey: stages, touchpoints, questions and emotions at each step.
- Watch session recordings and heatmaps on the weakest steps and note repeated friction.
- Run short on-site polls or customer interviews asking what almost stopped them.
- Do a heuristic review of key pages for clarity, trust, speed and form friction.
Milestone: A one-page CRO map listing the top friction points by funnel step, each backed by at least two sources of evidence.
Hypotheses and test backlog (Weeks 6-8)
Turn each friction point into a testable idea and rank the list.
- Write every idea as a hypothesis: because we saw X, we believe changing Y will improve Z for audience W.
- Score each idea with one framework, PIE, ICE or TIR, applied the same way by the same people.
- Check traffic: can the page reach the sample size your testing tool calculates in a reasonable time?
- Sort ideas into tests, quick fixes that need no test, and ideas that need more research.
Milestone: A ranked test backlog in one shared tool, with the first round of tests agreed by the CRO lead and page owners.
Testing setup and first experiments (Weeks 8-13)
Launch the first tests with a process you can repeat.
- Set up or confirm your experimentation tool and run an A/A test to check that traffic splits evenly.
- Write a one-page test plan per experiment: hypothesis, primary metric, guardrails, audience, minimum run time and stop rules.
- Build and QA variants on main devices and browsers, then launch two or three tests on the busiest steps.
- Ship the quick fixes from the map in parallel, outside the testing queue.
Milestone: First tests completed, each with a documented result, decision and learning in the test log.
Steady cadence (Weeks 13-22)
Keep tests running back to back and ship the winners.
- Hold a weekly CRO stand-up on running tests, QA status and the next tests in line.
- Ship winning variants through the normal development process, not only through the testing tool.
- Run follow-up tests on winners and losers to learn why they behaved as they did.
- Update the CRO map each month with new evidence and new pages.
Milestone: Tests running continuously on key funnel steps, and every winner shipped or scheduled in the development backlog.
Review and next roadmap (Weeks 22-26)
Report what the program learned and agree on the next six months.
- Summarize all tests: win, loss or flat, what was learned, what was shipped.
- Re-run the funnel report and compare each step with the baseline.
- Redraw the CRO map for the next round.
- Present a one-page Now, Next, Later roadmap with resources and a target for test velocity.
Milestone: Six-month CRO review shared with leadership and the next roadmap approved.
How CRO mapping works, step by step
A CRO map is two drawings on top of each other. The first is the funnel: the steps a visitor takes from landing to converting, with the number of people at each step. The second is the customer journey: what the visitor is trying to do, what they see, what they doubt and how they feel at each of those steps. The funnel tells you where people leave. The journey tells you why.
You need both. A team that only looks at the funnel ends up testing random changes on the worst step. A team that only draws a journey map ends up with a nice poster and no tests. Put them on one page and every friction point gets a location, a reason and a piece of evidence.
- Define the scope and goal: one primary conversion, one audience or traffic source to start, and the steps between landing and converting.
- Gather quantitative data: funnel drop-off by step, device and source, form field abandonment, page speed and error logs.
- Gather qualitative data: session recordings, heatmaps, on-site polls, support tickets, sales call notes and short customer interviews.
- Map stages, touchpoints and emotions: for each step, note what the visitor needs to know, what they see, and where doubt or effort appears.
- Mark friction points: circle each place where the data and the feedback point to the same problem.
- Turn friction into opportunities: write each one as a short "how might we" question, then as a hypothesis for the backlog.
How to build a CRO test backlog from your map
A backlog is the list of every idea you might test, all written in the same format so you can compare them. Each friction point on the map should produce at least one entry. Each entry needs a hypothesis, the evidence behind it, the page and funnel step, the primary metric and a rough effort estimate.
Keep three lanes from day one. Tests are changes where you are unsure of the result and the page has enough traffic. Quick fixes are bugs and obvious problems, such as a broken postcode field, that you should ship without testing. Research items are ideas you cannot test yet because the evidence is thin or the traffic is too low.
- Hypothesis: because we saw X, we believe changing Y will improve Z for audience W.
- Evidence: the data and feedback from the map, with at least two sources for top ideas.
- Location: page, funnel step, device.
- Primary metric and guardrails: what must go up, and what must not go down.
- Effort and owner: design and development time, and who builds it.
CRO prioritization framework: PIE vs ICE vs TIR
You will always have more ideas than traffic. A scoring framework stops the loudest opinion from winning. Three are common:
- PIE rates Potential, Importance and Ease from 1 to 10. Here we average the three scores.
- ICE rates Impact, Confidence and Ease from 1 to 5, and the scores are added.
- TIR rates Time, Impact and Resources from 1 to 5, and the scores are multiplied. Give a high score when an idea needs little time and few resources.
PIE vs ICE vs TIR on the same six ideas
To see how they differ, here is one backlog for an online furniture store scored three ways. The scores are a worked example, not benchmarks.
- Show a delivery estimate on product pages: PIE 8, 9, 7 = 8.0 (rank 1). ICE 5 + 4 + 4 = 13 (rank 1). TIR 4 × 5 × 4 = 80 (rank 1).
- Shorten the checkout address form: PIE 7, 8, 6 = 7.0 (rank 3, tie). ICE 4 + 4 + 3 = 11 (rank 2, tie). TIR 3 × 4 × 3 = 36 (rank 4).
- Add assembly information near the add to cart button: PIE 6, 6, 9 = 7.0 (rank 3, tie). ICE 3 + 3 + 5 = 11 (rank 2, tie). TIR 5 × 3 × 5 = 75 (rank 2).
- Offer guest checkout: PIE 8, 9, 4 = 7.0 (rank 3, tie). ICE 5 + 3 + 2 = 10 (rank 4). TIR 2 × 5 × 2 = 20 (rank 5).
- Add payment trust badges: PIE 5, 8, 9 = 7.3 (rank 2). ICE 2 + 2 + 5 = 9 (rank 5). TIR 5 × 2 × 5 = 50 (rank 3).
- Redesign the homepage hero: PIE 5, 4, 5 = 4.7 (rank 6). ICE 3 + 1 + 3 = 7 (rank 6). TIR 3 × 3 × 2 = 18 (rank 6).
What the three rankings tell you
All three frameworks agree on the top idea and the bottom idea. They disagree in the middle. TIR pushes cheap ideas like assembly information and trust badges up, because multiplying punishes any low score hard: guest checkout falls to fifth place despite having the highest impact. ICE ranks the shorter address form above trust badges because its evidence is stronger. PIE leaves four ideas almost tied.
The lesson for your CRO plan is to pick the framework that matches your constraint. Choose TIR if development time is your bottleneck, ICE if your team has plenty of ideas but weak evidence, and PIE if you need a simple shared language with stakeholders. Then score every idea with the same people, keep the scores visible, and treat close scores as a prompt for discussion, not a verdict.
Once your top ideas are ranked, they need a place in the plan. Generate your roadmap with AI, then drag the ranked tests into the phases where your team has the time to build them.
Traffic, data and test duration: what your CRO testing plan needs
A test is only as good as the data behind it. As a working method, collect about 30 days of clean data before you set your baseline, so you are not comparing against a week skewed by a promotion or a tracking bug. Run an A/A test after you set up the testing tool to confirm it splits traffic evenly.
Traffic decides what you can test. No single traffic threshold fits every site, because the sample you need depends on your current conversion rate, the smallest lift you want to detect and the number of variants. So let the numbers decide, not a rule of thumb:
- Before an idea enters the queue, run it through your testing tool's sample size or duration calculator with the page's real traffic and conversion rate.
- If the estimated run time is longer than your team can wait, test a bolder change that is easier to detect, test it on a busier step, or move the idea to research.
- Run each test over full weekly cycles, since behavior often differs between weekdays and weekends.
- Set the minimum run time and stop rules before launch, and never stop early because day three looks good.
- Keep a guardrail metric, such as order value or lead quality, on every test.
The first 90 days, week by week
The first quarter decides whether the program gets a second one. Leadership wants proof that the process works, not a list of wins. Plan concrete deliverables every few weeks so progress shows even before tests finish.
Notice that the CRO map arrives before any test. That order protects you: the first tests are chosen from evidence, so even a losing test teaches something you can explain.
- Weeks 1-2: primary conversion agreed, tracking audit done, gaps listed. Deliverable: measurement plan draft.
- Weeks 3-4: tracking fixes shipped, baseline collection running. Deliverable: signed-off measurement plan.
- Weeks 5-6: funnel report, recordings, polls and heuristic review. Deliverable: one-page CRO map with top friction points.
- Weeks 7-8: hypotheses written and scored. Deliverable: ranked backlog and first test plans.
- Weeks 9-10: A/A test, first two or three A/B tests launched, quick fixes shipped. Deliverable: test log started.
- Weeks 11-13: first tests read after their minimum run time. Deliverable: 90-day summary with results, learnings and next tests.
Who owns what in a CRO program
CRO touches marketing, product, design, development and analytics. When nobody owns the program, tests stall in QA and winners never get shipped. Name one CRO lead and agree who does each part of the work before week one.
On a small team, one person may wear several of these hats. That works, as long as development time for tests is booked in the sprint plan and not squeezed in after everything else.
- CRO lead or growth marketer: the roadmap, the backlog, test plans and reporting.
- Analytics lead: tracking, measurement plan, sample checks and result analysis.
- UX researcher or designer: journey mapping, research, variant design and usability checks.
- Front-end developer: building variants, QA and shipping winners to production.
- Page or product owners: approve tests on their pages and own shipping decisions.
- Sponsor: a head of marketing, growth or ecommerce who sets priorities and protects the testing cadence.
CRO milestone tracking and measuring ROI
Track milestones the same way you track tests: each one has an owner, a due date, a status and the evidence that it is done. "Tracking fixed" is not a milestone. "Purchases in analytics match the order system within the agreed tolerance for two weeks" is. Review milestone status in the weekly stand-up and flag anything late before it blocks the next phase.
Measuring return needs care. The headline metric is the conversion rate on your primary goal, but on its own it can mislead. If you add up the lift of every winning test and multiply by annual revenue, you will usually overstate the gain, because effects overlap and fade over time. Show the funnel before and after, revenue per visitor, and the cost of the program in team time and tools.
- Primary conversion rate: on the step being tested, from the testing tool and analytics.
- Revenue per visitor: for ecommerce, so that more orders with a smaller basket show up clearly.
- Guardrails: order value, refund rate, lead quality or activation.
- Test velocity: tests completed per month.
- Win rate and learning rate: share of tests with a clear winner, and share with a documented learning.
- Shipped wins: winning variants live in production, not only in the testing tool.
How to build a CRO roadmap for leadership buy-in
Leaders approve plans they can read in one minute. Put the whole program on one page: the goal, the CRO map in three lines, and a Now, Next, Later view. Now holds the tests and fixes running this quarter. Next holds the ranked ideas waiting for traffic or development time. Later holds bigger bets, such as a checkout rebuild, that need more evidence first.
Under the three columns, add what you need: development hours per sprint, tool costs and the sponsor's role. Then show how you will report: a monthly update with results, learnings and next tests. Promise a process and a review date, not a percentage lift. A plan like that is easier to approve and easier to defend when a test loses.
- Goal: one sentence tied to a business number leaders already track.
- Map: the three biggest friction points, each with its evidence.
- Now, Next, Later: five to eight items in total, no button colors.
- Resources: people, hours and tools needed.
- Review: the dates of the 90-day and six-month reviews.
CRO roadmap vs testing calendar
A CRO roadmap sets direction for months: which funnel areas get attention, what research comes first, how many tests you aim to run and what the team needs. A testing calendar lists the specific tests running this week and next, with launch and end dates.
Keep both, but do not mix them. The roadmap changes once a quarter, when the CRO map is redrawn. The calendar changes every week. If the roadmap turns into a list of button tests, leadership loses the big picture and the team loses focus on the steps that matter.
Your map, backlog and review dates already hold the content of a full plan. Generate your roadmap with AI to lay it out as phases, steps and milestones on a visual canvas. Adjust them with drag and drop, then share the roadmap or export it as an image for your leadership review.
Common mistakes to avoid
- If you test before checking tracking, you cannot trust the results. Audit key events and collect a clean baseline first.
- If you underestimate the time each test takes, the calendar stays half empty. Book design, development and QA hours in the sprint plan before launch.
- If you draw the CRO map once and never touch it again, the strategy drifts away from reality. Redraw it every quarter and update it monthly with new evidence.
- If you stop tests as soon as they look like winners, you get false wins. Write a minimum run time of full weekly cycles and stop rules into each test plan.
- If you test ideas with no evidence, you waste traffic. Tie every hypothesis to a friction point on the map and score it before it enters the backlog.
- If you measure only conversion rate, you can miss drops in order value or lead quality. Add guardrail metrics to every test.
Frequently asked questions
What is CRO mapping?
CRO mapping is the process of drawing your conversion funnel and customer journey, marking where and why visitors drop out, and turning those points into test ideas. It combines funnel data with qualitative feedback such as recordings, polls and interviews. The result feeds a ranked backlog and a CRO roadmap.
What should a CRO plan include?
A CRO plan should include the primary conversion, a measurement plan, the CRO map, a ranked backlog of hypotheses and a testing calendar. Add owners for each part of the work, milestones with dates, and the metrics you will report. A one-page summary for leadership makes it easier to get approved.
Which CRO prioritization framework should I use?
PIE, ICE and TIR all work if the same people apply them the same way. TIR multiplies its scores, so it favors cheap, fast ideas, which suits teams short on development time. ICE includes a confidence score, which helps when evidence is uneven, and PIE is simple to explain to stakeholders.
How long should an A/B test run?
Long enough to reach the sample size your testing tool calculates for that page, and always over full weekly cycles. The right duration depends on your traffic, your current conversion rate and the size of the change you want to detect. Fix the minimum run time and stop rules before launch, and do not stop early.
How do I get leadership buy-in for a CRO roadmap?
Show one page: the business goal, the top three friction points with evidence, and a Now, Next, Later view of tests and fixes. List the resources you need and the dates of the 90-day and six-month reviews. Promise a documented process rather than a specific lift.