11. Usability Methodology Prototypes WHAT? Dynamic simulations of the future interfaces, without care for the code behind it. WHY? To be able to test and iterate before actually developing the product.

12. Usability Methodology Iterative design WHAT? Ask a person to do a quick task on your interface. Apply a correction if they fail, then repeat. WHY? To detect early conception mistakes / improve product onboarding

15. Usability Methodology Quality surveys WHAT? A short and simple questionnaire. WHY? So you can measure user’s satisfaction (and eventually gather improvement suggestions by contacting them directly)

2. Usability Methodology What’s Usability about? Learnability How easy is it for users to accomplish basic tasks the first time they encounter the interface? Efficiency* Once users have learned the interface, how quickly can they perform tasks? Memorability When users return to the interface after a long period of not using it, how easily can they re - establish proficiency? Errors How many errors do users make, how severe are these errors, and how easily can they recover from the errors? Satisfaction How pleasant is it to use the interface? * Probably the most important for an ERP.

14. Usability Methodology As Is / To Be comparison As Is scenario To Be scenario Distribute his business cards / flyers at a fair. Manages incoming requests in his Email client Distribute his business cards at a fair, then manages the leads created automatically by Email. Manages his sales with an improvised system (ex: different folders in Email client) Follows a structured sales method with clear stages and a good overview of all ongoing opportunities Wants to estimate future revenues, uses an Excel file with custom calculations Switches to Graph view and immediately see Expected Revenues by Stage Manages each communication independently (messages by email, meetings in calendar, phone by mobile) Logs a history in Odoo of all his meetings, calls, discussions and documents sent.

13. Usability Methodology Test scenarios WHAT? Short descriptions of the user’s future tasks. WHY? To represent the To Be, and evaluate the new solution with accurate tasks. A sales representative: ● Distribute his business cards at a fair, then manages the leads created automatically by email. ● Follows a structured sales method with clear stages and a good overview of all ongoing opportunities. ● Switches to Graph view and immediately see Expected Revenues by Stage ● Logs a history by customer of all his meetings, calls, discussions and documents sent.

8. Usability Methodology User needs WHAT? The list of the Project’s Objectives, sorted by priority. WHY? So that all decisions are taken with the Project Objectives in mind. Charles 44 y.o, owner of a SME ● Knows his basic Sales jargon (understand what is a lead, an opportunity etc.) ● Has briefly used another CRM software before (familiar with the concepts of stages, probability, forecast etc.) ● Currently uses a Notepad, Excel file and Email client to manage his sales; one of his key objectives is to have everything in one place. ● Often on the road or at a customer’s place, so mobile is paramount for him.

10. Usability Methodology User scenarios A sales representative: ● Distribute his business cards at a fair, then manages incoming requests in his email client. ● Wants to manages his sales by stages. So he creates different folders in his email client. ● Wants to estimate future revenues, and uses an Excel file with custom calculations. ● Manages each communication independently (messages by email, meetings in calendar, phone by mobile) WHAT? Short descriptions of the user’s current tasks. WHY? To understand the As Is (current situation) versus To Be (proposed solution, represented by the test scenarios)

9. Usability Methodology Target users WHAT? Small and matter - of - fact description of your future user. WHY? So all the people working on the project have a tangible idea of who the end - users really is. Charles 44 y.o, owner of a SME ● Knows his basic Sales jargon (understand what is a lead, an opportunity etc.) ● Has briefly used another CRM software before (familiar with the concepts of stages, probability, forecast etc.) ● Currently uses a Notepad, Excel file and Email client to manage his sales; one of his key objectives is to have everything in one place. ● Often on the road or at a customer’s place, so mobile is paramount for him.