4. 1
2
INTRO CONCEPT MAP & USER JOURNEY
SITEMAP WIREFRAME
UNDERSTAND STAKEHOLDERS REQUIREMENTS/ USER NEEDS
AND USE IT AS DESIGN DIRECTION.
REQUIREMENTS
CONCLUDERECAP
Class Overview
11. Understanding Users
Who are they -
What do they use the website for – context of use
(hurry , critical?)
Identify goals, user experience ,values
Users
12. Researcher
Research Management
Academicians
Industry Partners
Extension Agents
Entrepreneurs
Farmers
and General Public.
Users Data
13. Pengetahuan mengenai
padi & beras?
% (n=139)
Sangat sedikit 8.6
Sedikit 12.9
Sederhana 56.8
Banyak 20.1
Sangat banyak 1.4
MENCARI MAKLUMAT PADI
& BERAS?
% (n=139)
Tidak pernah 0.7
Sekali sekala 10.1
Jarang-jarang 5.0
Kadang-kadang 26.6
Kerap 57.6
Frequency Percent Valid Percent
Cumulative
Percent
Valid 1 .7 .7 .7
extension 58 41.7 41.7 42.4
industri 12 8.6 8.6 51.1
pelajar 9 6.5 6.5 57.6
penyelidikan 54 38.8 38.8 96.4
petani 3 2.2 2.2 98.6
PTD 2 1.4 1.4 100.0
Total 139 100.0 100.0
GOLONGAN KERJA
14. Maklumat yang dicari?
% (n=139)
Pengurusan tanaman 81.3
Varieti padi 78.4
Penyakit & perosak 71.2
Pembajaan 66.9
Teknologi terbaru 64.7
Rumpai 57.6
Senario industri 57.6
Statistik 49.6
Lepas tuai 48.2
Mesin / alat 35.3
Ladang contoh 25.2
Produk berasaskan beras 18.0
Usahawan berjaya 18.0
Benih 4 responden
15. Sumber maklumat
Laman web 122 88%
Seminar 115 83%
Agensi kerajaan 114 82%
Buku 98 71%
Jurnal 85 61%
Majalah 77 55%
Kawan 55 40%
Brosur 53 38%
Blog 38 27%
Youtube 33 24%
Forum internet 21 15%
Radio 10 7%
Keluarga 8 6%
16. Tujuan cari maklumat padi
meningkatkan pengetahuan 101 73%
penyelidikan 73 53%
pengembangan 66 48%
menyelesaikan masalah 61 44%
meningkatkan hasil padi 59 42%
minatsejarah
Frequency Percent
tidak 9 6.5
ya 126 90.6
Total 135 97.1
keutamaan media
teks 1.6032
video 2.3730
imej 2.4524
audio 3.5714
tempat akses maklumat padi
Office 130 94%
rumah 108 78%
wifispot 48 35%
kafesiber 7 5%
Device
laptop 115 83%
PC 99 71%
smartphone 83 60%
tablet 44 32%
22. # STAKEHOLDERS
ideal solution
A one stop center for knowledge on paddy R&D and
TCT that can be searched in context to paddy
disciplines, which combines all aspects of the value
chain from planting to post-harvest, and links MARDI
artifacts together, to ensure the preservation of paddy
knowledge and also dissemination of paddy R&D and
TCT done in MARDI to others outside of MARDI.
24. Understanding Users
Who are they -
What do they use the website for –
context of use (hurry , critical?)
Identify goals,user experience ,values
# ACTIVITY - STAKEHOLDERS
25. Now you need to make sense of them
Splits in small groups
Organizing keywords
remove the duplicates
# 1 : DATA EXTRACTION ( 20 minutes)
you would want to understand how your target audiences go about browsing and use your website.
What is their motivation for purchase?
Do they enjoy browsing or is it a chore? Are they likely to go away and come back again or will they buy straight away?
What do they know about what they need from a shoe?
Its purpose (work or partying)? Its size? (If a particular shoe is not available in the customer’s size, they simply will not buy it.) Its fit? Shoes need to be tried on, and may not be comfortable even if they are the correct size, so return policies are likely to be vitally important.
Talking to real users of competitor products in order to generate a task model will help focus the project.
The aim of producing task models is to ensure that your product matches users’ expectations of how the system works.
Usability problems occur when there is a discrepancy between what the user wants to do and the way that the system requires them to do it.
Which user journeys are most important?
How can you structure your product to ensure these key journeys are smooth?
• Are there any pages that could be skipped?
• Is there extra information you could provide to prevent the need for jumping back and forth between pages?
• Are there any shortcuts needed?
• Is any extra functionality needed?
The aim of producing task models is to ensure that your product matches users’ expectations of how the system works.
Usability problems occur when there is a discrepancy between what the user wants to do and the way that the system requires them to do it.
Which user journeys are most important?
How can you structure your product to ensure these key journeys are smooth?