Your SlideShare is downloading. ×
0
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Top 5 usability mistakes development teams make - OutSystems
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Top 5 usability mistakes development teams make - OutSystems

1,531

Published on

Over the last few years at OutSystems, we’ve increased focus to improve user experience of every web app we develop. A hundred web apps later, this is what we’ve learned.

Over the last few years at OutSystems, we’ve increased focus to improve user experience of every web app we develop. A hundred web apps later, this is what we’ve learned.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,531
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
11
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. © 2013 outsystemsSpeed alone did not cut it anymore!Expectations have risen. We needed to evolve.
  • 2. © 2013 outsystems No UX Expert No Web DesignerWe needed to put development teams doing abetter job, without enlarging the teams.
  • 3. © 2013 outsystems No UX Expert No Web Designer
  • 4. © 2013 outsystems Concepts 1d Highly Practical 2dour examples Cheatsheets UX Angels Usability Checklist Assessments Vision Document User Research Usability Tests
  • 5. © 2013 outsystems Bad alignment Sloppy grouping & spacing Inconsistency (A)simmetry
  • 6. © 2013 outsystemsIn a project, we developed a mockup for animportant screen and sent it to the developer.
  • 7. © 2013 outsystemsAt the end of the day, he sent us this screen. Wesaid: I know it’s awful, but I have no idea why!!
  • 8. © 2013 outsystemsScreen delivered by developer with obviousmisalignments.
  • 9. © 2013 outsystems Bad alignment Sloppy grouping & spacing Inconsistency (A)simmetryBasic Design Trainingbased on many real examplesAdvanced CSS TrainingUI Framework for OutSystemsHow we addressed it…
  • 10. © 2013 outsystemsSame data displayed differentlyInconsistent text and labelsActions placement differedVisuals mismatch
  • 11. Labels and data formats changed from screen toscreen within the application.
  • 12. Obvious misfit between new control and theexisting visual framework.
  • 13. © 2013 outsystemsSame data displayed differentlyInconsistent text and labelsActions placement differedVisuals mismatchUsability Trainingbased on many real examplesOutSystems UI FrameworkCustomer-specific StyleguideHow we addressed it…
  • 14. © 2013 outsystems No text to help users Looong texts Technical jargon
  • 15. Large blob of text, just asking not to be read, andlegal jargon.
  • 16. Even feeback messages can be the problem.
  • 17. © 2013 outsystems No text to help users Looong texts Technical jargonVision DocumentApplication GlossaryInformation ArchitectureMockupsHow we addressed it…
  • 18. © 2013 outsystems No requirement prioritization All data is important at any time All actions are important at any time
  • 19. Without perspective, developers tend to puteverything on the page.
  • 20. Sometimes, even more than 1 table.
  • 21. © 2013 outsystems No requirement prioritization All data is important at any time All actions are important at any timeVision DocumentFocus on most frequent use casesMockupsHow we addressed it…
  • 22. © 2013 outsystems No clue on who the user really is No perspective on user task No user guidance
  • 23. The most important piece of information for theuser was scaled down because it was the largest.
  • 24. © 2013 outsystems No clue on who the user really is No perspective on user task No user guidanceVision DocumentRich User Context, User StoriesDevelopment WalkthroughsUsability TestsHow we addressed it…
  • 25. © 2013 outsystemsdidwesolvethem??
  • 26. © 2013 outsystems Paradigm shift for most developers Some people get it better than others Need to open space for usability Customers can be an obstacle

×