What is Object-Oriented User Experience (OOUX)?

A presentation at Lunch and Learn with Sony PlayStation in July 2022 in London, UK by Rik Williams

Slide 1

Slide 1

What is Object-Oriented UX? a a a a a Rik Willi ms, Senior Content Str tegist, Government Digit l Service (GDS) rikwilli ms.net/t lks/ooux/

Slide 2

Slide 2

Hi, I’m Rik

Slide 3

Slide 3

Content Architecture IA User Research Inclusive Design

Slide 4

Slide 4

Structure IA refresher What is OOUX? ORCA process walk through Bene its f Discussion

Slide 5

Slide 5

Information Architecture refresher

Slide 6

Slide 6

“Information architecture is the practice of deciding how to arrange the parts of something to be understandable.” IA Institute

Slide 7

Slide 7

OOUX is a philosophy and method in information architecture (IA)

Slide 8

Slide 8

Slide 9

Slide 9

You’re in front of the donut counter in your local supermarket at 2130 in the evening. What is the information? 🧐🤔

Slide 10

Slide 10

Slide 11

Slide 11

Information ≠ Content ≠ Data

Slide 12

Slide 12

Information is the meaning extracted from a particular sequence of things

Slide 13

Slide 13

Information is what a player understands to be true based what they experience

Slide 14

Slide 14

Content is whatever is being arranged or sequenced for a player to interpret

Slide 15

Slide 15

Data are the facts, observations and questions that a player has about a game

Slide 16

Slide 16

You cannot create information. Instead you make content that is able to be perceived in a way that you hope will be based on what players know

Slide 17

Slide 17

Without thinking about how your content is perceived and the data players might have available, you might not be creating the information intended

Slide 18

Slide 18

“If you’ve ever tried to [play a game] and thought, ‘where am I supposed to go next?’ or ‘this doesn’t make any sense’, you are encountering an issue with an information architecture.” IA Institute

Slide 19

Slide 19

What is OOUX?

Slide 20

Slide 20

Slide 21

Slide 21

fi ft OOUX deliberately aligns so ware to a user’s realworld mental model of concrete, de ned, objects, so that abstract digital worlds can be as naturally intuitive as the physical world we evolved in

Slide 22

Slide 22

OOUX is a philosophy for designing digital systems that respects the fact that people think in objects and need consistent, recognisable objects to understand an environment or product

Slide 23

Slide 23

A mental model is an explanation of someone’s thought process about how something works in the real world

Slide 24

Slide 24

Mental models play a major role in cognition, reasoning and decision-making

Slide 25

Slide 25

Mental models are an overarching term for any sort of concept, framework, or worldview that you carry around in your mind

Slide 26

Slide 26

a f Source: https://www. lickr.com/photos/rik-willi ms/

Slide 27

Slide 27

“‘Object oriented’ in this sense has nothing to do with whether object-oriented programming is used. Instead, it means that the interface as perceived by the user is aligned to the their domain objects rather than to the computer so ware paradigms.” ft a Tom D yton

Slide 28

Slide 28

fl Traditionally, digital product teams breakdown complexity by the verbs — feature, user story, task ow

Slide 29

Slide 29

However, action based architectures can easily become disjointed, confusing and fragmentary

Slide 30

Slide 30

OOUX breaks down complexity by nouns — the tangible things that naturally make up our real and digital worlds

Slide 31

Slide 31

“Object-based thinking is part of human nature” a Everyl Y nkee

Slide 32

Slide 32

“Humans think in objects. Users are human. And so are you.” a a Sophi Pr ter

Slide 33

Slide 33

Slide 34

Slide 34

When a user wakes up in the morning and starts to organise the day, which mental model is more likely? 🧐🤔

Slide 35

Slide 35

Slide 36

Slide 36

Slide 37

Slide 37

“Today I want to wash things” verb-noun thinking

Slide 38

Slide 38

“Today I have “Today I want dog things to to wash!” do” Noun-verb thinking

Slide 39

Slide 39

“Showing users things they can recognise improves usability over needing to recall items from scratch because the extra context helps users retrieve information from memory.” a a R luc Budiu

Slide 40

Slide 40

Dog Cut Style Wash Hair noun-verb thinking Colour Brush

Slide 41

Slide 41

In OO, navigation is centred around objects — nouns, not verbs

Slide 42

Slide 42

Objects are always the primary representations in the interface

Slide 43

Slide 43

Actions (verbs) performed on the objects comprise the tasks

Slide 44

Slide 44

Tasks are secondarily represented by actions on objects

Slide 45

Slide 45

“When users enter a digital environment you designed, you’ll want them to easily be able to answer the simple questions: “What are the things here? Where are the objects? How do they relate to each other? How do they relate to me? What can I do to them?” a a Sophi Pr ter

Slide 46

Slide 46

OOUX is a piece of your existing process (not a new process)

Slide 47

Slide 47

IA Source: Design Council

Slide 48

Slide 48

Source: Sophia Prater

Slide 49

Slide 49

Source: Sophia Prater

Slide 50

Slide 50

Source: Sophia Prater

Slide 51

Slide 51

“OOUX takes user research insights and synthesises them into structure” a a Sophi Pr ter

Slide 52

Slide 52

“Well-de ned leads to well-designed.” fi a Linds y Eryn Sutton

Slide 53

Slide 53

ORCA, a framework to practise OOUX

Slide 54

Slide 54

Slide 55

Slide 55

OOUX seeks to answer the following questions before interaction design/development:

Slide 56

Slide 56

What are the Objects in the users’ mental model? R What are the objects Relationships to each other? C What Calls-to-action do objects o er users? A What are the Attributes that make up the objects? ff O

Slide 57

Slide 57

Round 1: Discovery (uncovering complexity) Object discovery Relationship discovery Call-to-action discovery Attribute discovery Call-to-action requirements Attribute requirements Call-to-action prioritisation Attribute prioritisation Round 2: Requirements (untangling complexity) Object requirements Relationship requirements Round 3: Prioritisation (for users’, for the business) Object prioritisation Relationship prioritisation Round 4: Representation (sketching basic interfaces and interactions) Sketching Prototyping Validation

Slide 58

Slide 58

“The more complex the environment, the more OOUX brings clarity.” a a Sophi Pr ter

Slide 59

Slide 59

“OOUX is a process to get project questions from the future so that there are fewer surprises later in a process.” a a Sophi Pr ter

Slide 60

Slide 60

“It’s like IA and Business Analysis had a genius baby and UX raised it. That’s OOUX.” a a Sophi Pr ter

Slide 61

Slide 61

Working with Objects and ORCA

Slide 62

Slide 62

Objects the t ngible things th t m ke up the users’ ment l model nd/or the business process model Think… People Places Content types Products Services Things a a a … a a • • • • • • •

Slide 63

Slide 63

University Course Expert Subject School Paper Project Building News

Slide 64

Slide 64

Hospit l a Condition Treatment Consultant Location Appointment Research Project Training Course Press Release

Slide 65

Slide 65

Shop Shop Product Seller Buyer Review Collection Blog Policy

Slide 66

Slide 66

Government Minister Statistic Decision Press Release Dept. Report Guide Case Study

Slide 67

Slide 67

Bro dc ster (BBC Food) a a Recipe Chef Show Ingredient Occasion Diet Technique Story

Slide 68

Slide 68

Tangible Recipe Agnostic Durable

Slide 69

Slide 69

Recipe inclusive, gnostic, dur ble, future-proof a a ??

Slide 70

Slide 70

Structure Recipe Instances Purpose

Slide 71

Slide 71

Structure does proto-Object h ve content (title, im ge, video) nd/or met d t (ID, d tes, r ting)? Recipe has Content? has Metadata? Publish da te Title a a a a a a a a a Star rating Image

Slide 72

Slide 72

Instances does proto-Object h ve m ny inst nces in the system, or is it Object Inst nces a a a a a a Object Stencil unique/bespoke design?

Slide 73

Slide 73

Object Stencil a Recipe Object Inst nces

Slide 74

Slide 74

“People don’t care about the containers. They care about the things they contain.” a a a Mike Atherton nd C rrie H ne

Slide 75

Slide 75

🎩 School 🎓 University 🧢 Pub

Slide 76

Slide 76

📱 a Screen 🤖 M chine 📄 Print

Slide 77

Slide 77

Purpose “I want to know how popular a Recipe is before I choose it.” a a a a a a “I want to know how to properly prepare an Ingredient.” “I want to be able to make a copy of the Recipe for my recipe book.” a user would w nt to t ke? a does the object h ve re l/v lid ctions/t sks

Slide 78

Slide 78

“Structuring content within a well-de ned content model makes content scalable, reusable, adaptable, and measurable.” fi a a M xwell Hoffm nn

Slide 79

Slide 79

O Objects

Slide 80

Slide 80

Object Discovery 4 ctivities to ind nd de ine proto-Objects 1. Noun foraging 2. Object Consolidation 3. Object Instancing f a f a 4. Object Lists

Slide 81

Slide 81

“Noun foraging: the process of nding nouns in content, based on both its de nition and its context.” fi fi Me

Slide 82

Slide 82

Slide 83

Slide 83

Recorded interviews, us bility engineering sessions nd text-rich survey d t re gre t sources of prim ry d t Tip: automatic audio transcription services are true game changers. Record in tools like Zoom/Teams, or upload recordings to Otter.ai, Trint and Dovetail etc. a a a a a a a a a a a a a a a A user rese rch interview recorded in udio tr nscription en bled a a User research data Microsoft Te ms meeting with utom tic

Slide 84

Slide 84

PDF A justly m ligned form t, but still strong source of text-b sed nouns Tip: look for domain de nitive PDFs, both from your own organisation, competitors and the world, like: • • • • annual reports user manuals factual advice for users 5-year strategies … a a a a a a a fi f a a a a a An ex mple of vi PDF single dom in de initive d t source, of type typic lly served

Slide 85

Slide 85

Social conversations Use soci l listening d t , or mine d t b se t ble exports from user forums Tip: consider partnering with a social listening agency/partner to get the social data, at the greatest scale from the best mix of sources. a a a a a a a a a a a a a a a Soci l listening d t from 1 million re l convers tions bout termin l dise se

Slide 86

Slide 86

CRMs For ge your customer rel tionship records for nouns they cite when the eng ge with you Tips: • • look for rich content about user experience and user needs, usually captured by textArea form elds. ask your CRM developer for an en bloc export of speci c data, perhaps as CSV. a a a a fi a fi a a a a a A CRM for dementi service — extr ct rich user-centred d t entries t sc le

Slide 87

Slide 87

Content inventories Well formed titles, he dings, met descriptions nd URLs re ll noun sources Tips: look beyond your own website. a a a a a a a An inventory gener ted in 10-mins for Cr te & B rrel using Scre mingFrog Spider a • use machine-built inventories for their speed, scale, accuracy and (meta)data types. I use ScreamingFrog SEO Spider. a •

Slide 88

Slide 88

Project documents P rticul rly useful so th t ‘intern l only’ d t c n be included Tip: a good start point if you’re joining, or specifying, a project at its outset. But note that these are secondary and non user verbatim sources. a a a a f a a a a a a a a f f a A speci ic tion brief for public tender process to ind/select n gency p rtner for Moor ields Eye Hospit l.

Slide 89

Slide 89

Webpages At more th n 50 billion p ges, the WWW is n inexh ustible source! Tip: consider trialling Sketch Engine which can nd and fetch textual data via its automatic corpus builder. It can compile nouns at scale via its:… • • • web search, URLs list, website download (up to 10k pages) …functions. a a a a a a a a fi a a a Look for dom in relev nt sources, like blog posts, rticles, p pers, dvice. Both from your own org nis tion, competitors or the wider web.

Slide 90

Slide 90

a a a a rikwilli ms.net/t lks/m chine-noun-for ging/

Slide 91

Slide 91

Recipe Meal Method Recipe Chef Chef Cook Baker Cuisin ier Program Show Broadca st Podcast

Slide 92

Slide 92

e p i c Re x e d n I f e Ch x e Ind m a r g o r P x e Ind Recipe Chef Program Name (Gingerbr ead men) Name (Delia Smith) Name (Delia’s Christmas)

Slide 93

Slide 93

R Relationships

Slide 94

Slide 94

“You only understand something relative to something you already understand.” a a a Rich rd S ul Wurm n

Slide 95

Slide 95

a Recipe Chef Program Recipe has 1many has 1many has 1 Chef has 1many has 1many has 1many Progr mme has 1many has 1many has 1many

Slide 96

Slide 96

Chef h s 1-m ny Progr mmes h s 1-m ny Chefs h s 1-m ny Recipes h s 1-m ny Chefs Recipe Program h s 1 Progr mme a a a a a a a a a a a a a h s m ny Recipes

Slide 97

Slide 97

Slide 98

Slide 98

C Calls-to-Action

Slide 99

Slide 99

Content Designer User Recipe Rate Favourite Create Delete Print Share Update Review Chef Approve

Slide 100

Slide 100

Slide 101

Slide 101

A Attributes

Slide 102

Slide 102

Recipe Chef Program Name (Gingerbr ead men) Featured? Name (Saturday Kitchen) Lead Image Name (Delia Smith) Lede Rating Score Photo Latest episode Lede Bio Program Chef Recipe Recipe

Slide 103

Slide 103

Slide 104

Slide 104

Slide 105

Slide 105

Slide 106

Slide 106

Slide 107

Slide 107

Slide 108

Slide 108

Slide 109

Slide 109

fi Bene ts of OOUX

Slide 110

Slide 110

user-centred mapping real mental models to content objects creates naturally intuitive digital spaces

Slide 111

Slide 111

content- rst fi fi thinking of data objects forces teams to de ne and validate content, metadata, labels and their interrelationships before moving to interaction design

Slide 112

Slide 112

visible discovering, validating and mapping objects and relationships enable cross-functional teams to understand the proposed system

Slide 113

Slide 113

system-agnostic postponing detailed interface design allows data to be modelled independently of its ultimate contexts of use

Slide 114

Slide 114

sustainable real-world mental models are simple, authentic, and slow to change (vs digital/design)

Slide 115

Slide 115

lower-risk understanding objects, their interrelationships, content attributes and calls-to-action (ORCA) at the outset helps to ‘get project questions from the future’ early so that there are fewer nasty surprises later on

Slide 116

Slide 116

consistent OO thinking enables and informs aesthetic, functional, and internally consistent design in a system. Consistency improves learnability, usability and quality

Slide 117

Slide 117

accessible the consistent predictability of design components reduces cognitive load for everyone, including people with some cognitive impairments

Slide 118

Slide 118

scalable fi the more complex the problem domain, the more lucidity, coherence and consistency the ORCA process can bring by detangling/de ning requirements for the product(s) and/or the project team

Slide 119

Slide 119

e cient ffi decreases the need for work (and re-work)

Slide 120

Slide 120

serendipitous fi fi it creates inherently discoverable, usable and relevant heterarchical relationships between instances of objects. This enables people to nd unanticipated, but highly pertinent, content/results during their search and way nding

Slide 121

Slide 121

fi fi Role-speci c bene ts of OOUX

Slide 122

Slide 122

researcher-friendly synthesising research insights into an OO structure will expose high-risk assumptions/questions early

Slide 123

Slide 123

writer-friendly gives content designers early engagement in the design thinking process and provides them with visibility to the types and scale of content that might need designing and governing

Slide 124

Slide 124

content architect-friendly breaking data into its fundamental components helps ‘make sense of mess’ by wrangling complexity into understanding. This is particularly true if data/content is missing, duplicated, distributed or devolved across a system, siloes or organisation

Slide 125

Slide 125

designer-friendly provides a methodology of identifying objects which will need patterns in any design system and a framework for organising and governing it as the product/service develops over time

Slide 126

Slide 126

developer-friendly many coders already use Object-Oriented Programming (OOP) approaches and architectural decision records. Collaborating with a shared model for data can help join-up design with development and create better projects/models

Slide 127

Slide 127

business analyst-friendly the ORCA process helps BAs understand the system domain, its complexity, likely requirements and dependencies. In turn, this helps them to accurately forecast and monitor resources, budgets and risks for the project

Slide 128

Slide 128

consultant-friendly the ORCA process, is an excellent way to collaborate with clients and stakeholders. Socialising decision making improves the quality of the product/service and makes for happier project teams

Slide 129

Slide 129

What OOUX can’t do

Slide 130

Slide 130

detailed interface/interaction design fi ft it will help de ne calls-to-action for objects, but not what happens a er they’re used. Similarly, it can inform, but not create, interface design patterns

Slide 131

Slide 131

creating front-end content design fi it will de ne and scope the types of content and metadata needed, their hierarchies, relationships, and some labels. But it won’t deliver the outputs of detailed UX writing, media creation and broader aspects of a content strategy

Slide 132

Slide 132

representing every object fi whilst OOUX and OOP support each other, developers will still need to factor for, and de ne, additional objects in their code and databases

Slide 133

Slide 133

designing one-of-a-kind items fi fi factoring for facets of an object, like calls-to-action, content and metadata can help de ne single instance designs. However, the real bene t of OO thinking is at the system scale

Slide 134

Slide 134

Feedback

Slide 135

Slide 135

“Design depends on critique as an engine.” a D n Brown

Slide 136

Slide 136

rikwilliams.net/talks/ooux/

Slide 137

Slide 137

A cheeky plug…

Slide 138

Slide 138

a a a Join/spe k with us t: meetup.com/rese rchthing/

Slide 139

Slide 139

Discussion