Can Kilicbay: Feeding on change | UX Riga 2018
•
2 j'aime•128 vues
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.
Recommandé
Contenu connexe
Similaire à Can Kilicbay: Feeding on change | UX Riga 2018
Similaire à Can Kilicbay: Feeding on change | UX Riga 2018 (20)
Plus de UX Riga
Plus de UX Riga (18)
Dernier
Dernier (20)
Can Kilicbay: Feeding on change | UX Riga 2018
- 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. cONCLUSION UNDERSTAND THE REASONS OF CHANGE prepare your toolkit MOVE WITH YOUR TEAM
- 4. WHOo. are you?AM I ?
- 5. MY journey
- 7. q listening > making things beautiful
- 8. team took me further
- 9. I facilitate teams to solve problems.
- 10. WHEN SOMEONE TALKS ABOUT DESIGNWHAT DO THEY MEAN?
- 12. A story of a team UX Team Content Dev Team PO Scrum M. Insight
- 13. How shall we work?
- 14. How do we work now? Oooh!..
- 15. Where do we want to be? Dev Team UX Team Content
- 16. 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.
- 17. That doesn’t sound ‘Agile’
- 18. That doesn’t sound ‘Agile’ PAUSE
- 19. It is more than Agile
- 20. It is more than Agile Explore the problem Build the RIGHT things Build the thing RIGHT
- 21. DESIGN THINKING LEAN AGILE It is more than Agile Explore the problem Build the RIGHT things Build the thing RIGHT
- 22. Building the thing right AGILE ConceptDirection Problem Solution Build it
- 23. Begin to explore the problem AGILE ConceptDirection Problem Solution Experiment Build it Hypothesis
- 24. and understand the customer DESIGN THINK Customer Problem ConceptDirection Problem Solution Experiment Build it Hypothesis AGILE
- 25. DESIGN THINK LEAN AGILE Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis Also, we need to iterate
- 26. 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
- 27. 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
- 28. s TOOLKIT
- 29. change is not linear If you want to go fast, go alone If you want to go far, go together
- 30. invisible work is evil
- 32. ImplementationExploration Dev Team UX Team Content Investigation Who does what? Dev Team UX Team Content
- 33. ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ImplementationExploration Dev Team UX Team Content Investigation Who does what? Dev Team UX Team Content
- 35. Remember, it is a team work!
- 36. We need to avoid invisible work Exploration Investigation Implementation
- 37. And make them visible x% y% z% 100% + = + + Exploration Investigation Implementation
- 38. find and show the value of design
- 39. Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis
- 41. 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
- 42. WRITING A DESIGN HYPOTHESIS We believe that … So if we … Then we will see …
- 45. Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis
- 46. Customer Problem ConceptDirection Problem Solution Experiment New ideas Build it Feedback Update hypothesis Hypothesis REPEAT
- 47. lead by example Use your empathy, listen in your team Give them voice to raise their issues
- 48. trust in your team We are all here to play some Jazz
- 49. nothing is done, nothing is finished
- 50. 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.
- 54. cONCLUSION UNDERSTAND THE REASONS OF CHANGE prepare your toolkit MOVE WITH YOUR TEAM
- 55. 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