### Problem to Solve > We're proposing a number of additions to the profile dropdown: > - [What's new](https://gitlab.com/gitlab-org/gitlab-ce/issues/25341) > - [Contribute to GitLab](https://gitlab.com/gitlab-org/gitlab-ce/issues/47274) > - [Submit feedback](https://gitlab.com/gitlab-org/gitlab-ce/issues/43623) > - [Free health-check](https://gitlab.com/gitlab-org/gitlab-ee/issues/7345) > - [Status messages](https://gitlab.com/gitlab-org/gitlab-ce/issues/49075) > This is in addition to Help. reference: https://gitlab.com/gitlab-org/gitlab-ce/issues/48924 #### What questions are you trying to answer? - Where do users expect to find each of the proposed additions? - What do users currently do in each of these situations? (e.g. what's their process for submitting feedback, contributing to GitLab, alerting their team of their availability, etc) - What's their current process vs ideal process? #### What assumptions do you have? - > All of these "meta" items relate to interacting with and understanding your GitLab instance. > - The 4 items mentioned above don't seem to belong to the user menu. - > The profile dropdown should organize options that directly relate to me as a user; > - My user info, Profile, Settings, and Sign out all match this pattern. The rest do not. reference: https://gitlab.com/gitlab-org/gitlab-ce/issues/48924 ### Other Considerations - https://gitlab.com/gitlab-org/gitlab-ce/issues/48924#note_91288639 **Whats new** - Which releases should the user be most informed of? (or which aspects of a new release would users want to be informed of) - Why do some users not update their instance to the newest version? - Are customers more likely to update their instance if we inform them of a new version consistently? **Contribute to GitLab** - What percentage of users have contributed to GitLab? - What led them to contribute? - Did they look for guidelines on how to contribute before doing so? - If yes, where did they find information on how to contribute? - If no, how did they figure out what to do? - Are users of GitLab unaware that we are open source? - Are users of GitLab unaware that they are welcomed and encouraged to contribute? - If they are unaware and learn that this is possible, how likely are they to contribute? - Is promoting our open source nature something we should be pushing in product? Are marketing efforts enough? - Would a user visiting their profile/settings be likely to begin contributing if they see this link? - Are gitlab.com users aware that we added the "Contribute to GitLab" link to the user menu? (have they seen it before) **Submit feedback** - Where are users currently looking to submit feedback? - Were the customers who reported issues with submitting feedback looking at about.gitlab.com? - We have a contact page on the about website, but it only links to the contributing page, not a feedback form or something similar. Why is this? Would correcting this page alleviate concerns from customers? - Do users know where to go to report a bug? - How do they decide when to contact support vs. when to create an issue? (perhaps we can include a question that has users sort different scenarios into "Contact Support" vs "Create an Issue") - Re: current design; How do we know the user dropdown is where people would go for this? #### Methodology - Survey Research - User Outreach: reach out to 2-3 customers who have expressed related concerns. Understand their experiences/perspectives on contributing to GitLab, reporting bugs/submitting feedback, and generally other issues they have with understanding their GitLab instance. #### Progress **Research Phase 1** Survey - [x] Write survey questions [Deadline: Mon Sept 10th] - [x] Share survey draft with PM for review [Deadline: Mon Sept 10th] - [x] Import survey questions into SurveyMonkey [Deadline: Mon Sept 10th] - [x] Test survey logic [Deadline: Mon Sept 10th] - [x] Write email to accompany survey [Deadline: Mon Sept 10th] - [x] Distribute survey to test segment of the research panel [Deadline: Tues Sept 11th] - [x] Review answers and make any necessary amendments [Deadline: Weds Sept 12th] - [x] Distribute survey to full segment of the research panel [Deadline: Weds Sept 12th] - [x] Close Survey [Deadline: Tues Sept 18th] - [x] Cleanse data [Deadline: Weds Sept 19th] - [x] Conduct prize draw, contact winners [Deadline: Weds Sept 19th] - [x] Analyze data [Deadline: Thurs Sept 20th] - [x] Purchase Amazon vouchers [Deadline: Fri Sept 21st] - [x] Write report on survey findings [Deadline: Mon Sept 24th] - [x] Add survey report to UX Research Archive [Deadline: Weds Sept 26th] User Outreach - [x] Contact support or sales team to gain contact information for 2-3 users. [Deadline: Fri Sept 7th] - [x] Create a script that reviews their concerns and includes additional questions [Deadline: Fri Sept 7th] - [x] Send emails to identified users [Deadline: Mon Sept 10th] - [x] Reshma: https://gitlab.slack.com/archives/C0NFPSFA8/p1528826306000050; https://gitlab.com/gitlab-org/gitlab-ce/issues/43623#note_84023222 reshma@readysurgery.com - [x] Customer - NWM - meeting will be scheduled for a few weeks out - [x] Conduct research with users. [Target Deadline: Mon Sept 24th (Depending on availability)] - (research can be conducted via video call or by submitting responses to google form) - [x] Reshma: https://gitlab.com/gitlab-org/gitlab-ce/issues/43623#note_101408914 - [ ] NWM: Pending, waiting on customer to schedule meeting. **Planning Next Phase** - [x] Consolidate Results from Survey Research [Deadline: Weds Sept 19th] - [x] Communicate findings to designers and PMs [Deadline: Weds Sept 19th] - [x] Discuss next stepss:[Deadline: TBD] ### Results [Survey Report](https://drive.google.com/file/d/1XcbEhd1aiHsbRf1XZlLPUO6hAgGuEotg/view?usp=sharing)