Merge pull request #67 from devansXD/jill-branch3

Design history update

Author: jillru

app/views/design-histories/v4.html

@@ -34,7 +34,7 @@ <h1 class="nhsuk-heading-xl">Wrapping up the alpha phase</h1>
 
     <hr class="nhsuk-section-break nhsuk-section-break--l nhsuk-section-break--visible">
 
-      <p class="nhsuk-body-m"><blockquote>&QUOT;We swept user research transcripts to identify remaining pain points and ensure feedback is reflected in the prototype ahead of handover to the beta team. We also created experimental dashboards and data visualisations to test ways of contextualising search results, as well as a new flow for sharing different types of documents.&QUOT;</blockquote></p>
+      <p class="nhsuk-body-m"><blockquote>&QUOT;We swept user research transcripts to identify remaining pain points and make sure feedback was reflected in the prototype ahead of handover to the beta team. We also created experimental dashboards and data visualisations to test ways of contextualising search results, and a new flow for sharing different types of documents.&QUOT;</blockquote></p>
 
     <!-- ============ THE PROBLEM ============ -->
     <h2 class="nhsuk-heading-l">The problem</h2>
@@ -71,10 +71,10 @@ <h3 class="nhsuk-heading-m">6. Stripped-back homepage content</h3>
     <!-- ============ CONTENT UPDATES ============ -->
     <h2 class="nhsuk-heading-l">Content updates</h2>
 
-    <p>Alongside structural changes, we made a range of content improvements across the prototype informed by user research findings and legal guidance.</p>
+    <p>Alongside structural changes, we made a range of language-focused content improvements across the prototype informed by user research findings and legal guidance.</p>
 
     <h3 class="nhsuk-heading-m">Reducing information density</h3>
-    <p>We further reduced text throughout the prototype, particularly on the homepage and on product and evaluation cards, responding to recurring feedback about feeling overwhelmed by content.</p>
+    <p>We further reduced text throughout the prototype, particularly on the homepage and on product and evaluation cards, responding to recurring feedback that users felt overwhelmed by content.</p>
 
     <h3 class="nhsuk-heading-m">Surfacing personal activity</h3>
     <p>Saved items and recent searches are now more prominently displayed on the search page within a dedicated "Your activity" area, making it easier for returning users to pick up where they left off.</p>
@@ -106,17 +106,21 @@ <h3 class="nhsuk-heading-m">Multiple answers on the uploading page</h3>
     <h3 class="nhsuk-heading-m">Terminology for "evaluation"</h3>
     <p>In some parts of the service, we updated the word "evaluation" to alternative terms such as experience, contribution, and document. Research showed that "evaluation" carries a specific meaning for some users — typically a formal clinical evaluation — that did not always match how we were using the term on the service.</p>
 
-    <h3 class="nhsuk-heading-m">What makes a "good" upload</h3>
-    <p>We began exploring what users need to know to feel confident about what they are sharing, and whether guidance around upload quality would reduce hesitation to submit.</p>
-
     <hr class="nhsuk-section-break nhsuk-section-break--l nhsuk-section-break--visible">
 
     <!-- ============ HOW IT TESTED ============ -->
     <h2 class="nhsuk-heading-l">How it tested</h2>
 
     <div class="nhsuk-inset-text">
       <span class="nhsuk-u-visually-hidden">Information: </span>
-      <p>Testing findings to be added following final research sessions.</p>
+      <p>Final testing sessions revealed some additional insights:</p>
+        <ul>
+          <li>Some users didn't realise there were more sections to explore in the body of the search page.</li>
+          <li>One user wanted to be able to see similar products once they've drilled down to the single product level. For example, when navigating directly to a specific insulin pump, they wanted to see alternatives to be sure of their choice.</li>
+          <li>Users weren't necessarily interested in supplier size or maturity.</li>
+          <li>Users found the visualisations we tested on the search results page interesting in theory but weren't sure about the usefullness of the information presented.</li>
+          <li>Specific mention of "procurement" made at least one clinician feel this service wasn't for them.</li>
+        -</ul>
     </div>
 
     <hr class="nhsuk-section-break nhsuk-section-break--l nhsuk-section-break--visible">