Upload
odoo
View
2.449
Download
0
Embed Size (px)
Citation preview
Nom du fichier – à compléter Management Presentation
OpenERPFeedback from our useability team.
- Fabien Pinckaers, CEO -
April 12th, 2012
Nom du fichier – à compléter Management Presentation
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
Example: Search View
Nom du fichier – à compléter Management Presentation
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
Useability Statistics
Nom du fichier – à compléter Management Presentation
Timing Comparison 6.0/6.1
PO SO0
4
8
12
16
20 19.819.44
14.16
11.93
6.06.1
Number of minutes to perform a full business flow for a lambda user. (Quotation → Sale Order → Delivery Order → Invoicing → Payment)
Nom du fichier – à compléter Management Presentation
Main issues encountered in 6.1 (%)
Menu
Form View
List View
Page View
Kanban View
Configuration
Search View
Business Flow
Widgets
0 10 20 30 40 50 60 70 80 90 100
14.28
14.29
28.57
33.33
37.5
38.19
46.43
56.35
73.68
Nom du fichier – à compléter Management Presentation
Global score given by users (/10)
Score /100
2
4
6
8
10
0.6
5.5
6.06.1
Nom du fichier – à compléter Management Presentation
Useability ExamplesV7.0 – demo new design
Nom du fichier – à compléter&A Management Presentation
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.
Nom du fichier – à compléter Management Presentation
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&A Management Presentation
Simplification → Remove ElementsSimplification → Remove Elements
12
Nom du fichier – à compléter&A Management Presentation
To simplify, we must reduce!
Remove what's:• Redundant• Not used
Hide:• What's not required to use the application
Adding features → complexity for the application
Simplification through reduction
Nom du fichier – à compléter&A Management Presentation
Remove redundant/unused features
To be removed:• Shortcuts → if the menu is simple, we don't 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)
Nom du fichier – à compléter&A Management Presentation
Extended View: Simplify Forms
We don't need all those stuff in simplified view!Current forms are overloaded.
Nom du fichier – à compléter&A Management Presentation
Extended View: Web Client Elements
Nom du fichier – à compléter Management Presentation
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
Example 2: Remove Address
On 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&A Management Presentation
Page view of documentsAn invoice should look like an invoice.
Page view of documentsAn invoice should look like an invoice.
19
Nom du fichier – à compléter&A Management Presentation
Information is beautifull
OpenERP forms have been designed for a creation / edition purpose. But when people browse existing data, they have a completely different need. 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.
Nom du fichier – à compléter&A Management Presentation
Page View, example 2
Nom du fichier – à compléter&A Management Presentation
Don't make me think.We should better guide the user to the next step
Nom du fichier – à compléter&A Management Presentation
Next Steps: not too much possibilities
What should I do ?
Nom du fichier – à compléter&A Management Presentation
Propose next steps
Only one mainbutton/option
Nom du fichier – à compléter&A Management Presentation
Example: blinksale.com
Nom du fichier – à compléter&A Management Presentation
Easy to use / configureExplain complex features
Easy to use / configureExplain complex features
26
Nom du fichier – à compléter&A Management Presentation
Avoid configuration menu
Configure from the main document itself!
Nom du fichier – à compléter&A Management Presentation
Explain complex features (1/4)
Complex features must be explainedby an image or a dynamic sentence.
Complex features must be explainedby an image or a dynamic sentence.
← Javascript Tangle lib
Nom du fichier – à compléter&A Management Presentation
Explain complex features (2/4)
Complex features must be explainedby an image or a dynamic sentence.
Complex features must be explainedby an image or a dynamic sentence.
Test Tangle here: http://worrydream.com/#!/TangleIt's impossible to compute good mini/maxi without complex computations !
Nom du fichier – à compléter&A Management Presentation
Explain complex features (3/4)
Complex features must be explainedby an image or a dynamic sentence.
Complex features must be explainedby an image or a dynamic sentence.
When changing a value, it updates the flow schema.
Nom du fichier – à compléter&A Management Presentation
Misc Improvements
Nom du fichier – à compléter&A Management Presentation
Many2Many
Should be like a many2one with tags inside.
Exemples:• Taxes on invoice lines
o Will allow many2many in editable lists.
• Categories on partners
Nom du fichier – à compléter&A Management Presentation
Train new users
Empty lists must display an instructive message on how to proceed. → good replacement for our current menutips.
Nom du fichier – à compléter&A Management Presentation
Better Workflow
Nom du fichier – à compléter&A Management Presentation
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?)