Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js User Feedback initiative #96

Closed
hackygolucky opened this issue Jul 27, 2017 · 14 comments

Comments

@hackygolucky
Copy link
Member

commented Jul 27, 2017

I was chatting with @mhdawson this week, and he expressed the need for forming Node.js user feedback mechanisms so that we as a project can be improving on a much shorter timeline from said feedback that we've gotten from work such as our annual user survey. This also allows us to get perspectives from a much wider audience than we generally get in our committee meetings(TSC, CommComm, CTC, etc). We'd discussed this as an area of scope with the CommComm when it is was formed, but no one has kicked off a formal 'let's do this'.

So let's do this!

Suggested mediums for user feedback:

  • surveys: much smaller, more tightly scoped, and can be shared in a shorter timeframe than the annual survey.
  • user focus groups: gathering users at events such as meetups, confs, and internal meetings at companies that allow us to observe, gather data, and synthesize for actionable change.

Please suggest other forms of user research formats that could be helpful. If you know any folks with user research experience, it would be awesome to ping them and have them chime in here. After we establish types of formats we can be doing, we'll open individual issues about the how-to for approaching implementing each of these.

@mhdawson

This comment has been minimized.

Copy link
Member

commented Jul 29, 2017

The two options you have are the best 2 I can think of as well. One more that may or may not be uesfull is to see if any of the existing foundation members fall into the category of "users"s versus vendors and if so reach out to them to see if they are willing/capability of participating in capturing user feedback.

@nebrius

This comment has been minimized.

Copy link
Contributor

commented Jul 31, 2017

Would this be something for @nodejs/evangelism to take a look at? I suspect this could fall under their domain.

@lordKnighton

This comment has been minimized.

Copy link

commented Jul 31, 2017

@hackygolucky Sounds like a plan.

And I think https://nodejs.org/en/ wouldn't be a bad portal to get some feedback.

@bnb

This comment has been minimized.

Copy link
Member

commented Aug 1, 2017

Great idea. Coming from an Evangelism perspective, it's really nice to have some collateral to be able to easily share on social for feedback on technical issues.

@nebrius definitely could be a good fit for the Evangelism WG. Defining some questions, length, and structure are a 👌 way to start out.

@mhdawson

This comment has been minimized.

Copy link
Member

commented Aug 15, 2017

I'm wondering how we define next steps so that we can move this forward. @bnb do think somebody from the Evangelism and lead the effort ?

@gtewallace

This comment has been minimized.

Copy link

commented Aug 15, 2017

In addition to promoting this on the web site and via evangelism channels, in the annual survey we ask respondents to provide their email if they would be willing to be contacted by the Node.js Foundation for additional questions. @hackygolucky could create an alias with these folks and send them an email - or we can do out of mailchimp. there are around 250 people in the list who provided email addresses saying they are OK being contacted.

@hackygolucky

This comment has been minimized.

Copy link
Member Author

commented Aug 15, 2017

For the Community Committee to be able to really act on anything, getting this feedback/data is a core responsibility of the CommComm members themselves and the Individual Membership Directors.

Each Individual Membership Director is responsible for soliciting feedback and data that represents the wishes of other individual members and the community at large. source

Evidence-based decision-making tends to produce better outcomes thanks to getting the perspectives needed to act. Evangelism is a vehicle for sharing out what we are doing through communications, social media, etc.

Why not have a member of the CommComm directly volunteer to do this work? To some extent, CommComm itself also needs to be producing output, which is why I filed this issue. We certainly need to figure out a way to project manage this type of work , but I don't think delegating work is getting it done. We've got a ton of open issues right now that aren't getting tackled.

My suggestion for next steps:

  • File an issue for a planning meeting where the initiative can be hashed out and a project plan is written. The Individual Directors should be present. In this meeting:
    • choose a survey medium(SurveyMonkey, Google forms, etc.)
    • make a list of current small surveys/feedback we need and create a schedule for these
    • document how folks could request a survey question/set(likely issue filing or a PR flow) so we could continue to add to the survey schedule moving forward
    • Identify relevant gatherings for holding user focus groups: choose a few places as a first step that people IN the meeting will be present at and could hold a meeting, collect feedback, and synthesize for publish.
  • Publish User Feedback Initiative plan, implement, and iterate.
  • coordinate with the Evangelism WG to share the surveys via their platform using the schedule
@dshaw

This comment has been minimized.

Copy link
Member

commented Oct 26, 2017

@hackygolucky I met with @williamkapke and @mikehostetler. In terms of availability and interest, it looks like it will fall on me to lead this initial bootstrap phase with their support. I'm game, but am going to seek some very explicit permission first since this is a massive undertaking.

  1. Can I even lead this effort since I am only a CommComm Observer?
  2. I would like to start by focusing on establishing end user communications channels first with tooling and technique as a secondary consideration.
  3. Who are the individuals who would need to sign-off to ensure that handoff of this initiative is explicit and that none of the original objectives are lost? As far as I can tell, that would be @hackygolucky and @mhdawson.

Many folks know me and I have been an active community member for a very long time, but I am actually not well versed in the norms and processes of Node.js here on GitHub. I welcome all of your feedback and am intentionally trying to follow new user paths and behavior to help model process and governance improvements. 🙏

@dshaw

This comment has been minimized.

Copy link
Member

commented Oct 26, 2017

Notes from 2017-10-26 breakout meeting on #96

We discussed bootstrapping a new group in the Node.js CommComm focused on User Feedback and Outreach.

@dshaw is spearheading the effort with active contributions to the scoping efforts from @williamkapke, Individual Member Director of the Node.js Foundation, and @mikehostetler, Chicago Node.js/JS Community Leader.

We have identified key areas of interest for each of the bootstrap team:
@dshaw - Enterprise Users
@williamkapke - Individual Members of the Node.js Foundation
@mike Hostetler - Chicago Node.js/JS Community - with the intention to see how solving local needs in Chicago can serve as a model for other local communities

Since there’s a pretty massive potential scope of effort with this project, @dshaw is going to seek explicit permission first. This goes against the current norms of the Node.js project, but is vital to the bootstrap team to be able to justify the investment of time and effort.

All are welcome and will always be welcome. At this time we are explicitly seeking collaborators who can dedicate 5+ hours/month to get this effort off the ground and assist in project scoping. If you are engaged with community in any of the 3 key interest areas: Enterprise, Individual Membership, Local Communities and have interest and availability, please join us.

@hackygolucky

This comment has been minimized.

Copy link
Member Author

commented Oct 31, 2017

Google Doc from the initial meeting that @bnb and @mhdawson and I had on this. Glad y'all are hopping on this!

@dshaw

This comment has been minimized.

Copy link
Member

commented Oct 31, 2017

I wanted to say thank you to @hackygolucky @mhdawson @bnb and @williamkapke for all the support in working through this and getting this effort off the ground. 🙏

@bnb bnb added the user-feedback label Dec 4, 2017
@bnb

This comment has been minimized.

Copy link
Member

commented Dec 28, 2017

@dshaw @hackygolucky since there's been a significant amount of work done on the User Feedback Initiative outside of this issue, can we close this issue?

@mhdawson

This comment has been minimized.

Copy link
Member

commented Jan 8, 2018

I'd be +1 on closing this and tracking through issues in the user-feedback repo.

@bnb

This comment has been minimized.

Copy link
Member

commented Jan 8, 2018

Closing 👍

@bnb bnb closed this Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.