Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Statistically significant taxonomy
Search
Matt Jukes
February 18, 2017
Technology
140
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Statistically significant taxonomy
Talk at World Information Architecture 2017 in Manchester by Jonathan Porton and myself.
Matt Jukes
February 18, 2017
More Decks by Matt Jukes
See All by Matt Jukes
Roadmaps and Missions for the Scottish Digital Academy
jukesie
0
1.3k
A ChatGTP Christmas Quiz
jukesie
0
410
Jukes - User Manual
jukesie
0
160
my adidas
jukesie
1
450
This is a team sport
jukesie
0
530
Working in the open works
jukesie
1
76
Digital is a team sport
jukesie
0
650
The importance of being open
jukesie
1
96
The Wrong Users?
jukesie
0
640
Other Decks in Technology
See All in Technology
AIで仕事のやり方を変える
matsu7874
3
1.1k
AI時代だからこそ、スケールしないことをやろう
yutashigemura
1
140
「図書館」という名前のままでいいのか -Code4Lib JAPANカンファレンス2026 アンカンファレンス報告- / Code4Lib JAPAN Conference 2026: Unconference Report
ykiyota
0
160
OpenTelemetryのメトリクスをCloudWatchに送ってPromQLで見てみた
ota1022
0
120
enechainの内製セルフサービスプラットフォーム
hiyosi
0
160
Redmine 7.0で私が開発した新機能の狙いと背景
vividtone
1
160
From Vanilla Kubernetes to a Batteries-Included Platform: Developer Experience at 1,300+ Clusters
yosshi_
0
680
Snowflakeのコスト最適化を支えるアーキテクチャ設計
ktatsuya
1
1.5k
家のリアーキテクト・リファクタリング
suguruooki
0
110
薬剤師(ドメインエキスパート)と一緒に育てる薬局向けAIアシスタント
kakehashi
PRO
2
150
アリアドネの糸と、20年ごとの建て替え ── 長尾真『電子図書館』を、伊勢で読み直す / Rereading Makoto Nagao’s "Electronic Library" in Ise
ykiyota
0
160
AI時代のAPI品質を支えるガードレール / API Guardrails for API quality in the AI era
yokawasa
1
220
Featured
See All Featured
Future Trends and Review - Lecture 12 - Web Technologies (1019888BNR)
signer
PRO
0
3.7k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
31
3.4k
Scaling GitHub
holman
464
140k
sira's awesome portfolio website redesign presentation
elsirapls
0
410
svc-hook: hooking system calls on ARM64 by binary rewriting
retrage
2
570
The Curse of the Amulet
leimatthew05
2
14k
Paper Plane (Part 1)
katiecoart
PRO
1
11k
Taking LLMs out of the black box: A practical guide to human-in-the-loop distillation
inesmontani
PRO
3
2.4k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
17k
RailsConf 2023
tenderlove
30
1.5k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
23k
Impact Scores and Hybrid Strategies: The future of link building
tamaranovitovic
0
440
Transcript
A statistically significant taxonomy.
Matt Jukes ..formerly known as ‘Head of Product, Office for
National Statistics’
Jonathan Porton ..formerly known as ‘UX Architect, Office for National
Statistics’
1.What we faced 2.What we did 3.What we learned 4.Questions
1.What we faced 2.What we did 3.What we learned 4.Questions
The Office for National Statistics is the UK’s largest independent
producer of official statistics. @jukesie @iauxbod
The website gets approximately 500,000 visitors per month. @jukesie @iauxbod
The website had approximately [shed loads] pages & documents. Publishing
an additional [boat loads] a week. @jukesie @iauxbod
The annual list of baby names is the single most
popular release. @jukesie @iauxbod
@jukesi e @jukesi e @jukesie
The site was called “..a national embarrassment” in the
Financial Times. @jukesie @iauxbod
@jukesi e According to the Parliamentary Administration Select Committee; “The
Office for National Statistics website makes figures hard to find and statistics are often presented in a confusing way..” @jukesie @iauxbod
A respondent to the website satisfaction survey ended their response
“The ONS website makes me want to cry..” @jukesie @iauxbod
The previous taxonomy for the website had 1400 categories that
went down five levels. @jukesie @iauxbod
A number of the categories were in fact empty and
reflected statistical publications that the ONS did not actually publish. @jukesie @iauxbod
The site search was referred to as like “..using
Google on LSD” @jukesie @iauxbod
1.What we faced 2.What we did 3.What we learned 4.Questions
We had to persuade a risk-averse organisation to trust us.
@jukesie @iauxbod
Outlined and agreed the approach and methodology with ONS methodology
team. @jukesie @iauxbod
Web analytics - analysis to identify patterns within the taxonomy
@jukesie @iauxbod
None
Previous research - reviewed every minute of every usability test
conducted on the website. Not the binge watch of choice! @jukesie @iauxbod
Competitor analysis - just as applicable as private sector organisations.
Lots of mini standardisations, but no real consistency @jukesie @iauxbod
Content audit - what was there, why was it there
and how the hell did it get there? Reviewed and consolidated structure and content. @jukesie @iauxbod
Card sort - closed, compromised and complicated. Yet still a
step forward. 200 participants, moderated and unmoderated. @jukesie @iauxbod
Tree tests - proposed vs status quo and benchmarking the
hell out of things. 100+ participants, moderated and unmoderated. Tested and iterated...a lot @jukesie @iauxbod
None
None
None
The new (not quite a) taxonomy for the website has
173 categories and three levels. @jukesie @iauxbod
1.What we faced 2.What we did 3.What we learned 4.Questions
Everyone has a plan until they get punched in the
mouth. Mike Tyson
Real life gets in the way of implementing research no
matter how comprehensive. @jukesie @iauxbod
There was consensus as to what made up the main
navigation categories - unfortunately nobody agreed what fitted under them. @jukesie @iauxbod
Usability tests on live website show top level is essentially
surplus to requirements. Exposing the 2nd level makes the user’s life so much simpler! @jukesie @iauxbod
Content confuses as often as clarifies and specialised terminology is
a burden even to expert users. @jukesie @iauxbod
In removing friction from publishing we had failed to capture
sufficient metadata. This became a major issue. @jukesie @iauxbod
Internal politics creep back in and the requirements of the
‘business’ start to crowd out the needs of the user. @jukesie @iauxbod
If I had my time again...
None
It should have been an open card sort.
1.What we faced 2.What we did 3.What we learned 4.Questions
@jukesi e Thanks. @jukesie and @iauxbod