Adoption and appropriation are about actually getting things used. You might have the most amazing design that is useful, usable and has glorious user experience, but f no-one actually uses it, your work is in vain. Adoption is about the first hurdle, moving from not be used to being used, from no users to any users. Crucially it is about understanding that there is a path between the two and thinking about the path, the route to use, as much as the end point, when it is being used. Part of this is about effective marketing, but for digital products the design can be critical, leveraging connections between users and products and creating zero-point value – the gain for the very first user. Appropriation comes later, when the product is being sued and users find things to do with it that you never expected. Designing for unexpected uses sounds like an oxymoron, but in fact there are strategies that make it more likely your users can be creative with your creation.

1. designing to be used:
adoption and appropriation
Alan Dix
www.alandix.com
www.hcibook.com/e4/

2. three use words
useful
– functional, does things
usable
– easy to do things, does the right things
• used
– attractive, available, acceptable to organisation
used
– attractive, available, acceptable to organisation
including ongoing experience

3. adoption
– getting initially used
appropriation
– getting eventually USED

4. dynamics of use
no use
use
personalised
use disuse
useful
usable
adoption
appropriation

6. designing for adoption

7. managing the path
marketing life cycle: ‘early adopters’, etc.
how ‘design’ it in
just think
no use
use
easy to
focus here
think about
the whole path

8. if you are big
just stick it in the OS (Microsoft, Apple)
or stick it on your web site (Google, Yahoo!)
does NOT guarantee use
(e.g. Apple OpenDoc, automator)
… but it does help ;-)

9. if not …
you have to think harder!

10. if you want someone to do something …
make it easy for them!
understand their values

11. designing for value
people use something
ONLY IF
it has perceived value
AND
value exceeds cost
BUT NOTE
exceptions (e.g. habit)
value NOT necessarily personal gain or money

12. weighing up value
value: helps me get my work done
fun
good for others
cost: download time
money £, $, €
learning effort

13. in economics Net Present Value:
discount by (1+rate)years to wait
in life people heavily discount
both future value and future cost
hence resistance to learning
so ... need low barriers
and high perceived present value
value depends on time

14. value depends on other people
network effects
value of Word for ME
is higher if YOU have it too
critical mass (Grudin)
 reduce initial cost
 increase initial value
 find cliques

15. different kinds of people
– market ecologies
critical isues: – fan-out (gain)
– feedback loops (exponential growth)
– adding paths (information prodicts)
teachers
parents
children

16. design guidelines …
• think about the path
• increase zero point value
• identify cliques
• understand relationships
• create community value
• leverage existing products
see also
Andy Cockburn’s
PhD thesis

18. designing for appropriation

19. dynamics of use
no use
use
personalised
use disuse
useful
usable
adoption
appropriation

20. what is appropriation?
personalised use
using something in a way the designer didn’t intend
both physical and digital

22. photo: Ken Banks, kiwanja.net

23. motivation
appropriation seen in many studies
growing literature
Paul Dourish lots, also Jennie Carroll (RMIT, Melbourne),
various workshops, Illyenkov (cultural timescale)
… but hard to find explicit guidance

24. why appropriation?
+ situatedness – every environment different
+ dynamics – environments and needs change
+ ownership – feelings of control, pride
? subversion

25. design for appropriation ?
≈ design for the unexpected
an oxymoron?

26. design guidance
• allow interpretation
• provide visibility
• expose intentions
• support not control
• plugability and configuration
• encourage sharing
• learn from appropriation

27. example - onCue
suggestions based on clipboard
observed use:
– open blank temp doc
– type in words
– do ‘copy’
– use onCue
– discard temp doc
learn from appropriation
redesign had pop-down type-in area
approp

28. example – prototyping tools
tools are great at prototyping screens …
figma.com

29. example – prototyping tools
… but ignore context
https://www.samsung.com/us/explore/family-hub-refrigerator/

31. design idea 1
every frame has screen + context

32. design idea revised
allow multiple viewpoints
user 1’s screen + user 2’s screen
phone + laptop
screen + context
fridge + its screen + phone-app + user in chair …
support not control

33. .. so
you can design for appropriation
often seems trivial but really powerful
needs humility

35. … and now …
Web … community content + mashups
adoption = appropriation?
what about end-user mashups
(not just the techie ones!)
UI + infrastructure issues (e.g. local resource URIs)
mashups in the home?
(hard enough with wires!)
not just usability - Green agenda too

36. summary
useful and usable not enough
things need to be used
adoption – from no use to use
think path
appropriation – from use to personal use
think enable
maybe coming together?