Add Platform Product Group
Overview
In a recent Investment case, we have discussed adding a Verify Platform team that is dedicated to three main focuses across the Verify Stage
- Address our S1/S2 bug backlog
- Create forward-looking technical blueprint architecture scope to resolve technical debt
- Support Verify Scaling initiatives in our CI Scaling direction
We are proposing that instead of nesting the 2 new approved headcount inside product teams, we establish a new product group that will support these purely engineering tasks and are driven by two KPIs: Verify Availability and Verify SLO adherence. This has the advantage of keeping the team exclusively focused on these results without compromising on growing MAU, Paid user experience, and market share - which is what all the other product groups are intended to support. Deconflictig our results focus keeps this team dedicated to the initiatives that support our ability to scale long term.
Essentially, this Platform Group
in Verify dedicates a product group to support Verify-wide Engineering Allocations and the results we expect to drive out of the EAs.
Another alternative benefit of this structure is knowledge transfer across the groups. Instead of embedding these two new headcounts into existing teams, we are asking this team establishes domain knowledge at the Stage-level. This sharing protects us from any given group being the single point of failure for technical expertise resulting in ineffectively managed technical debt.
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
Chief Product Officer @sfwgitlab
-
VP of Product @adawar
-
The Product Director relevant to the stage group(s) @kencjohnston
-
The Engineering Director relevant to the stage group(s) @sgoldstein
-
Director of Product Design @vkarnes
-
CEO @systes
The following people need to be on the merge request so they stay informed:
-
Chief Technology Officer @edjdev
-
Vice President of Development @clefelhocz1
-
Vice President of Quality @meks
-
Vice President of User Experience @clenneville
-
The Product Marketing Manager relevant to the stage group(s) -
Senior Manager, Technical Writing @susantacker
After Approvals and Merge
-
Create an issue in the triage-ops project to update GitLab Bot automation -
Mention the product group Technical Writer to update the documentation metadata -
Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels