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.
1. UX in ZOOM
Vaclav Slovacek
vaclav.slovacek@zoomint.com
2. 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
4. UX Designer
• at ZOOM for 8 months
• in product management
• writing specifications
• long term design decisions
• planning and prioritization
• day-to-day consulting
13. 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 CallR
of 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
16. Projects Boom tuning specifications
2011 vision presentation
talk with users vision for developers
UX Guidelines and checklist
long term projects specifications
22. Inspiration
Man, I feel excited about every new feature we
design now. I feel totally inspired.
do not design alone
23. one week planning of 4 sprints next sprint
Agile
daily meetings review retrospective
24. Agile
one week planning of 4 sprints 15 enhancements having 200 tasks
more accurate estimates
daily meetings
review
retrospective
next sprint
25. Agile
one week planning of 4 sprints
daily meetings know what is happening
enforce relationship with developers
review
retrospective
next sprint
26. Agile
one week planning of 4 sprints
daily meetings
different kind of feedback
review notes for next sprint
retrospective
next sprint
27. Agile
one week planning of 4 sprints
daily meetings
review
improving communication
retrospective
know what you do wrong
next sprint
28. UX Checklist use during testing Future
User 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
r s
che
rs
- 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
- 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