Oct 21, 2019 - Emily von Hoffmann    

5 things we learned from you in recent UX research

How you use Snippets, whether to rename Auto DevOps, how to improve our billing process, and more.

This blog post is Unfiltered

This past quarter, the UX research team was charged with supporting some big OKRs:

  • Create products and experiences that users love and value.
  • Complete at least 5 qualitative interviews per Product Manager — part of scaling UX research across the org, which we’ll continue next quarter.
  • Implement a pilot of customer satisfaction surveys.

Throughout all of it, researchers continued working to learn more about each stage group. Here are some of the highlights.

1. Snippets can be an extremely useful knowledge base

Using Snippets to share commonly used code throughout an organization (fixes, install scripts, social icons, etc) can be beneficial for consistency, saving time on searching for solutions, and onboarding new or junior team members.

Group-level Snippets, Multi-file Snippets, and Version control for Snippets are highly upvoted issues in GitLab’s issue tracker.

Check out the full results.

GitLab First Look Make every release the best release ever. Sign up

2. After considering other options, you prefer the name “Auto DevOps”

We surveyed nearly 200 developers to evaluate 4 terms: ‘Auto Config’, ‘Auto Pipelines’, ‘NoOps’, and ‘Auto DevOps’ (our existing name). The term that did best both in terms of 1) allowing users to accurately predict what the feature does and 2) was considered appropriate for the feature’s definition (i.e. a feature that automatically detects, builds, tests, deploys, and monitors you applications) was Auto DevOps, with Auto Pipelines as a very close second. Consequently, it was decided to stick with Auto DevOps.

Full results

3. You wanted a new flow for enabling security checks

Based on insights gathered in a previous usability study around users’ mental model, the Secure team created a new flow for enabling security checks, which allows users to configure security checks from the UI itself. We then tested the new flow and saw significant improvement - all participants were able to complete the task, as opposed to only 1 out of 5 before the new design was created. Yay for evidence-based design!

Full results

4. Logs contain rich data, and you need a better way to manage it

Logs are captured for a number of reasons: audit/compliance, security (to monitor against abuse/attacks), and for troubleshooting when things go wrong. Logs are able to capture more information than metrics, but because they capture so much more information, users need a way of managing them, searching through them, and surfacing insights.

Another interesting finding: You use tracing when things aren’t running as expected and you want to find out what’s going on “under the hood.” It’s underutilized compared to logging.

Full results

5. Our billing processes just aren't cutting it

Our billing processes are optimized for large orgs, but don’t support the needs of small businesses as effectively or efficiently. Additionally, our true-up policy is not transparent. We saw customers mistakenly expect adding users to be automatically prorated, often leading to surprise charges at renewal time.

Finally, we have an opportunity to help more customers self-serve. Self-hosted customers must contact GitLab every time they want to add users to their license, creating friction for customers and taking up valuable support/sales time.

Full results

Join GitLab First Look

Did you recognize some of the above as your own needs and wants? Or did you disagree with everything completely?! Either way, we want to hear from you.

You can participate in interviews, surveys, beta tests, and more from the comfort of your own computer 💻✨Your feedback is incredibly important to us, and we hope you consider joining our research program, GitLab First Look.

This round-up was compiled using research and analysis by Katherine Okpara, Tali Lavi, Amelia Bauerly, Iain Camacho, Eileen Ruberto, Lorie Whitaker, and Jeff Crow

DISCLAIMER: This blog is intended for user-generated content submitted by the GitLab team. The views and opinions represented in this blog are personal to the author of each respective blog post and do not represent the views or opinions of GitLab unless explicitly stated. All content provided on this blog is for informational purposes only. Neither GitLab nor any of the individual blog contributors ("Contributors") make any representations as to the accuracy or completeness of any information on this site. Neither GitLab nor any Contributors will be liable for any errors or omissions in this information or any losses, injuries, or damages from the display or use of this information. Comments are welcome, and in fact, encouraged. However, GitLab reserves the right to edit or delete any comments submitted to this blog without notice should GitLab determine them to i) be spam or questionable spam; ii) include profanity; iii) include language or concepts that could be deemed offensive, hate speech, credible threats, or direct attacks on an individual or group; or iv) are in any other way a violation of GitLab's Website Terms of Use. GitLab is not responsible for the content in comments. This policy is subject to change at any time.

Try all GitLab features - free for 30 days

GitLab is more than just source code management or CI/CD. It is a full software development lifecycle & DevOps tool in a single application.

Try GitLab for Free

Try GitLab risk-free for 30 days.

No credit card required. Have questions? Contact us.

Gitlab x icon svg