The document outlines the core design methodology for a digital hive project. It details the 5 step design process: 1) Empathy through user interviews and empathy maps, 2) Define the issue through POV statements, 3) Ideate alternative solutions, 4) Build prototypes, and 5) Test prototypes with user feedback. The schedule involves bi-weekly meetings to discuss progress and POVs. Teams will conduct interviews, create empathy maps and POVs, brainstorm ideas, build simple prototypes, and get feedback to iterate on solutions. The overall goal is to design a website infrastructure that allows for collective intelligence and knowledge flow.

1.
EOD
Digital
Hive
Project
CORE
Design
Methodology

2. Schedule
• October
15
– Introduc?on
to
design
challenge
– Review
of
empathy
phase
– Introduce
user
interviews
– Extract
interview
informa?on
on
post-­‐it
notes.
– Crea?on
of
an
empathy
map
– POV
statement

3. What
is
Design?
Design
is
the
process
of
crea?ng
something
new:
• Product
Design
• Process
Design
• Organiza?on
Design
• Course
Design
• Curriculum
Design
• Architectural
Design

4. Design
Process
Step
1:
Empathy.
Step
2:
Define
Issue.
Step
3:
Ideate.
Step
4:
Build
a
Prototype..
Step
5:
Test.

5. Elements
of
Design?

6. Principles
of
Design
Process
Human-­‐centered—search
for
how
and
why
people
think
and
feel
as
they
do.
Bias
toward
ac?on—move
quickly
to
test
your
ideas.
Radical
collabora?on—group
u?lizes
talents
of
everyone.
Prototyping—crea?ng
something
visual,
a
mockup,
etc.
(Embodied
learning).
Show
don’t
tell—visuals,
visuals,
visuals!

7. Brainstorming
Encourage
Wild
Ideas.
Defer
Judgment.
Build
on
the
Ideas
of
Others.
Go
for
Volume.
One
Conversa?on
at
a
Time.
Be
Visual.
Headline
your
Ideas.
Stay
on
Topic.

8. Design
Challenge
Self-­‐organize
in
teams
• How
to
design
a
website
infrastructure
to
best
allow
for
collec?ve
intelligence
and
knowledge
flow?

9. Step
1:
Empathize
Purpose:
Gather
&
organize
informa?on
around
the
design
challenge.
Technique:
User
interviews.
Interview
Guidelines:
-­‐Listen
and
understand
from
user’s
perspec?ve.
-­‐Have
a
conversa?on
–who
is
s/he,
background,
interests?
-­‐Seek
stories.
-­‐Avoid
ques?ons
that
can
be
answered
with
yes/no.
-­‐Ask
how,
why
ques?ons.

10. Step
1:
Empathize
Con?nued
Mechanics
of
Interview
process:
One
person
asks
ques?ons
and
takes
notes.
Second
person
takes
notes
and
asks
follow-­‐up
ques?ons,
or
when
there
is
a
lull.

11. Step
1:
Empathize
Con?nued;
Organize
Interview
Informa?on
Create
an
Empathy
Map
Descrip?ve
Statements
AWribu?ons?
Your
Observa?ons,
What
might
the
speaker
What
is
said;
words
used?
be
thinking?
His/her
beliefs?

12. Step
1:
Empathize
Con?nued;
Organize
Interview
Informa?on
• Extract
informa?on
from
your
notes
and
put
on
post-­‐its.
• One
comment
per
post-­‐it.
• Place
post-­‐its
on
the
empathy
map.

13. Step
2:
Define
the
Issue
• Use
a
POV
(point
of
view)
exercise
to
help
you
create
an
issue
statement.
User—Briefly
describe
based
on
your
post-­‐-­‐-­‐it
notes.
Needs—Use
verbs
to
describe
things
they
want
to
do/
or
happen
based
on
your
post-­‐it
notes.
Insights—what
you
have
learned
about
your
user’s
feelings/world
view
based
on
your
post-­‐it
notes
to
leverage
in
your
design.
Issue
Statement
created
for
each
interviewee.

14. POV
Statement

15. Schedule
-­‐Bi-­‐weekly
CORE
Design
Team
mee?ng
to
discuss
progress
and
POV
statements
-­‐Brainstorming
-­‐Feedback
from
group
at
large
-­‐Prototyping
op?ons
(rapid/simple
moving
to
me?culous/
itera?ve)

16. Step
3:
Ideate
• Generate
alterna?ve
solu?ons
to
the
design
issue.
• Generate
list
of
ideas
within
the
team;
one
idea
per
post-­‐it
note.
• Reflect
and
select
a
solu?on
the
team
wants
to
prototype.

17. Step
4:
Build
a
Prototype
• Use
whatever
supplies
you
want.
• Create/build
something.
• Have
fun!

18. Step
5:
Test
Share
your
solu?on
and
get
feedback
from
interviewee
• What
worked?
What
can
be
improved?
• Ques?ons?
Ideas
to
pursue?

19. Concluding
Remarks