Paul Louis BISBARRE
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # User testing template :::danger This template is prefill with *Lorem ipsum* text and some gaps "...". Replace it with your words. ::: :::warning ## Qualitative interview guide **Introduction** *Introduce yourself, briefly explain the purpose of the test and allow the participant(s) to comment or ask questions.* Q1: Are you female or male ? Q2: How old are you ? Q3: Where are you from ? **General information related to the topic** *Query the tester with general questions. Talk about his habits.* Q4: How often do you travel for work ? Q5: Do you often listen to music during your trips ? Q6: Are you frequently on conference calls ? **Behavior related to particular issues** *Ask him to express himself on your application, product or service. Feel free to use the prototype for this part.* Q7: Was the application clear and simple to use ? Q8: Did you have any issues when using the app ? Q9: Did you find the app efficient ? **Constructive suggestions for improvement** *Ask him how you could improve your prototype* Q10: What did you find missing / what can we improve ? ::: --- :::warning ## Testcard ## Pre-testing **Name:** Camille Guise **Age:** 43 years old **Occupation:** Entrepreneur **Context of the meeting (where, with who, etc.):** I asked Camille to test our application when we were together, in Lyon, in order to witness how the test would actually go and to help her understand what was the point of the whole exercise. **Duration of the meeting:** 40 minutes ## User scenarios testing **1st instruction** (this is your first scenario): You are an entrepreneur and you have to travel for professional reasons. During your trip, and more specifically during your waiting time at the airport, you use the Sound Freeze App in order to be able to keep working without being disturbed by your environement. **Observations:** My instructions were very broad and gave a lot of freedom to the entrepreneur testing the app. It was therefore sometimes hard for her to understand the point of the meeting. With these broad instructions, she did not spend a lot of time actually testing the application. Most of the times, she gave a quick look to the different parts we had designed without really trying to see if they were functionnal or helpful. --- **2nd instruction:** (this is your second scenario): You are an entrepreneur who travels a lot for her work and whose time is very important. You cannot afford to waste your time waiting, especially when you travel. You are in an airport, waiting for the moment to board your flight, and you have to be on an important conference call. You turn on your phone and open the Sound Freeze App to be sure that you will not miss any important information concerning your flight. During your call, you need to check once again these informations to confirm the time of your flight and to be sure you haven't missed anything too important. **Observations:** Creating a more realistic situation actually helped the tester knowing how she was supposed to behave and what she should look for on the application. This time, she did not explore all the parts of the application, but just the ones that were in the scenario. Even so, she spent more time actually testing the application and not just looking at it and therefore her review was more precise and more helpful. ## Qualitative testing **Positive feedback:** - The design is great - The application was quite easy to use and to understand - It also seems very efficient, it seems to get the job done --- **Neutral feedback:** - A functionality that enables the user to send the flight information or the various alerts by text message or through other applications would be useful and relevant - A category with real-time information concerning the flight of the user could be added, on the homepage for instance --- **Negative feedback:** - The part "History of flights" is not, in my opinion, interesting, especially as it is on the homepage --- **Learning & insights:** From that, we've learned that the design does a lot, but the practical aspects of the application are also very important. We understood that it is more important to have a clear application, easy to understand, than a complex one that would not be practical to use. --- **Decisions & actions:** To iterate, we will change the "History part" of our homepage and add a part were information about the flights is updated in real-time. ::: :::warning ## Qualitative interview guide **Introduction** *Introduce yourself, briefly explain the purpose of the test and allow the participant(s) to comment or ask questions.* Q1: Are you female or male ? Q2: How old are you ? Q3: Where are you from ? **General information related to the topic** *Query the tester with general questions. Talk about his habits.* Q4: How often do you travel for work ? Q5: Do you often listen to music during your trips ? Q6: Are you frequently on conference calls ? **Behavior related to particular issues** *Ask him to express himself on your application, product or service. Feel free to use the prototype for this part.* Q7: Was the application clear and simple to use ? Q8: Did you have any issues when using the app ? Q9: Did you find the app efficient ? **Constructive suggestions for improvement** *Ask him how you could improve your prototype* Q10: What did you find missing / what can we improve ? ::: --- :::warning ## Testcard ## Pre-testing **Name:** Sylvain Lagarde **Age:** 35 years old **Occupation:** Entrepreneur **Context of the meeting (where, with who, etc.):** I could not actually meet in real life with Sylvain so I organised a video-call during which I gave him the instructions and answered his questions. I sent him the link of our application, gave him the practical details on how to navigate through it and stayed with him on the call while he tested it to ask him the questions and take notes of his observations. **Duration of the meeting:** One hour ## User scenarios testing **1st instruction** (this is your first scenario): You are an entrepreneur and you have to travel for professional reasons. During your trip, and more specifically during your waiting time at the airport, you use the Sound Freeze App in order to be able to keep working without being disturbed by your environement. **Observations:** I decided to keep the exact same instructions as with Camille in order to have a more accurate representation of how the different tests would go. I had also found that it was quite a good idea to give the tester a lot of freedom in a first time, as it enabled him to have a full overview of our work. --- **2nd instruction:** (this is your second scenario): You are an entrepreneur who travels a lot for his work and whose time is very important. You cannot afford to waste your time waiting, especially when you travel.You are in an airport, waiting for the moment to board your flight, and you have to be on an important conference call. You turn on your phone and open the Sound Freeze App to be sure that you will not miss any important information concerning your flight. During your call, you need to check once again these informations to confirm the time of your flight and to be sure you haven't missed anything too important. **Observations:** I also kept exactly the same instructions as during the first time, for the same reasons as before. I thought it was important to be quite directive in a second time, to ensure that the tester would actually use the application and not just look at it. ## Qualitative testing **Positive feedback:** - The application is clear and simple to use - The application is efficient, it works well - It is well thought as everything is quite easy to understand and to use --- **Neutral feedback:** - No issues in particular --- **Negative feedback:** - I only had some troubles at first when trying to understand how the homepage works, it just took a little while but wasn't a major issue --- **Learning & insights:** From that, we've learned once again that the practical aspects of our work cannot be neglected and that it is crucial to our testers to understand how the application works. For this, we gathered that we had to be very clear in our layout and in the icons we used. Furthermore, all the information in the application should be easy to access. --- **Decisions & actions:** To iterate, we will probably reorganise the homepage to make sure it is as clear as possible. :::warning ## Qualitative interview guide **Introduction** *Introduce yourself, briefly explain the purpose of the test and allow the participant(s) to comment or ask questions.* Q1: Are you female or male ? Q2: How old are you ? Q3: Where are you from ? **General information related to the topic** *Query the tester with general questions. Talk about his habits.* Q4: How often do you travel for work ? Q5: Do you often listen to music during your trips ? Q6: Are you frequently on conference calls ? **Behavior related to particular issues** *Ask him to express himself on your application, product or service. Feel free to use the prototype for this part.* Q7: Was the application clear and simple to use ? Q8: Did you have any issues when using the app ? Q9: Did you find the app efficient ? **Constructive suggestions for improvement** *Ask him how you could improve your prototype* Q10: What did you find missing / what can we improve ? ::: --- :::warning ## Testcard ## Pre-testing **Name:** Thierry Bazoche **Age:** 49 years old **Occupation:** Entrepreneur **Context of the meeting (where, with who, etc.):** I found that meeting in real life was a lot more efficient to get the insights of the tester and to understand the difficulties he might encounter, so I met with Thierry in Paris, in order to make it practical and easy for both of us. **Duration of the meeting:** one hour ## User scenarios testing **1st instruction** (this is your first scenario): You are an entrepreneur and you have to travel for professional reasons. During your trip, and more specifically during your waiting time at the airport, you use the Sound Freeze App in order to be able to keep working without being disturbed by your environement. **Observations:** I decided to keep the exact same impressions as previously in order to have a more accurate representation of how the different tests would go. I had also found that it was quite a good idea to give the tester a lot of freedom in a first time, as it enabled him to have a full overview of our work. --- **2nd instruction:** (this is your second scenario): You are an entrepreneur who travels a lot for his work and whose time is very important. You cannot afford to waste your time waiting, especially when you travel.You are in an airport, waiting for the moment to board your flight, and you have to be on an important conference call. You turn on your phone and open the Sound Freeze App to be sure that you will not miss any important information concerning your flight. During your call, you need to check once again these informations to confirm the time of your flight and to be sure you haven't missed anything too important. **Observations:** I also kept exactly the same instructions as during the times before, for the same reasons as with the first instructions. I thought it was important to be quite directive in a second time, to ensure that the tester would actually use the application and not just look at it. ## Qualitative testing **Positive feedback:** - It is a really good idea and a great concept - Practicaly, it can be quite useful especially since travelling can take a lot of our personal time and be very stressful - Very good design, the application is easy to understand and to use --- **Neutral feedback:** - Why isn't the "Home" icon on the far-left? It seems more logical to me - It would be nice to have a place in the application where we could find real-time updated information --- **Negative feedback:** - Practicaly, where do I enter my flights? As this part is missing, the application does not seem too realistic - I do not understand the point of the "History" part of the homepage, what is its use ? Why would I need to see information about my previous flights ? --- **Learning & insights:** From that, we've learned that there are some practical issues that we do not always think about, just like the way to add a new flight through the application! We understood that testers can see things and think about details because of the distance they have when confronted with our work. --- **Decisions & actions:** To iterate, we will add an icon that enables the user to add his own flights. ::: :::warning ## Qualitative interview guide **Introduction** *Introduce yourself, briefly explain the purpose of the test and allow the participant(s) to comment or ask questions.* Q1: Are you female or male ? Q2: How old are you ? Q3: Where are you from ? **General information related to the topic** *Query the tester with general questions. Talk about his habits.* Q4: How often do you travel for work ? Q5: Do you often listen to music during your trips ? Q6: Are you frequently on conference calls ? **Behavior related to particular issues** *Ask him to express himself on your application, product or service. Feel free to use the prototype for this part.* Q7: Was the application clear and simple to use ? Q8: Did you have any issues when using the app ? Q9: Did you find the app efficient ? **Constructive suggestions for improvement** *Ask him how you could improve your prototype* Q10: What did you find missing / what can we improve ? ::: --- :::warning ## Testcard ## Pre-testing **Name:** Camille Guise **Age:** 43 years old **Occupation:** Entrepreneur **Context of the meeting (where, with who, etc.):** Once again, I met with Camille in Lyon at her appartment. **Duration of the meeting:** 30 minutes ## User scenarios testing **1st instruction** (this is your first scenario): You are an entrepreneur and you have to travel for professional reasons. During your trip, and more specifically during your waiting time at the airport, you use the Sound Freeze App in order to be able to keep working without being disturbed by your environement. **Observations:** I kept the exact same impressions as during the first test in oder to be able to compare them both easily and to be able to spot directly if we had made some progress. --- **2nd instruction:** (this is your second scenario): You are an entrepreneur who travels a lot for her work and whose time is very important. You cannot afford to waste your time waiting, especially when you travel.You are in an airport, waiting for the moment to board your flight, and you have to be on an important conference call. You turn on your phone and open the Sound Freeze App to be sure that you will not miss any important information concerning your flight. During your call, you need to check once again these informations to confirm the time of your flight and to be sure you haven't missed anything too important. **Observations:** For the same reasons as earlier, I kept the exact same scenario. ## Qualitative testing **Positive feedback:** - As with the first time, the design is really great - The application is still very efficient and quite easy to use --- **Neutral feedback:** - I see you simplified the bottom part of the application --- **Negative feedback:** - The part "History of flights" is still not, according to me interesting. However, it does not get in the way of a good use of the application and it does not disturb the user's experience --- **Learning & insights:** This time we learned that when something bothers a user, it will most likely keep bothering him or her during its use of the application. Most users will not get used to something they dislike, but they might keep using the application in spite of that. --- **Decisions & actions:** We will maybe delete the "History of flights" part of the application. ::: :::warning :::warning ## Qualitative interview guide **Introduction** *Introduce yourself, briefly explain the purpose of the test and allow the participant(s) to comment or ask questions.* Q1: Are you female or male ? Q2: How old are you ? Q3: Where are you from ? **General information related to the topic** *Query the tester with general questions. Talk about his habits.* Q4: How often do you travel for work ? Q5: Do you often listen to music during your trips ? Q6: Are you frequently on conference calls ? **Behavior related to particular issues** *Ask him to express himself on your application, product or service. Feel free to use the prototype for this part.* Q7: Was the application clear and simple to use ? Q8: Did you have any issues when using the app ? Q9: Did you find the app efficient ? **Constructive suggestions for improvement** *Ask him how you could improve your prototype* Q10: What did you find missing / what can we improve ? ::: --- :::warning ## Testcard ## Pre-testing **Name:** Sylvain Lagarde **Age:** 37 years old **Occupation:** Entrepreneur **Context of the meeting (where, with who, etc.):** This time again I was not able to meet in person with Sylvain, so we proceded the same time as before, by video call. **Duration of the meeting:** 40 minutes ## User scenarios testing **1st instruction** (this is your first scenario): You are an entrepreneur and you have to travel for professional reasons. During your trip, and more specifically during your waiting time at the airport, you use the Sound Freeze App in order to be able to keep working without being disturbed by your environement. **Observations:** I kept the exact same impressions as during the first test in oder to be able to compare them both easily and to be able to spot directly if we had made some progress. --- **2nd instruction:** (this is your second scenario): You are an entrepreneur who travels a lot for her work and whose time is very important. You cannot afford to waste your time waiting, especially when you travel.You are in an airport, waiting for the moment to board your flight, and you have to be on an important conference call. You turn on your phone and open the Sound Freeze App to be sure that you will not miss any important information concerning your flight. During your call, you need to check once again these informations to confirm the time of your flight and to be sure you haven't missed anything too important. **Observations:** For the same reasons as earlier, I kept the exact same scenario. ## Qualitative testing **Positive feedback:** - The application is still just as simple and efficient - The design is great --- **Neutral feedback:** - Nothing in particular was said --- **Negative feedback:** - I found that there are a lot of different pages and different categories that are not always very simple to understand - The application could be a little simpler --- **Learning & insights:** We learned once again that it is very important for users to have a simple and easily understable application. --- **Decisions & actions:** We will try to simplify as much as possible our application without deleting any functionnalities. ::: :::warning :::warning ## Testcard ## Pre-testing **Name:** Thierry Bazoche **Age:** 49 years old **Occupation:** Entrepreneur **Context of the meeting (where, with who, etc.):** This time I was not able to meet Thierry in person, so I proceeded just like with Sylvain, through video call. **Duration of the meeting:** 35 minutes ## User scenarios testing **1st instruction** (this is your first scenario): You are an entrepreneur and you have to travel for professional reasons. During your trip, and more specifically during your waiting time at the airport, you use the Sound Freeze App in order to be able to keep working without being disturbed by your environement. **Observations:** I decided to keep the exact same impressions as previously in order to have a more accurate representation of how the different tests would go. I had also found that it was quite a good idea to give the tester a lot of freedom in a first time, as it enabled him to have a full overview of our work. --- **2nd instruction:** (this is your second scenario): You are an entrepreneur who travels a lot for his work and whose time is very important. You cannot afford to waste your time waiting, especially when you travel.You are in an airport, waiting for the moment to board your flight, and you have to be on an important conference call. You turn on your phone and open the Sound Freeze App to be sure that you will not miss any important information concerning your flight. During your call, you need to check once again these information to confirm the time of your flight and to be sure you haven't missed anything too important. **Observations:** I also kept exactly the same instructions as during the times before, for the same reasons as with the first instructions. I thought it was important to be quite directive in a second time, to ensure that the tester would actually use the application and not just look at it. ## Qualitative testing **Positive feedback:** - The application still seems just as practical as before - I am glad to see you took my advice into account and added a "New flight" icon --- **Neutral feedback:** - The layout is clear --- **Negative feedback:** --- **Learning & insights:** The feedback was globally very positive this time, so we understood the importance of the role of the testing part of an application. --- **Decisions & actions:** As the testers seemed happy with our application, we decided to leave it the way it is. ::: :::warning

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully