Understanding Roles in Our Organization

Author: Matt Carleton | Last edit: September 19, 2024

Intro

Responsibilities in our organization span various specialized roles, each contributing uniquely to the overall success of our work. To clarify these roles and their contributions, we’ve created a series of linked Google Docs that provide detailed insights into each role. Here's a quick overview:

Role links/descriptions

Design Team Lead – The purpose of this role is to establish a clear point of contact for a specific grouping of our portfolio. This individual will have a wider understanding of this area and can report on its status as well as drive connections across the group. View Role Doc

Design SME (Subject Matter Expert) – Provides specialized expertise in specific areas of design, offering in-depth knowledge and insights to enhance the quality and accuracy of designs across projects. View Role Doc

Content Designer – Specializes in crafting clear, concise, and user-centered content that aligns with design elements. They ensure that all textual components are intuitive and meaningful to the user. View Role Doc

Research Lead – Guides the research strategy, overseeing research initiatives to ensure that insights are aligned with project goals. They collaborate closely with designers and stakeholders to translate user data into actionable design improvements.  View Role Doc

Researcher – Gathers insights through user interviews, testing, and data analysis. Researchers ensure that design decisions are grounded in user needs and behaviors, guiding the team toward user-centric solutions. View Role Doc

Ops Specialist – Supports the entire team to do their best work, providing access to tooling, information, and team standards. They focus on simplifying and improving processes to increase quality and efficiency, and to quantify and amplify the impact of our teams work .  View Role Doc

Architect – Plays an essential role in Influencing  Red Hat’s business and technology strategies to ensure Red Hat is designing and building valuable user-centric solutions. As strategic partners to the research and design functions in UXD, UXD Architects help ensure consistent, outcome-driven, innovative experience design across Red Hat’s portfolio. View Role Doc

Developer Lead - Acts as a bridge between design, development, and product teams. They lead the development team, ensuring technical execution aligns with design intentions and product goals. In addition to managing the development workflow, the Developer Lead collaborates closely with product teams to ensure that technical implementation meets both design and business objectives, while also considering scalability, performance, and timelines. Role Doc in progress.

Each of these roles plays a crucial part in driving excellence within our organization. By reading through these documents, you’ll gain a deeper understanding of how we function as a cohesive, dynamic team!

Don't see Your Role?

The purpose of this entry is to cover the specific roles that have been defined in UXD that are not encapsulated in the overall competencies covered under engineering. To better understand the role and responsibilities of an individual contributor at any level see the engineering competencies.