A | B | C | |
---|---|---|---|
1 | Templates that project teams are using to track input and responsiveness | ||
2 | The process of recording user feedback enhances transparency and can help demonstrate that the input is valued — with users as well as within project teams. This tool includes a series of templates developed by various project teams to support their needs related to tracking user input. You may find one of these templates to be just what you need or be inspired to craft your own, drawing on one or more elements you see in these examples. | ||
3 | |||
4 | Description of templates in the following tabs: | ||
5 | Meeting input and follow up response | A project team uses this spreadsheet to organize feedback captured during advisory committee meetings and their process for developing responses that will be shared ahead of the next meeting. Source: Mangrove Coast Collaborative / Colaboración En Mangles Costeros: Understanding Links between Degradation, Recovery, and Community Benefits | |
6 | Feedback from multiple sources | A project team uses this template to organize user feedback gathered through surveys and emails. The template tracks the team’s process for deciding whether or not to raise the topic with the advisory group as well as corresponding actions and responses. Source: A National Synthesis of Tidal Marshes to Detect Impacts of Climate Change across Multiple Scales | |
7 | Decision making processes | This spreadsheet is used during advisory group meetings to organize key questions to raise to the group and to capture the individual opinions along with the overall consensus on the appropriate action and response. Source: A National Synthesis of Tidal Marshes to Detect Impacts of Climate Change across Multiple Scales | |
8 | |||
9 | Notes from teams: | ||
10 | - It's helpful to track end user input and requests carefully, and record what you're doing with this information. It is useful to share the input and response with the advisory group for transparency, either in the form of these spreadsheets or summaries of the information. - Keep track of the things that you can't work on too, and elaborate on it - what would it take to actually respond to these things adequately? - Take time to listen and respond to ideas and concerns. Following up with thoughtful responses and, where possible, adjustments to the plan or process. It feels especially meaningful when a project team pivots in a real way because of the feedback - users see it and feel motivated. - If input is collected over a period of time, make an effort to occasionally stop and acknowledge what you've been hearing (names if appropriate!), specifics of how the input is incorporated into the work, and what comes next. | ||
11 | |||
12 | |||
13 | |||
14 | |||
15 | |||
16 | |||
17 | |||
18 | This tool is part of an online Guide to Collaborative Science and was developed by the National Estuarine Research Reserve System’s Science Collaborative Program. | ||
19 | |||
20 | |||
21 | |||
22 | |||
23 | |||
24 | |||
25 | |||
26 | |||
27 | |||
28 | |||
29 | |||
30 | |||
31 | |||
32 | |||
33 | |||
34 | |||
35 | |||
36 | |||
37 | |||
38 | |||
39 | |||
40 | |||
41 | |||
42 | |||
43 | |||
44 | |||
45 | |||
46 | |||
47 | |||
48 | |||
49 | |||
50 | |||
51 | |||
52 | |||
53 | |||
54 | |||
55 | |||
56 | |||
57 | |||
58 | |||
59 | |||
60 | |||
61 | |||
62 | |||
63 | |||
64 | |||
65 | |||
66 | |||
67 | |||
68 | |||
69 | |||
70 | |||
71 | |||
72 | |||
73 | |||
74 | |||
75 | |||
76 | |||
77 | |||
78 | |||
79 | |||
80 | |||
81 | |||
82 | |||
83 | |||
84 | |||
85 | |||
86 | |||
87 | |||
88 | |||
89 | |||
90 | |||
91 | |||
92 | |||
93 | |||
94 | |||
95 | |||
96 | |||
97 | |||
98 | |||
99 | |||
100 |