Design at Red Hat

What is your role and what team do you work on?

I manage the Design side of Digital Experience Design Engineering. Our team is responsible for improving and creating digital experiences for customers seeking answer and support and for those associates who interact with our customers.

How do you get inspired first thing in the morning?

A double-shot of espresso from a moka pot with 4 oz of oat milk.

I wish I could say that I wake up every morning abound with inspiration, but I don’t - and I don’t think that most people do. I chose to become a designer because I like making things, but it turns out I also like fixing them. As creatives we have a chance to repair things that are broken and to make new things to replace the irreparable. I find inspiration when I see something that could be improved.

What makes leading a design team at Red Hat unique?

Design teams at Red Hat have more shared accountability for the business outcomes than designers in other companies, and certainly more than those in the Agency world. The communication and organizational structures that we’ve chosen in CEE encourage an inclusive approach to decision making — PMs, Engineers, DevOps, and QA participate in our design processes and decisions. With so many brilliant contributors sharing their expertise, we’ve adopted a servant leadership approach to team management. It allows me to focus my energy on the part of the job that I really love: cultivating a culture of sustainable growth and psychological safety.

How are you incorporating open source principles into your designs or design processes?

Our collective group of PMs, Engineers, and Designers follows a workstream model that invites any contributors and stakeholders to weigh in at various appropriate stops along a project’s journey. Everything goes through a system of checks and balances to ensure that multiple eyes see our work, multiple voices are heard in every phase of design, and multiple approvals are required before any big changes are made.

Jason Brock

It’s normal for designers to shoot for the moon and for engineers to want to deliver things quickly and efficiently. The natural tension between those perspectives is what drives innovation.

How do you prioritize collaboration across teams in your design process?

The relationship between our Design Engineering team and our Product and Portfolio team is critical for successful collaboration across all of our disciplines. In our space, Design is just one section of a large orchestra and we get to work with some of the best conductors in the business.

How do you think diverse voices and perspectives make the design process stronger?

When you bring people together from various disciplines, backgrounds, and departments to weigh in on a business problem, there needs to be plenty of space for courteous dissent. It’s normal for designers to shoot for the moon and for engineers to want to deliver things quickly and efficiently. The natural tension between those perspectives is what drives innovation.

How does your design work contribute to the creation of helpful and accessible experiences?

Our team is working very closely with all members of the DPO and both Design System teams (RHDDS and PatternFly) to build better alignment for the future. Both teams are dedicated to rigorous accessibility standards and their UI components are designed with accessibility in mind. The Customer Portal is in a fairly unique spot where we have to consume the output of both systems, so it’s important to our success that these systems approach accessibility and design in similar ways.

What does open design mean to you?

Open means a willingness to listen. At the end of the day, our design teams have a responsibility to do the best design work that we can, but sometimes other solutions are more elegant, or more simple, or even just more affordable. We have to be open to the ideas of non-designers so that we never let perfect become the enemy of good.