Slides from Martina Welander and myself's workshop at UX Bristol 2016. This workshop looked at how domain, content and data modelling play a key part in creating brilliant user experiences.
Scaling your ideas to create better experiences
Bonny Colville-‐Hyde & Martina Welander
User Experience Architect
at Immediate Media
Give you a basic understanding of how structured data
can scale to support product development
-‐ and -‐
Understand the role you can play as a UX to ensure the
information stored in your product databases meet user
1. Scaling over time: Products always change
2. Intro to Service Oriented Architecture
3. Understanding domains and content
4. Problems with structuring content
5. Communicating data requirements
are Guaranteed to Change
lies in it’s data model
way we understand relationships
between pieces of information
Service Oriented Architecture!
Each team will become its own Service Oriented
Within each team, you will split into roles following
the instructions in your team pack
You’ll either play the part of a user, an interface, a
service or a database
points to consider about
queries the user can request
information from the database if
it exists and is Aindable
meaningfully if the database is not
content modeled with
users in mind
planned and structured to
ensure all the data needed for
the interface & user is present
experiences, we have to understand and
communicate our audience’s data
requirements so they can be built
database: it’s just hard work
free text search?
a silver bullet
u Natural language is very dif`icult to build for, and is
probably beyond the scope of our teams (unless you
work for a super power like Google)
u The computing power required to do this well is also
beyond the scope of your server budgets due to the
u If its done poorly it’s a dreadful user experience
Understanding Content &
“Our CMS comes with built in
tags and categories:
we’ll use those”
a review of Madonna’s 1985 single
‘Into The Groove’
In your teams write out how you could tag
and categorise this review.
u Small sites (under 2000
u One language
u One / very few editors
u Static content that
doesn’t need to be used
beyond the page its on
NO / BEWARE!:
u Medium sites and larger
(or those likely to grow)
u More than one language
u Multiple editors
u Need to extend or
syndicate content into
Modeling: First Steps
u What are the users doing?
u What information do they need to access?
u What information do they need to store?
u What information do they need to cross reference?
u What are the constituent parts of that information?
u What relationships do different types of information have
with each other?
u How is information linked together?
u Where does the information come from?
u What limitations does the information have?
Mapping and Communicating
Relationships between Data
In your groups, work together to map the content and
information associated with music albums
Use a post it note to deAine each of the constituent
pieces of information (data)
Draw lines to link together the data relationships e.g:
singles belong to an album (e.g: ‘Artist’ <-‐-‐-‐-‐> ‘Album’)
in the Real World
You need a domain expert and a database expert –
this is not something to do on your own – it’s a team
u Work with your domain expert and content creators to
understand the domain
u Talk through what you learn with your developers: don’t
chuck documentation at them
u Be patient: this is a collaborative process
u Expect to be confused
u Work on paper and whiteboards
u Don’t try to design the database!
What happens if you produce wireframes or prototypes
for your developers and you’ve not modeled the
domain, the content or data?
How can a developer understand the relationships
between information in a domain on a wireframe if you
have not explained them?
And how can a developer plan and structure a data
model to support future growth if you’ve not
Linear Color Icons: Designed by Freepik and distributed
Database Essential Icon: Designed by Madebyoliver and
distributed by FlatIcon