►
From YouTube: The Future of Web3UX - a Paradigm Shift for a Better Collaboration between Design and Development
Description
Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on IPFS and more.
https://archive.devcon.org/archive/watch/6/the-future-of-web3ux-a-paradigm-shift-for-a-better-collaboration-between-design-and-development/index
70% of UX design on Ethereum is defined within the Smart Contracts. So why are so few UX experts involved in Smart Contract design? It’s time for a shift towards better crypto UX.
The future of a better web3 UX will rely heavily on a paradigm shift. The necessity of change in the way we work and the way we look at how products are designed and planned is more and more needed.
So are you ready to embrace the change?
Speaker(s): Sasha Tanase
Skill level: Beginner
Track: UX & Design
Keywords: design research,smart contracts,product development
Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/
Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 6 was held in Bogotá, Colombia on Oct 11 - 14, 2022.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/
A
A
A
Good
to
see
so
many
new
faces,
I
am
a
product
designer
and
a
researcher.
I
am
one
of
the
co-founders
of
the
web3
ux
user
research
panels
and
I
am
leading
the
ux
design
and
ux
research
for
the
threshold
Network,
which
was
formerly
known
as
keep
Network
and
new
Cipher
I
am
also
part
of
the
team
who's
building
tbtc,
which
is
the
first
fully
decentralized
Bitcoin
to
ethereum
bridge
I
like
to
say
about
my
job,
that
is,
to
transform
extremely
complex
products
into
palatable
bits.
A
A
Today's
talk
is
about
a
new
collaboration
flow
between
designers
developers
and
business
developers.
It's
a
critique
brought
to
the
way
things
are
currently
handled,
we'll
try
to
go
together
over
what
could
be
the
issues
of
the
present
building
process,
how
they
affect
the
product
life
cycle,
and
we
will
explore
how
might
we
collaborate
better
from
the
start
and
how
to
be
more
inclusive?
Today's
talk
is
an
open
conversation.
Hopefully
this
subject
will
set
the
wheels
in
motion
and
I
would
be
happy
to
hear
any
ideas.
Suggestions
on
how
we
better
the
proposed
approach.
B
A
So
the
future
of
Wave
3
ux.
Why
do
we
even
talk
about
this?
Is
there
an
issue
so
anecdotally,
70
of
the
user
experience
of
a
web
3
protocol
ordap
is
dictated
by
the
smart
contract.
Smart
contracts
are
usually
not
upgradable,
so
the
experience
should
be
Flawless
from
the
start.
If
you
are
not
familiar
with
how
this
could
be
translated
to
then.
A
The
products
are
extremely
complex
and
difficult,
and
the
development
teams
are
more
focused
on
solving
the
problems
which
are
localized
at
the
Smart
contract,
and
there
are
many
levels
in
between
the
smart
contract
and
the
user.
So
this
is
what's
happening.
The
development
team
meets
decides
how
to
how
the
protocol
or
dap
will
work.
They
write
the
smart
contract
and
afterwards
they
send
it
to
the
audit.
Usually
there
are
multiple
all
these
done.
In
average,
two
to
four
and
after
the
code
has
been
audited
and
fixed,
it
fixed.
A
A
So
there
is
a
tendency
for
technology
to
lead
the
product
versus
the
other
way
around.
This
means
that
there
is
a
high
likelihood
of
over
engineering
and
unfortunately,
ux
becomes
the
a
byproduct
tech.
People
do
not
have
the
priority
to
put
themselves
in
the
user's
shoes,
which
is
not
really
an
issue
unless
the
entire
experience
depends
on
them.
A
So
the
teams
are
siled,
which
means
there
is
zero
collaboration.
Any
findings
from
research
design,
research
that
require
redesigning
the
experience
is
impossible
because
the
smart
contract
has
been
audited
and
fixed.
So
there
is
no
turning
back.
Design
can
improve
the
experience
only
by
adding
explanations
and
ux
writing
gimmicks.
A
A
A
A
A
A
A
This
process
is
based
on
a
diverge
converge
process
developed
by
the
linguist
Bella
vanity.
This
methodology
suggests
that
a
product
process
should
have
four
phases:
Discovery
and
definition
which
together,
make
the
explorative
and
Divergent
phase
and
then
development
and
delivery,
which
together,
make
the
iterative
and
convergent
phase.
A
So
explorative
design
helps
us.
Do
the
right
thing.
Iterative
design
helps
us
do
the
thing
right.
This
is
my
Mantra
and
I
think
this
should
become
everybody
else's
mantra.
So
what
could
be
a
flow
that
respects
the
two
important
phases
in
a
product
development
cycle
and
it
can
also
respond
to
the
web
3
environment
needs.
A
A
So
in
the
explorative
Divergent
phase,
everyone
is
brought
to
the
table
from
the
start,
design,
development
and
business.
A
designer
will
facilitate
stakeholder
interviews
and
each
team
will
map
out
their
requirements.
The
user
needs
technical
constraints,
business
goals,
they
are
all
considered
and
taken
into
account.
A
User
Journeys
are
created
based
on
each
team's
insights
and
requirements,
evm
constraints,
security
issues,
user
needs,
pain,
points,
kpis
and
business
requirements.
All
of
these
elements
are
Incorporated
in
a
high-level
user
Journey
map
that
will
Mark
each
step
a
user
needs
to
take
in
order
to
achieve
their
desired
goal.
The
user,
Journeys
assumed
needs
and
pain
points
are
probed
in
explorative
research
by
speaking
to
real
people.
A
This
is
a
very
impactful
moment
in
the
process,
since
we
are
moving
from
merely
assuming
things
to
actually
spending
time
and
observing
the
people
who
will,
in
the
end,
use
our
product.
So
in
this
type
of
the
process,
we're
testing
our
ideas,
and
this
may
be
the
moment
in
which
we
might
need
to
Pivot.
We
might
find
out
that
maybe
this
is
not
the
way
to
go
so
afterwards.
A
All
of
the
Unearthed
insights
and
findings
will
be
incorporated
into
the
new
user
Journeys,
so
research
has
been
conducted,
assumptions
have
been
probed,
findings
had
been
Incorporated
in
the
into
the
new
user
journey
and
all
of
the
stakeholders
have
validated
them
now.
The
interactive
phase
can
start.
A
A
The
design,
prototype
and
smart
contract.
Writing
is
a
very
important
step
in
which
the
two
teams
will
need
to
have
constant
check-ins
and
will
need
to
accommodate
each
other's
findings.
So,
basically
the
design
team
will
test.
The
Prototype
will
have
some
findings.
They
will
communicate
them
to
the
smart
contract
developers.
The
smart
contract
developers
will
incorporate
these
findings
into
the
smart
contract
and
then
they
will
find
Solutions.
A
Of
course,
maybe
some
Technical
Solutions
will
won't
be
necessarily
perfectly
answering
to
the
new
needs
that
have
been
discovered,
so
they
will
also
communicate
these
new
issues
and
findings
to
the
design
team.
So
there
needs
to
be
a
constant
back
and
forth
in
between
these
teams,
and
there
needs
to
be
constant
collaboration
between
the
design
team
and
the
development
team.
A
A
So
if
this
sounds
like
a
good
approach,
I
invite
you
to
adopt
the
methodology
and
adapt
it
to
your
organization.
We
need
to
think
of
this
proposal
as
a
work
in
progress
which
will
be
shaped
up
by
our
experiences
and
needs.
Let's
consider
this
our
explorative
phase,
if
you
plan
to
adopt
this
methodology
and
implement
it
in
your
organization.
Please
let
me
know
what
were
your
struggles
which
parts
of
the
process
worked
and
which
didn't?
What
did
you
have
to
do
to
adapt
it
to
your
own
company
needs?
A
So
some
great
news
from
the
threshold
Network
and
the
tbtc
team,
my
team
was
convinced
about
the
benefits
of
this
new
methodology,
so
it
was
decided
to
adopt
it
and
implement
it
into
our
product
development
process.
Starting
2023-
and
this
means
I,
will
also
share
with
you.
My
experiences
of
adopting
and
adopting
adapting
the
process.
A
Some
thoughts
of
from
my
colleague
Doug,
who
is
a
great
supporter
of
ux
in
our
organization,
he's
talking
about
this
methodology,
and
he
says
there
is
no
hoping
and
guessing
only
principled
aligned
movement
that
values
the
user,
Above
All
Else
and
some
more
good
news
threshold
network
has
open
source,
its
entire
ux
research
and
past
ux
studies.
You
can
find
here
user
research
guidelines
all
of
the
past
studies
that
I've
conducted
for
keep
and
threshold
Network
and
different,
helpful
artifacts.
C
D
A
So
you
mean
explorative
phase.
What
like?
Okay,
so
generative
user
research
should
take
two
three
weeks
at
most,
which
is
not
a
lot
and
it's
very
easy
to
implement
the
findings
afterwards.
So
you
need
to
start
with
this.
It
can
take
even
less
than
that,
but
the
most
time
that
it
takes
is
finding
the
the
participants
that
are
meeting
the
user
profile
that
you're
trying
to
to
build
for
yeah.
A
C
E
I
have
a
question.
Thank
you
basically,
on
the
face
of
integrating
users,
what's
your
proposal
for
testnet
versus
mainnet
or
of
inclusion
of
the
users,
because
we
realize
that
when
users
are
on
test
net
and
we
when
we
are
on
this
kind
of
user
testing,
the
users
as
they
are
not
integrating
with
real
money
or
real
assets,
their
concerns
are
Way,
Beyond,
the
when
they
are
on
my
net.
But
when
you
are
on
minute,
you
should
have
already
a
functional
solution
that
should
work.
So
what's
your
take
on
that,
so.
A
I
think
it's
best
to
to
do
usability
tests
on
testnet,
but
try
to
make
it
as
real
as
possible,
like
what
you're
testing
will
be
mirroring
your
product
that
you're
deploying
on
mainnet,
and
the
thing
is
that
if
you're,
giving
the
users
testnet
tokens
and
everything-
and
they
will
go
to
to
the
entire
experience
at
some
point,
they
will
forget
that
they
are
actually
testing.
So
you
will
get
very
good
insights.
You
will
find
what's
fearful
and
scary
for
them,
because,
basically,
we
are
designing
for
fear.
A
A
F
B
A
We
don't
have
a
huge
pool
of
participants,
so
first
of
all,
I
think
we
should
stick
to
the
most
important
Persona
that
we
have
and
then
after
you're
building
your
user
profile-
and
you
know
who
you
want
to
build
for
then
I
think
you
should
use
a
screener
and
also
web3
ux,
which
is
our
user
research
panel.
It
actually
started
from
this
need
and
this
hurdle
that
is
very
hard
to
find
participants
so
yeah
screeners
and
then
a
pool
where
these
people
are
and
try
to
invite.