Professional Documents
Culture Documents
• EXPLORATION
CONCEPT can be done by
individual or group UXDesign element
discussions to gather and EXPLORATION
discuss an idea with CONCEPT
various viewpoints
CONCEPT ~ abstract idea
9 Questions for Concept Exploration and
Development
Sumber : http://www.dtic.mil/ndia/2005systems/thursday/surber2.pdf
Difference between
Wireframes and Mockups
o After having outline the research and find out how many
participants from each group, it's time to perform scheduling
• Collect general information,
• Determining compensation,
• Screening,
• Space and Equipment Planning
Usability Testing
Writing Discussion Guides
• Memilih platform : web, • Mengidentifikasi apa yang • Buat rencana untuk menarik
mobile, android, ios bekerja dan apa yang tidak pengguna kembali
• Mengidentifikasi pengguna • Perhatikan dan kenali • Optimalkan aplikasi agar
dan penguji aplikasi beta aplikasi yang berhasil memberikan nilai lebih
• Membuat rencana akuisisi • Menganalisis tingkat retensi • Mengevaluasi kembali untuk
hasil pengujian pada minggu pertama pengembangan
Alpha vs. Beta Testing
Alpha Test Beta Test
Improve product quality, integrate
Improve product quality and ensure
What they do customer input on the finished product,
readiness beta.
and ensure the readiness of the release.
Towards the end of the development Just prior to launch, sometimes ending in
When they
process if the product is in a state of almost a few weeks or a few days before the
happen
complete. final release.
Usually very long and see many iterations. Usually only a few weeks (sometimes up
How long they
It’s not uncommon for alpha to last 3-5x to a couple of months) with few major
last
the length of beta. iterations.
Usually involves product marketing,
Who cares Almost exclusively quality/engineering
support, docs, quality and engineering
about it (bugs, bugs, bugs).
(basically the entire product team).
Normally performed by test engineers,
Who Tested in the “real world” with “real
employees, and sometimes “friends and
participates customers” and the feedback can cover
family”. Focuses on testing that would
(tests) every element of the product.
emulate ~80% of the customers.
http://www.centercode.com/blog/2011/01/alpha-vs-beta-testing/
Alpha vs. Beta Testing
Alpha Test Beta Test
What testers Plenty of bugs, crashes, missing docs and Some bugs, fewer crashes, most docs,
should expect features. feature complete.
Much of the feedback collected is
Most known critical issues are fixed, some
How they’re considered for and/or implemented in
features may change or be added as a result
addressed future versions of the product. Only
of early feedback.
important/critical changes are made.
About chaos, reality, and imagination.
About methodology, efficiency and
Beta tests explore the limits of a product
What they regiment. A good alpha test sets well-
by allowing customers to explore every
achieve defined benchmarks and measures a
element of the product in their native
product against those benchmarks.
environments.
You have a good idea of what your
You have a decent idea of how a product
customer thinks about the product and
When it’s over performs and whether it meets the design
what s/he is likely to experience when
criteria (and if it’s “beta-ready”)
they purchase it.
What happens
Beta Test! Release Party!
next
http://www.centercode.com/blog/2011/01/alpha-vs-beta-testing/
Post launch Analytics.
TERIMA KASIH
Overview UX
1. 2.
3.
UX Design Business
User Research
Methodology Requirement
7. 8.
4. 5.
6. SITE WIREFR
CREATIN CONTEN 9.
DESIGN MAPS AMES
G T PROTOT
PRINCIP AND AND
PERSON STRATEG YPING
LE TASK ANNOTA
A Y
FLOWS TIONS