Speaker Feedback Tool – Final Outline

Since the last request for feedback regarding the scope and requirements for the proposed speaker feedback tool, we received plenty of very useful comments and were able to refine the requirements for the project down even further. This post outlines everything from that document taking into account the feedback given and decisions made since the last post.

Thank you to everyone who submitted feedback on the previous document: @iandunn @sippis @ryelle @jillbinder @andreamiddleton @coreymckrill @andymci & @mrwweb.

Project Goal

Improve the quality of content at WordCamps by providing a platform for WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. speakers to receive feedback from attendees about their talks.

Components

A. Feedback form

The frontend form will be for WordCamp attendees to provide feedback to speakers. The form includes the following elements:

  • Session selection drop-down menu – must be an autocomplete drop down menu, with accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) concerns taken into account.
  • Star rating for session
  • Three text area questions in the keep/tweak/delete format – these still need to be defined (and can be iterated upon after launch), but here is an example set:
    • What’s one good thing you’d keep in this session?
    • What’s one thing you’d tweak to improve the session?
    • What’s one unhelpful thing you’d delete from the session?

The form will be publicly accessible and anyone can fill it in. Form submissions will need to be run through Akismet, and if further spam becomes an issue then we can look into other spam prevention methods. If necessary, we could attempt to limit the form to only people who attended the WordCamp (perhaps by asking for their email address to use purely as verification). The talk selection, star rating and first text area will be required fields with the rest being optional.

B. Data storage

Feedback data will be stored as comments on the wcb_session post using a custom comment type. The star rating and each question will be stored as individual comment metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., and the comment content will be filtered on the fly to display all the answers when viewed.

C. Accessing stored feedback

Feedback will be displayed in the WordCamp site dashboard using the edit-comments.php template – this will either be a custom list table that mimics the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. one, or a direct usage of the core template. This will be accessible to anyone who has access to the site dashboard (the organising team, their mentor and all network admins).

An option will be added to allow this feedback view to be shared with the speaker. Speakers can be sent an email with a unique URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org that can be used to view the feedback. We could also allow speakers to access the feedback directly if we have their WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ username, and they are logged into the site.

Flows

A. Organiser

The feedback page will be automatically set up on site creation, so all the organiser will need to do is send the feedback link to attendees via email, social media and/or the site blog. After feedback has been received, organisers will have the chance to moderate the feedback before sending a unique link to speakers for them to view it. The feedback form will be automatically closed after a set amount of time (most likely 2 weeks). We can send an automated reminder email to organisers 2 weeks after the event to remind them about sending the feedback to speakers.

B. Attendee submitting feedback

A post-event email sent to attendees can direct them to the feedback page and/or speakers can include a link to the feedback page at the end of their session. Attendees select the talk they are giving feedback on, select a star rating, and fill in the answers to the three questions after which they will receive a “submitted successfully” alert.

C. Speaker

Speakers will receive a link from the organisers to view their feedback. We can add a “Was this feedback useful?” question for the speaker to submit as a way of tracking the value of the feedback.

Measuring Success

What can we measure?

  • How many people submit speaker feedback (compared to how people attended the event).
  • The quality of WordCamp talks, based on the star ratings that are submitted.
  • What percentage of speakers actually look at their feedback (we can log view counts).
  • The quality of the written feedback based on ratings supplied by speakers as well as manual processing.

We could also build a report (scrubbed of personal information) that is available along with the other meetup and WordCamp reports.

How do we know if it is a success?

We could set some specific targets here, but in general, we would know if this tool is a success if we see a reasonable percentage of attendees submitting quality speaker feedback. Knowing how many speakers are actually viewing the feedback would also be a useful metric here.

Pages

  1. Frontend feedback form on its own page (e.g. 2020.narnia.wordcamp.org/feedback).
  2. Frontend feedback form included on the session page itself (e.g., 2020.narnia.wordcamp.org/sessions/modern-leadership-is-about-empowerment-not-control). This page will not have the session selection drop-down menu.
  3. wp-admin screen for viewing feedback (based on the comments.php template)

Mockups