OpenERP - Usability

2,767 views
2,646 views

Published on

Published in: Business, Technology, Design
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,767
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
174
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

OpenERP - Usability

  1. 1. OpenERP Feedback from our useability team. - Fabien Pinckaers, CEO - April 12th, 2012Nom du fichier – à compléter Management Presentation
  2. 2. We are blind!✔ We use to work with OpenERP. We are blind !✔ An evidence for us can be an issue for lambda users✔ If we want OpenERP to be sexy and accessible to the mass, we have to satisfy the smallest companies. Nom du fichier – à compléter Management Presentation
  3. 3. Example: Search ViewNom du fichier – à compléter Management Presentation
  4. 4. Search View: users take search for a form✔ V6.0: issue for 100 % of users✔ V6.1: issue for 42.9 % of users✔ V7.0: issue for 0% of users (to be confirmed) Nom du fichier – à compléter Management Presentation
  5. 5. Useability StatisticsNom du fichier – à compléter Management Presentation
  6. 6. Timing Comparison 6.0/6.1Number of minutes to perform a full business flow for a lambda user.(Quotation → Sale Order → Delivery Order → Invoicing → Payment) 20 19.8 19.44 16 14.16 11.93 12 6.0 8 6.1 4 0 PO SO Nom du fichier – à compléter Management Presentation
  7. 7. Main issues encountered in 6.1 (%) Widgets 73.68Business Flow 56.35 Search View 46.43 Configuration 38.19 Kanban View 37.5 Page View 33.33 List View 28.57 Form View 14.29 Menu 14.28 0 10 20 30 40 50 60 70 80 90 100 Nom du fichier – à compléter Management Presentation
  8. 8. Global score given by users (/10) 10 8 6 5.5 6.0 4 6.1 2 0.6 0 Score /10Nom du fichier – à compléter Management Presentation
  9. 9. Useability Examples V7.0 – demo new designNom du fichier – à compléter Management Presentation
  10. 10. Useability Process  We need to analyze: Google Analytics on SaaS • Statistics to know what to improve • Measurable feedback to know how to improve  Organize communication on every new features  Do user testing with lambda users per new feature, at least one usertesting.com per feature.&A Nom du fichier – à compléter Management Presentation
  11. 11. Widgets: m2o✔ V6.0: issues for 33 % of users✔ V7.0: issues for 73.6 % of users✔ Improvement for 6.1: ✔ Quick create ✔ Create and edit✔ Improvements for 7: ✔ Tooltip if the record is not created ✔ Simplification by removing widget icon Nom du fichier – à compléter Management Presentation
  12. 12. Simplification → Remove Elements Simplification → Remove Elements&A Nom du fichier – à compléter Management Presentation 12
  13. 13. Simplification through reduction  To simplify, we must reduce!  Remove whats: • Redundant • Not used  Hide: • Whats not required to use the application  Adding features → complexity for the application&A Nom du fichier – à compléter Management Presentation
  14. 14. Remove redundant/unused features  To be removed: • Shortcuts → if the menu is simple, we dont need shortcuts. This would require to review the menu. • Homepage → directly go to the latest application. Confusing to have two way to access a root app like “Sale”. • Dashboards → nobody use them, put in Reporting section • Top right toolbar → with home, preferences, help...; simplify ala google • Pager / Multi-Views on one2many → only if several exists • Menu tips (use them in empty lists or help tooltip only) • Res.Logs (directly integrated in the history of a document, through the new “chatter” system) • Default filters on state for list views • Edit icon (pencil) in lists (they click on the record, then click edit)&A Nom du fichier – à compléter Management Presentation
  15. 15. Extended View: Simplify Forms We dont need all those stuff in simplified view! Current forms are overloaded.&A Nom du fichier – à compléter Management Presentation
  16. 16. Extended View: Web Client Elements&A Nom du fichier – à compléter Management Presentation
  17. 17. Example: Social Feature• In v7.0, social widget replace: – Information fields (create date, validated by, ...) – Internal requests system – “Res.log” message system – Communication & History tab on opportunities – View Log (created, modified by...) feature Nom du fichier – à compléter Management Presentation
  18. 18. Example 2: Remove AddressOn single “Contacts” menu for Partners, Addresses,Contacts. → No need anymore to have two fields(partner, address) per document (sale order,invoices, ...) Nom du fichier – à compléter Management Presentation
  19. 19. Page view of documents Page view of documents An invoice should look like an invoice. An invoice should look like an invoice.&A Nom du fichier – à compléter Management Presentation 19
  20. 20. Information is beautifullOpenERP forms have been designed for a creation / edition purpose. Butwhen people browse existing data, they have a completely differentneed. We need to show the information efficiently ! Not usefull when browsing or using customers, but good for creation ! I propose to create a PAGE view, which is the current readonly form → example on partners.&A Nom du fichier – à compléter Management Presentation
  21. 21. Page View, example 2&A Nom du fichier – à compléter Management Presentation
  22. 22. Dont make me think. We should better guide the user to the next step&A Nom du fichier – à compléter Management Presentation
  23. 23. Next Steps: not too much possibilities What should I do ?&A Nom du fichier – à compléter Management Presentation
  24. 24. Propose next steps Only one main button/option&A Nom du fichier – à compléter Management Presentation
  25. 25. Example: blinksale.com&A Nom du fichier – à compléter Management Presentation
  26. 26. Easy to use / configure Easy to use / configure Explain complex features Explain complex features&A Nom du fichier – à compléter Management Presentation 26
  27. 27. Avoid configuration menu  Configure from the main document itself!&A Nom du fichier – à compléter Management Presentation
  28. 28. Explain complex features (1/4) Complex features must be explained Complex features must be explained by an image or a dynamic sentence. by an image or a dynamic sentence. ← Javascript Tangle lib&A Nom du fichier – à compléter Management Presentation
  29. 29. Explain complex features (2/4) Complex features must be explained Complex features must be explained by an image or a dynamic sentence. by an image or a dynamic sentence. Test Tangle here: http://worrydream.com/#!/Tangle Its impossible to compute good mini/maxi without complex computations !&A Nom du fichier – à compléter Management Presentation
  30. 30. Explain complex features (3/4) Complex features must be explained Complex features must be explained by an image or a dynamic sentence. by an image or a dynamic sentence. When changing a value, it updates the flow schema.&A Nom du fichier – à compléter Management Presentation
  31. 31. Misc Improvements&A Nom du fichier – à compléter Management Presentation
  32. 32. Many2Many  Should be like a many2one with tags inside.  Exemples: • Taxes on invoice lines o Will allow many2many in editable lists. • Categories on partners&A Nom du fichier – à compléter Management Presentation
  33. 33. Train new users Empty lists must display an instructive message on how to proceed. → good replacement for our current menutips.&A Nom du fichier – à compléter Management Presentation
  34. 34. Better Workflow&A Nom du fichier – à compléter Management Presentation
  35. 35. Review main flows: SO  More business oriented: • You do not want to print a quotation → you want to send it to the customer (you may need to print it to do so, or email) • Sending a quotation to customer IS a step in the process • Done is not clear → Paid is better  ONE (and only one) button must mark clearly the NEXT action to avoid the user to think (what should I do now?)&A Nom du fichier – à compléter Management Presentation

×