Learning patterns/Feedback cycle
What problem does this solve? edit
Most promising projects start with a great idea and a detailed and realistic plan of action. However, project teams may lose sight of their original goals, or may realize too late that they made some incorrect assumptions at the beginning of their project about what their audience needed, or how to address those needs most effectively. New opportunities and new challenges arise during the course of every project. All of these factors affect your final outcome: whether the tool you designed is useful and widely-used, or whether the event you planned is successful and well-attended.
What is the solution? edit
Whether your goal is to directly engage people to do something or provide them with resources to help them do it on their own, you need to ask for their input on both your initial plans and on your progress. Ask for feedback from your target audience at regular intervals during your project, ideally at points where you have new questions to ask them, or new information to share.
You also need to be willing to make changes to your process or your plan based on that feedback. Highly successful projects often repeat the cycle of eliciting feedback and making changes based on that feedback several times over the course of the project. This process, called iteration, is an important part of user-centered design, which is a set of methods that can be used to design many different things, from software and websites to an edit-a-thon or a curriculum.
General considerations edit
- Ask for input when you have something new to share. Good times to ask for feedback include after you have revised your project plan, or created a prototype, or collected data from a survey.
- Respond to feedback. Let the people you know that you appreciate their feedback, even if you do not intend to follow their advice. Ask follow-up questions if someone gives feedback that surprises you, or that you do not immediately understand.
- Unvoiced feedback Some users or attendees will provide little or no feedback. At times they can represent the "silent majority". Look for incongruities between your expectations and actual use. This article from Visual Studio Magazine gives some helpful ideas on listening to feedback. It is also important to request feedback sincerely rather than because it is expected. Most users/attendees have an opinion or idea to improve but do not want to spend their time giving feedback that will not be heard.
When to use edit
- Educational initiatives
Members of the WikiArs project, which focused on designing an initiative to encourage art students to contribute high-quality graphics to Wikimedia Commons, asked for feedback from art school professors on their initial drafts of the art course assignment sheets they were asking the professors to use. They worked with the professors to improve the assignments and integrate them into the rest of the course materials.
- Tutorials and online games
Members of The Wikipedia Adventure project ran usability studies with early prototype of the game, and later recruited Wikipedians to play an Alpha version. Significant changes were made to the design of the interface and the specific game missions based on these two feedback cycles.
- Jmorgan (WMF)
- bonjour je souhaite faire mon groupe avec les autre Papykabi (talk) 12:12, 9 June 2016 (UTC)
- Very useful reminder. Fjjulien (talk) 16:42, 30 January 2021 (UTC)
- In the Web2Cit project we are trying to promote feedback cycles with our community by having an Advisory Board. Diegodlh (talk) 12:10, 28 March 2022 (UTC)