<aside> 🤔 How this document should be used? Defines the roles and responsibilities needed to drive your program forward and outlines how they should be engaged.
When does this come into play? The roles outlined below should be defined and assigned at the start of the implementation.
Executive Sponsor: Senior executive within the product organization to govern key program decisions, provide influence among cross-functional leadership, and provide support for program communications.
Program Owner: Accountable for determining the project requirements, enablement materials, and driving resource allocation. Liaise with Executive Sponsor for leadership support. Participates in retrospectives once per quarter to validate partnership success and is ultimately responsible for Productboard success.
Product Operations: Supports the Project Sponsor to facilitate communications and knowledge sharing within the Product org, defines the processes to coordinate and rally teams to promote adoption, and helps identify any key adoption gaps/issues for resolution.
Product (Maker) Champion(s): Designated Productboard admin and power users to make key design decisions throughout the program. Identifies the change impacts based on future state processes, provides insight into enablement materials, and maintains regular touchpoints cross-functionally to outline progress to adoption or potential adoption risks.
Stakeholder (Contributor) Champion(s): Designated “Contributor” power users to surface stakeholder requirements and provide inputs into key design decisions throughout the program. Provide insight into contributor enablement and help drive adoption across the contributor teams.
Technical Manager: Configure VPN, SAML SSO, Jira, Zendesk, or other integrations that require a more technical background and we require integration specific admins to connect various integrations. This person will be working more closely with any technical members of the Productboard team, as needed.
Subject Matter Experts (SMEs): A designated “subject matter expert” for each functional group you onboard to Productboard to provide insight into processes and specific needs. These power users will receive additional enablement sessions from your CSM and then act as a power user resource to others on their team.
Makers: These individuals will likely be Product Managers. Responsible for actioning customer feedback, enhancing the backlog, making prioritization decisions and creating roadmaps. Depending on workflow, Designers may also be part of this group.
Contributors: These individuals will likely be customer-facing team members (ex: Sales, Success, Support). These individuals will focus on providing user feedback to help prioritization as well as view product roadmaps.