From 345d12d5b91a68db6e55da4e49c226722f3e10ad Mon Sep 17 00:00:00 2001
From: Natalie Pinto <npinto@gitlab.com>
Date: Fri, 6 Dec 2024 19:59:23 +0000
Subject: [PATCH 1/5] Update 6 files
- /content/job-families/product/technical-program-manager/_index.md
- /content/job-families/product/technical-program-manager/product-technical-program-management.md
- /content/job-families/product/technical-program-management.md
- /content/handbook/product/groups/product-technical-program-management.md
- /content/job-families/product/technical-program-manager.md
- /content/job-families/product/technical-program-manager-leadership.md
---
.../product-technical-program-management.md | 66 +++++++++++++++
...> technical-program-manager-leadership.md} | 6 +-
..._index.md => technical-program-manager.md} | 56 ++++++-------
.../product-technical-program-management.md | 80 -------------------
4 files changed, 90 insertions(+), 118 deletions(-)
create mode 100644 content/handbook/product/groups/product-technical-program-management.md
rename content/job-families/product/{technical-program-management.md => technical-program-manager-leadership.md} (88%)
rename content/job-families/product/{technical-program-manager/_index.md => technical-program-manager.md} (69%)
delete mode 100644 content/job-families/product/technical-program-manager/product-technical-program-management.md
diff --git a/content/handbook/product/groups/product-technical-program-management.md b/content/handbook/product/groups/product-technical-program-management.md
new file mode 100644
index 00000000000..02010e2cac0
--- /dev/null
+++ b/content/handbook/product/groups/product-technical-program-management.md
@@ -0,0 +1,66 @@
+---
+title: "Product Technical Program Manager"
+description: "The Product Technical Program Manager (TPM) role supports cross-division initiatives across Product, UX, Engineering and other functions within R&D along with functions across GTM"
+---
+
+### Mission
+
+Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.
+
+### Long-Term Vision
+
+* Define and consistently deliver against a standard of excellence for Program Management at GitLab.
+* Have a team reputation as a fundamental and necessary resource when R&D needs to deliver against complex business objectives and ultimately results for customers.
+* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab’s strategic business objectives.
+
+### Near-Term Goals for FY26
+
+* Excel in strategic program delivery; focus on a core group of highly visible and impactful programs, setting the tone for how our expanded team delivers value.
+* Create scalable workflows and processes that have a positive impact on GitLab’s overall efficiency and solicits positive sentiment from stakeholders.
+* Continue to build our TPM team identity as the team expands; develop a strong team foundation and niche within the business. In doing so, evangelize TPM best practices.
+
+### Core Responsibilites
+
+More information can be found on the [Product TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Product TPM Leadership Job Family](content/job-families/product/technical-program-manager-leadership.md)
+
+### How We Work
+
+#### Communication:
+
+* Slack is the best way to reach out to our team; our goal is to respond to all requests within 24 hours. The best way is to send us a message via #technical-program-management.
+* Alternately, if an issue exists for a scope of work, you can tag us directly there.
+
+#### Working hours:
+
+* Our team is (as of this writing) distributed across the United States and can accomodate requests during US Business Hours - both east and west coast. We are looking to expand our team's time zone coverage to EMEA.
+* Many of our TPMs schedules are more flexible and accommodate hours outside of the hours noted above.
+
+#### Async vs. Sync:
+
+* Generally, our team will default to async communication in alignment with GitLab values. When it is needed, we will pull team members into a call or meeting to ensure we are working effectively and efficiently if needed.
+* Cross-functional initiatives typically need more sync time. If you are part of a core project team, TPMs will likely find recurring meeting time to drive execution for the length of the project.
+
+### How You Can Leverage The Product TPMs
+
+If you have an initiative that you think could benefit from program management support, the best first step is to message #technical-program-management following this template to intake a request.
+
+Work that can benefit from program management support is typically complex, cross-functional, and critical to the business. We determine if a project is a good match for TPM support with the [TPM Coverage Calculator](https://docs.google.com/spreadsheets/d/1Tv9WK9LIBJgLbEWWMEvXLtewDDv-luJWPjQDtkhWaJ0/edit?usp=sharing) (internal only link)
+
+#### What about TPMs, outside of Product?
+As Technical Program Management is a relatively new function at GitLab, we're continually iterating on how the various TPM and PgM teams collaborate.
+
+|Product|Infrastructure|Security|
+|:-----------------|:-------------|:---------------|
+|**The R&D Technical Program Manager role supports cross-division initiatives across PM, UX, Engineering and other functions within R&D along with functions across GTM**| **Infrastructure Technical Program Management Team drives the planning, execution, and delivery of complex infrastructure projects across Engineering and Product.**|**The Security Program Manager will be responsible for complete overview and driving security initiatives across product, engineering and business enablement.**|
+|Manage and collaborate on key initiatives with stakeholders and leadership across R&D. Drive accountability ensuring all program objectives are met.|Establish a reliable and visible cadence for initiative reviews, decision making, prioritization, and staffing management.|Communicate successfully with partners and drive accountability across teams to ensure program objectives are met |
+|Refine and optimize division processes improving overall efficiency and execution of the division.|Lead and drive Infrastructure projects such as: Availability, Disaster Recovery, Releases, CI/CD Pipeline Efficiency, and Engineering Productivity|Gather and examine customer and internal security team needs and opportunities for new information security programs, products and projects |
+|Gather inputs and feedback and suggest improvements to our Product Process, and operational model within the Product division.|Provide technical project management, coordination, and inter/intra team communications to deliver outstanding program outcomes.|Drive organizational needs cross-functionally with product, engineering and finance including tracking and reporting of progress and metrics |
+| [Product Technical Program Management](/job-families/product/program-manager/) | [Infrastructure Program Management](/job-families/engineering/technical-program-management/technical-program-management-ic/) | [Security Program Management](/job-families/security/security-program-manager/) |
+
+### Contacting The Team
+
+The best way to reach out to our team is through #technical-program-management slack channel.
+
+#### Why use the channel and not direct message a PM I already know?
+
+Even though this can seem like a good idea, it [limits visibility to the larger TPM team](/handbook/communication/) and doesn’t allow for proper resource allocation. Sending your requests in this channel will allow for full visibility and ensure our team is connecting you with the program manager who is a good fit for your project and has bandwidth to take on something new.
diff --git a/content/job-families/product/technical-program-management.md b/content/job-families/product/technical-program-manager-leadership.md
similarity index 88%
rename from content/job-families/product/technical-program-management.md
rename to content/job-families/product/technical-program-manager-leadership.md
index 7befb5ce3d7..c98ef075cf9 100644
--- a/content/job-families/product/technical-program-management.md
+++ b/content/job-families/product/technical-program-manager-leadership.md
@@ -3,11 +3,7 @@ title: "Technical Program Management - Leadership"
description: "This job family represents all Managers in the Technical Program Management sub-department."
---
-This job family represents all Managers in the Technical Program Management sub-department within the Product Leadership department. They are responsible for managing,
-directly or indirectly, GitLab team members performing in the role of [Technical Program Manager](/job-families/product/technical-program-manager/). The R&D Technical
-Program Management teams support cross-division initiatives and projects across PM, UX, Engineering and other functions within R&D along with functions across GTM. These
-roles are responsible for building and managing a world-class team and putting them in the best position to succeed. They own the delivery of technical programs, are
-always looking to improve productivity, and are responsible for meeting and exceeding deliverable timeline expectations.
+This job family represents all Managers in the Technical Program Management sub-department within the Product Leadership department. They are responsible for managing, directly or indirectly, GitLab team members performing in the role of [Technical Program Manager](/job-families/product/technical-program-manager/). More info about the Product Technical Program Management team can be found in the [TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Team Page](content/handbook/product/groups/product-technical-program-management.md).
## Levels
diff --git a/content/job-families/product/technical-program-manager/_index.md b/content/job-families/product/technical-program-manager.md
similarity index 69%
rename from content/job-families/product/technical-program-manager/_index.md
rename to content/job-families/product/technical-program-manager.md
index d13fc732d40..1d23a1b642a 100644
--- a/content/job-families/product/technical-program-manager/_index.md
+++ b/content/job-families/product/technical-program-manager.md
@@ -3,16 +3,17 @@ title: "Technical Program Manager"
description: "This role supports cross-division initaitives across PM, UX, Engineering and other functions within R&D along with functions across GTM"
---
-## Technical Program Management Context and Mission
+## Technical Program Management Mission and Vision
-### Context
+### Mission
-As we incorporate more program management functions at GitLab, we want to ensure our role, vision, and responsibilities are clear. There are currently Program Managers in Product, IT, Infrastructure within the R&D, along with other areas of the business. We want to ensure there are clear boundaries for each of these program managers and work cross-functionally to align on best practices, process, and overall efficiency across the various programs.
+Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.
-### Mission
+### Long-Term Vision
-Our mission as program managers is to own the execution of cross-functional initiatives that are critical to the business. We lead programs from start to finish to help GitLab meet our organizational goals.
-Program managers develop strategies, evaluate the performance of projects, keep teams organized, and allocate budgets and resources across projects. Program managers may oversee several different teams, all working toward different goals and separate work schedules. We take the lead on tracking project progress, aligning team members, and strategizing program outcomes.
+* Define and consistently deliver against a standard of excellence for Program Management at GitLab.
+* Have a team reputation as a fundamental and necessary resource when R&D needs to deliver against complex business objectives and ultimately results for customers.
+* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab’s strategic business objectives.
## Core Competencies
@@ -20,7 +21,7 @@ Technical Program Managers drive complex and cross-functional technical initiati
The role of TPM can mean different things at different organizations. At GitLab, TPMs should be proficient in 5 core competencies:
-### Communication
+#### Communication
* Communicates efficiently and effectively, with the intent to drive clarity across stakeholders
@@ -30,7 +31,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Keeps communication focused on impacts and outcomes
-### Critical Thinking
+#### Critical Thinking
* Is not an order taker or a "cat herder." Instead, applies and fosters an environment of analytical thinking in regards to project goals, prioritization, execution, and decision making.
@@ -38,7 +39,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Leads projects outside of immediate domain expertise by learning about the work and self-educating about the problem to be solved
-### Organization & Execution
+#### Organization & Execution
* Executes projects and programs end-to-end, from inception to release
@@ -46,7 +47,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Switches between a range of context and corresponding responsibilities with ease, from vision and goal setting to managing operational cadences
-### Relationship-Building
+#### Relationship-Building
* Creates a trusted reputation across the organization with a variety of stakeholders (for both themselves and program management as a function)
@@ -56,27 +57,17 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Collaborates with team members and stakeholders in a way that drives business outcomes and earns stakeholder trust
-### Technical Knowledge & Application
+#### Technical Knowledge & Application
* Understands organizational systems, architecture, and applications and how they fit together into an enterprise tech stack
* Connects the dots between upstream decisions and downstream impacts to people, process, and technology
* Has and or creates domain expertise
* Applies program management methodologies and best practices, but knows how and when to flex to the project rather than simply following rigid standards.
-### Technical Program Management Performance Indicators
+#### Technical Program Management Performance Indicators
Division Wide Operational Efficency of programs within the Product Division
-## Division Structure
-
-|Product|Infrastructure|Security|
-|:-----------------|:-------------|:---------------|
-|**The R&D Technical Program Manager role supports cross-division initiatives across PM, UX, Engineering and other functions within R&D along with functions across GTM**| **Infrastructure Technical Program Management Team drives the planning, execution, and delivery of complex infrastructure projects across Engineering and Product.**|**The Security Program Manager will be responsible for complete overview and driving security initiatives across product, engineering and business enablement.**|
-|Manage and collaborate on key initiatives with stakeholders and leadership across R&D. Drive accountability ensuring all program objectives are met.|Establish a reliable and visible cadence for initiative reviews, decision making, prioritization, and staffing management.|Communicate successfully with partners and drive accountability across teams to ensure program objectives are met |
-|Refine and optimize division processes improving overall efficiency and execution of the division.|Lead and drive Infrastructure projects such as: Availability, Disaster Recovery, Releases, CI/CD Pipeline Efficiency, and Engineering Productivity|Gather and examine customer and internal security team needs and opportunities for new information security programs, products and projects |
-|Gather inputs and feedback and suggest improvements to our Product Process, and operational model within the Product division.|Provide technical project management, coordination, and inter/intra team communications to deliver outstanding program outcomes.|Drive organizational needs cross-functionally with product, engineering and finance including tracking and reporting of progress and metrics |
-| [Product Technical Program Management](/job-families/product/program-manager/) | [Infrastructure Program Management](/job-families/engineering/technical-program-management/technical-program-management-ic/) | [Security Program Management](/job-families/security/security-program-manager/) |
-
## Responsibilities
* Manage and collaborate on key initiatives with stakeholders and leadership across R&D. Drive accountability ensuring all program objectives are met.
@@ -95,7 +86,7 @@ Division Wide Operational Efficency of programs within the Product Division
### Technical Program Manager
-This position reports to the VP of Product Management.
+This position reports to the Manager of Technical Program Management.
#### Technical Program Manager Job Grade
@@ -103,7 +94,7 @@ The role is a grade 6.
#### Technical Program Manager Responsibilities
-All responsibilities listed below (applicable to all roles) plus:
+All responsibilities listed above (applicable to all roles) plus:
* Identify and coordinate the interdependencies among programs, products and other critical initiatives for a single sub-department
* Provide insight and suggestions to improving product process and operations
@@ -120,7 +111,7 @@ All requirements listed above (applicable to all roles)
### Senior Technical Program Manager
-This position reports to the VP of Product Management.
+This position reports to the Manager of Technical Program Management.
#### Senior Technical Program Manager Job Grade
@@ -147,7 +138,7 @@ All requirements of previous roles plus:
### Staff Technical Program Manager
-This position reports to the VP of Product Management.
+This position reports to the Manager of Technical Program Management.
#### Staff Technical Program Manager Job Grade
@@ -172,9 +163,9 @@ All requirements of previous roles plus:
* Understanding of our product, and market with a willingness to dive deep
* Strong anaytical skills for assessing and recommending solutions based on data and research
-### Technical Program Management Specialities
+## Technical Program Management Specialities
-#### Escalation Specialist
+### Escalation Specialist
This role has commonalities with the standard TPM (Technical Program Management) role above and can vary by level accordingly. This speciality is primarily focused on issue management; both in defining a process for long-term success and leading our teams through coordination and resolution of large scale customer issues or escalations, when needed. While collaborating on processes is a major area of focus for this role, we don’t expect that to represent 100% of the time. Any remaining bandwidth will be spent on supporting cross-functional projects that span the Product, Engineering, Support, and Customer Success teams.
@@ -192,12 +183,11 @@ The responsibilities and requirements for this speciality are largely the same a
## Hiring Process
-Candidates for this position can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find their job title on our team page.
+Candidates for TPM positions can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find their job title on our team page.
* Qualified candidates will be invited to schedule a 30 minute screening call with one of our Global Recruiters.
-* Candidates will be invited to schedule a 50-minute interview directly with the Sr Director of Product Management.
-* Candidates will be invited to schedule 2-3 separate 50-minute interviews with Directors in the Product Division.
-* Candidates will be invited to schedule a 30-minute interview with a cross division stable counterpart.
-* Candidates will be invited to schedule a final 30-minute interview with the CPO.
+* Candidates will be invited to schedule a 50-minute interview directly with the Manager of Technical Program Management
+* Candidates will be invited to schedule 2-3 separate 50-minute interviews with stakeholders across the Product and Engineering division
+* Candidates will be invited to schedule a final 30-minute interview with a member of the Product Leadership Team
Additional details about our process can be found on our hiring page.
diff --git a/content/job-families/product/technical-program-manager/product-technical-program-management.md b/content/job-families/product/technical-program-manager/product-technical-program-management.md
deleted file mode 100644
index 5ceaf3d7d53..00000000000
--- a/content/job-families/product/technical-program-manager/product-technical-program-management.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: "Technical Program Manager"
-description: "The R&D Technical Program Manager role supports cross-division initiatives across PM, UX, Engineering and other functions within R&D along with functions across GTM"
----
-
-### Core Responsibilites
-
-* Manage and collaborate on key initiatives with stakeholders and leadership across R&D. Drive accountability ensuring all program objectives are met.
-* Refine and optimize division processes improving overall efficiency and execution of the division.
-* Gather inputs and feedback and suggest improvements to our Product Process, and operational model within the Product division.
-
-### How We Work
-
-1. Working Norms
-
-Communication:
-
-* Slack is the best way to reach out to our team; our goal is to respond to all requests within 24 hours. The best way is to send us a message via #technical-program-management.
-* Alternately, if an issue exists for a scope of work, you can tag us directly there
-
-Working hours:
-
-* The majority of our team works from 8am PST-4pm PT.
-* Some of our PMs schedules are more flexible and accommodate hours outside of the hours noted.
-
-Async vs. Sync:
-
-* Generally, our team will default to async communication in alignment with GitLab values. When it is needed, we will pull team members into a call or meeting to ensure we are working effectively and efficiently if needed.
-* Cross-functional initiatives typically need more sync time. If you are part of a core project team, TPgMs will likely find recurring meeting time to drive execution for the length of the project.
-
-1. How You Can Leverage The TPgM
-
-If you have an initiative that you think could benefit from program management support, the best first step is to message #technical-program-management following this template to intake a request
-
-Work that can benefit from program management is typically complex, cross-functional, and critical to the business. Our team is great partner for these types of initiatives that require:
-
-* Communication
-* Critical Thinking
-* Organization & Execution
-* Relationship-Building
-* Technical Knowledge & Application
-
-Please read more here for [additional information](/job-families/product/program-manager/) on each area.
-
-1. Contacting The Team
-
-The best way to reach out to our team if you have a technical program management need is through #technical-program-management slack channel.
-
-Why use the channel and not direct message a PM I already know?
-
-* Even though this can seem like a good idea, it [limits visibility to the larger program management team](/handbook/communication/) and doesn’t allow for proper resource allocation. Sending your requests in this channel will allow for full visibility and ensure our team is connecting you with the program manager who is a good fit for your project and has bandwidth to take on something new.
-
-### More About The Team
-
-Product TPgM team
-
-Natalie Pinto: Manager of Technical Program Management
-
-* Slack handle: @natalie
-* GitLab handle: @natalie.pinto
-* [READ.me](https://gitlab.com/natalie.pinto)
-
-Clarissa Ersoz: Technical Program Manager
-
-* Slack handle: @cersoz
-* GitLab handle: @cersoz
-
-Michaela Seferian-Jenkins: Technical Program Manager
-
-* Slack handle: @Michaela SJ
-* GitLab handle: @mseferian-jenkins
-* [READ.me](https://gitlab.com/mseferian-jenkins)
-
-TBH: Technical Program Manager, Escalation Specialist
-
-* Slack handle:
-* GitLab handle:
-* Email:
-
-[Click here](/handbook.gitlab.com/job-families/product/program-manager/) to learn more about technical program management roles & responsibilites.
--
GitLab
From 067bc9a4f33a1146f870265f97c7f3a4f59b3e2e Mon Sep 17 00:00:00 2001
From: Natalie Pinto <npinto@gitlab.com>
Date: Fri, 6 Dec 2024 20:10:00 +0000
Subject: [PATCH 2/5] Update file _index.md
---
content/handbook/product/_index.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/handbook/product/_index.md b/content/handbook/product/_index.md
index b1d39d522ad..cf966ae8784 100644
--- a/content/handbook/product/_index.md
+++ b/content/handbook/product/_index.md
@@ -13,6 +13,7 @@ description: "Most of the content in the product handbook talks about _how_ we d
- [Product Management](/handbook/product/product-management/)
- [User Experience](/handbook/product/ux/)
+- [Product Technical Program Management](content/handbook/product/groups/product-technical-program-management.md)
## Product Team Mission
--
GitLab
From 506ed83243b1adfa2c3ca4ee11bf869871974d5b Mon Sep 17 00:00:00 2001
From: Natalie Pinto <npinto@gitlab.com>
Date: Fri, 6 Dec 2024 22:55:06 +0000
Subject: [PATCH 3/5] Update 3 files
- /content/handbook/product/groups/product-technical-program-management.md
- /content/job-families/product/technical-program-manager.md
- /content/job-families/product/technical-program-manager-leadership.md
---
.../product-technical-program-management.md | 34 +++++++++----------
.../technical-program-manager-leadership.md | 2 +-
.../product/technical-program-manager.md | 24 ++++++-------
3 files changed, 30 insertions(+), 30 deletions(-)
diff --git a/content/handbook/product/groups/product-technical-program-management.md b/content/handbook/product/groups/product-technical-program-management.md
index 02010e2cac0..136ebf45f1f 100644
--- a/content/handbook/product/groups/product-technical-program-management.md
+++ b/content/handbook/product/groups/product-technical-program-management.md
@@ -5,49 +5,49 @@ description: "The Product Technical Program Manager (TPM) role supports cross-di
### Mission
-Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.
+Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.
### Long-Term Vision
-* Define and consistently deliver against a standard of excellence for Program Management at GitLab.
+* Define and consistently deliver against a standard of excellence for Program Management at GitLab.
* Have a team reputation as a fundamental and necessary resource when R&D needs to deliver against complex business objectives and ultimately results for customers.
-* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab’s strategic business objectives.
+* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab's strategic business objectives.
### Near-Term Goals for FY26
* Excel in strategic program delivery; focus on a core group of highly visible and impactful programs, setting the tone for how our expanded team delivers value.
-* Create scalable workflows and processes that have a positive impact on GitLab’s overall efficiency and solicits positive sentiment from stakeholders.
+* Create scalable workflows and processes that have a positive impact on GitLab's overall efficiency and solicits positive sentiment from stakeholders.
* Continue to build our TPM team identity as the team expands; develop a strong team foundation and niche within the business. In doing so, evangelize TPM best practices.
-### Core Responsibilites
+### Core Responsibilities
More information can be found on the [Product TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Product TPM Leadership Job Family](content/job-families/product/technical-program-manager-leadership.md)
### How We Work
-#### Communication:
+#### Communication
-* Slack is the best way to reach out to our team; our goal is to respond to all requests within 24 hours. The best way is to send us a message via #technical-program-management.
+* Slack is the best way to reach out to our team; our goal is to respond to all requests within 24 hours. The best way is to send us a message in the #technical-program-management slack channel.
* Alternately, if an issue exists for a scope of work, you can tag us directly there.
-#### Working hours:
+#### Working hours
-* Our team is (as of this writing) distributed across the United States and can accomodate requests during US Business Hours - both east and west coast. We are looking to expand our team's time zone coverage to EMEA.
-* Many of our TPMs schedules are more flexible and accommodate hours outside of the hours noted above.
+* Our team is (as of this writing) distributed across the United States and can accomodate requests during US Business Hours - both east and west coast. We are looking to expand our team's time zone coverage to EMEA.
+* Many of our TPM's schedules are more flexible and accommodate hours outside of the hours noted above.
-#### Async vs. Sync:
+#### Async vs. Sync
* Generally, our team will default to async communication in alignment with GitLab values. When it is needed, we will pull team members into a call or meeting to ensure we are working effectively and efficiently if needed.
-* Cross-functional initiatives typically need more sync time. If you are part of a core project team, TPMs will likely find recurring meeting time to drive execution for the length of the project.
+* Cross-functional initiatives typically need more sync time. If you are part of a core project team, we will likely find recurring meeting time to drive execution for the length of the project.
-### How You Can Leverage The Product TPMs
+### How You Can Leverage The Product TPM Team
-If you have an initiative that you think could benefit from program management support, the best first step is to message #technical-program-management following this template to intake a request.
+If you have an initiative that you think could benefit from program management support, the best first step is to message #technical-program-management following this template to intake a request.
Work that can benefit from program management support is typically complex, cross-functional, and critical to the business. We determine if a project is a good match for TPM support with the [TPM Coverage Calculator](https://docs.google.com/spreadsheets/d/1Tv9WK9LIBJgLbEWWMEvXLtewDDv-luJWPjQDtkhWaJ0/edit?usp=sharing) (internal only link)
-#### What about TPMs, outside of Product?
-As Technical Program Management is a relatively new function at GitLab, we're continually iterating on how the various TPM and PgM teams collaborate.
+#### What about Program Managers outside of the Product Org?
+As Technical Program Management is a relatively new function at GitLab, we're continually iterating on how the various TPM and PgM teams collaborate.
|Product|Infrastructure|Security|
|:-----------------|:-------------|:---------------|
@@ -63,4 +63,4 @@ The best way to reach out to our team is through #technical-program-management s
#### Why use the channel and not direct message a PM I already know?
-Even though this can seem like a good idea, it [limits visibility to the larger TPM team](/handbook/communication/) and doesn’t allow for proper resource allocation. Sending your requests in this channel will allow for full visibility and ensure our team is connecting you with the program manager who is a good fit for your project and has bandwidth to take on something new.
+Even though this can seem like a good idea, it [limits visibility to the larger TPM team](/handbook/communication/) and doesn't allow for proper resource allocation. Sending your requests in this channel will allow for full visibility and ensure our team is connecting you with the program manager who is a good fit for your project and has bandwidth to take on something new.
diff --git a/content/job-families/product/technical-program-manager-leadership.md b/content/job-families/product/technical-program-manager-leadership.md
index c98ef075cf9..e52dd6bd24c 100644
--- a/content/job-families/product/technical-program-manager-leadership.md
+++ b/content/job-families/product/technical-program-manager-leadership.md
@@ -3,7 +3,7 @@ title: "Technical Program Management - Leadership"
description: "This job family represents all Managers in the Technical Program Management sub-department."
---
-This job family represents all Managers in the Technical Program Management sub-department within the Product Leadership department. They are responsible for managing, directly or indirectly, GitLab team members performing in the role of [Technical Program Manager](/job-families/product/technical-program-manager/). More info about the Product Technical Program Management team can be found in the [TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Team Page](content/handbook/product/groups/product-technical-program-management.md).
+This job family represents all Managers in the Technical Program Management sub-department within the Product Leadership department. They are responsible for managing, directly or indirectly, GitLab team members performing in the role of [Technical Program Manager](/job-families/product/technical-program-manager/). More info about the Product Technical Program Management team can be found in the [TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Team Page](content/handbook/product/groups/product-technical-program-management.md).
## Levels
diff --git a/content/job-families/product/technical-program-manager.md b/content/job-families/product/technical-program-manager.md
index 1d23a1b642a..cd95e02c071 100644
--- a/content/job-families/product/technical-program-manager.md
+++ b/content/job-families/product/technical-program-manager.md
@@ -7,21 +7,21 @@ description: "This role supports cross-division initaitives across PM, UX, Engin
### Mission
-Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.
+Our mission as Technical Program Managers is to own the execution of complex, cross-functional initiatives that better enable GitLab to meet company objectives. We aim to make complex programs simpler with proactive, transparent, and efficient practices, while adapting our methodologies to the scenario at hand. We aspire to be trusted partners to stakeholders across the company, in order to accelerate and improve upon program outcomes over time.
### Long-Term Vision
-* Define and consistently deliver against a standard of excellence for Program Management at GitLab.
+* Define and consistently deliver against a standard of excellence for Program Management at GitLab.
* Have a team reputation as a fundamental and necessary resource when R&D needs to deliver against complex business objectives and ultimately results for customers.
-* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab’s strategic business objectives.
+* TPMs are seen across our company-wide stakeholders as a key element to accelerate GitLab's strategic business objectives.
## Core Competencies
Technical Program Managers drive complex and cross-functional technical initiatives by leveraging domain expertise, building a holistic execution strategy and harnessing human leadership qualities to deliver strategic business outcomes that have wide-reaching impact.
-The role of TPM can mean different things at different organizations. At GitLab, TPMs should be proficient in 5 core competencies:
+The role of TPM can mean different things at different organizations. At GitLab, Technical Program Managers should be proficient in 5 core competencies:
-#### Communication
+### Communication
* Communicates efficiently and effectively, with the intent to drive clarity across stakeholders
@@ -31,7 +31,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Keeps communication focused on impacts and outcomes
-#### Critical Thinking
+### Critical Thinking
* Is not an order taker or a "cat herder." Instead, applies and fosters an environment of analytical thinking in regards to project goals, prioritization, execution, and decision making.
@@ -39,7 +39,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Leads projects outside of immediate domain expertise by learning about the work and self-educating about the problem to be solved
-#### Organization & Execution
+### Organization & Execution
* Executes projects and programs end-to-end, from inception to release
@@ -47,7 +47,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Switches between a range of context and corresponding responsibilities with ease, from vision and goal setting to managing operational cadences
-#### Relationship-Building
+### Relationship-Building
* Creates a trusted reputation across the organization with a variety of stakeholders (for both themselves and program management as a function)
@@ -57,14 +57,14 @@ The role of TPM can mean different things at different organizations. At GitLab,
* Collaborates with team members and stakeholders in a way that drives business outcomes and earns stakeholder trust
-#### Technical Knowledge & Application
+### Technical Knowledge & Application
* Understands organizational systems, architecture, and applications and how they fit together into an enterprise tech stack
* Connects the dots between upstream decisions and downstream impacts to people, process, and technology
* Has and or creates domain expertise
* Applies program management methodologies and best practices, but knows how and when to flex to the project rather than simply following rigid standards.
-#### Technical Program Management Performance Indicators
+### Technical Program Management Performance Indicators
Division Wide Operational Efficency of programs within the Product Division
@@ -161,13 +161,13 @@ All requirements of previous roles plus:
* Proven track record of complex, cross divisional program management.
* Understanding of our product, and market with a willingness to dive deep
-* Strong anaytical skills for assessing and recommending solutions based on data and research
+* Strong analytical skills for assessing and recommending solutions based on data and research
## Technical Program Management Specialities
### Escalation Specialist
-This role has commonalities with the standard TPM (Technical Program Management) role above and can vary by level accordingly. This speciality is primarily focused on issue management; both in defining a process for long-term success and leading our teams through coordination and resolution of large scale customer issues or escalations, when needed. While collaborating on processes is a major area of focus for this role, we don’t expect that to represent 100% of the time. Any remaining bandwidth will be spent on supporting cross-functional projects that span the Product, Engineering, Support, and Customer Success teams.
+This role has commonalities with the standard TPM (Technical Program Management) role above and can vary by level accordingly. This speciality is primarily focused on issue management; both in defining a process for long-term success and leading our teams through coordination and resolution of large scale customer issues or escalations, when needed. While collaborating on processes is a major area of focus for this role, we don't expect that to represent 100% of the time. Any remaining bandwidth will be spent on supporting cross-functional projects that span the Product, Engineering, Support, and Customer Success teams.
The responsibilities and requirements for this speciality are largely the same as a standard TPM role. Here are a couple of key differences to be aware of:
--
GitLab
From bc2f0b9974341f516eb08b7c924230903025569c Mon Sep 17 00:00:00 2001
From: Natalie Pinto <npinto@gitlab.com>
Date: Fri, 6 Dec 2024 23:07:22 +0000
Subject: [PATCH 4/5] Update 2 files
- /content/handbook/product/groups/product-technical-program-management.md
- /content/job-families/product/technical-program-manager.md
---
.../product/groups/product-technical-program-management.md | 1 +
content/job-families/product/technical-program-manager.md | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/content/handbook/product/groups/product-technical-program-management.md b/content/handbook/product/groups/product-technical-program-management.md
index 136ebf45f1f..b8f3a6779a9 100644
--- a/content/handbook/product/groups/product-technical-program-management.md
+++ b/content/handbook/product/groups/product-technical-program-management.md
@@ -47,6 +47,7 @@ If you have an initiative that you think could benefit from program management s
Work that can benefit from program management support is typically complex, cross-functional, and critical to the business. We determine if a project is a good match for TPM support with the [TPM Coverage Calculator](https://docs.google.com/spreadsheets/d/1Tv9WK9LIBJgLbEWWMEvXLtewDDv-luJWPjQDtkhWaJ0/edit?usp=sharing) (internal only link)
#### What about Program Managers outside of the Product Org?
+
As Technical Program Management is a relatively new function at GitLab, we're continually iterating on how the various TPM and PgM teams collaborate.
|Product|Infrastructure|Security|
diff --git a/content/job-families/product/technical-program-manager.md b/content/job-families/product/technical-program-manager.md
index cd95e02c071..5df53477862 100644
--- a/content/job-families/product/technical-program-manager.md
+++ b/content/job-families/product/technical-program-manager.md
@@ -171,12 +171,12 @@ This role has commonalities with the standard TPM (Technical Program Management)
The responsibilities and requirements for this speciality are largely the same as a standard TPM role. Here are a couple of key differences to be aware of:
-##### Responsibilities
+#### Responsibilities
* Collaborate with cross-functional stakeholders and internal customers to determine improvements to the existing escalation process. Continue to iterate as our product space broadens and complexity increases.
* Guide teams through escalation processes as needed. Act as the calm center of focus for the team; help teams through challenging moments while ensuring that we are reaching the right outcomes for our customers.
-##### Requirements
+#### Requirements
* Prior experience working across Product, Engineering, and Customer Success functions
* Prior experience crafting and executing on cross functional process improvements, including capturing and redefining requirements into impactful work items.
--
GitLab
From f8831f367a9d8b8b3004098666747c83023c1cad Mon Sep 17 00:00:00 2001
From: Natalie Pinto <npinto@gitlab.com>
Date: Fri, 13 Dec 2024 18:35:09 +0000
Subject: [PATCH 5/5] Update 4 files
- /content/handbook/product/groups/product-technical-program-management.md
- /content/handbook/product/_index.md
- /content/job-families/product/technical-program-manager-leadership.md
- /content/job-families/product/technical-program-manager.md
---
content/handbook/product/_index.md | 2 +-
.../product/groups/product-technical-program-management.md | 6 +++---
.../product/technical-program-manager-leadership.md | 2 +-
content/job-families/product/technical-program-manager.md | 6 +++---
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/handbook/product/_index.md b/content/handbook/product/_index.md
index cf966ae8784..5caaff4d4cc 100644
--- a/content/handbook/product/_index.md
+++ b/content/handbook/product/_index.md
@@ -13,7 +13,7 @@ description: "Most of the content in the product handbook talks about _how_ we d
- [Product Management](/handbook/product/product-management/)
- [User Experience](/handbook/product/ux/)
-- [Product Technical Program Management](content/handbook/product/groups/product-technical-program-management.md)
+- Product Technical Program Management
## Product Team Mission
diff --git a/content/handbook/product/groups/product-technical-program-management.md b/content/handbook/product/groups/product-technical-program-management.md
index b8f3a6779a9..3134839b90d 100644
--- a/content/handbook/product/groups/product-technical-program-management.md
+++ b/content/handbook/product/groups/product-technical-program-management.md
@@ -21,7 +21,7 @@ Our mission as Technical Program Managers is to own the execution of complex, cr
### Core Responsibilities
-More information can be found on the [Product TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Product TPM Leadership Job Family](content/job-families/product/technical-program-manager-leadership.md)
+More information can be found in the Product TPM Job Family and the Product TPM Leadership Job Family
### How We Work
@@ -32,7 +32,7 @@ More information can be found on the [Product TPM Job Family](content/job-famili
#### Working hours
-* Our team is (as of this writing) distributed across the United States and can accomodate requests during US Business Hours - both east and west coast. We are looking to expand our team's time zone coverage to EMEA.
+* Our team is (as of this writing) distributed across the United States and can accommodate requests during US Business Hours - both east and west coast. We are looking to expand our team's time zone coverage to EMEA.
* Many of our TPM's schedules are more flexible and accommodate hours outside of the hours noted above.
#### Async vs. Sync
@@ -56,7 +56,7 @@ As Technical Program Management is a relatively new function at GitLab, we're co
|Manage and collaborate on key initiatives with stakeholders and leadership across R&D. Drive accountability ensuring all program objectives are met.|Establish a reliable and visible cadence for initiative reviews, decision making, prioritization, and staffing management.|Communicate successfully with partners and drive accountability across teams to ensure program objectives are met |
|Refine and optimize division processes improving overall efficiency and execution of the division.|Lead and drive Infrastructure projects such as: Availability, Disaster Recovery, Releases, CI/CD Pipeline Efficiency, and Engineering Productivity|Gather and examine customer and internal security team needs and opportunities for new information security programs, products and projects |
|Gather inputs and feedback and suggest improvements to our Product Process, and operational model within the Product division.|Provide technical project management, coordination, and inter/intra team communications to deliver outstanding program outcomes.|Drive organizational needs cross-functionally with product, engineering and finance including tracking and reporting of progress and metrics |
-| [Product Technical Program Management](/job-families/product/program-manager/) | [Infrastructure Program Management](/job-families/engineering/technical-program-management/technical-program-management-ic/) | [Security Program Management](/job-families/security/security-program-manager/) |
+| Product Technical Program Management | [Infrastructure Program Management](/job-families/engineering/technical-program-management/technical-program-management-ic/) | [Security Program Management](/job-families/security/security-program-manager/) |
### Contacting The Team
diff --git a/content/job-families/product/technical-program-manager-leadership.md b/content/job-families/product/technical-program-manager-leadership.md
index e52dd6bd24c..c76185d8f82 100644
--- a/content/job-families/product/technical-program-manager-leadership.md
+++ b/content/job-families/product/technical-program-manager-leadership.md
@@ -3,7 +3,7 @@ title: "Technical Program Management - Leadership"
description: "This job family represents all Managers in the Technical Program Management sub-department."
---
-This job family represents all Managers in the Technical Program Management sub-department within the Product Leadership department. They are responsible for managing, directly or indirectly, GitLab team members performing in the role of [Technical Program Manager](/job-families/product/technical-program-manager/). More info about the Product Technical Program Management team can be found in the [TPM Job Family](content/job-families/product/technical-program-manager.md) and the [Team Page](content/handbook/product/groups/product-technical-program-management.md).
+This job family represents all Managers in the Technical Program Management sub-department within the Product Leadership department. They are responsible for managing, directly or indirectly, GitLab team members performing in the role of Technical Program Manager. More info about the Product Technical Program Management team can be found in the TPM Job Family and the Team Page.
## Levels
diff --git a/content/job-families/product/technical-program-manager.md b/content/job-families/product/technical-program-manager.md
index 5df53477862..de9dfc9a8dd 100644
--- a/content/job-families/product/technical-program-manager.md
+++ b/content/job-families/product/technical-program-manager.md
@@ -66,7 +66,7 @@ The role of TPM can mean different things at different organizations. At GitLab,
### Technical Program Management Performance Indicators
-Division Wide Operational Efficency of programs within the Product Division
+Division Wide Operational Efficiency of programs within the Product Division
## Responsibilities
@@ -167,9 +167,9 @@ All requirements of previous roles plus:
### Escalation Specialist
-This role has commonalities with the standard TPM (Technical Program Management) role above and can vary by level accordingly. This speciality is primarily focused on issue management; both in defining a process for long-term success and leading our teams through coordination and resolution of large scale customer issues or escalations, when needed. While collaborating on processes is a major area of focus for this role, we don't expect that to represent 100% of the time. Any remaining bandwidth will be spent on supporting cross-functional projects that span the Product, Engineering, Support, and Customer Success teams.
+This role has commonalities with the standard TPM (Technical Program Management) role above and can vary by level accordingly. This specialty is primarily focused on issue management; both in defining a process for long-term success and leading our teams through coordination and resolution of large scale customer issues or escalations, when needed. While collaborating on processes is a major area of focus for this role, we don't expect that to represent 100% of the time. Any remaining bandwidth will be spent on supporting cross-functional projects that span the Product, Engineering, Support, and Customer Success teams.
-The responsibilities and requirements for this speciality are largely the same as a standard TPM role. Here are a couple of key differences to be aware of:
+The responsibilities and requirements for this specialty are largely the same as a standard TPM role. Here are a couple of key differences to be aware of:
#### Responsibilities
--
GitLab