Filter by topic and date
IETF 122 post-meeting survey
- Jay Daley IETF Executive Director
17 Apr 2025
The IETF 122 Bangkok meeting was held 15-21 March 2025.
The results of the post-meeting survey are now available on a interactive dashboard. Thank you to all of you who responded to this survey as we use your views to continually adjust the meeting experience.
Analysis
We received 244 responses, 196 onsite and 48 remote. With 1424 registered participants, this gives the survey a maximum margin of error of +/- 5.71%.
The results for satisfaction questions include a mean and standard deviation using a five point scale scoring system of Very satisfied = 5, Satisfied = 4, Neither satisfied nor dissatisfied = 3, Dissatisfied = 2, Very dissatisfied = 1. While there’s no hard and fast rule, a mean of above 4.50 is sometimes considered excellent, 4.00 to 4.49 is good, 3.50 to 3.99 is acceptable and below 3.50 is either poor or very poor if below 3.00. The satisfaction score tables also include a top box, the total of satisfied and very satisfied, and a bottom box, the total of dissatisfied and very dissatisfied, both in percentages. Please note that a small number of questions are on a four point scale.
Question changes since the last survey
For this survey a new question about side meetings was added and new questions relating to the revised new participant program. The question on avoiding conflicts was dropped as no further changes are planned to improve this. The question about various aspects of the hotel was reintroduced as this meeting was in a hotel but with some different choices.
Actions taken following the last survey
For this meeting, we made the following changes, prompted by survey feedback:
- The side meeting booking process was revised, as the first step in improving the side meeting experience overall.
- The amount of rented furniture was increased to supplement the venue provided furniture and to provide additional seating areas in the distributed spaces
- Break options for food were reviewed in light of better data about dietary requirements
- Directional signage was increased to guide participants through the distributed space
Satisfaction
Overall satisfaction is 4.49, a good result. With some key exceptions, the satisfaction scores remain high.
The table below shows the satisfaction scores for the last six meetings, along with colour coded indicators for the five point scale above: excellent (🔵), good (🟢), acceptable (🟡), poor (🔴), very poor (⚫️)
IETF 122 Bangkok | IETF 121 Dublin | IETF 120 Vancouver | IETF 119 Brisbane | IETF 118 Prague | IETF 117 San Francisco | |
---|---|---|---|---|---|---|
Overall satisfaction | 4.49 🟢 | 4.30 🟢 | 4.37 🟢 | 4.24 🟢 | 4.42 🟢 | 4.30 🟢 |
AGENDA | ||||||
Overall agenda | 4.40 🟢 | 4.21 🟢 | 4.19 🟢 | 4.05 🟢 | 4.20 🟢 | 4.16 🟢 |
Sessions for WGs | 4.46 🟢 | 4.42 🟢 | 4.29 🟢 | - | 4.32 🟢 | 4.22 🟢 |
BOFs | 4.07 🟢 | 4.33 🟢 | 4.12 🟢 | - | 4.12 🟢 | 3.95 🟡 |
Sessions for RGs | 4.22 🟢 | 4.22 🟢 | 4.20 🟢 | - | 4.09 🟢 | 4.12 🟢 |
Plenary | 4.10 🟢 | 4.25 🟢 | 3.84 🟡 | - | 3.94 🟡 | 3.99 🟡 |
Side meetings | 3.93 🟡 | 3.91 🟡 | 3.87 🟡 | - | 3.79 🟡 | 3.75 🟡 |
Hackathon | 4.50 🔵 | 4.32 🟢 | 4.30 🟢 | - | 4.27 🟢 | 4.25 🟢 |
HotRFC | 4.02 🟢 | 4.13 🟢 | 3.94 🟡 | - | 3.90 🟡 | 3.89 🟡 |
Pecha Kucha | 4.20 🟢 | 4.08 🟢 | - | - | 4.00 🟢 | 4.15 🟢 |
Office hours | 4.15 🟢 | 4.27 🟢 | 3.97 🟡 | - | 4.07 🟢 | 3.98 🟡 |
Opportunities for social interaction | - | - | - | - | 4.06 🟢 | 4.11 🟢 |
STRUCTURE | ||||||
Overall meeting structure | 4.38 🟢 | 4.31 🟢 | 4.28 🟢 | 4.15 🟢 | 4.34 🟢 | 4.28 🟢 |
Start time | 4.39 🟢 (9:30am) | 4.40 🟢 (9:30am) | 4.40 🟢 (9:30am) | - | 4.49 🟢 (9:30am) | 4.28 🟢 (9:30am) |
Finish time Friday | 4.24 🟢 (4:30pm) | 3.63 🟡 (5pm) | 3.67 🟡 (5pm) | - | 3.65 🟡 (5pm) | - |
Lunch break timing | 3.95 🟡 (11:30am) | 3.91 🟡 (11:30am) | - | - | - | - |
Length of day | 4.31 🟢 | 4.11 🟢 | 4.18 🟢 | - | 4.20 🟢 | 4.30 🟢 |
Number of days | 4.33 🟢 (5+2) | 4.13 🟢 (5+2) | 4.15 🟢 (5+2) | - | 4.18 🟢 (5+2) | 4.27 🟢 (5+2) |
Session lengths | 4.42 🟢 (60 / 90 / 120) | 4.36 🟢 (60 / 90 / 120) | 4.36 🟢 (60 / 90 / 120) | - | 4.38 🟢 (60 / 90 / 120) | 4.41 🟢 (60 / 90 / 120) |
Break lengths | 4.38 🟢 (30/90) | 4.31 🟢 (30/90) | 4.31 🟢 (30/90) | - | 4.38 🟢 (30/90) | 4.32 🟢 (30/90) |
Number of parallel tracks | 4.09 🟢 (8) | 4.06 🟢 (8) | 3.94 🟡 (8) | - | 3.94 🟡 (8) | 4.08 🟢 (8) |
CONFLICTS | ||||||
Conflict avoidance | - | 4.05 🟢 | 3.93 🟡 | 3.88 🟡 | 4.00 🟢 | 3.90 🟡 |
VENUE & ACCOMM | ||||||
Venue overall | 4.38 🟢 | - | - | 3.90 🟡 | ||
Options for accommodation | - | 3.71 🟡 | 3.68 🟡 | 4.10 🟢 | - | - |
Cost of rooms | 3.69 🟡 | - | - | - | 3.54 🟡 | 2.87 ⚫️ |
Proximity to other accommodation | 4.44 🟢 | - | - | - | - | - |
Proximity to amenities | 4.51 🔵 | - | - | - | - | - |
Hotel location | 4.14 🟢 | - | - | - | 4.52 🔵 | 3.60 🟡 |
Layout of the venue | 4.17 🟢 | - | - | - | - | - |
ONSITE | ||||||
Overall | 4.47 🟢 | 4.19 🟢 | 4.44 🟢 | 4.37 🟢 | 4.50 🔵 | 4.29 🟢 |
Badge collection | - | 4.65 🔵 | 4.73 🔵 | 4.71 🔵 | 4.70 🔵 | 4.69 🔵 |
WiFi | 4.42 🟢 | 4.37 🟢 | 4.25 🟢 | 4.09 🟢 | 4.17 🟢 | 3.98 🟡 |
Realtime transcripts | - | 4.08 🟢 | - | - | - | - |
QR Codes | - | 4.17 🟢 | 4.31 🟢 | 4.31 🟢 | 4.18 🟢 | 4.11 🟢 |
Break F&B | 4.70 🔵 | 2.88 ⚫️ | 4.15 🟢 | 3.75 🟡 | 4.05 🟢 | 4.44 🟢 |
Breakout seating | 4.13 🟢 | 3.43 🔴 | 3.54 🟡 | 3.93 🟡 | 3.80 🟡 | 4.08 🟢 |
Signage | 4.33 🟢 | 4.14 🟢 | 4.08 🟢 | 3.96 🟡 | 4.15 🟢 | 4.22 🟢 |
Coffee carts | - | 4.31 🟢 | 4.65 🔵 | 4.08 🟢 | 4.64 🔵 | 4.56 🔵 |
Childcare | - | 4.50 🔵 | 4.43 🟢 | 3.76 🟡 | 4.12 🟢 | 4.06 🟢 |
Games night | 4.07 🟢 | 4.15 🟢 | - | - | - | - |
Welcome reception | 4.33 🟢 | 4.05 🟢 | 4.01 🟢 | 3.97 🟡 | 4.08 🟢 | - |
Farewell reception | 4.42 🟢 | 4.29 🟢 | 4.31 🟢 | 4.15 🟢 | 4.34 🟢 | - |
REMOTE | ||||||
Sound quality | - | 4.53 🔵 | - | - | - | - |
Video feed | - | 4.42 🟢 | - | - | - | - |
Audio and video | 4.48 🟢 | - | - | - | - | - |
Onsite respect of remote | - | 4.47 🟢 | - | - | - | - |
Queue management | - | 4.61 🔵 | - | - | - | - |
Tool features | 4.43 🟢 | - | - | - | - | - |
Remote support in sessions | 4.51 🔵 | - | - | - | - | - |
Remote support generally | 4.48 🟢 | - | - | - | - | - |
High satisfaction scores
Overall
The overall satisfaction score for this meeting was at the top end of good. Given that onsite participation was only 54% of total participation, this cannot all be down to the excellent food and beverage service during breaks.
Remote participation
The questions here were adjusted to focus on the quality of the remote experience and the satisfaction scores here are very good. The IETF has invested significantly in improving this experience, both financially and in changing processes, and this has clearly paid off.
Hackathon
The satisfaction score for the Hackathon jumped into the excellent range for the first time. though the survey otherwise has little evidence as to what led to that.
New Participant Program
Each of the individual areas of the New Participant Program that were surveyed about received a good satisfaction score, with an excellent overall score. There are some further improvements that could be made, and some specific comments to consider, but overall the revised program was real success.
Areas for improvement
Lunch break timing
The lunch break at 11:30am has never been popular. For IETF 123 Madrid an attempt will be made to have this later in the day, which is hoped will improve satisfaction here.
Side meetings
Scores for side meetings are slowly improving as minor, incremental changes are made but improvement is still needed. This will be a topic for discussion between the IESG, IETF LLC and Secretariat, before the next meeting and further changes are likely to come from that.
Individual comments
The individual comments covered a number of key themes, most of which have already been covered above, leaving the following:
- IETF 127. There were several comments recommending that the IETF does not meet in the US for IETF 127. The IETF LLC board issued a request for feedback regarding this matter, soon after the meeting and will be considering this at its May retreat.
- Room temperature. The meeting rooms were far too cold and this was not dealt with well enough. I apologise for that - we will try to ensure this does not happen again.
- Inconvenience of location/timezone. There were a number of comments recommending changes to our meeting booking policy to avoid inconveniences of location, travel or timezone. Unfortunately it is never going to be possible to find a location or timezone that suits everyone.
- Social events. One commenter asked why we were not having social events given "It costs pennies overall". Social events generally cost from $100,000 to $150,000 even with tickets sales accounted for, and are paid for solely by the meeting host, not the IETF. For several meetings now, meeting hosts have not had the budget to pay for these. If the IETF were to pay then that would mean an additional $100-$200 per registration, not including the cost of the social event ticket.
- Other comments. Other comments will be passed on to the appropriate people to consider.
And finally
Thank you everyone who responded to this survey, your feedback is much appreciated.