The process we used to have:
Product Defining the requirement
UX Providing the UI guidelines
(Delivering on the sprint preplanning)
Development Producing the code
UX & QA
Detailed prototype + User stories and instructions in TFS.
Miss-communication of requirement
Un-clear UX DoD
It is all about direct communication
Defining the requirement
Discussing the requirement and DoD
UX+ + Dev.
UX+ + Dev. + QA + TW
(A.K.A. the “same same but different” problem)
There is more than one (correct) way to skin a cat
Different application, same issues –
Tables, popups, pagination, date range picker, etc.
The problem: We kept reinventing the wheel
We should use unified, consistent,
and well thought-through methods
Title & a short description
When to use
When not to use
Visual design (Style guide, graphic assets)
The design pattern structure
Local feedback (i.e. – @Israel) from PMs & R&D
Remote groups had some issues with the guidelines
” it is saving development time...
(ensuring) very high quality of our products”
“A reference implementation of all of these
widgets in action would be far more useful "
Live gallery >
Meet the Users (A.K.A. “Contextual Inquiries”)
Feedback from Our Product Directors
“This is extremely important observation...
we can learn from it and use it as a baseline for improvement”
“This is very good and important…
I will share the PPT with my team”
Utilize Sprint 0 to define the vision
Involved everyone in direct F2F communication
Build UX pattern & guidelines repository
Usability testing & user observations - Early and
And the bottommost bottom line…
Methods for Effective UX
Generating a great user experience in
large organizations requires that
everyone – Product, R&D and QA –
take an active part in the UX design.
Bottommost Bottom Line