diff --git a/.azad/.locked-paths b/.azad/.locked-paths index 07b119f..2f75ad9 100644 --- a/.azad/.locked-paths +++ b/.azad/.locked-paths @@ -1,6 +1,5 @@ [ "/Users/davidevans/Documents/Projects/procurement-prototype/app/views/current/search-results.html", "/Users/davidevans/Documents/Projects/procurement-prototype/app/views/current/create-account/email-verification.html", - "/Users/davidevans/Documents/Projects/procurement-prototype/app/views/current/create-account/email-welcome.html", - "/Users/davidevans/Documents/Projects/procurement-prototype/app/views/design-histories/v3.html" + "/Users/davidevans/Documents/Projects/procurement-prototype/app/views/current/create-account/email-welcome.html" ] \ No newline at end of file diff --git a/app/assets/images/dh-4-a-z-page.png b/app/assets/images/dh-4-a-z-page.png new file mode 100644 index 0000000..02d383b Binary files /dev/null and b/app/assets/images/dh-4-a-z-page.png differ diff --git a/app/assets/images/dh-4-product-page.png b/app/assets/images/dh-4-product-page.png new file mode 100644 index 0000000..6998351 Binary files /dev/null and b/app/assets/images/dh-4-product-page.png differ diff --git a/app/assets/images/dh-4-search-category.png b/app/assets/images/dh-4-search-category.png new file mode 100644 index 0000000..69b23cb Binary files /dev/null and b/app/assets/images/dh-4-search-category.png differ diff --git a/app/views/design-histories/v3.html b/app/views/design-histories/v3.html index b5458c3..e5145ea 100644 --- a/app/views/design-histories/v3.html +++ b/app/views/design-histories/v3.html @@ -20,29 +20,29 @@

Information architecture

Designing search for four modes of information seeking

Based on Donna Spencer's framework

- +

The problem

Our original search page failed to support the different ways NHS procurement users seek information. Some users know exactly what they want, others are exploring options, some don't know what questions to ask, and others are trying to find something they've seen before.

- +

Design solution

-

We restructured the search page to support all four information-seeking modes:

+

We restructured the search landing page to support all four information-seeking modes:

- +

Key insight

-

Procurement users often think they're doing known-item search ('I need product X') but actually need exploratory support ('what are trusts finding works?') or guidance ('what evidence should I even care about?'). The page now supports all paths without forcing users to self-identify.

+

Procurement users often think they're doing known-item search ('I need product X') but actually need exploratory support ('what are trusts finding works?') or guidance ('what evidence should I even care about?').


Category results page for exploratory users

- +

The problem

When users selected a category to explore (e.g. 'Wound care'), we needed a results page that supported discovery rather than just listing products.

- +

Design solution

We designed the category results page with:

- -

Rationale

-

Exploratory users' needs change as they discover. The page supports the journey from 'what's out there?' through filtering, scanning trust adoption, to selecting products for comparison.

-
+ + - -

Product pages

+
+
+
+ image of the search by category landing page +
Search by category page iteration
+
+
+
+
+ image of the category A to Z page +
Category A-Z page: not yet tested
+
+
+
-

Leading with trust adoption visibility

- -

The problem

-

User research revealed NHS procurement professionals rely heavily on informal personal networks to discover what other trusts are procuring. Our initial product page design followed a conventional pattern: supplier branding and marketing content at the top, trust evaluations buried lower as supporting content. This didn't reflect how users actually make decisions.

- -

Design solution

-

We restructured product pages to prioritise peer intelligence:

-
    -
  1. Trust adoption section moved to hero position: '12 NHS trusts have evaluated this product' with outcomes (9 procured, 2 under review, 1 excluded)
  2. -
  3. Featured contact cards: 'Sarah is happy to discuss: implementation, clinical outcomes, supplier experience'
  4. -
  5. 'How they evaluated' sections: Shows process, business case approach, and decision factors
  6. -
  7. Evaluation type badges: Clinical trial, pilot study, usage report, quick review
  8. -
  9. Technical details collapsed: Specifications and cost analysis in expandable accordions
  10. -
- - -
+
+
+ +

Rationale

+

Exploratory users' needs change as they discover. The page supports the journey from 'what's out there?' through filtering, scanning trust adoption, to selecting products for comparison.

-

What else we changed

+
- +

What we kept

Supplier contact card in sidebar, technical specs in accordion, cost details in accordion, contact details in cards with discussion topics.

+
+ image of the product page with new charts and regional breakdown +
Product page with data visuuals and contact details
+
+
-

Content design

+

Content design

-

At this stage, a content designer performed a content review and made minor changes based on insights from user research transcripts, discussions about service functionality with team members, GDS content design guidelines and NHS style guidelines.

+

At this stage, a content designer performed a content review and made minor changes based on insights from user research transcripts, discussions about service functionality with team members, GDS content design guidelines and NHS style guidelines.

-

This included:

- +

This included:

+

User research

Selected user research insights

-
-{% endblock %} \ No newline at end of file +{% endblock %}