Improving conversion is a diagnostic process

diagnostic.PNG

Showing up to a new project with a bunch of ideas on how to improve things is a strong indicator that someone doesn’t know what they are doing. Comparable to a doctor performing surgery before asking what the problem is.

Improving conversion starts as a diagnostic process.

Diagnostic information typically comes from three places:

Analytics can include all the data you get from Google Analytics or a similar platform. How long people are spending on your site, goal completion rates, where they are dropping off, that kind of stuff. Then there is the more functional aspect to analytical data, like page speed problems, bugs associated with different browsers, server downtime, etc. Broadly speaking, analytical data is about observing what people do in aggregate.

Then there’s user testing. User testing is about observing what individual people do. This can be done in-person or remotely. You give people specific tasks to complete and then watch how well they do and where they get stuck.

Finally, there is qualitative research. This encompasses things like pop-up polls, email surveys, customer interviews, public reviews and live chat interactions (the data your customer support team is already collecting).


All this came from a free course on research-driven optimization by Peep Laja over at CXL. They categorise the above differently but it’s the same idea.

If you’d like to read more posts about conversion optimisation you can follow me on twitter @joshpitzalis.

This is post 1 in a series. The rest of the posts are listed here.

 
8
Kudos
 
8
Kudos

Now read this

Redux Observable Loops

You can make redux complicated but at the most fundamental level, you have a view layer that lets you fire actions that can update the state. There is middleware and actions hit reducers which update the store, but let’s consider those... Continue →