CARD SORTING
INFORMATION ARCHITECTURE VALIDATION
Users grouped the platform
before I structured it.
12 participants · 3 profiles · 48 cards · hybrid sort, open naming then closed validation
WHERE USERS AGREED
Payments
Tracking
Drivers and fleet
Finance
Integrations
New freight payment
Payment templates
Batch payments
Payment status
Receipts
Corrections
Driver registry
Vehicles and cargo
Statements
Reports and exports
API keys
Webhooks and logs
92%
agreement
88%
agreement
84%
agreement
76%
agreement
71%
agreement
ONE CARD SPLIT THE ROOM
Batch payments: 52% filed it under Payments, 48% under Tracking.
Left unresolved on purpose and tested in the prototype, where 10 of 12 users looked for it inside Payments.