UX in ZOOM

1,728 views

Published on

Early experience with bringing usability to ZOOM International. What I did in the first eight months and how that worked. Slides for my UX Camp CZ speech.

Published in: Technology, Design
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,728
On SlideShare
0
From Embeds
0
Number of Embeds
943
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • - I do not share knowledge, do not have blog\n\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
  • \n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
  • - might sound boring, but it is not\n- one flagship product, another merging into it and new emerging product\n
  • - we will skip childhood, school, university\n
  • - we will skip childhood, school, university\n
  • - we will skip childhood, school, university\n
  • - we will skip childhood, school, university\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - I actually found just 9 differences\n
  • - lorem ipsum story\n
  • - lorem ipsum story\n
  • - lorem ipsum story\n
  • - lorem ipsum story\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • - not only developers\n
  • \n
  • \n
  • \n
  • \n
  • - somebody tells you do it, don't do it\n- request in JIRA to add button\n- developers now ask, how things are used\n
  • - somebody tells you do it, don't do it\n- request in JIRA to add button\n- developers now ask, how things are used\n
  • \n
  • \n
  • \n
  • \n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - 50 projects (epic - 2 or more sprints)\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
  • - it helps you\n- it spreads a spirit, people are playing all the time\n- Jirka Valasek's quote\n- water of life\n
  • - it helps you\n- it spreads a spirit, people are playing all the time\n- Jirka Valasek's quote\n- water of life\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
  • - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
  • - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
  • - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
  • - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
  • - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
  • - developers are also fundamental\n- http://www.zoomint.com/en/jobs/129-senior-software-engineer\n- 5 years experience, persistence frameworks, english, GWT\n
  • \n
  • \n
  • UX in ZOOM

    1. 1. UX in ZOOM Vaclav Slovacek vaclav.slovacek@zoomint.com
    2. 2. ZOOM
    3. 3. ZOOM• call recording, agent evaluation, speech analysis
    4. 4. ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit
    5. 5. ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries
    6. 6. ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries• about 10 developers
    7. 7. ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries• about 10 developers• your voice is heard
    8. 8. ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries• about 10 developers• your voice is heard• flexible and evolving
    9. 9. UX Designer
    10. 10. UX Designer• at ZOOM for 8 months
    11. 11. UX Designer• at ZOOM for 8 months• in product management
    12. 12. UX Designer• at ZOOM for 8 months• in product management• writing specifications
    13. 13. UX Designer• at ZOOM for 8 months• in product management• writing specifications• long term design decisions
    14. 14. UX Designer• at ZOOM for 8 months• in product management• writing specifications• long term design decisions• planning and prioritization
    15. 15. UX Designer• at ZOOM for 8 months• in product management• writing specifications• long term design decisions• planning and prioritization• day-to-day consulting
    16. 16. My Story no!ing more
    17. 17. Preparation
    18. 18. Preparation
    19. 19. Preparationseeing ZOOMs product
    20. 20. Preparationseeing ZOOMs product studying stuff about user research
    21. 21. Preparationseeing ZOOMs product studying stuff about user research user research cost calculator
    22. 22. Preparationseeing ZOOMs product studying stuff about user research user research cost calculator playing with prototyping tools
    23. 23. First Days
    24. 24. First Days
    25. 25. First Daysdesigning a new player
    26. 26. First Daysdesigning Excel report template designing a new player
    27. 27. First Daysdesigning Excel report template checking implementation designing a new player
    28. 28. First Daysdesigning Excel report template checking implementation designing a new player discussing what went wrong
    29. 29. 10 differences game
    30. 30. 10 differences game
    31. 31. 10 differences game
    32. 32. 10 differences game It is totally different from the prototype.
    33. 33. 10 differences game What is the difference?
    34. 34. 10 differences game What is the difference?explain why features are important
    35. 35. Unusable Specification
    36. 36. Unusable Specification
    37. 37. Unusable Specification
    38. 38. Unusable Specification usability of specifications matters
    39. 39. Quick Fixes
    40. 40. Quick Fixes
    41. 41. Quick Fixesredesigning toolbars
    42. 42. Quick Fixesfixing a customers issue redesigning toolbars
    43. 43. Quick Fixes developers coming to askfixing a customers issue redesigning toolbars
    44. 44. Request Origins
    45. 45. Request Origins
    46. 46. Request Origins
    47. 47. Easier Development /browse/SC-2150  and we had a lot an had s olved http://jira:81 EC” specification.Ju problems with foll owing “As in CallRof logical   t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu
    48. 48. Easier Development /browse/SC-2150  and we had a lot an had s olved http://jira:81 EC” specification.Ju problems with foll owing “As in CallRof logical   t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu
    49. 49. Easier Development /browse/SC-2150  and we had a lot an had s olved http://jira:81 EC” specification.Ju problems with foll owing “As in CallRof logical   t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu ask why a feature is requested
    50. 50. Triangle
    51. 51. Triangle
    52. 52. Trianglesimple
    53. 53. Triangle simpleeasy to develop
    54. 54. Triangle simpleeasy to develop flexible
    55. 55. Triangle simpleeasy to develop flexible
    56. 56. Triangle simpleeasy to develop flexible
    57. 57. Projects Boom
    58. 58. Projects Boom
    59. 59. Projects Boomlong term projects specifications
    60. 60. Projects Boom UX Guidelines and checklistlong term projects specifications
    61. 61. Projects Boom 2011 vision presentation UX Guidelines and checklistlong term projects specifications
    62. 62. Projects Boom 2011 vision presentation talk with users UX Guidelines and checklistlong term projects specifications
    63. 63. Projects Boom 2011 vision presentation talk with users vision for developers UX Guidelines and checklistlong term projects specifications
    64. 64. Projects Boom tuning specifications 2011 vision presentation talk with users vision for developers UX Guidelines and checklistlong term projects specifications
    65. 65. Specification
    66. 66. Specification
    67. 67. Specification
    68. 68. Specification
    69. 69. Specificationmedia are stronger than text
    70. 70. Project
    71. 71. Project 1 Project 2
    72. 72. Project 1 Project 2
    73. 73. temporary featuresProject 1 Project 2
    74. 74. critical stuff fixed now vision of the futureProject 1 Project 2
    75. 75. InspirationMan, I feel excited about every new feature we design now. I feel totally inspired.
    76. 76. InspirationMan, I feel excited about every new feature we design now. I feel totally inspired. do not design alone
    77. 77. Agile
    78. 78. Agile
    79. 79. one week planning of 4 sprints Agile
    80. 80. one week planning of 4 sprints Agile daily meetings
    81. 81. one week planning of 4 sprints Agile daily meetings review
    82. 82. one week planning of 4 sprints Agile daily meetings review retrospective
    83. 83. one week planning of 4 sprints next sprint Agile daily meetings review retrospective
    84. 84. Agileone week planning of 4 sprints daily meetingsreview retrospective next sprint
    85. 85. Agileone week planning of 4 sprints 15 enhancements having 200 tasks daily meetingsreview retrospective next sprint
    86. 86. Agileone week planning of 4 sprints 15 enhancements having 200 tasks more accurate estimates daily meetingsreview retrospective next sprint
    87. 87. Agileone week planning of 4 sprints daily meetings know what is happeningreview retrospective next sprint
    88. 88. Agileone week planning of 4 sprints daily meetings know what is happening enforce relationship with developersreview retrospective next sprint
    89. 89. Agileone week planning of 4 sprints daily meetings different kind of feedbackreview retrospective next sprint
    90. 90. Agileone week planning of 4 sprints daily meetings different kind of feedbackreview notes for next sprint retrospective next sprint
    91. 91. Agileone week planning of 4 sprints daily meetingsreview improving communication retrospective next sprint
    92. 92. Agileone week planning of 4 sprints daily meetingsreview improving communication retrospective know what you do wrong next sprint
    93. 93. Future
    94. 94. Future
    95. 95. FutureUser Research 2011
    96. 96. UX Checklist use during testing FutureUser Research 2011
    97. 97. UX Checklist use during testing FutureUser Research 2011 keep stuff in sync
    98. 98. UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical s
    99. 99. UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical s 20 ca ll c en te rs
    100. 100. UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 ca up ll c s en te rs
    101. 101. UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 ca up 3 re ll c s en te sear rs che rs
    102. 102. UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 half a y ca up 3 re ll c s en te sear ear rs che rs
    103. 103. UX is fund
    104. 104. UX is fundamental for your company
    105. 105. recommendations
    106. 106. explore
    107. 107. explore
    108. 108. seek inspiration
    109. 109. we are lookingfor developers
    110. 110. Q&Avaclav.slovacek@zoomint.com
    111. 111. Thank you for your attention

    ×