From the course: Delivering and Analyzing a Software Pilot: GitHub Copilot

Methods for collecting feedback - Github Copilot Tutorial

From the course: Delivering and Analyzing a Software Pilot: GitHub Copilot

Methods for collecting feedback

“

- [Instructor] Whilst I'm certainly no expert in the kitchen, I know that you should never cook a new recipe without tasting it along the way. You might follow the instructions perfectly, but without that instant feedback, you won't know if the dish is too bland or salty, or just right, until it's too late. The same is true of running a project. You need that feedback to make timely adjustments and ensure success. So, let's explore in this video the importance of collecting feedback during a project, discuss different methods of gathering that feedback and help you choose the right method for your specific needs. Collecting feedback is crucial because it allows you to make informed decisions, identify potential issues early, and understand how well your project is meeting its objectives. Feedback helps you stay on course and to make necessary adjustments before it's too late. One of the most common methods of collecting feedback that I personally recommend is through surveys. Surveys can be distributed to a large audience, allowing you to gather a broad range of opinions. They can be structured with multiple choice questions to gather quantitative data or open-ended questions for qualitative insights. Another effective method is conducting interviews. Now, interviews provide a more in-depth understanding of participant experiences and opinions. While they are more time consuming, interviews allow for follow-up questions and deeper exploration of specific topics. One of the ways I've used interviews is to explore specific negative feedback about a project to find out the reason that specific user might have been having a hard time and what I could do to help. Focus groups are also really valuable, particularly when you want to explore ideas in a collaborative setting. In a focus group, participants can discuss their experiences and ideas, often leading to richer feedback as they build on each other's thoughts. And don't overlook the power of being on observation duty. Sometimes watching how users interact with your product or process can reveal issues or opportunities that participants might not think to mention in a survey or an interview. Observational feedback is especially useful for any UI or UX projects or when physically testing products. Each of these methods has its strength. So, how do you choose the right one? Well, consider your project's specific needs, the type of feedback you are looking for, and your available resources. For instance, if you need broad quantitative data, surveys might be best. If you are exploring complex issues, interviews or focus groups could be more effective. It's also important to consider the timing of your feedback collection. Early stage feedback might require broader methods like surveys, while mid or late stage feedback could benefit from more in-depth methods like interviews or focus groups. So, collecting feedback is a vital part of managing a successful pilot project. By understanding the different methods available, surveys, interviews, focus groups, and direct observation, you can choose the right approach for your needs and gather the insights necessary to guide your project to success. And coming up next, we'll look at how to organize and prepare the feedback you've collected for analysis, ensuring that you can extract meaningful insights and take action effectively. So, stay tuned!

Contents