<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Report Archives - davehone.com</title>
	<atom:link href="https://davehone.com/tag/report/feed/" rel="self" type="application/rss+xml" />
	<link>https://davehone.com/tag/report/</link>
	<description>Design portfolio</description>
	<lastBuildDate>Mon, 30 Mar 2026 02:12:32 +0000</lastBuildDate>
	<language>en-AU</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Optimising shopping cart experience</title>
		<link>https://davehone.com/quantitative-design-research-case-study/</link>
		
		<dc:creator><![CDATA[Dave]]></dc:creator>
		<pubDate>Mon, 21 Jun 2021 02:57:54 +0000</pubDate>
				<category><![CDATA[Case studies]]></category>
		<category><![CDATA[Corporate]]></category>
		<category><![CDATA[Product design]]></category>
		<category><![CDATA[Report]]></category>
		<category><![CDATA[Research]]></category>
		<guid isPermaLink="false">https://davehone.com/?p=1672</guid>

					<description><![CDATA[<p>How to keep the development squad moving with quantitative design evaluation</p>
<p>The post <a href="https://davehone.com/quantitative-design-research-case-study/">Optimising shopping cart experience</a> appeared first on <a href="https://davehone.com">davehone.com</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="has-text-align-center lead">Keeping customer insights flowing with quantitative evaluation</p>



<p class="has-text-align-center">I was asked which of two shopping cart designs was more likely to meet user needs. A live test wasn&#8217;t practical, so I needed data to inform a high-risk decision.</p>



<div class="wp-block-group section-dark text-center"><div class="wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow">
<h2 class="wp-block-heading has-text-align-center">The challenge</h2>



<ul class="pillars make-row-4 hide-me sequence-me wp-block-list">
<li><i class="pillar-icon fa-clock"></i>Inform an urgent decision with customer preferences</li>



<li><i class="pillar-icon fa-balance-scale"></i>Evaluate usability of two shopping cart design options</li>



<li><i class="pillar-icon fa-project-diagram"></i>Assess how usability and journeys were impacted</li>



<li><i class="pillar-icon fa-signal"></i>Measure preferences and report on significant inferences</li>
</ul>
</div></div>



<p class="lead">I proposed a robust and achievable research plan to support a redesign of a shopping cart. When the need arose for unplanned research, I needed a way to get more customer insights and keep the rest of my schedule intact.</p>



<p>Urgent unplanned work is not ideal, but when new discoveries raised important questions, I needed to adapt my plan. Although qualitative activities could have given us more depth, they would have disrupted my scheduled activities, inconvenienced participants and exceeded my budget. Quantitative, unmoderated research was an achievable and effective way to get a &#8216;quick read&#8217; of categorical preferences.</p>



<p>As part of a broader research program that included multiple research methods, planning a contingency for quantitative design evaluation got the best outcome for the project.</p>



<p>The question, &#8220;Which of these two design concepts will we develop?&#8221;, could have been researched using multiple methods but the question was one of probability. Which design, A or B, was most likely to meet user needs?</p>



<h3 class="wp-block-heading has-text-align-center">The problem to solve</h3>



<ul class="sticky-notes small pillars make-row-4 hide-me sequence-me wp-block-list">
<li><div class="card-body red-sticky"><i class="pillar-icon fa-question"></i>Design axioms (rules of thumb) and customer feedback indicated two potential design solutions (A or B)</div></li>



<li><div class="card-body red-sticky"><i class="pillar-icon fa-question"></i>Both designs (A and B) followed reasonable practice and weaknesses were not immediately obvious</div></li>



<li><div class="card-body red-sticky"><i class="pillar-icon fa-question"></i>Axioms for simplicity and affordance when taken to extremes, appeared to conflict</div></li>



<li><div class="card-body red-sticky"><i class="pillar-icon fa-question"></i>Preferences were important and experience (not price alone) was driving channel value</div></li>
</ul>



<h3 class="wp-block-heading has-text-align-center">Approach</h3>



<ul class="sticky-notes small pillars make-row-4 hide-me sequence-me wp-block-list">
<li><div class="card-body green-sticky"><i class="pillar-icon fa-check"></i>Participants used a mobile prototype to perform tasks and answer questions on their own device</div></li>



<li><div class="card-body green-sticky"><i class="pillar-icon fa-check"></i>300 participants were split into two balanced cells with similar characteristics, and each cell rated one design</div></li>



<li><div class="card-body green-sticky"><i class="pillar-icon fa-check"></i>Non-parametric tests found statistically significant differences in how the designs were rated</div></li>



<li><div class="card-body green-sticky"><i class="pillar-icon fa-check"></i>Results were shared quickly, followed by a report and a solutions workshop</div></li>
</ul>



<div class="wp-block-group section-dark text-center"><div class="wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow">
<h2 class="wp-block-heading has-text-align-center">Key takeaways</h2>



<p>Lessons learned from what worked well with this approach:</p>



<ul class="pillars make-row-4 hide-me sequence-me wp-block-list">
<li><i class="pillar-icon fa-gift"></i>Planning contingency allowed me to accommodate new discoveries and support innovation</li>



<li><i class="pillar-icon fa-hat-cowboy"></i>Quantitative unmoderated usability testing gave insight on journeys, not just interfaces</li>



<li><i class="pillar-icon fa-signal"></i>Statistical tests identified statistically significant customer preferences</li>



<li><i class="pillar-icon fa-user-clock"></i>Results gave the project confidence and the direction they needed to support decisions</li>
</ul>
</div></div>



<h2 class="wp-block-heading has-text-align-center">Report</h2>



<p>The report drew conclusions by analysing closed-question responses (what responses participants chose) with sentiment analysis of free-text responses (why they chose that), and a statistical test on how customers rated each design (A or B).</p>



<p>Non-parametric tests were used to report on statistical significance of preferences. This analysis was the first step of an ongoing optimisation experimentation program, and the methods evolved after live experimentation capability was deployed.</p>



<p>It&#8217;s important to note that although analysis revealed a statistically significant result by comparing 2 variations, and did so at the early stages of design before development, that this experiment wasn&#8217;t concluded until an uplift was observed in production.</p>



<div class="wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-16018d1d wp-block-buttons-is-layout-flex">
<div class="wp-block-button wp-block-buttons downloads"><a class="wp-block-button__link wp-element-button" href="/download/1714/?version=1-0">Read analysis report (PDF 1.2Mb)</a></div>
</div>
<p>The post <a href="https://davehone.com/quantitative-design-research-case-study/">Optimising shopping cart experience</a> appeared first on <a href="https://davehone.com">davehone.com</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
