How to organize your team for implementation

As you prepare to implement Amplitude, assign these three roles to members of your implementation team.

Project Lead

Also known as the Adoption Lead, the Project Lead is usually the main point of contact between your company and Amplitude, especially on paid plans. Depending on the team that implements Amplitude, a product manager or someone from the data science team often fills this role.

Example tasks and responsibilities:

• Coordinate with your Success Manager (Growth and Enterprise plans only) to organize training or other workshops with your teams.
• Drive Amplitude adoption and usage across teams at your company.
• Manage implementation where needed. For example, when you expand Amplitude to a new platform or product, confirm that a tracking plan (taxonomy) exists and that engineering resources are available.

Data Governor

The Data Governor designs your team's tracking plan and maintains your Amplitude data quality. This person must align your business goals to the data you need to track in Amplitude. A product manager, an analyst, or someone else from the data science team often fills this role.

Example tasks and responsibilities:

• Establish a consistent naming convention and build the taxonomy you need to send data to Amplitude.
• Confirm that you aren't tracking data that may violate privacy policies or legislation you're subject to.
• Design and manage the process for ongoing tracking development. For example, when planning a new feature, the Data Governor challenges the product manager on how to measure the success of that feature. After you decide what to measure, connect with an engineering resource to track the relevant events and properties to Amplitude.
• One Data Governor can oversee multiple products or projects, or you can have one Data Governor per project.

Instrumentation Lead

The Instrumentation Lead is primarily responsible for instrumenting new Amplitude events. A senior developer or dev lead often fills this role, especially when data comes from multiple locations.

Example tasks and responsibilities:

• Confirm that you have the expertise to instrument Amplitude events and, where needed, guide other developers on the topic.
• If data comes from sources other than client-side SDKs, understand and document these sources and their constraints, such as how real-time the back-end data is.
• Work with the Data Governor to validate Amplitude data. Troubleshoot potential duplicate events and other data issues.
• Depending on your developer team structure, you can split this role by platform (iOS, Android, web) or by product.