The AXA case: improve the point of entry
The AXA decision-tree form began with a specific observation: Contentsquare analysis showed low engagement with an important product-page form. The page sent people through a CTA into a separate experience. The redesign brought an easy first question into the page itself.
Mobile and desktop prototypes were built in Figma, including progressive steps and micro-interactions. The intention was to make starting feel lighter and preserve continuity with the offer. The project record describes improved engagement and a possible wider rollout, but provides no numerical baseline, traffic segmentation or experiment method.
That limits the conclusion. It is a documented approach to an entry problem, not evidence that every quote form needs an embedded decision tree or that a particular uplift will repeat.
Map the questions before choosing the interface
For a new journey, I would put each question beside the decision it supports. Which answer changes the next step? Which information belongs later? Which term requires a plain-language explanation? Product and operational owners should confirm these dependencies before the interface hides or removes anything.
A branch needs an explicit response to uncertainty. If someone cannot answer, show an appropriate next route rather than encouraging a guess. If changing an earlier answer invalidates later information, explain the consequence and let the person review it.
Be precise about the action at the end. A request for contact, an indicative calculation and a submitted application are different expectations. The page and its button should describe the action the implemented service actually performs. These are proposed design checks; the AXA record does not document every branch or recovery state.
Verify the whole flow, including recovery
The first answer is only the start of the assessment. In a prototype session, ask someone to begin without explanation, change an answer, encounter a relevant validation message and describe what will happen after submission. Include a small-screen route and a participant who does not already know the product vocabulary.
During implementation, keep labels visible and associate them with their controls, following W3C WAI guidance. Check focus, error messages and retained answers in the working form. Visual polish in Figma cannot verify those behaviors.
For measurement, agree the definitions of form start, meaningful progress and successful submission before comparing versions. Note the period, device mix and other page changes. An increase in starts alone cannot establish that more people received a suitable quote or understood their next step.
Your brief
Tick what you can already answer. Unknowns are fine: just name them.
Questions & answers
Is one question per screen always easier?
No. It can make individual steps manageable, but may add navigation and hide the remaining effort. Compare it with grouped questions using the actual task and dependencies.
How much did the AXA form improve conversion?
The portfolio describes increased engagement without a published numerical result or experiment protocol. It does not support a conversion percentage or a causal estimate.
Should the form ask for contact details first?
Decide from the purpose of the journey, operational needs and user expectations. Test whether people understand why details are requested and what will happen next; the AXA case does not establish a universal ordering rule.
Sources & context
- AXA: Decision Tree Form Redesign (2023)
Documents the separate-form handoff, Contentsquare analysis and embedded decision-tree prototypes. The record describes improved engagement without a published numerical baseline or attribution method. First-person project account; the underlying research and analytics are not published here. Checked .
- W3C WAI: Labeling Controls
Primary implementation guidance fetched on 10 November 2026; page states updated 13 May 2024. Used for the association between labels and controls, not to certify any portfolio implementation. Checked .
Find the friction in your quote journey
Send the current flow, what you know about abandonment and the constraints your team needs to keep. We can identify a focused redesign and validation scope.