O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
as a designer
Feeding on change
as a designer
Feeding on change
Feeding on change
as a designer
Feeding on change
as a des...
cONCLUSION
UNDERSTAND THE
REASONS OF CHANGE
prepare your toolkit
MOVE WITH YOUR TEAM
WHOo.
are you?
WHOo.
are you?AM I ?
MY journey
q
listening > making things beautiful
team took me further
I facilitate
teams to
solve problems.
WHEN SOMEONE TALKS ABOUT
DESIGNWHAT DO THEY MEAN?
A story of a team
UX Team
Content
Dev Team
PO
Scrum M.
Insight
How shall we work?
How do we work now?
Oooh!..
Where do we want to be?
Dev Team
UX Team
Content
It turns out that
Content and UX Team, want to work more integrated.
Dev Team, wants to see a set delivery of content and ...
That doesn’t sound ‘Agile’
That doesn’t sound ‘Agile’
PAUSE
It is more
than Agile
It is more than Agile
Explore
the problem
Build the
RIGHT things
Build the
thing RIGHT
DESIGN
THINKING
LEAN AGILE
It is more than Agile
Explore
the problem
Build the
RIGHT things
Build the
thing RIGHT
Building the thing right
AGILE
ConceptDirection
Problem Solution
Build it
Begin to explore the problem
AGILE
ConceptDirection
Problem Solution
Experiment
Build it
Hypothesis
and understand the customer
DESIGN THINK
Customer Problem
ConceptDirection
Problem Solution
Experiment
Build it
Hypothesis...
DESIGN THINK LEAN AGILE
Customer Problem
ConceptDirection
Problem Solution
Experiment
New ideas
Build it
Feedback
Update
h...
DESIGN THINK LEAN AGILE
Customer Problem
ConceptDirection
Problem Solution
Experiment
New ideas
Build it
Feedback
Update
h...
DESIGN THINK LEAN
Build the RIGHT things
AGILE
Build the thing RIGHT
Customer Problem
ConceptDirection
Problem Solution
Ex...
s
TOOLKIT
change is not linear
If you want to go fast, go alone
If you want to go far, go together
invisible work is evil
Exploration
Investigation
Implementation
ImplementationExploration
Dev Team
UX Team
Content
Investigation
Who does what?
Dev Team
UX Team
Content
✅ ✅ ✅
✅ ✅ ✅
✅ ✅ ✅
ImplementationExploration
Dev Team
UX Team
Content
Investigation
Who does what?
Dev Team
UX Team
Content
Remember, it is a team work!
We need to avoid invisible work
Exploration
Investigation
Implementation
And make them visible
x%
y%
z%
100%
+
=
+
+ Exploration
Investigation
Implementation
find and show
the value of design
Customer Problem
ConceptDirection
Problem Solution
Experiment
New ideas
Build it
Feedback
Update
hypothesis
Hypothesis
Sprints
Design variations
Go live
A/B PRIO A/B PRIO A/B PRIO A/B PRIO A/B PRIOA/B PRIO
Test is running Analyse
Demo
Archet...
WRITING A DESIGN HYPOTHESIS
We believe that …
So if we …
Then we will see …
Original Alternative
Customer Problem
ConceptDirection
Problem Solution
Experiment
New ideas
Build it
Feedback
Update
hypothesis
Hypothesis
Customer Problem
ConceptDirection
Problem Solution
Experiment
New ideas
Build it
Feedback
Update
hypothesis
Hypothesis
REP...
lead by example
Use your empathy, listen in your team
Give them voice to raise their issues
trust in your team
We are all here to play some Jazz
nothing is done,
nothing is finished
streamline “design”
Think of 80/20 and prioritise accordingly.
If you reinvent UI all the time,
you are not solving the co...
streamline “design”
cultivate design thinking
understand your customer
cONCLUSION
UNDERSTAND THE
REASONS OF CHANGE
prepare your toolkit
MOVE WITH YOUR TEAM
q
• q
as a designer
Feeding on ch
as a design
Feeding on change
as a designer
Feeding on change
Feeding on change
as a des...
Can Kilicbay: Feeding on change | UX Riga 2018
Can Kilicbay: Feeding on change | UX Riga 2018
Can Kilicbay: Feeding on change | UX Riga 2018
Can Kilicbay: Feeding on change | UX Riga 2018
Can Kilicbay: Feeding on change | UX Riga 2018
Terminou este documento.
Transfira e leia offline.
Próximos SlideShares
What to Upload to SlideShare
Avançar
Próximos SlideShares
What to Upload to SlideShare
Avançar
Transfira para ler offline e ver em ecrã inteiro.

Compartilhar

Can Kilicbay: Feeding on change | UX Riga 2018

Baixar para ler offline

Can is speaking about how to navigate in complex companies. It is on practical matters, what to pay attention in a team, how to understand the scope and treat different perspective during the change and how designers can facilitate the change.

Can Kilicbay: Feeding on change | UX Riga 2018

  1. 1. as a designer Feeding on change as a designer Feeding on change Feeding on change as a designer Feeding on change as a designer Feeding on change as a designer Feeding on change as a designer Feeding on change as a designer Feeding on change as a designer
  2. 2. cONCLUSION UNDERSTAND THE REASONS OF CHANGE prepare your toolkit MOVE WITH YOUR TEAM
  3. 3. WHOo. are you?
  4. 4. WHOo. are you?AM I ?
  5. 5. MY journey
  6. 6. q listening > making things beautiful
  7. 7. team took me further
  8. 8. I facilitate teams to solve problems.
  9. 9. WHEN SOMEONE TALKS ABOUT DESIGNWHAT DO THEY MEAN?
  10. 10. A story of a team UX Team Content Dev Team PO Scrum M. Insight
  11. 11. How shall we work?
  12. 12. How do we work now? Oooh!..
  13. 13. Where do we want to be? Dev Team UX Team Content
  14. 14. It turns out that Content and UX Team, want to work more integrated. Dev Team, wants to see a set delivery of content and UX.
  15. 15. That doesn’t sound ‘Agile’
  16. 16. That doesn’t sound ‘Agile’ PAUSE
  17. 17. It is more than Agile
  18. 18. It is more than Agile Explore the problem Build the RIGHT things Build the thing RIGHT
  19. 19. DESIGN THINKING LEAN AGILE It is more than Agile Explore the problem Build the RIGHT things Build the thing RIGHT
  20. 20. Building the thing right AGILE ConceptDirection Problem Solution Build it
  21. 21. Begin to explore the problem AGILE ConceptDirection Problem Solution Experiment Build it Hypothesis
  22. 22. and understand the customer DESIGN THINK Customer Problem ConceptDirection Problem Solution Experiment Build it Hypothesis AGILE
  23. 23. DESIGN THINK LEAN AGILE Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis Also, we need to iterate
  24. 24. DESIGN THINK LEAN AGILE Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis Brainstorm concepts Prio Insights Clear needs Research Deepen learning the customer
  25. 25. DESIGN THINK LEAN Build the RIGHT things AGILE Build the thing RIGHT Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis Brainstorm concepts Prio Insights Clear needs Research Experiment, and iterate Explore the problem
  26. 26. s TOOLKIT
  27. 27. change is not linear If you want to go fast, go alone If you want to go far, go together
  28. 28. invisible work is evil
  29. 29. Exploration Investigation Implementation
  30. 30. ImplementationExploration Dev Team UX Team Content Investigation Who does what? Dev Team UX Team Content
  31. 31. ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ImplementationExploration Dev Team UX Team Content Investigation Who does what? Dev Team UX Team Content
  32. 32. Remember, it is a team work!
  33. 33. We need to avoid invisible work Exploration Investigation Implementation
  34. 34. And make them visible x% y% z% 100% + = + + Exploration Investigation Implementation
  35. 35. find and show the value of design
  36. 36. Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis
  37. 37. Sprints Design variations Go live A/B PRIO A/B PRIO A/B PRIO A/B PRIO A/B PRIOA/B PRIO Test is running Analyse Demo Archetype Test First test Independent Test First test Design variations Go live Test is running Analyse Demo Front-end
  38. 38. WRITING A DESIGN HYPOTHESIS We believe that … So if we … Then we will see …
  39. 39. Original Alternative
  40. 40. Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis
  41. 41. Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis REPEAT
  42. 42. lead by example Use your empathy, listen in your team Give them voice to raise their issues
  43. 43. trust in your team We are all here to play some Jazz
  44. 44. nothing is done, nothing is finished
  45. 45. streamline “design” Think of 80/20 and prioritise accordingly. If you reinvent UI all the time, you are not solving the core of the problem.
  46. 46. streamline “design”
  47. 47. cultivate design thinking
  48. 48. understand your customer
  49. 49. cONCLUSION UNDERSTAND THE REASONS OF CHANGE prepare your toolkit MOVE WITH YOUR TEAM
  50. 50. q • q as a designer Feeding on ch as a design Feeding on change as a designer Feeding on change Feeding on change as a designer Feeding on change as a designer Feeding on chang as a designer Feeding on chang as a designer Feeding on change as a designerCan Kilicbay @socialdistress commonground.se
  • jamesherrera

    Oct. 28, 2018
  • daengdoang

    Jun. 28, 2018

Can is speaking about how to navigate in complex companies. It is on practical matters, what to pay attention in a team, how to understand the scope and treat different perspective during the change and how designers can facilitate the change.

Vistos

Vistos totais

123

No Slideshare

0

De incorporações

0

Número de incorporações

0

Ações

Baixados

6

Compartilhados

0

Comentários

0

Curtir

2

×