This year at Red Hat Summit, we spoke with more customers and collected more feedback than ever before. Through activities like our live journey mapping exercise in the Expo Hall, in-depth interviews at our Executive Briefing Center, and more, we got a glimpse into how Red Hat Summit attendees feel about our products and services, and their overall experience with Red Hat.
In our previous blog, we provided an overview of how we collected feedback at Red Hat Summit this year. Since the event, our Customer Experience and Adoption team has worked with groups across Red Hat to ensure attendees’ voices were heard and action was taken on this critical feedback.
One team that works to drive these enhancements is our Portfolio Lifecycle Management team, which includes product experience engineers. These individuals own and drive technical enhancements based on customer and partner feedback and work to influence product releases, ensure high-quality delivery, and improve the usability and interoperability of Red Hat products.
Read on for some of the action items the team has helped to plan and execute based on the feedback we collected from users at Red Hat Summit this year.
Red Hat Ansible Automation Platform
You Spoke: Event attendees indicated that we could improve backup and state management features. From this, we determined that we should leverage certified Terraform collections to provide content for state management.
We Acted: Our team met with the Red Hat project managers responsible for driving tooling and content who helped certify the current Terraform content collections. The goal is to help showcase the desire for these collections and to suggest potential use cases and improvements.
You Spoke: We heard you when you indicated that we could better audit playbooks and Open Policy Agent (OPA) integration. With this feedback, we determined that we needed to investigate implementing/supporting Ansible Risk Insights (ARI).
We Acted: Our product experience engineers reached out to our product teams to assess the possibility of getting ARI implemented with existing tooling. We also provided some insight into how the current strategy for that tool could help improve the usage/impact of others.
You Spoke: Customers let us know that they had encountered some issues that they felt could be improved with versioning. Our team investigated creating a platform-level backup method by component, utilizing platform UI/gateway.
We Acted: We aligned this request with our strategy of providing a single pane of glass for customers to run their automation through, end to end. This suggestion will allow customers to back up/restore specific components of the platform from within the platform, leading to a more seamless and straightforward recovery process.
Red Hat OpenShift Service on AWS (ROSA)
You Spoke: Our customers asked us to meet them where they are and provide alerting integrations with the top three alerting providers, or to provide a mechanism to allow for custom web hooks so they can implement their own alerting strategy.
We Acted: We logged ticket SDE-1112, which enables customers to monitor their own workload and configure their own alert receivers. We are also discussing the feasibility of enabling customers to configure additional receivers for the cluster alerts.
You Spoke: We want our customers to be successful throughout their lifecycle with our products, starting with Day One operations. Our team understands that customers want more configurability at installation and more insights into the practical status of an installation of ROSA.
We Acted: Our product experience experts are working on several action items based on this feedback, which can be tracked in the following Jira tickets:
- HAC-3801 (UI) OCM-23 (rosa-cli) for changing the default machine pool type
- OCM-1055 and OCM-1178 for better OpenShift Cluster Manager cluster installation status
- SDE-1768 Network Load Balancer ingress will be the default in 4.13+
- RFE-4011 for S3 bucket security
Red Hat Enterprise Linux (RHEL)
You Spoke: Red Hat Summit attendees noted that they love how stable and reliable RHEL is and indicated that release notes are critical for their work. They suggested that our documentation could provide more detailed and specific information on new releases; for example, when rebases happen.
We Acted: We are in the process of engaging across RHEL engineering to ensure that more granular information is available in the release notes for our customers moving forward.
The feedback we receive from customers and partners not only helps to inform the future of Red Hat’s products and services, but also helps us to improve your overall experience and achieve your business outcomes.
We appreciate the insightful feedback we received from customers and partners throughout the Red Hat Summit event in Boston this year. We welcome your comments and look forward to acting on more insights throughout the year and at Red Hat Summit 2024!
About the author
Red Hat's Customer and Partner Experience team works to drive customer and partner success by collecting, analyzing and operationalizing feedback. The team works with all areas of Red Hat to drive enhancements based on the feedback we receive from users.